What drives the cost of a project?

Mostly integrations with external systems (payments, CRM, ERP, third-party APIs), compliance requirements (GDPR, invoicing, sensitive data), real-time, legacy data migrations, and bespoke design vs reusable components. The number of screens matters less than people think; what's expensive is the logic and the integrations underneath.

← Blog · Jul 2, 2026 · Business

How we price a project: from idea to a fixed quote

Q: Why won't you give me a price on the first call?

Because a price without scope is a made-up number. An off-the-cuff figure either pads to cover risk or falls short and ends in overruns. We prefer 20-30 minutes of questions to understand the real problem, then give an honest range, and a fixed price only once the scope is written down.

Q: Fixed price or hourly?

For a well-defined scope we prefer a fixed price by milestones: you know what you pay and we take on the estimation risk. For exploration, ongoing support or open-ended evolution, a block of hours or a monthly retainer fits better. What we don't do is 'fixed price' on a fuzzy scope: that always ends badly for someone.

Q: How long does a quote take?

An indicative range usually takes under 30 minutes after we understand the project. A proposal with scope, phases, timeline and a fixed price typically takes 1 to 3 days depending on complexity and whether integrations need investigating.

"How much would an app cost me?" is the question we get most, and the one a loose number answers worst. A price without scope is a made-up number: it either pads to cover risk or falls short and ends in overruns and bad blood. Here's how we go from a fuzzy idea to a fixed price by milestones where both sides know exactly where they stand.

1. The problem first, not the solution

Many people arrive with the solution already decided ("I need an app with login and a dashboard"). We start one step earlier: what business problem is behind it and how is it measured. Want to cut no-shows? Capture more leads? Save hours of manual work? The answer changes the scope completely: sometimes the "app" you asked for is solved with an automation at a third of the cost.

2. The questions that actually move the budget

In 20-30 minutes we ask what has a real impact on cost:

Integrations: does it connect to payments, CRM, ERP or third-party APIs? Each integration is work and risk.
Data: is there legacy data to migrate? From where, in what state, what volume?
Compliance: GDPR, legal invoicing, sensitive data, regulated sectors.
Users and roles: one profile or several with different permissions? Complex roles cost.
Real-time: notifications, live sync, overlays… they change the architecture.
Design: bespoke to the brand or built from components? It drives UI time.
Platform: web, native mobile, both? Each platform is another front.

What almost never matters as much as people think: the number of screens. The expensive part isn't drawing views, it's the business logic and integrations underneath.

3. Scoping: the "not in v1" list

Before putting a price on it, we write down what's in and what's out of this phase. The "out of scope" list is as important as the feature list: it's what stops the project growing 40% without anyone deciding to. Everything deferred doesn't vanish; it goes to a v2 with its own budget. This protects both your wallet and our schedule.

4. From range to fixed price by milestones

With the problem understood and the scope set, we first give an honest range (usually in under 30 minutes) and, if it fits, a proposal with a fixed price split into milestones: each milestone is a reviewable deliverable with an associated payment. You see real progress every 1-2 weeks and we take on the estimation risk. If midway you want to add something from the v2 list, it's quoted separately, without renegotiating everything.

Fixed price Well-defined scope. You know what you pay; the estimation risk is ours.

Block of hours Exploration or frequent changes where the scope is still moving.

Monthly retainer Ongoing evolution and support after launch.

5. Why we don't quote off the cuff

If someone throws you a fixed price on the first call without asking about integrations, data or compliance, be wary: either they're over-padding or they'll ask for add-ons later. A good quote is a short, honest conversation, not an auction. To get into the right order of magnitude before talking, you can use our cost calculator; it gives a realistic range in two minutes.

FAQ

Why won't you give me a price on the first call?

A price without scope is a made-up number. We prefer 20-30 minutes of questions then an honest range; a fixed price only with the scope written down.

What drives the cost?

Integrations, compliance, real-time, data migrations and bespoke design. The number of screens matters less than the logic and integrations.

Fixed price or hourly?

Defined scope → fixed price by milestones. Exploration or support → block of hours or retainer. Never "fixed price" on a fuzzy scope.

How long does a quote take?

A range in under 30 minutes; a proposal with scope, phases and a fixed price in 1 to 3 days depending on complexity.

Have an idea and want an honest number?

Tell us the problem and we'll give a realistic range; if it fits, a proposal with a fixed price by milestones.

Talk about your project Calculate a range

Related resources

How much custom software costs in 2026 — ranges by project type and what multiplies them.
How to hire custom software — billing models and red flags.
MVP in 4-8 weeks checklist — scope the work before asking for a quote.
The stack we use in 2026 — what we build by default.

Published: July 2, 2026 · Written by the RoviDev studio.