Why the third part exists
If there’s no funded route for change, users start working around the system. Workarounds move to spreadsheets. Spreadsheets become the real process. And the platform you paid to build becomes a reporting obligation rather than an operating tool.
Three phases, one contract
Build
Process workshops to map what actually happens
Configuration and customisation
Data migration with reconciliation
User acceptance testing
Go live with rollback plan
Run
Named engineers, not a ticket queue
Defined SLAs for response and resolution
Proactive monitoring and alerting
Monthly health reporting
Change
Funded allocation of engineering days each month
Spent against a prioritised backlog you control
No separate SOW for every small enhancement
Changes tested in staging before production
Governance
Monthly steering call with your project sponsor and ours
One backlog across departments, not separate queues per team
Named engagement lead who knows the system and your business
When BRC is the wrong choice
The process isn't defined yet
If you're still discovering what the workflow should be, you need Forward Deployed Engineering first. BRC assumes a buildable scope exists.
You want to build the capability in house
BRC keeps us in the loop permanently. If the goal is to hand everything to your team within a year, the AI Center of Excellence model is a better fit.
It's a one off project with a hard end date
BRC is designed for systems that need to keep running and evolving. A fixed scope, fixed end project is just a Build phase with no Run or Change.
Common questions
Can we take over the Run phase ourselves later?
Yes. We document everything during Build specifically so handover is possible. We'll run a transition period and stay available for escalation until your team is confident.
Do unused Change days carry forward?
By default, Change days are use or lose within the month. We can agree quarterly pooling if your change volume is lumpy, but we don't carry forward indefinitely because it distorts capacity planning.
Is there a lock in period?
Run and Change renew annually with 90 days' notice to exit. We don't rely on lock in to retain clients; we rely on being useful.
Who owns the system and the data?
You do. Code, configuration, data models, documentation, prompts, all of it is yours from day one. We operate it; we don't own it.
Ready to build something that keeps working?
Talk to us about how Build Run Change applies to your platform.
Book a working session