Three ways to work with us. Scope drives price, so every format is quoted rather than listed.

What it includes

• Interviews with the people who actually run the process
• A written map of the current workflow, including its undocumented rules
• Technical review of the systems and data involved
• A proposed solution with architecture and trade-offs stated
• A scoped, costed delivery plan and a sequencing recommendation
• Everything produced is yours, whether or not you continue with us

Best suited to

• A problem that is felt clearly but not yet defined
• A decision that needs a costed plan before budget can be approved
• Teams comparing build, buy and do-nothing honestly
• Anyone burned before by a fixed quote against an undefined scope

Typical shape

A few weeks, a small senior team, ending in a written plan and a working session — not a slide deck.

What it includes

• Design system and interface design, or extension of your existing one
• Implementation with tests, code review and CI
• Integration with your existing systems
• Accessibility and performance targets agreed as numbers and verified
• Deployment, monitoring, backups and a documented rollback
• Handover documentation and a walkthrough with your team

Best suited to

• A defined scope, whether from our Discovery or from your own work
• A new site, product, portal or automated workflow
• Replacing something that exists and can no longer be maintained
• Teams who want a single accountable delivery partner

Typical shape

Short iterations against a live deployment you can use throughout, with a fixed scope and a written change process rather than a fixed price against a moving target.

What it includes

• Reserved delivery capacity each cycle, planned with you
• Feature development against an agreed roadmap
• Dependency updates, security patching and technical maintenance
• Monitoring, incident response and an agreed escalation path
• Regular review of performance, accessibility and cost
• For AI systems: evaluation runs and quality monitoring over time

Best suited to

• A live system that needs to keep evolving
• AI systems, which require ongoing evaluation rather than one-off delivery
• Teams without in-house capacity for a whole technical surface
• Organisations who want a partner rather than a series of projects

Typical shape

A recurring cycle with reserved capacity, a shared backlog you prioritise, and no lock-in — everything stays in your accounts, so leaving is a decision rather than a migration.