Engagement model
How an organisation begins, and how the work is delivered.
The first commercial step is a bounded discovery or pilot. A full programme is agreed only once scope, timeline and responsibilities are written down.
Commercial path
- 01
Introductory discussion
A conversation to understand the requirement, constraints and success criteria. There is no charge and no obligation.
- 02
Written proposal
If we are in a position to assist, we issue a written proposal for a discovery, a bounded pilot, or a delivery engagement, with scope, timeline and commercial terms.
- 03
Discovery or pilot
The usual first paid step with a new organisation. It is time-boxed so both parties can judge the working relationship before a longer commitment.
- 04
Delivery
Architecture, iterative development, validation, production release and a defined support arrangement. The same engineering contact remains accountable.
First engagement
- 01
Introductory discussion
A conversation to understand the requirement. There is no charge and no obligation.
- 02
Confidentiality
If existing systems or data must be reviewed, a non-disclosure agreement is executed first.
- 03
Discovery or pilot
A written, time-boxed proposal so both parties can judge the working relationship before a longer commitment.
- 04
Delivery engagement
Once scope is agreed, the same team proceeds to architecture, build, validation, release and support.
Delivery, once scope is agreed
- 01
Discover
Business objectives, users, existing systems and constraints are documented before technology is selected.
- 02
Architect
Scope, security, integrations and a phased delivery plan are agreed in writing.
- 03
Build
Development proceeds in short iterations, with working software reviewed regularly and testing conducted continuously.
- 04
Validate
Automated checks, security review and performance assessment are completed prior to release.
- 05
Launch
Deployment to production with CI/CD, monitoring and a defined rollback procedure.
- 06
Support
Operational support, optimisation and planned evolution of the system after go-live.