A realistic cost range
Not a number pulled from a rate card. What your scope actually implies, what would move it up or down, and where the expensive parts hide.
5.0
Based on 100+ successful projects
Thirty minutes
before you commit.
A conversation about scope, cost and what to build first — with someone who builds these things rather than someone who sells them.
No obligation, no follow-up sequence. If we are not the right studio for it, we will tell you on the call.
TRUSTED BY BUSINESSES WE’VE WORKED WITH
Useful whether or not
you ever work with us.
Answers you can
act on.
A view on what to build first
Which parts belong in version one for the result to tell you anything, and which are safe to defer without painting yourself into a corner.
The technical decisions that matter
The handful of architecture choices that are expensive to reverse later, and a recommendation on each — stack, data model, hosting.
An honest read on feasibility
Including when the answer is that the idea needs reshaping, or that you do not need a custom build at all. That answer is free and saves the most money.
Why this call exists
The most expensive decisions in a software project get made before anyone writes code — what to build first, what to leave out, which technical choices are cheap now and ruinous to reverse in a year. Those decisions usually get made in a hurry, by someone who has not built this kind of thing before, under pressure to start.
Thirty minutes with someone who has shipped this before is generally enough to catch the worst of it. Most of the rescue work we take on traces back to a decision made in a project’s first week — a data model that could not accommodate the second customer type, a first version so large it ran out of budget before launch, a platform choice that made the obvious next feature impossible.
What to bring
- A sentence on what the product is for, and who for
- Anything that already exists — a site, a repo, a Figma file, a half-built app
- Your constraint: a launch date, a budget ceiling, an investor conversation
- The one thing that worries you most about building it
If none of that is settled yet, book anyway. Working out what you are actually building is a reasonable use of the half hour.
What this is not
It is not a sales call with a discovery script, and it is not a free specification document — thirty minutes buys a direction, not a delivery plan. If the project is a fit, the scoping that follows is a separate, more thorough conversation.
Before you
book.
Ask something else Yes, and there is no obligation attached to it. It is thirty minutes and it works out for us often enough to be worth doing: some calls become projects, some become referrals, and some end with us telling you not to build the thing. All three are fine outcomes.
You describe what you are trying to do and we ask questions — mostly about the business behind the software rather than the software itself, because that is what determines what should be built. Then we give you our actual read: cost range, what to build first, and the decisions worth getting right early.
Nothing formal. Knowing roughly what problem you are solving and for whom is enough. If something already exists — a site, a repository, designs, a half-finished build — send a link beforehand and we will have looked at it before we speak.
No, and it would be a poor strategy: overselling a project that is wrong for you produces a difficult build and no referral. If a smaller scope, a different approach or an off-the-shelf tool serves you better, we will say so on the call.
That is a perfectly good reason to talk. Plenty of people book a call months before starting, precisely so the early decisions get made properly. Knowing the likely cost and shape of a build well ahead of time is useful for planning and for fundraising conversations.
The person who would be responsible for your project. The call is not a qualification screen handed off to someone else afterwards — what you are told on the call is what carries into the work.
5.0
Based on 100+ successful projects
Turn your idea into
a product people love.
Get a clear quote, a realistic timeline, and a plan tailored to your goals.
