You built something that works. People are using it, or would if they knew it existed. That's the hard part, and you've already done it.
What's left is a list of unglamorous problems that have nothing to do with the product: an entity, some paperwork, a hosting bill that scales badly, and a way for anyone to find the thing. None of it is technically interesting. All of it is needed before "side project" becomes "business".
Here's the actual checklist, not the vague version.
| Area | What it involves | One-off or ongoing? |
|---|---|---|
| Legal | A company, a business bank account, Terms of Service and a Privacy Policy | Mostly one-off, then maintained |
| Compliance | The ICO fee, GDPR, and any rules for your sector | Ongoing |
| Hosting | Reliable uptime and a plan for when things break | Ongoing |
| Marketing | Technical SEO, useful content and measuring what works | Ongoing |
Legal
The business needs somewhere to legally live. For a UK-facing product that usually means a limited company:
- registered with Companies House
- a registered office address
- a director (you)
- a bank account the company controls, not your personal one
If you're building from outside the UK and want UK customers to pay a UK entity, that's a slightly more involved version of the same problem. Get proper advice rather than guessing.
Terms of Service and a Privacy Policy aren't optional decoration. If you collect an email address, you're processing personal data, and UK GDPR applies whatever your revenue or headcount.
Get both documents right before you have customers. Retrofitting them once you have real users is harder and riskier.
Compliance
This is the one people skip and regret. What applies depends on what you're building.
A SaaS collecting emails has a lighter load than a fintech product handling payments, or an app in a regulated sector like gambling or financial services.
The ICO's annual data protection fee catches almost everyone with a signup form, and surprises almost everyone who didn't know it existed.
In a regulated space, compliance isn't a tick-box. It's ongoing, and it needs someone actually watching it, not a one-time review.
Hosting
A prototype on a free tier is fine until real usage arrives. Then it isn't.
Production hosting means:
- uptime you can stand behind
- a plan for when something breaks outside office hours
- infrastructure that doesn't fall over the day your product gets real attention
This is boring work. It's also what turns "I hope it stays up" into "it stays up".
Marketing
Nobody finds a product by accident. This is where solo founders usually either burn a weekend on things that don't compound, like a one-off social post or a Product Hunt launch with no follow-up, or quietly stall.
The work that does compound is technical SEO, content that answers real search queries, and consistently measuring what's working. Like compliance, it's ongoing and unglamorous. It needs doing regularly, not once.
What helps at each stage
None of the above is optional. Some of it, specifically the legal and compliance groundwork, needs a solicitor's or accountant's sign-off, not a shortcut.
What can be taken off your plate is the ongoing operational load: hosting, marketing, and the recurring parts of compliance and legal upkeep that don't need reinventing for every product.
That's the gap Qeetoto works in:
- Marketing & Growth, an ongoing, done-for-you service
- LaunchUK, if you need a genuine UK presence without relocating
- a free introductory offer for a limited number of products
You keep 100% of your IP in every case.
If this sounds like where you're stuck, get in touch and tell us where you are.