Know the day you run out of cash, before it sneaks up on you, self-serve every week.
Runway Watch reads your cash on hand, measures how fast you are actually burning, and tells you how many months of runway you have left, with the state marked plainly as healthy, watch, or critical.
The problem
If you are running a startup on a finite bank balance, runway is the number that decides everything, and it is almost always stale. It lives in a spreadsheet tab you updated three weeks ago, or in a founder's head as a rough guess, or in a monthly cash model that a fractional CFO produces after the month is already gone. By the time a shortening runway is obvious, you are a payroll cycle too late to do the calm version of something about it.
The tooling splits into two unhelpful piles. Your bank dashboard shows you a balance, which is not a runway, because it says nothing about burn. The real FP&A tools model burn beautifully, and they are priced and shaped for a company that already has a finance team. The founder who just wants to see cash, burn, and months-left on a Tuesday morning is stuck between a stale spreadsheet and a tool built for someone else.
How it works
Runway Watch runs the same read a careful operator would, on demand, and shows its work.
- Read the cash. It pulls your current cash on hand across the accounts you connect, so the runway rests on a real balance and not on last month's number.
- Measure the burn. It measures your trailing burn rate over a window you choose (ninety days by default), so the denominator is your actual spending, not a plan.
- Project the runway. It projects cash forward from balance and burn to compute the months of runway you have left.
- Check your line. It compares that runway against a threshold you set (healthy above your line, watch as you approach it, critical below it), so the warning is yours to define, not a consultant's.
One honest boundary, stated up front: this is the watch, it reads and reports. When you want the number to warn you on a cadence, it hands off to Anya's existing Alert workflow, and any action that would move money stays a separate step that you confirm by hand.
What you get
- A live runway read on demand: cash on hand, trailing burn, and months remaining, as three plain numbers.
- A state you can act on (healthy, watch, or critical) against a threshold you chose, not one we guessed for you.
- A weekly watch, when you want it, that warns you as the runway crosses your line instead of after.
- The work shown at each step, because a runway number you cannot check is a number you should not bet payroll on.
Who it is for
This is for early-stage founders and owner-operators running a company on a countable cash balance, who want a live runway number without building and babysitting a spreadsheet, and for the fractional CFOs and operators who watch runway across a few companies at once. If you are already profitable, or well-capitalized with a finance team producing a board-grade cash model, you do not need this.
Pricing
Pricing is still being validated, so treat these as starting points rather than promises.
- Self-serve read. Connect an account and get cash, burn, and months-left on demand. Free, or close to it, because this is the part that earns your trust.
- Always-on watch. The read runs on a weekly cadence and the Alert workflow warns you when runway crosses your threshold. Starting hypothesis, around 29 dollars a company each month.
- Operator seat. A per-seat subscription for fractional CFOs and operators watching several companies from one seat. Priced by conversation.
Alerts are notifications, nothing more. Any step that would move money, or take a payment, is fail-closed and waits for a human to confirm it.
Proof, and how we dogfood it
AYA is itself a startup running on a finite cash balance, so we are a real in-house user of this. Our own cash on hand and our own burn are exactly the balance and burn this product reads and projects, and watching AYA's own runway (on our own account) is the same capability pointed inward. The self-serve product is that dogfood generalized, so any founder can run the read we run on ourselves.
The deliverable behind this page is a composition of capabilities Anya already had (read balance, measure burn, project the forecast, check against a threshold), joined into one runway flow as configuration rather than new machinery. Building it left the same kind of receipt the product is about: the flow was scored for quality and passed, and every piece it composes was verified to exist before this page went up.
Honest note
Here is the part most landing pages leave out. As of today, this deliverable is authored, quality-scored, and correctly composed, and its four steps were each verified to exist on disk. What has not happened yet is a full run through a booted system against a real connected account, so no live runway has been computed for anyone through this flow, including us. That is a runtime-witnessing step, and it is honest to say it is not done.
What that means for you, concretely: this is a product we are building in the open, toward the runway question every 2026 founder is already getting asked in diligence, not one you can point at your bank account this afternoon. If that timeline works for you, telling us you want the free self-serve read helps us decide what to witness first.
*This page is a specification. The capability it describes is not built yet, and nothing here is a claim that it runs today.*