How we work
Clear scope, the same senior team from first workshop to production, and working software you can see every two weeks. Here is what that looks like in practice.
Three ways to work together
Most clients start with a project and stay on a retainer. Pick what fits where you are.
Fixed-scope project
- Best for
- A defined problem with a clear finish line.
- How it works
- We run a short discovery, agree scope and price per phase, and deliver against it. Changes go through a simple, written change process.
- Includes
- Discovery and written scope
- Design, build and launch
- 30 days of warranty support
- Pricing
- Fixed price per phase
Dedicated team
- Best for
- Ongoing product work or extending your own team.
- How it works
- Senior engineers who work as part of your team, in your tools and rituals, with a lead who owns technical quality.
- Includes
- One to five senior engineers
- A technical lead on our side
- Flexible scope, monthly planning
- Pricing
- Monthly, per engineer
Support and retainer
- Best for
- Systems in production that need care and steady improvement.
- How it works
- A monthly block of hours for fixes, changes and small features, with agreed response times and a shared backlog.
- Includes
- Agreed response times
- Monitoring and updates
- Monthly report and review
- Pricing
- Monthly retainer
The process
The route is the same for a four-week automation and a year-long platform. Only the scale of each stage changes.
- 01
Discover
Workshops with the people who do the work. We map processes, systems, data and constraints, and agree what success looks like.
You get
Written scope, risks, architecture sketch and a price per phase
- 02
Design
Data model, architecture and interface, designed together and reviewed with you. Clickable prototypes for anything users will touch.
You get
Approved designs, technical design and a release plan
- 03
Build
Two-week iterations, each ending with a demo of working software in a staging environment you can use yourself.
You get
Tested, documented releases every two weeks
- 04
Run
We launch, monitor and improve. Either we keep running it under a support agreement, or we hand over to your team with documentation and training.
You get
Production system, runbook and a support plan
How we keep it on track
Three habits that make a project predictable, whichever model you pick.
Communication
- LeadOne technical lead who is your main contact and writes code on the project
- ChannelA shared channel in Teams or Slack, with response times agreed up front
- CadenceA demo every two weeks and a short written update every week
- RecordDecisions recorded in writing, so nothing depends on memory
Quality
- ReviewCode review on every change, by a second senior engineer
- TestsAutomated tests and CI pipelines from the first week
- EnvironmentsSeparate development, test and production environments
- DeliveryPower Platform work delivered as managed solutions through pipelines
Security
- AccessLeast-privilege access, granted per project and removed at the end
- SecretsSecrets kept in a key vault, never in code or chat
- DataYour data stays in your tenant whenever the platform allows it
- LegalNDA as standard, and personal data handled under GDPR
Not sure which model fits?
Describe the problem and your constraints. We will suggest a model and a first step, with no obligation.