How we work
Six weeks. A demo every week. No surprises.
Here’s exactly what happens after you say hello — so you can decide whether we’re the right people before you spend a cent.
Here’s how a project actually goes.
No 40-page proposal. No “phase gates.” Six-week cycles with a fixed scope, a fixed price, and a demo every week.
- WEEK 1 · THE BETA working prototype of the riskiest part, on your real data.A one-page plan. What we’ll build next, what we won’t, and what it costs.
- WEEK 2 · DESIGNClickable screens, not mood boards. You tap through the real flow.The hard parts first. We prove the risky bits work before polishing the easy ones.
- WEEKS 3–6 · BUILDA demo every Thursday. Working software on your phone, not a slide.One shared room. Every decision written down in plain English.Scope, not time, bends. If something has to give, you choose what.
- WEEK 7 · SHIPIt goes live. App stores, production servers, real users.You get the keys. Repo, infrastructure, docs and a runbook.
- AFTER · STICK AROUNDAnother cycle, a monthly crew, or a clean goodbye. Your call.No lock-in. Ever. That’s why people come back.
Shape
Before anyone writes production code, we make sure we’re building the right thing.
We start with a 30-minute call about the problem — not the feature list. Who has it, what it costs them today, and what “solved” looks like. If we’re not the right people for it, we’ll say so on that call.
Then comes the week-one bet: a working prototype of the riskiest part of your idea, built on your real data. You set the bar before we start. If it clears, we keep going. If it misses, you keep the prototype and pay nothing.
Included
- 30-minute problem call
- Week-one prototype
- A one-page plan
- Fixed scope and price
- Architecture notes in plain English
Build
Six weeks, small steps, and nothing you have to take on trust.
Every Thursday you get a demo of working software — on your phone, in your browser, against your data. Not a status report, not a burndown chart. If something is behind, you hear it early and with a plan attached.
Everything lives in one shared project room: demos, decisions, files, and what shipped this week. The person you talk to is the person writing the code, so questions get answered in hours, not days.
When something has to give, scope bends, not time or money. You decide what moves to the next cycle.
Included
- Weekly demos
- One shared project room
- Code review on every change
- Automated tests and CI
- Decisions written down
Ship & hand over
Launching is the start, not the finish. So we build for the day after.
We take it live — app stores, production servers, real users — with monitoring in place so we know about problems before your customers do.
Then you get the keys: the repository, the infrastructure, the docs and a runbook written for whoever runs this next. At most agencies confusing code is a business model. Ours is software your own team can pick up on Monday.
After that, it’s your call: another cycle, a monthly crew, or a clean goodbye.
Included
- Production launch
- Monitoring and alerts
- Repo and infrastructure handover
- Runbook and docs
- Optional monthly crew
The rules we work by.
They’re short so we can actually keep them.
- Senior people only.Everyone on your project has shipped real products. No juniors learning on your budget.
- Prices up front.Fixed scope and price per cycle. No hourly meter quietly running in the background.
- Bad news travels fast.Risks and delays reach you the day we spot them, with options attached.
- Write it down.Decisions, trade-offs and how things work live in plain English, not in someone’s head.
- Boring technology on purpose.Rails, React, Postgres. Proven tools your next hire already knows.
- You own everything.Code, accounts, infrastructure and data are yours from day one, not at the end.
It always seems impossible until it’s done.
Tell us what you’re building. You’ll hear back from a human — usually the founder — within one business day.
Start a project with Navio Labs