A SaaS business plan needs more than a subscription revenue target. It needs a clear customer problem, acquisition assumptions, service costs, churn and enough cash to continue while the model is tested. The figures below are fictional USD examples, not NexalyPlanner product metrics.
Separate subscriptions, revenue and cash
Assume a small software service begins a month with 100 paying accounts at $30 per month. It adds 20 accounts and loses five. Ending accounts are 115. If new accounts start halfway through the month and cancellations stop at month-end, a simplified recognized monthly revenue estimate is 100 × $30 + 20 × $15 = $3,300. Actual billing and revenue recognition depend on contract and payment terms. Cash receipts may differ.
| Line | Assumption | Monthly amount |
|---|---|---|
| Starting recurring billings | 100 × $30 | $3,000 |
| Service cost | 115 ending accounts × $4 | $460 estimate |
| Marketing spend | 20 acquired accounts × $40 acquisition spend | $800 |
| Other cash operating costs | Hosting, support and founder draw | $3,000 assumed |
| Illustrative cash movement | $3,300 receipts − $460 − $800 − $3,000 | −$960 |
This model deliberately treats the $3,300 as cash received for the illustration. If annual plans, refunds or unpaid invoices exist, replace it with actual receipts. Five cancellations from 100 starting accounts imply 5% monthly logo churn; the number is an assumption to test, not a normal benchmark.
Check runway without pretending the burn is constant
With $12,000 unrestricted cash and $960 of monthly net outflow, simple runway is $12,000 ÷ $960 = 12.5 months. It is a snapshot, not a forecast: hiring, taxes, renewals or seasonal sales will change burn. Make a month-by-month cash schedule and a downside case. If receipts fall to $2,500 while outflows stay $4,260, burn becomes $1,760 and simple runway falls to about 6.8 months.
The Business Runway & Burn Rate planner helps keep cash assumptions and scenarios visible. For a wider planning outline, consult the SBA business plan guidance. Financing or accounting decisions require the relevant professional records and advice.
What to review every month
Track beginning customers, new customers, cancellations, ending customers, receipts, service cost, acquisition spend and cash balance. Name the owner of each metric and the source system. Revisit pricing only after examining customer retention and unit economics; increasing signups at a loss can shorten runway.
Check acquisition payback with the right denominator
The example spends $800 to acquire 20 accounts, or $40 per new account. If the service costs $4 per account per month, the simplified contribution at a $30 price is $26 per month before support, refunds, payment fees and overhead. A $40 acquisition cost divided by $26 suggests roughly 1.54 paid months to recover that particular spend, but only if accounts remain and collectable receipts arrive as modeled. It is not a full customer lifetime value calculation.
Five cancellations are also a warning about the denominator. Five of 100 starting customers is 5% logo churn for that month. If the lost customers paid different prices, revenue churn would differ. Track both when plans vary. One month’s churn is too little evidence to extrapolate years of retention. Keep the cohort and cancellation reason rather than replacing observed data with an industry benchmark.
Use the plan as a decision schedule
By the first review, validate whether 20 new accounts came from the $800 channel spend and whether onboarding succeeded. By month 2, compare actual service cost per active account and unpaid invoices. By month 3, rerun the downside runway scenario with current cash and signed commitments. If acquisition is efficient but support costs are rising, improving onboarding may be a better test than buying more traffic. Document who owns each experiment and when it will stop.
The SaaS plan from customer problem to a tested runway
Step 1 — Choose one workflow and prove the problem
The fictional software team interviews a narrow group of potential customers about a recurring workflow, its current tools, monthly cost of the problem and who can authorize payment. They document at least five recent examples rather than asking whether a speculative feature sounds useful. They compare alternatives, including manual work and existing software. A waiting-list signup is not a paying account, so the first milestone is a paid, usable workflow with support and cancellation paths.
Step 2 — Define the offer and service boundary
The initial $30 monthly plan states the user, included workflow, limits, support channel, data handling, billing date and cancellation terms. It distinguishes an active paying account from trial users and failed payments. The team maintains a source of truth for subscriptions, invoices, refunds and access. It measures successful onboarding and time to first useful result. Privacy, security and legal commitments must match the actual product and applicable requirements, not a promise invented for the business plan.
Step 3 — Build an acquisition and retention model
The illustration starts with 100 paying accounts, adds 20 at an assumed $40 acquisition spend each and loses five at month-end. Ending accounts are 115 and marketing spend is $800. Starting-account logo churn is 5/100 = 5% for this one month. Track where the 20 came from, which cohort they joined, how many activated and why five left. Do not extend one observed month into a lifetime value claim. At $30 price and an illustrative $4 service cost per account, $26 is a narrow monthly contribution before support, payment fees and overhead.
Step 4 — Link the operating plan to monthly cash
| Month | Start + adds − losses = end | Assumed receipts | Outflows | Net cash |
|---|---|---|---|---|
| 1 | 100 + 20 − 5 = 115 | $3,300 | $460 service + $800 acquisition + $3,000 other = $4,260 | −$960 |
| 2 | 115 + 20 − 6 = 129 | $3,750 | $516 + $800 + $3,000 = $4,316 | −$566 |
| 3 | 129 + 20 − 6 = 143 | $4,170 | $572 + $800 + $3,000 = $4,372 | −$202 |
The illustrative receipts count starting accounts at $30 and new accounts at a half-month $15. Cancellations occur at month-end. With $12,000 starting cash, the simplified closing cash after these three net movements is $10,272. Real billing cycles, annual prepayments, refunds, taxes and unpaid invoices can change cash substantially. The month-1 snapshot runway of 12.5 months is not a three-month forecast; the dated table is more useful.
Step 5 — Set decision gates and a downside case
In the first 30 days, confirm activation and support load for the initial cohort. By day 60, compare acquisition cost and cancellations by cohort, not just aggregate signups. By day 90, reconcile billings to bank receipts and update the 12-month cash schedule. If receipts are $2,500 while the month-1 $4,260 outflows persist, cash burn is $1,760 and $12,000 divided by it is about 6.8 months before the other changes. Pause additional acquisition spend if the service cannot onboard or retain customers at a supportable cost; document the next experiment and its stop date.
Maintain the operating evidence behind the forecast
Use a monthly cohort sheet with signup month, acquisition source, activation, first payment, later payments, cancellation and refund. A trial that never paid belongs in a separate trial funnel. A customer who cancels but retains access until period end needs consistent counting rules; write them down once and apply them every month. Reconcile the subscription system to bank receipts and service invoices before reporting growth to anyone else.
The product workback is problem interviews → narrow usable workflow → billing and cancellation test → onboarding → support queue → cohort review. Assign a named owner and deadline to each. If 20 new customers sign up but ten never complete the first useful action, optimize onboarding before buying another 20 at $40 acquisition cost. If support costs rise above the modeled $4 per account, update both contribution and cash runway.
The 90-day review should produce one decision among continue the narrow offer, change the customer segment, change onboarding or pause acquisition. It should cite activation, retained paying accounts, cash receipts, service cost and support backlog. The model’s $10,272 month-3 cash balance is a scenario output, not proof the product has reached sustainable economics.
Test dated receipts, hiring and a minimum reserve with the monthly cash-runway template and scenarios.