Engagement models
How we engage — and how pricing is determined
We do not sell fixed tiers. Each engagement is scoped to the actual work, so the price reflects what your system needs — no more, no less. Below are the ways we work together and what each one produces.
- 01
No published fixed prices
- 02
Scoped after a discovery conversation
- 03
Staged by milestones or recurring
Engagement models
- 01Fixed-scope assessment
Architecture Review
You have a system in production or under construction, and you need an independent read on its structure, risks, and readiness before committing further.
What you receive
A written architecture assessment with prioritised findings and clear recommendations.
- Included
- A structured review of the current design
- Risk and dependency mapping
- A prioritised findings record
- A readout session with your team
- Not included
- Implementing the recommended fixes
- Ongoing monitoring or support
- Changes to production access
- Scope drivers
- Size and surface area of the system
- Number of integrations under review
- Depth of review requested
- How pricing is determined
- Scoped after a discovery conversation, based on the surface area reviewed and the depth requested.
- 02Scoped definition
System Definition
You know the outcome you need but not yet the shape of the system. This engagement turns intent into a defined, buildable specification.
What you receive
A system model and written specification that a team can build against.
- Included
- Framing of the operational problem
- Data and workflow modelling
- A written specification
- An architecture direction
- Not included
- Full build and delivery
- Long-run engineering
- Production infrastructure
- Scope drivers
- Number of workflows and decisions modelled
- Number of stakeholders involved
- Clarity of the starting brief
- How pricing is determined
- Scoped after a discovery conversation, based on the number of workflows modelled and the depth of specification required.
- 03Milestone-staged build
Product Engineering
You have a defined direction and need a system engineered to run in production — not a prototype.
What you receive
A working, production-grade system with its supporting documentation.
- Included
- Implementation against an agreed specification
- Integration work
- Testing and release
- Handover documentation
- Not included
- Open-ended scope without a specification
- Unrelated existing systems
- Long-term stewardship (contracted separately)
- Scope drivers
- Scope of the product surface
- Number of integrations to build
- Governance and compliance requirements
- How pricing is determined
- Scoped after a discovery conversation and a review of the specification, then staged by delivery milestones.
- 04Milestone-staged migration
Platform Modernization
You operate a system that works but is costly to change, and you need it brought to a maintainable, current footing — without a rebuild-from-zero risk.
What you receive
A modernised platform with a documented migration path and a reduced cost of change.
- Included
- An assessment of the existing platform
- A staged migration plan
- Incremental modernisation
- Documentation of the new footing
- Not included
- Preserving every legacy behaviour without review
- Feature expansion beyond the agreed scope
- Scope drivers
- Size of the existing codebase
- Extent of legacy dependencies
- Migration and data constraints
- How pricing is determined
- Scoped after a discovery conversation and an assessment of the existing platform, then staged to reduce risk.
- 05Recurring engagement
Ongoing Stewardship
You have a live system and need it kept healthy, current, and accountable over time — rather than left to drift.
What you receive
A maintained system with a regular operating review and a clear point of accountability.
- Included
- Monitoring and maintenance
- Scheduled operating reviews
- Prioritised change work within an agreed envelope
- A named point of contact
- Not included
- Large new build work (scoped separately)
- Guarantees beyond the agreed terms
- Scope drivers
- Number of systems under care
- Support responsiveness required
- Expected change cadence
- How pricing is determined
- A recurring engagement scoped after a discovery conversation, based on the systems under care and the responsiveness required.
Nothing here is a fixed quote. Every price is agreed in writing before any work begins.