Pricing
How We Price Work
Three engagement models, quoted against a written scope. Start with a fixed-price discovery and you'll have a firm number before the build begins.
Engagement models
Pick the shape that fits your team
Most startups begin with a fixed-scope build and move to a dedicated team once the product is live.
Fixed-scope build
A defined product — an MVP, a rebuild, or a v2 with a clear feature list.
We scope the work in discovery, then quote a fixed price and timeline for that scope.
- Written scope and architecture plan before a line of code
- Fixed price and milestone plan for the agreed scope
- Weekly demos of working software
- App Store and Google Play submission support
Dedicated team
Ongoing product work where priorities shift month to month.
You get a named team — engineers, designers, QA — reserved for your product on a monthly basis.
- The same people on your product each sprint
- Your backlog and priorities, re-planned each sprint
- Direct access to the team in your own Slack channel
- Scale the team up or down as the roadmap changes
Staff augmentation
An in-house team that needs specific skills for a defined period.
Individual engineers join your existing team, your process, and your tooling.
- Flutter, React Native, Swift, Node.js, NestJS or Laravel specialists
- Work inside your repo, your sprints, your code review
- Timezone overlap arranged for US and EU working hours
- Ramp up or down without a new contract each time
What drives the number
Where the cost actually goes
These are the factors that move a quote up or down, so you can see which trade-offs are available.
- Number of platforms
- One cross-platform app costs less than separate native iOS and Android builds. Adding a web app or admin panel adds scope.
- Real-time and media features
- Live chat, calls, location tracking and audio/video processing need more engineering than standard CRUD screens — as in Leklok's live rooms or Chattick's calling.
- Third-party integrations
- Payments (Stripe, Square), subscriptions (RevenueCat), maps, and messaging each add integration and testing work.
- Backend complexity
- Firebase gets an MVP live fastest. Custom NestJS, Node.js or Laravel APIs cost more and suit products that need bespoke logic or data ownership.
- Design depth
- Adapting a design system is quicker than research, wireframes and custom UI for every screen.
- Compliance and launch requirements
- Store review requirements, platform rules and data-handling obligations add QA and documentation time.
Start here
Get a fixed quote in two weeks
The MVP Discovery turns a rough idea into a scoped plan with a fixed build price — and the fee comes off your build if you go ahead.
Already have a detailed spec? Send it through the contact form and we'll quote from it directly. You can also see how we run projects before committing.
FAQ
Pricing Questions
How do I get a price for my project?
Why don't you publish a price list?
What is the MVP Discovery and is it credited?
Do you work fixed-price or time-and-materials?
What happens if the scope changes mid-project?
Do you support the app after launch?
Want a number for your project?
Send us the scope you have — however rough — and we'll tell you what it takes to build.
Reply within 24 hours · No commitment required