Practical guides, and the ideas behind them, for turning a working app into a real business.
Step-by-step answers to the questions that come after launch.
You don't need a limited company to start charging for a UK side project, but there's a specific point where registering with HMRC becomes mandatory, and a separate, genuinely judgement-based question about when incorporating is worth it.
Read guide →GDPR doesn't have a "too small to matter" exemption, but it also isn't the compliance nightmare it's made out to be for a solo SaaS. Here's what actually applies, including the fee almost every solo founder misses.
Read guide →Most indie apps either skip legal pages entirely or paste in a generator's boilerplate. Neither works. Here's what UK law actually requires you to disclose, and what's just there to reduce arguments.
Read guide →If Claude, Copilot or Cursor wrote a meaningful chunk of your codebase, the question of who owns it isn't fully settled, and it's a genuinely different answer in the UK than in most other countries.
Read guide →Getting Stripe wired up is the easy part. The compliance obligations that come with actually taking payment, PCI, cancellation rights, refund timing, don't show up in the integration docs.
Read guide →Nothing forces a solo SaaS founder to buy insurance the way employing staff does, but that doesn't mean it's irrelevant. Here's what the main types actually cover and when they start earning their cost.
Read guide →Shipping a working prototype and running a real business are different problems. The actual checklist: legal, compliance, hosting, marketing, and what genuinely needs doing at each stage.
Read guide →A working definition of Continuous Creation, the shift from software as a sequence of releases to software as a continuous, AI-assisted creation loop, and Qeetoto's own framework for it.
Read guide →The vibe-coding community explains a lot through memes. Each one below makes a serious point, and links to the guide that explains the fix. Browse the full gallery.
An AI-built app can run perfectly while nobody can explain how. The fix is cheap if you capture the why as you go.
Memes: It runs. Don't ask how. · Now only God knows 🙂 · There are only two kinds of pull request
Read: The continuous creation manifesto →Users only see the surface. Security, compliance and maintainability are what customers, investors and acquirers check.
Memes: If only it were that easy! · Same launch pad. Very different basement. · Vibe construction · Please stop asking questions 😬
Read: From vibe-coded to venture-ready →Re-prompting until the error goes away feels quicker every time. Tech debt now builds as fast as AI can write.
Memes: The short route is the long one · Just keep vibe coding · The new productivity · A market emerges
Read: The continuous creation manifesto →Every part can work while the whole leaks. One careless error message can expose credentials and someone else's data.
Memes: Passes the demo. Fails the inspection. · The most helpful error message ever written 🙂
Read: GDPR for a one-person SaaS →AI lets anyone into the water. Version control, runbooks and knowing when you're out of your depth still don't come free.
Memes: Ten apps shipped. Never met Git. · Everyone else is swimming 🐔 · The AI-optimised route 🌍 · The runbook nobody opens 📕
Read: From vibe-coded to venture-ready →Roles and production lines are shifting fast, but an agent can't be held accountable. Someone still has to own the call.
Memes: The building with no ground floor · Four job titles in four years 🙂 · Paradigm Shift 3.0 | Same product, different production line! · Agents act, humans answer 🤝
Read: Do I need a company for my side project? →