For founders and idea owners
Your idea has been “almost ready” for two years
Not because it’s a bad idea. Because between you and a live app sits development, design, testing, two app store accounts, review rejections, privacy policies, POPIA registration, hosting, payment integration, and a permanent responsibility for security updates — and none of that is what you’re good at.
What usually happens
Three ways app ideas usually die
The quote that ends the conversation.
You approach an agency. They ask for a spec you don’t have, then quote a number with a lot of zeros for a scope nobody’s fully defined. You go quiet, and the idea goes back in the drawer.
The freelancer who disappears.
You find someone cheaper. It goes well for a while. Then replies slow down, the last 20% never lands, and you’re left with a half-finished codebase you can’t read, can’t run, and can’t hand to anyone else.
The app nobody can find.
It gets built. Then it sits there, because getting an app live is a second job — developer accounts, store listings, review rejections, screenshots at seven different sizes, a privacy policy that satisfies both Apple and POPIA — and nobody told you that was on your plate.
Every one of those is a structural problem, not a personal failing. So we structured the work to remove them.
How we structure it instead
So here’s how we’ve set it up
You don’t need a spec to talk to us.
The Blueprint exists precisely because you don’t have one yet. We build the spec, the prototype and the quote — for a small fixed fee — before anyone commits to a build.
Fixed scope, fixed price, and you own everything.
Your code sits in a repository you own from the first commit. If we vanished tomorrow, any competent developer could pick it up on Monday. That’s not a promise about our character — it’s how the work is set up.
Launching is part of the job, or it isn’t — but you’ll know which.
Store submissions, listings, screenshots, review responses, privacy policy, POPIA registration: on the Launch and Partner options, that’s ours. On Build, it’s yours, and we tell you that upfront instead of at handover.
Three ways to work
Three ways to work with us
The difference isn’t quality — it’s how much of the ongoing weight you want to carry, and how you’d rather pay for it.
Build
We build it. You take it from there.
You’ve got the commercial side handled and you just need the thing built properly.
We do
- Product design and UX
- Full build — app and backend
- Testing across devices
- Handover: your repository, your accounts, your documentation
- Optional Care Plan: hosting, security patching, backups, uptime monitoring and a support channel, billed monthly
You do
- App Store and Google Play accounts, submissions and review responses
- Marketing, launch and everything after it
- POPIA registration and your own regulatory obligations
- Deciding what gets built next
Fixed project fee, invoiced in phases. Optional monthly Care Plan if you’d rather not run the infrastructure yourself.
Launch
We build it, take it live, and keep it running.
You want to own 100% of your app and none of the technical responsibility.
We do
- Everything in Build, plus:
- App Store and Google Play submission, listing copy, screenshots, and handling review rejections
- Your marketing website
- Privacy policy, terms, and POPIA readiness
- Hosting, security, backups, monitoring
- Analytics set up so you can see what users actually do
- Ongoing updates and OS-version maintenance
You do
- Own the product and 100% of the revenue
- Marketing and growth — we’ll tell you what we see in the data
- Decide the roadmap
Fixed project fee, plus a monthly management fee covering hosting, infrastructure, security and support.
Partner
We carry the cost and the work. We share what it earns.
The idea is strong, you know the market better than anyone, and capital is the thing standing in the way.
We do
- Everything in Launch, at a reduced build fee — or none at all
- Carry the infrastructure, compliance and maintenance cost ourselves
- Treat it as our product too, because it is
You do
- Bring the idea, the market knowledge, and the access we don’t have
- Stay involved — this is a partnership, not an outsourcing arrangement
A share of revenue or equity, agreed in writing before anything starts. The split depends on what each side brings.
We can only do a small number of these at a time, and we say no to most of them. That’s not scarcity marketing — it’s just how much risk one studio can carry at once.
Build
Launch
Partner
Not sure which one? The Blueprint prices out all three for your specific idea, so you can compare real numbers instead of guessing.
What actually happens
From here to live
A 20-minute call
FreeWe find out what you’re trying to build and whether we’re the right people for it. If we’re not, we’ll say so and point you somewhere better.
Talk. No documents required.
The Blueprint
1–2 weeksWe turn the idea into a clickable prototype, a written spec, a POPIA and store readiness checklist, and a fixed quote across all three ways of working.
Two working sessions with us, and one round of feedback on the prototype.
You decide
No pressure, no expiryBuild, Launch, Partner — or walk away with the Blueprint and use it elsewhere. All four are fine outcomes.
Take as long as you need.
Build
Scoped in the BlueprintWe build in phases with something you can open and use at the end of each one. No six-week silences.
Review each phase. Roughly an hour a fortnight.
Launch
2–4 weeks after buildStore submissions, listings, privacy policy, monitoring, analytics. On Launch and Partner, we handle the rejections and resubmissions — there are usually some, for everyone.
Approve the listing. Start telling people.
Run
OngoingHosting, security patches, OS updates, backups, support. Software isn’t finished when it ships — it’s finished when you stop paying for it, and we’d rather that day never comes.
Send us what users are asking for.
The Blueprint
Start with a Blueprint
The cheapest possible way to find out whether your idea is worth building — and what it would actually cost.
A clickable prototype.
Not a design mockup. Something you can open on your phone, tap through, and put in front of ten people to see whether they get it.
A written specification.
Every screen, every rule, everything the app does — in plain language, not developer language. This is the document that makes fixed pricing possible.
A fixed quote across all three options.
Build, Launch and Partner, priced for your idea specifically, so you can compare real numbers instead of imagining them.
A readiness checklist.
What your specific idea needs for POPIA, for Apple’s review guidelines, and for Google Play — found now, not three weeks before you’d hoped to launch.
Objections
The questions everyone asks
What does an app actually cost?
Anywhere from a small fixed project to a significant investment, depending entirely on what it does. Anyone who gives you a number before understanding the scope is either guessing or protecting themselves with padding. The Blueprint exists to replace that guess with a real number, cheaply.
How long does it take?
Most first versions land in two to four months of build time. The Blueprint gives you a real timeline for your specific project.
What if I run out of money halfway?
We build in phases, and each phase ends with something that works. If you stop, you stop with a working piece of software and a repository you own — not a half-finished mess.
What happens if Neevo closes down?
Your code lives in your repository, on your accounts, with documentation. Any competent developer can continue it. We’ve set it up that way deliberately, because you shouldn’t have to bet your idea on our survival.
Do I own the app?
Yes — on Build and Launch, completely: code, data, accounts, intellectual property. On Partner, ownership is shared and defined in writing before any work starts.
Can you do the marketing too?
No. We build, launch and run software. We’ll set up analytics so you can see what’s working, and we’ll happily point you to people who do marketing well — but we won’t pretend to be an agency we’re not.
I don’t know if my idea is any good.
Then start with the Blueprint. A clickable prototype in front of ten real people will tell you more in a week than another year of thinking about it will.