Most software programmes miss the business case on process, data and people - not the technology.
Outputs follow inputs. So we manage the things that actually decide whether yours lands. We select the right system without bias, then deliver it ourselves or govern the integrator who does - your choice - and we leave you able to run it yourselves. Across ERP, CRM, HRIS, ITSM, EAM and AI, through Select, Implement and Realise.
Whatever stack you’re choosing, the method is the same.
We work across three overlapping markets. The vendor list is different in each. The discipline isn’t - your processes, your data, your people, your decisions.
On your side of the table. Every meeting.
Who pays us, and who else? You do, and nobody else - no vendor commission, no preferred-partner kickbacks. That keeps the recommendation unbiased. We then deliver it ourselves or govern someone who does, and we hand it over so you run it, not us.
We are…
- Vendor-independent, not delivery-independent. No vendor commission, no platform ties - independent in whose software we recommend, not in whether we build. We can, and do, deliver.
- Your selector and your delivery team - your choice. We select the right system without bias, then implement it ourselves, build what it needs, or govern the integrator who delivers it.
- The defender of your signed-off design. When a vendor says 'it can't do that' or 'do it our way', we hold the blueprint you approved.
- Built to hand over. We transfer the skills and the toolset and leave you able to run your system and your next project - the ongoing relationship is the toolset, not a retainer.
We are not…
- Not paid commission by any vendor, and not locked to one platform.
- Not your software's operator. We deliver or govern the implementation and hand it over; we don't run your ERP, CRM or agents for you.
- Not an open-ended managed service or body-shop retainer. We engineer the exit from week one.
- Not delivery-independent. We can and do build, so we'll never pretend we don't touch the delivery.
Select. Implement. Realise.
Three phases for ERP, CRM, HRIS, ITSM and EAM. Four for AI - Select, Pilot, Productionise, Operate. The same disciplined arc from the day you start scoping to the day you can run it without us.
Select
Outcome · OptimiseAs-is and to-be Operating Blueprints, business case, vendor long-list, ITT, demo scripts, contract negotiation. The vendor you sign is the one scored against your target operating model, not the one with the best demo.
Implement
Outcome · BuildDesign challenge against the blueprint you signed off, data readiness, test and go-live assurance - whether we build it ourselves or govern the integrator who does. Either way we’re accountable for your business case, not the vendor’s cutover plan.
Realise
Outcome · InnovateValue realisation, adoption recovery, process maturity, second-wave automation. We finish the job by handing your operating model back to you, running.
One approach, sized to your programme.
Not three different products - the same method, scaled to what you need. Start with a free self-check, take a one-day read, or run the whole programme. Either way you keep the toolset and can run your next project yourselves.
Start small, or self-serve
Smaller or simpler programmes run light: the readiness read, the requirements that matter, a single gated build, and the exit. You can even run the free self-check yourself.
Run the whole programme
Large, complex or regulated work gets the full method: the deep situation read, gated delivery, and continuous value tracking from contract through to handover.
Platform already chosen?
If your system is already mandated, we skip the selection and put the work into getting it implemented right - the operating model, the readiness, and the delivery.
Three phases above the waterline. Five inputs underneath.
The phases are what the board reviews. The inputs are what determines whether the phases land. Most programmes track the first, and discover - usually around month nine - that they had the second backwards.
The five things that decide whether it works.
Most programmes track outputs and hope. We read the five things underneath that actually decide the result. Get those right and the outputs follow; get them wrong and no amount of programme management saves the date.
Every recommendation we put in front of you ladders back to one of these five answers. No abstract maturity scores. No 47-page assessments. One page; five inputs; named owners; clear next actions.
On day one of the readiness read you leave with your filled-in scorecard, a single accountable owner for each of the five, and the handful of actions that have to land before any vendor conversation is worth your time.
Process Design Fitness
Will your busiest processes run on the standard software - and where they won’t, is that a real advantage worth paying to keep?
Master-Data Ownership
Who owns the master record after go-live, and is it clean enough to run on?
Role Clarity
Does every step have one accountable owner today? A new system exposes ambiguity, it doesn’t fix it.
Decision Authority
For anything a rule or an AI agent will act on: with what oversight, audit and rollback does it get to act?
People Readiness
Can your people own the new way of working - and sustain it after we leave?
Four practices most advisors don’t carry.
Three of these apply to every software programme you’ll run. The fourth is what makes AI safe to actually ship.
The readiness scorecard
Process Design Fitness, Master-Data Ownership, Role Clarity, Decision Authority and People Readiness. One page that tells you, and your board, what’s actually ready and what isn’t.
The documented exit
Every artefact lives in your wiki, in your naming, from day one. The exit is written into the engagement letter as a milestone - with a target date you sign off.
A live value dashboard
From contract signature through to M+36, every line of the business case is tracked monthly: target, actual, owner, action. It’s software, not slides.
Clear authority for AI agents
For your AI and agents: a clear line for every step - human-decided, human-approved, agent-with-an-audit-trail, or fully autonomous. The boundary that keeps an agent useful instead of frightening.
Every method we run is engineered to end.
Most advisors design to stay - the next phase is always the natural extension of this one. We design to taper. Co-chaired governance becomes your governance, the seat at the head of the table empties, and the date it empties on is in the engagement letter from week one.
Twelve months to handover. The exit is the deliverable.
Most advisors commit to “complement your team and deliver results.” That’s an invitation to stay. We commit to leave. The taper from co-chaired governance to your team chairing the room is in the engagement letter from week one.
“You should not need us. If you want a second set of eyes in twelve months, ask then.”
We can implement it - so we prove the choice was unbiased.
Because we can also deliver, we have a stake in the answer. So we don’t ask you to take our independence on trust - we build it into how the selection works, and leave you the evidence.
No vendor commission, any platform
We take no payment from any software vendor and we’re tied to no product. The recommendation isn’t bought, so it can be honest.
The assumptions are on the record
The handful of design choices that could tilt the field toward one kind of system are written down, with the alternative - so you can see them and challenge them.
You sign off the scoring first
The weights that decide which system wins are locked and signed by you before any vendor is rated. No moving the goalposts to fit a favourite.
Start where you are.
A free self-check, a one-day read, or the full programme from there. Each step earns the next - and we’ll tell you, in writing, if we don’t think you should continue with us.
The readiness self-check
Answer a short set of questions and get your first read on the five inputs - where you’re likely ready, and where you’re not. The lowest-risk way to start, and yours to keep.
Start the free self-checkThe readiness read
We come to you and fill the five inputs with real evidence: a board-ready findings pack, and the handful of actions that have to land before vendor selection is worth starting.
Request a readThe readiness roadmap
Not ready isn’t a no. It’s a costed plan to get ready - what to fix, in what order, to what bar, and what it costs - run it with us or on your own.
Get the roadmapChoose the right system without bias - the operating model, the value case, and the requirements that decide it.
We build it ourselves or govern the integrator who does, defending the design you signed off through to go-live.
Bank the value on a live dashboard, transfer the skills and the toolset, and hand over.
Turn on assistants like Copilot with the guardrails: what they can see, acceptable use, light monitoring. No autonomous agents.
Already mature? Licence the toolset and run your own programmes with it.
Our walk-away rule. If the five inputs aren’t in evidence by week 6, we’ll recommend you pause - not push on. We’d rather lose the engagement than watch you spend money against a business case that won’t earn.
Four ways to run the programme. We’re option four.
Your realistic alternatives reduce to four. We name them honestly - including the three that aren’t us - and then tell you why option four exists.
Run it with your own team
You know your business better than anyone. But the team that runs the day-job can’t also run the programme, and the programme is the day-job for the next 18 months.
Hire a freelance advisor
Cheap and fast to start. Single point of failure when it counts. No team to escalate to when the SI pushes back on the design challenge at month nine.
Use the vendor or SI’s consulting arm
Convenient on paper. Structurally conflicted in practice - they don’t get paid to recommend a different vendor, or to tell you to slow down.
APTIM·Bridge
Independent in the selection, and able to deliver: we lead the programme from your side of the table, build it ourselves or govern the integrator who does, and hand it over on the date you signed. Accountable for your business case, not the vendor’s cutover plan.
A bridge was first a beam.
In Old English brycg meant a plank or log laid across water - the word for the thing predates the engineering by a thousand years. Cognate with German Brücke and Dutch brug; descended, eventually, from a Proto-Germanic word for a wooden beam. Four more places that small word has turned up over the centuries, and one of them you almost certainly didn't know.
The Pope is, literally, a bridge-builder.
Rome's high priest carried the title Pontifex - pons (bridge) plus facere (to make). Crossing a river was civic and sacred work; the man who built or blessed the crossing held the office. The same word survives, two thousand years later, as Pontiff.
Bryggja meant the landing, not the span.
In Old Norse, the cognate referred to a quayside or jetty - the place you stepped off, not the crossing itself. Bergen's medieval waterfront is still called Bryggen, and English surnames like Briggs and Bridges come from the same root: not bridge-builders, but the people who lived where you landed.
Euclid's fifth proposition is the bridge of asses.
Pons asinorum - the bridge of asses - is the medieval name for the proof in Euclid that an isosceles triangle has equal base angles. It is the first proposition where lazy students get stuck and refuse to cross. The phrase has stood in, ever since, for the test a serious practitioner has to pass before the harder work begins.
Bridging a gap is younger than the steel suspension cable.
The verbal sense - to bridge a difference, to bridge a divide - only enters business English in the 1880s, contemporaneous with John Roebling's wire-cable suspension method and the opening of the Brooklyn Bridge. The metaphor follows the engineering, not the other way round.
APTIM·Bridge takes the older meaning literally. We are the beam laid between two states - the one where you have a tactical problem identified but no proven way across, and the one where the right solution is implemented and the business case has earned out. That crossing begins before any software is bought: we hold it from framing the problem and choosing the right answer, through the implementation that makes the value real. Then we lift the beam.
Thirty minutes. No software. No sales. A real conversation about your programme.
If the conversation is useful, we’ll tell you what a Readiness Read would look like for you. If it isn’t, you’ve spent thirty minutes thinking out loud with someone who’s done this before. Either way you owe us nothing.
