A defined build, for an agreed scope and price.
For work with a clear scope and acceptance criteria. After a short discovery we agree the scope, a fixed price and a payment plan with you, then own the delivery. You make the decisions and accept the result.
When the scope is clear, the price can be too.
Some work is genuinely defined: an MVP with a clear feature set, a migration with a fixed target, an integration between known systems. For that kind of work a fixed price is fair to both sides. You know the cost before anything starts, and we carry the delivery risk.
What makes it work is the discovery before the price. We learn the domain, the systems and the acceptance criteria first, so the scope we price is the one you actually need. We decline fixed price on undefined scope; that contract just prices in mistrust, and time and materials serves that work better.
You manage acceptance and decisions. We own delivery, schedule and quality.
One party accountable for the delivery.
Decide and accept
- Make the product decisions
- Agree the acceptance criteria with us
- Accept the result against them
Own the delivery
- Write the scope: what is in and what is out
- Plan the schedule and keep it in view
- Deliver to our engineering standard
How the model works, from discovery to handover.
Discovery before the price
A short discovery comes first: the domain, the systems the work touches and what “done” means. The price is set after it, not before.
- Acceptance criteria agreed before pricing
- Risks and assumptions written down
A scope you can hold us to
The scope is written down with what is in, what is out and how each piece will be accepted. It is the reference for the whole project.
- Written scope, fixed price
- Payment plan agreed with you
Changes, handled openly
If something new comes up, it is written down with its effect on price and plan before anything changes. Nothing is added quietly, and nothing is charged by surprise.
- Every change agreed in writing first
- Its effect on price and plan stated up front
Acceptance, then handover
You accept the result against the agreed criteria. Documentation and a handover come with the delivery, whether the work continues with us or not.
- Acceptance against the criteria agreed at the start
- Documentation and handover included
From discovery to acceptance.
Discovery
A short discovery to understand the work, the systems it touches and the acceptance criteria.
Scope and price
A written scope, a fixed price and a payment plan agreed with you.
Build
We deliver against the scope, with progress you can see along the way.
Acceptance and handover
You accept the result against the agreed criteria; documentation and handover follow.
Turnkey, time and materials, or a dedicated team.
How the three models where Odeontech directs the work differ.
When to choose this model.
Choose a turnkey project when the scope is defined with acceptance criteria, when a fixed budget matters most, and when you want one party accountable for delivering it. A well-defined MVP or a migration with a clear target are typical examples.
If the scope is still evolving, time and materials keeps you flexible without pricing in uncertainty. If the work is a roadmap that keeps going, a dedicated team fits better.
Frequently asked questions
Have a build with a clear scope?
Tell us what has to be built and what “done” means. An engineer comes back with how the discovery would run and what we would need to price it.