You know the stack needs to change. The question is what to change first.
I map what you're running now: every tool, what it costs, who inside the business is responsible for it, and the places two systems do the same job. You get a written recommendation at the end, in the order to do it in.
What the assessment covers.
Three things, and they are inseparable in practice. The software you buy. The platforms that have to talk to each other. The processes sitting on top of both.
Most of what I find isn't a software problem. It's a process shaped by a tool that made sense when it was chosen and doesn't now, which is why an assessment that only inventories licenses tells you what you spend and nothing about why. Replacing a system without changing the process around it reproduces the same problem on a new platform.
The same goes for AI. If you're planning to build something, the assessment answers the questions that usually get skipped: what work it actually takes over, whose job changes when it does, and who owns it once it's live. Sometimes the answer is to build it. Sometimes it's to fix the process first.
I've led custom software, CMS, and CRM implementations from first scope to live, so I know where they stall long before it shows. That is the same judgment applied earlier, before you have committed to a direction.
Sound like what your stack needs? Let's talk it through.
Book a 30-min introWhat you leave with.
-
Stack auditEvery tool you pay for, what it costs, who owns it, and which renewals are coming. Including the ones still renewing after the person who bought them moved on.
-
Process mappingHow work actually moves through those tools, as opposed to how it was designed to. This is where the redundancy shows up.
-
Cost and redundancyThe places two systems do the same job badly, and what consolidating them is worth against what it costs to do.
-
Written roadmapWhat to keep, what to cut, what to replace, and the order to do it in. A document you can act on, take to a board, or hand to whoever runs the work next.
Nothing was failing in one place. The foundation had stopped being supported.
A storage operator ran several consumer brands, each with its own design and UX requirements, on a CMS built on a codebase nobody maintained any more. Day to day that showed up as reliability slipping, availability going with it, and third-party integrations breaking as the vendors on the other end kept changing. The finding was that these were not faults to fix in turn. Every one of them traced back to the same unsupported foundation, and patching them one at a time would have gone on indefinitely.
Two constraints shaped what could be recommended. The live platform had to keep running until a changeover was possible, so nothing could be a switch-off. And the brands had to stay visually distinct while they stopped being separate builds. The recommendation was multiple domains on a single codebase, with the property management systems those sites run on integrated through the API with redundancies rather than one fragile connection each.
Many brands, one codebase What the assessment produced: the architecture, the integration requirements, and an order to do it in that kept the existing platform live throughout. The work it led to has run on since as a retainer.Recognise the situation? Start with a 30-minute call.
Book a 30-min introQuestions I get asked before this one starts.
-
What do I actually get at the end?
A written recommendation: what to keep, what to cut, what to replace, and the order to do it in. It is a document you can act on, take to a board, or hand to whoever runs the work next, not a slide deck of observations.
-
What if the problem turns out not to be the software?
That is the usual finding. Most of what an assessment turns up is not a software problem, it is a process shaped by a tool that made sense when it was chosen and doesn't now.
The recommendation covers the process as well as the tools, because replacing a system without changing the process around it reproduces the same problem on a new platform.
-
Do you write the code, or run the implementation afterwards?
Not the code. The role is steering the team that builds it and answering for whether it ships.
An assessment often leads into running the implementation it recommends, and that is a separate engagement you decide on after you have the recommendation, not something committed to up front.
Question not answered here? Ask it on the call.
Book a 30-min introNot sure an assessment is what you need? Say so on the call.
Thirty minutes, no pitch, no slides. We talk through what's going sideways and whether I'm the right person to help. If I'm not, I'll say so.
Tell me what you're working on. I'll reply within 24–48 hours.
Thanks for reaching out.
I'll respond in 24–48 hours. Looking forward to chatting soon!