Initial Studios Logo
Pricing

No two builds cost the same.
Here is how yours gets worked out.

We stopped publishing a price list because it was never the real answer. Anyone quoting your project before looking at it is guessing, and you end up paying for the guess. This page is what we do instead.

15+ yearsFounder's experience
NoneRecruitment fees
100%Source code yours
FreeFirst conversation

Three ways to work with us.

The shape of the engagement changes how it is priced. Most people start with a sprint or a call and move once they know what they are dealing with.

Fixed outcome

Build Sprint

Scoped, quoted, then fixed

One outcome · agreed before kickoff

For one defined outcome: feature rescue, prototype, audit, integration, migration, or launch support.

Outcome scoped before kickoff
Acceptance criteria and handover notes
Slack/Teams access during the sprint
Full source ownership
Can roll into embedded capacity
Most direct pathRecommended

Embedded Developer

Scoped and quoted up front

Minimum engagement applies

One of the two of us working inside your roadmap now, without recruiting, onboarding theatre, or agency layers.

React, React Native, and full-stack delivery
Daily standups and direct access to the person building it
Timezone-aligned collaboration
Short minimum engagement, not a long lock-in
First meaningful PR before first invoice
Enterprise available

Retained Capacity

Reserved month to month

Reserved time · notice period applies

For ongoing roadmap continuity, more than one workstream, or procurement support, with both of us on your product.

Reserved time with Jake and Ben
Roadmap and sprint planning support
Both of us on it when the work needs two
Security and procurement-friendly terms
Priority support for launches

What moves the number.

Five things do most of the work. If you can answer these, you can usually predict which end of a quote you are going to land on before we say a word.

01

What already exists

Working on a clean, well-structured codebase is faster than untangling one that grew in a hurry. The read-through tells us which one you have before anyone quotes.

02

How much has to be certain

A tool used by your own staff and a product taking public payments need very different amounts of testing, hardening and review. That gap is real money either way.

03

How many moving parts

Payments, live data, file handling, third-party integrations and anything with a login each bring their own edge cases. Feature count matters less than feature type.

04

Who else is involved

If we are the whole team, we move fast. If we are working alongside your devs, another agency, or a procurement process, plan for coordination time and price it in.

05

How fast you need it

Ordinary timelines cost ordinary money. Compressing a schedule means more hours in parallel, more coordination, and a higher number for the same scope.

How a quote gets built.

Three steps, and you are not committed to anything until the last one.

1

A call

Twenty minutes, free, with the engineer who would do the work. Enough to tell you whether we are the right fit, and to say so plainly if we are not.

2

A read-through

We go through what exists and what you want. You get it back in plain English: what is solid, what is risky, and what the work actually involves.

3

A number you can hold us to

A written scope with the number attached and the assumptions it rests on. If something changes later, we tell you before it changes the price, not after.

Not sure which fits?

Tell us the problem. We will tell you what it takes.