Skip to main content

Dev Station Technology

Fixed price

A fixed price is only honest when the scope is settled

We quote fixed price for defined work and carry the overrun ourselves. We turn it down when requirements are still moving, because the alternative is an argument about change requests by week six.

What must exist before we can quote

Written scopeIncluding what is excluded
Integrations examinedShown to us, beyond a name
One person who decidesSign-off without a committee
Acceptance criteriaHow we know it is done
Design still movingThen fixed price is wrong

Four greens and no red is roughly the test. A quote takes about a week of scoping, and you keep the scope document either way.

1 weekOf scoping before any number
10 to 14 weeksA proof of concept or cut first version
3 monthsWhere fixed scope stops working well
OursThe overrun, if we estimated wrong
What makes a scope fixable

Four things, and all four have to hold

A fixed price is a bet on a specification
Testable acceptanceCriteria somebody can test against, with no room for opinion.
Shown integrationsInterfaces you can show us, beyond a description.
Known dataShape and volume measured before the quote.
One deciderA person authorised to say yes without a committee.

With two of the four, we quote the scoping work and hold the build quote back.

Fit check

Is fixed price right for this work?

Pick us when

  • A first version with an agreed feature list
  • A migration where source and target are known
  • An integration against a documented interface
  • Procurement that needs a single number to approve

Look elsewhere when

  • A product whose direction may change after user feedback
  • Anything that depends on a system nobody has opened
  • Long programmes where priorities will shift
  • Work you want to steer sprint by sprint
How we quote

Scope first, then a number we stand behind

From scoping week to warranty
Week 1

Scoping

The scope written down, exclusions included, with acceptance criteria agreed.

Signature

Fixed quote

One number, payment tied to milestones you can see.

Build

Changes, used sparingly

Written variations with a price and a schedule impact, agreed before the work.

Go-live

Warranty

Defects against the agreed scope fixed at no charge.

A common pattern: discovery on time and materials, then a fixed price once the scope stops moving.

Technologies

What fixed scope usually runs on

The stack follows the scope, and we name it in the quote.

Builds

Warranty after go-live, in practice

National education analytics platform rebuilt by Dev Station
Case study, Norway

A school data platform rebuilt with nothing lost

A previous vendor had missed the delivery date and the deadline with schools was contractual. Our dedicated team rebuilt the platform in modules, with a separate group on the migration alone.

60 daysWarranty support after go-live

Tell us what needs building

Three fields. An engineer reads it, and you get an answer within one working day.

  • We tell you whether fixed price is honest for this work
  • If it is, you get a scoping week and then a number
  • No obligation, and no phone number needed to start
FAQs

Questions we get on the first call

Why is fixed price more expensive per hour?

Because we price the risk of being wrong about the estimate. On settled work that premium is small, and on unsettled work it is large, which is a sign to use another model.

Do you charge for the scoping week?

Yes, as a small fixed engagement. You keep the scope document and can take it elsewhere.

What if we change our minds mid-project?

Changes are quoted separately. If they become frequent, we suggest moving to a dedicated team.

What if you underestimate?

We absorb it. That is the deal, and it is why we are careful about which work we accept on this basis.

Send us the scope you already have

Even a rough one. Within a call we will tell you whether a fixed price is honest for this work, or which model would serve you better.

Let's Talk