From Vibe-Coded Prototype to Paying Customers: A Practical Launch Checklist
You prompted your way to a working app in a weekend. The gap between "it runs" and "it earns" is smaller than you think — if you work the list instead of polishing the code.
Vibe coding got you a prototype in days that would once have taken months. That's the good news. The bad news: the prototype was never the hard part of a business. Here's the honest checklist between your working demo and your first invoice — most of it isn't code.
1. Decide what the £1 version is
Not the vision. The smallest thing someone will pay for this month. Cut features until it fits in one sentence: "It does X for Y people." If your landing page needs three paragraphs to explain the product, the product is still too big.
2. Harden the three things AI code gets wrong
AI-assisted code is remarkably good at features and remarkably casual about the unglamorous parts. Before real users touch it, have an agent (or a friend who codes) audit exactly three areas:
- Auth and permissions — can user A see user B's data? This is the classic vibe-code hole.
- Secrets — API keys hard-coded anywhere in the client or the repo history.
- Input handling — what happens with empty, enormous, or malicious input.
You don't need enterprise security. You need to not be embarrassed on day three.
3. Put a real payment rail in front of it
Stripe, Paddle or Lemon Squeezy, wired to a paywall, even if the price is a placeholder. A waitlist measures politeness; a checkout measures demand. Merchant-of-record services (Paddle, Lemon Squeezy) also handle sales tax/VAT for you, which for a solo founder is worth the slightly higher fee.
4. Ship a landing page that answers four questions
What is it, who is it for, what does it cost, what happens when I click? One page, one call to action. Your prototype energy is better spent on ten headline variations than on a settings screen nobody asked for.
5. Price like a business, not an apology
Solo founders systematically underprice. Start at the price that feels slightly uncomfortable, monthly and annual, and remember: at £9/month you need 1,000 customers for a modest salary; at £29 you need a few hundred. Cheap isn't kind — it's just a slower way to quit.
6. Get ten real conversations before you "launch"
Forget the big bang. Find ten people with the problem — in communities you already inhabit, or one warm intro at a time — and watch them use it. Five of those conversations will rewrite your homepage. Two will become your first customers. One will tell you the feature that actually matters.
7. Set up the boring layer the same week money arrives
First payment means you have a business: separate bank account, accounting software, terms of service and privacy policy (AI drafts, you review), and a decision about whether it's time for an LLC or company. An afternoon now, versus a very bad April later.
8. Pick one growth channel and commit for 90 days
SEO content, a newsletter, short video, community presence — any of them can work; none of them work in two weeks. Choose the one you can sustain on your worst week, and judge it after a quarter, not a fortnight.
The prototype proves you can build. The first ten customers prove you should.
We're building out step-by-step guides for each item on this list — join the Monday Briefing and we'll send them as they land.