Ship billing before you ship the dashboard

Dashboards feel like progress. Billing feels like plumbing. Founders usually ask for the chart first, then discover they cannot charge anyone for what the chart describes.

An MVP that cannot take money is a demo. The order of the first four systems decides whether you learn from paying customers or from polite feedback.

The first four systems, in order

We push teams to sequence work so revenue and retention are measurable before polish.

1. 01
   Identity and accessAccounts, roles, and a path for the buyer to invite the people who will actually use the product.
2. 02
   Billing and entitlementsPlans, invoices, and the gates that turn a feature on when money clears. Without this, every other metric is theatre.
3. 03
   The core job-to-be-doneOne narrow workflow that delivers the promise. Not five. Not the roadmap — the reason someone pays.
4. 04
   Operational visibilityOnly then the dashboard: who paid, who activated, where they stalled. Charts without billing are vanity.

Why billing has to come early

An MVP that cannot take money is a demo. The order in which we build the first four systems, and why.

If you cannot take money, you are still pitching. Shipping starts when a stranger can pay and use the product the same day.

What we leave for the second slice

Admin tools beyond the buyer, multi-currency edge cases, and beautiful empty states. They matter — after someone has paid and told you what is missing.

A short test before you prioritise

Ask: can a new customer pay, get access, and complete the core job without a founder on a call? If not, the dashboard is not the bottleneck.