We are a small studio and we work remotely. This page explains what that actually means, because "remote" covers everything from a well-run process to an offshore team you never speak to.
What the fortnight looks like from your side
- Day 1
Kick-off and scope
We go through your goals, your users, and the one job the app has to do. Everything that is not that job goes on a version-two list.
- Days 2 to 3
Design
Screens, flows, and the look of the thing. You review and revise until you sign off. Nothing gets coded until you have.
- Days 4 to 10
Build
Front end, backend, accounts, notifications, admin dashboard. You see working builds as they land rather than a reveal at the end.
- Days 11 to 12
Test and fix
Real devices, real data, edge cases. This is where most of the unglamorous work happens.
- Days 13 to 14
Submit and launch
Store listings, screenshots, privacy details, and submission to the App Store and Play Store. Then 30 days of support while your first users arrive.
Your involvement is four touchpoints, totalling four to six hours.
Your four touchpoints
- Kick-off call, day oneVideo, about an hour. We decide what the app does and what goes on the version-two list.
- Design review, day threeYou look at screens and say yes or what to change. The one that cannot slip.
- Mid-build checkShort. You look at a working build on your own phone.
- Sign-off before submissionAround day twelve.
Between those, you get working builds as they land. That is a stronger signal than a weekly status call, because you are looking at the software rather than at a summary of it.
Why remote is part of why the price works
Not a compromise we are apologising for. Travel time, meeting rooms, and the account-management layer that exists to fill them are real costs, and they sit inside a traditional agency quote.
Removing them is one of several reasons the price is what it is.
Where remote genuinely is a limitation
What we need from you
One decision-maker who can say yes without going away to ask three other people, and a reply within a working day during the fortnight. On a fourteen-day build, a three-day wait for feedback costs a fifth of the sprint.
Full detail on how a sprint runs.
Common questions
How much of my time does a remote build need?
Four to six hours across the fortnight: a kick-off call, a design review, a mid-build check, and sign-off. Less than an in-person project, because there is no travel and no meeting held for the sake of being seen.
What if I want to meet in person?
For most fourteen-day builds it is not necessary and it costs you a day. If your project genuinely needs it, say so on the first call and we will tell you honestly whether we can make it work.
How do I know work is actually happening?
You see working builds as they land rather than a reveal at the end. That is a better signal than a status meeting, because you are looking at the thing itself.