Home / Engagements
Engagement models
Choose a dedicated team, a scoped project or ongoing maintenance — and change the model as your product evolves.
Project Delivery
Use a scoped engagement when the deliverable can be described and reviewed.
Cross Functional Product Teams
Combine engineering, design, QA and coordination as needed for your scope.
Dedicated Development Teams
Extend your development team with the skills needed for your roadmap.
Software Maintenance
Support an existing product through issue resolution, dependency updates and planned improvements, with a process that makes priorities and responsibilities clear.
Product Discovery
Work through business goals, user journeys, technical constraints and open questions.
Engagement models
Choose the engagement that fits your next step.
Dedicated Team
For a changing roadmap or ongoing development. Agree roles and working process, then manage priorities through a shared backlog.
Best for team extension and long-term product work.
Scoped Project
For a defined product or milestone. Align on requirements, deliverables and acceptance criteria, with changes reviewed before they affect the plan.
Best for MVPs, integrations and focused releases.
Maintenance and Improvement
For software that already exists. Start with a technical review, then agree support routines and planned improvements.
Best for live applications and modernisation.
Comparison
Which model fits your situation?
| Model | Best when | How scope is managed |
|---|---|---|
| Dedicated team | Your roadmap is ongoing and changes often | Priorities evolve through your backlog |
| Scoped project | Requirements and deliverables are clear | Changes are estimated before they affect the plan |
| Product team | You need all skills to ship a product | Shared roadmap with regular reviews |
| Maintenance | Software is live and needs care | Support plan with agreed priorities |
Process
A practical path from requirements to release.
Each stage ends with something you can review: a scope, a prototype, a working increment or a release.
01
Understand
Discuss your users, business needs, existing systems and delivery constraints.
02
Define
Agree scope, technical approach, responsibilities and a delivery plan.
03
Design and build
Develop in manageable increments with visible progress and review points.
04
Test and release
Validate agreed workflows, resolve release blockers and prepare deployment.
05
Support and improve
Document the handover, review production feedback and plan the next priorities.
Not sure which model fits?
Describe your situation and we will suggest a sensible starting point.