“To launch a startup you first build the boring 80%.” Accounts, auth, billing, payments, an admin panel, a mobile app — months of undifferentiated plumbing before you touch the thing that makes you a business. A new build guide argues that the plumbing should ship switched-on, so a founder spends week one on the idea instead of the infrastructure.

One backend, every surface

The core claim is that a single codebase covers the web and both mobile platforms. As the original write-up on VBWD puts it:

a single Python backend serves a Vue/TypeScript web front end, a native iOS SDK and a native Android SDK — from the same source of truth.

For a two-person team that’s the difference between shipping on all three platforms and shipping on one while promising the rest “later.” The core stays agnostic; everything specific is a plugin that toggles on or off without a restart — subscription, marketplace, booking, a token economy, datasets, a CMS, an agent-callable MCP surface — so building becomes a question of which capabilities you switch on.

Why it stays coherent

The trick that keeps a fast build from turning into spaghetti is a single billing spine:

everything sellable — a subscription, a booking, a token top-up, a marketplace commission, a dataset licence — is declared as an invoice line item against one shared interface.

Add a new way to make money and it inherits pricing, tax, discounting and reconciliation for free. The honest caveat the guide makes is worth repeating:

VBWD is a substrate, not a business plan.

It won’t find product-market fit or run your operations, and self-hosting means you own uptime and updates. What it removes is the generic foundation that eats a startup’s first three months.

The full week-one plan is published on VBWD; the platform’s public SDK is on GitHub.

Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.