Engagement scoping
Pricing built around your scope
Start with the problem, the systems involved and the outcome you need. We discuss the scope with you before proposing an engagement.
What shapes the proposal
- Outcome & acceptance criteria
- The workflow or system to deliver, how it will be tested and what successful handover means.
- Technical scope
- Your existing stack, data readiness, integrations, access requirements and security review.
- Team & collaboration
- The engineering skills, delivery responsibilities and working-hour overlap your project needs.
- Delivery & ongoing support
- Milestones, dependencies, documentation and any support or iteration after launch.
Bring your brief. We’ll scope it together.
Share the business problem, current systems, intended users, constraints and target dates. The proposal should make deliverables, responsibilities, assumptions and exclusions clear so you can review the engagement before committing.