Fixed-scope project pricing
For a defined product, feature, integration or modernisation outcome with agreed deliverables and acceptance criteria.
Pricing factors made visible
We use the information available to document a defensible quote. Where uncertainty remains, the assumption and its effect are stated instead of hidden.
What shapes the commercial proposal
- Agreed scope and deliverables
- Delivery complexity and dependencies
- Milestones, acceptance and target timeline
- Required engineering, design and specialist roles
What the proposal defines
- Documented assumptions and exclusions
- Delivery plan and milestone schedule
- Review, testing and acceptance approach
- Handover expectations for the agreed scope
New requirements or changed assumptions are assessed through visible change control before they affect cost or schedule.
Understand the model before committing
It works best when the outcome, users, integrations, deliverables and acceptance criteria are understood well enough to create a reliable delivery boundary.
We document the proposed change, its effect on cost and timing, and obtain approval before adding it to the agreed scope.
Only costs explicitly listed in the proposal are included. Cloud usage, licences, paid APIs, app-store charges and other third-party services remain visible as separate assumptions or client costs.