The simple road to ownership

The full code repository and every intellectual property right in the build, transferred to you when the final invoice is settled. You can modify it, run it, resell it or license it without asking us. Open-source components keep their own licences, which we identify at handover.

Because you can see it. A build that has been claimed stays on this site marked Claimed rather than quietly disappearing, so the roster shows you what has gone as well as what is left. We do not build and sell the same listed product twice.

Yes. This is a one-time affair, and the business is set to close either once all opportunities are claimed, or if I feel like enough of the good opportunities have been claimed. Read more about me here and why I'm doing this.

Handover is typically two to four weeks after the scope is agreed, for a web build. Multi-app mobile ecosystems take longer, which is why those are quoted after a scoping call rather than listed at a fixed price. Timelines assume we are not waiting on content, branding or decisions from your side.

Offline — bank transfer or another method we agree in writing. There are two invoices: a deposit that starts the project, and the balance at handover. Both appear in your dashboard with their status from the day the project is created, so you are never guessing what is outstanding.

A listing is retired when a deposit is settled, not when an inquiry arrives. Until then it is still on the market and we will tell you if someone else is moving on it. An inquiry costs nothing and commits you to nothing.

Don't sign off. Sign-off is a deliberate step you take yourself in your dashboard, and it is your acceptance that the build matches the agreed scope — so if it doesn't, say so on the project thread and we put it right first. There is no clock on it.

In full, if you change your mind before work starts. After that it covers the work done to that point and the remainder is refunded. If we are the ones who can't deliver, you get everything back regardless of how much work has happened. The refund policy sets out each case.

Every build includes the option of three months of post-service support, renewable, charged separately. It covers defects in what we delivered. Most people don't need it. Hosting and infrastructure become yours at handover, billed by your provider rather than by us.

You do, on your own account — that is part of owning it. Everything ships Dockerised and runs on GCP or the cloud provider of your choice. Running costs depend on your provider and your traffic, and we will give you a realistic estimate for your build during scoping.

No. Every build comes with an admin dashboard, full documentation and handover training. You will need someone technical eventually if you want to extend it substantially — but operating it, onboarding customers and running the business side does not require it.

Yes — that's the Custom Web App entry, and the custom build inquiry on the homepage. Same exclusivity, same ownership terms, same standard feature baseline, scoped and priced after a discovery call.

Because that market is already well served by mainstream SaaS, and a bespoke build rarely repays its cost there. The roster deliberately sticks to products you can sell to a market of your own, rather than tools a business runs itself with.