A familiar situation
The Setup Mostly Works
Which is exactly why nobody wants to touch it.
A CRM or marketing setup can keep running while workarounds, unclear ownership, and fragile workflows make every useful change feel risky.
Nothing is broken enough
Leads still arrive. Emails still send. Reports still load. The CRM has not fallen over.
But a former employee still owns an important workflow. Sales uses one field while marketing reports from another. A spreadsheet quietly fixes the gaps between the website and the CRM. Nobody can explain the whole setup without pulling three people into a call.
It mostly works. That is what makes it hard.
A system can be live and still make the work harder every week.
When something is completely broken, fixing it becomes a priority. A fragile setup survives because the team has learned how to work around it. Every workaround makes the next change feel riskier.
The tool is only part of the picture
This often shows up in HubSpot, Salesforce, or another CRM, but the tool is rarely the whole problem.
The setup also includes the website forms, ad platforms, reporting, lifecycle definitions, sales handovers, data imports, and the decisions people make outside the system. A workflow can be configured correctly and still produce the wrong result because two teams mean different things by “qualified lead.”
That is why starting with a cleanup list can miss the point. Deleting properties and rebuilding workflows makes the portal look tidier. It does not fix unclear ownership or conflicting definitions.
What discovery makes visible
I start by following a few important flows end to end. How does a new enquiry enter the system? What decides where it goes? Which fields drive the reports? Where does a person step in because the automation cannot be trusted?
From there we map:
- The systems and data involved
- The workflows and manual handovers between them
- The definitions people rely on
- The workarounds holding the setup together
- The owners and decisions behind the system
The goal is not a catalogue of every setting. It is a shared picture of what matters, what is fragile, and what should change first.
I use agents to compare exports, trace workflow logic, check where definitions disagree, and keep the map current while we learn. They make the investigation faster. They do not decide what a lifecycle stage should mean for the business.
Then we decide how much change the setup needs
Sometimes the right answer is a small, focused repair. Sometimes the architecture needs rebuilding. Sometimes the tool is fine and the real work sits in the team around it.
A focused discovery can give you that diagnosis, the priorities, and a plan your team can take forward.
If the work already has a clear shape, or the next phase needs someone inside the flow to rebuild workflows, clean data, connect systems, document decisions, and help the team operate the new setup, I can join embedded.
No automatic rebuild. No tool-first answer. Send me the setup nobody wants to touch.