Prove the fit on real work
Nobody should sign a year of software work with a company they have never worked with. A first sprint is small enough to say yes to and real enough to judge us on: a scoped release, a fixed price, and the code in your repo at the end of it. If it goes well, the same team keeps going. If it does not, you still own everything.
Fixed scope, fixed price
You approve what is in the sprint and what is out before we start. The number in the proposal is the number on the invoice. Change your mind mid-sprint and we price the change in writing rather than bury it.
A working release, not a prototype
It goes live on your domain, your hosting, your repo. Real people can use it the day we hand it over, and nothing gets thrown away when the next phase starts.
A team still here in month six
Software we shipped years ago is still live and still ours to look after. If you want us to keep going after the sprint, ongoing work continues from $3K a month. If you do not, nothing is locked in and you already hold the code.
Everything the first release needs
Written into the proposal so there is nothing to argue about in week four. No hidden costs, no phase-two surprise.
Up to 5 Core Features
The features the first release actually needs. Sign-in, dashboard, payments, notifications, whatever your users or your staff touch first. Everything else goes on the roadmap with a price against it.
Design Made For You
Screens and flows drawn in Figma and reviewed with you before anyone writes code. Your brand, your layout, not a theme bought off a marketplace.
Works on Every Screen
Phones, tablets and desktops, tested on real devices. Your customers and your own team will open it on whatever is already in their hand.
Deployed to Your Accounts
Hosting, domain and deployment set up in your accounts and your repo, never ours. When the sprint ends you can keep shipping without asking us for a password.
30 Days of Support After Launch
Bugs, tweaks and small fixes for a month after go-live, included. Not a ticket queue. The same engineers who built it.
A Weekly Demo, Not a Status Report
Every week you get a recorded walkthrough and a link you can click. You message the engineers directly, not an account manager relaying answers.
How We Price
One number, agreed upfront
We scope the sprint first, then quote one fixed price for it. No hourly billing and no scope-creep invoice. If the work you want is bigger than one sprint, we tell you that on the call, not after the deposit.
From first call to live in six weeks
Step by step, so you know what happens in every week you are paying for.
Discovery Call
Day 130 minutes with an engineer, not a salesperson. You describe the problem and who has it. We ask the questions that decide the scope, and say so on the call if we are not the right fit.
Scope and Fixed Price
Day 2-3Within 48 hours you get it in writing: what is in the sprint, what is deliberately out, the timeline and the price. Mutual NDA first if you want one.
Design
Week 1-2We draw the screens and the flows, you review them, we iterate. Nothing goes into the build until you have seen what it will look like.
Build
Week 2-5Engineers build in your repo. You see commits as they land and a working demo every week. Features you can click, not wireframes.
Launch and Handover
Week 5-6We deploy to production on your domain, hand over the accounts and the documentation, and stay on for 30 days of support. Then you decide whether there is a next sprint.
The questions we get before the first sprint
Tell us what needs building
Send the details and we come back within 24 hours, with a written scope, timeline and fixed price inside 48. If a call is easier, book one instead and we will do the same thing out loud.
Send project details
Tell us what you're building. An engineer reads it and replies within 24 hours.
Next step
Start with one sprint. Decide about the rest later.
30 minutes with an engineer, not a salesperson. You'll leave with a scope you could hand to anyone, even if we're not the ones who build it.