Runwait vs Pilot
Pilot gives you a human finance team. Runwait gives founders a self-serve decision layer.
- You want humans to own bookkeeping, tax, or CFO work.
- Strategic judgment and hands-on service matter more than self-serve access.
- You are comfortable paying service pricing for that responsibility.
- A founder still owns the runway and the money questions.
- Hiring, spending, and fundraising decisions are the immediate job.
- You want one guided model, sourced answers in Slack, and a clean accountant handoff.
| Capability | Pilot | Runwait |
|---|---|---|
| One current runway for founder decisions | Books, reporting, and cash visibility | Cash, revenue, team costs, funding, and plans together |
| Month-end coverage and audit trail | Handled by software and a finance team | Coverage, open items, confirmations, and history |
| Hiring and fundraising scenarios | Available through CFO services | Before and after runway, with assumptions shown |
| Answers in Slack | Service communication and higher-tier access | Ask in plain English and get the basis and math |
| Shared document space | Records within the service workflow | Documents by month with scoped guest access |
| Deterministic math and visible basis | Reviewed and explained by finance people | Finance functions calculate every figure |
| Designed for a founder to operate | Service onboarding and account connections | Guided model with direct entry and connected sources |
6 ways Runwait differs from Pilot.
Founder decisions
The decision is the starting point.
Runwait is designed around the questions a founder has to answer before hiring finance: what can we afford, how long do we have, and what does the next round buy us.
Pilot sells accounting and finance expertise. Runwait gives the founder a product to use directly on daily decisions.
One financial model
Actuals and plans stay together.
Cash, revenue, team costs, funding, and plans share one model. The runway answer and the scenario both begin from the same financial picture.
Pilot's team owns bookkeeping and close. Runwait surfaces the current runway and month-end state for the founder.
Answers in Slack
Ask where the decision happens.
Ask about runway, burn, a hire, or a raise in Slack and get the figure with its basis and assumptions, using the same calculations as the product.
Pilot provides human advice and service communication. Runwait returns deterministic decision math in the product and Slack.
Accountant handoff
The evidence has a shared home.
Keep statements, invoices, and receipts together by month, then give an accountant or investor scoped access when review time comes.
Pilot keeps records in its service workflow. Runwait includes a shared data room controlled by the startup.
Team costs
See the hire in months of runway.
Runwait calculates loaded monthly cost, places it from the correct start month, and shows runway before and after the person joins.
Pilot can advise on headcount. Runwait lets the founder model loaded team cost and runway impact directly.
Portability
Your data stays yours.
The runway, financial records, and supporting documents remain exportable, so adopting Runwait does not create a costly exit later.
Pilot is an ongoing service relationship. Runwait keeps the underlying data exportable as a product promise.
Bring one real decision.
Bring the hire, spend, or raise you are considering. See the tradeoff before you commit.