/ Modernization
Old systems, made modern. Without stopping the business.
For US and North American businesses: we break monoliths apart a slice at a time, turn manual processes into automated workflows, and add AI where it genuinely pays. Salesforce included.
Legacy monolith
still running · fenced by tests
Modern services
one slice at a time · automated · AI where it pays
The business outgrew the system years ago.
The system nobody wants to touch.
One codebase, ten years of decisions, and the two people who understood it have left. Every change is a risk, so changes stop.
The process lives in people's heads.
Spreadsheets, inboxes and a checklist someone keeps on their desktop. It works until that person is on leave.
The CRM grew by accident.
A Salesforce org shaped by every team that ever needed a field. Automations firing other automations, and nobody sure what breaks if one is switched off.
Six steps, and the old system runs the whole time.
- 01
Map
Read the code and the process and write down what the system actually does: roles, states, rules, integrations. Before anyone changes anything.
- 02
Fence
Put tests around today's behaviour, warts included. Now a change that breaks something is caught by a build, not a customer.
- 03
Slice
Carve out one capability at a time behind a clean seam, the strangler fig way. The old system keeps running while the new one grows around it.
- 04
Automate
Turn the manual steps into workflows: approvals, hand-offs, reminders, reports. People stop being the integration layer.
- 05
Add AI
Only where it pays: reading documents, drafting replies, classifying requests. Behind guardrails, with a person on anything that matters.
- 06
Flow
Ship a slice to production every few weeks, measure flow time, and let the next slice be decided by what the last one taught us.
Code, CRM, process and apps.
Monoliths
Any stack. Split by business capability, not by technical layer, so each slice is something a user notices.
Salesforce
Untangle automations, retire custom code that a standard feature now does, and put tests around the flows that move money.
Spreadsheet and inbox processes
The work that runs on email and shared sheets becomes a workflow with an owner, a state and an audit trail.
Mobile apps
Apps inherited from another vendor, stabilised first, then rebuilt screen by screen on a modern stack.
Four rules we hold ourselves to.
“No big-bang rewrites.”
“Tests before touching.”
“Keep the lights on.”
“Working software every few weeks.”
Show us the system everyone is afraid of.
We will map what it does, tell you where the first slice should be, and what it would take to have it live in a few weeks.