Fixed-Scope Project
Suitable when deliverables and acceptance criteria can be specified before work.
- Written SOW and exclusions
- Milestone/acceptance arrangement
- Changes assessed separately
Different requirements call for different engagement structures. The best model depends on clarity of scope, delivery risk, responsibilities and expected change.
All scope, specialist availability, deadlines and commercial terms require project-specific confirmation.
These models are discussed rather than sold through an automatic checkout.
Suitable when deliverables and acceptance criteria can be specified before work.
Useful for iterative work with evolving priorities and an agreed budget control method.
For clients who need diagnosis, feasibility, architecture or an independent review before commissioning development.
For repeated, bounded support and maintenance tasks with agreed access, availability and service windows.
Document requirements scale with technical risk and engagement complexity.
Quotation, concise SOW and applicable terms.
Proposal, MSA/SOW if appropriate, milestones and acceptance plan.
Dedicated discovery, detailed assumptions, change control and governance checkpoints.
Support scope, response expectations, exclusions, renewals and exit/handover plan.
The essentials remain the same regardless of engagement type.
No. Each quote is based on confirmed deliverables, assumptions, dependencies and risk.
Deposit, development and final acceptance milestones may be discussed, but exact ratios and dates are binding only when agreed in writing.
Hosting, domains, APIs, licences and other recurring charges must be allocated explicitly in the project documents.
Ownership, licensing, third-party materials and handover conditions are specified in the contract and subject to legal review.
Termination, refunds, suspension and change impacts are governed by the signed terms and applicable law.
Send the project background. We can discuss which model aligns with the work and decision process.