Engagement models
Three ways to work with us. Every model comes with the same delivery standards: weekly demos, code you own, and a named lead accountable for the result.
Fixed-scope project
- Best for A defined first release, a prototype, an integration or a migration.
- How it works Scope is agreed in discovery and delivered in milestones, each with a demo and sign-off.
- Team An engineering lead plus the designers and engineers the scope needs.
- Billing Fixed fee per milestone.
Dedicated team
- Best for Ongoing product development, or a roadmap you expect to change.
- How it works A stable team works in two-week cycles against priorities set with your product owner.
- Team An engineering lead, engineers and a designer as needed; scale up or down with notice.
- Billing Monthly, per team member.
Ongoing partnership
- Best for Software in production that needs care, security updates and steady improvement.
- How it works A monthly plan covering monitoring, maintenance and a block of improvement time.
- Team A named lead who knows your system, backed by engineers who can step in.
- Billing Monthly plan.
How every engagement is governed
- Weekly demo Working software every week, not slides or status reports.
- Two-week planning Priorities agreed with your product owner at the start of each cycle.
- Monthly review Progress, risks, budget and the next quarter, with your leadership.
- Direct access A shared channel with the people doing the work, not an account manager.
- Written decisions Architecture and scope decisions recorded where your team can find them.
- Clean handover Documentation and access you can take in-house at any point.
Delivery standards
The same on every project, whatever the model.
- Code review on every change
- Automated tests and continuous integration
- Separate development, staging and production environments
- Security review before every launch
- Accessibility to WCAG 2.2 AA for user interfaces
- Infrastructure defined as code where it fits