Representative work story
The CRM Mostly Worked. That Was the Problem.
Making a fragile setup visible, understandable, and safe to change
A representative CRM story: the portal looked fine until the team needed to trust a report, change a workflow, or explain who owned the data.
It looked reasonable from the dashboard
The pipeline stages had names. Reports loaded. Workflows were active. Nobody could point to one dramatic failure.
Then someone asked why marketing and sales had different lead numbers.
One report used lifecycle stage. Another used a custom status field. A workflow updated both, except when a contact entered through an older form. That form was still connected to a sequence nobody remembered creating.
The portal mostly worked. Which is exactly why it had been left alone for so long.
The systems nobody wants to touch are often the ones carrying the most business risk.
The CRM was only part of the picture
I did not start by cleaning properties.
I started with the way a lead moved through the company. Where did the data begin? When did sales take over? Which fields actually changed a decision? Which reports did people trust, and which ones did they quietly rebuild in a spreadsheet?
That map made the technical problems easier to see. It also exposed the ownership gaps behind them.
Several fields existed because different teams had solved the same question separately. Workflows contradicted each other because nobody owned the whole journey. Reporting was inconsistent because the underlying definitions had never been agreed.
Rebuild the logic, not just the portal
We agreed the data model first: the stages that mattered, the fields that had one clear purpose, and the points where ownership changed.
Then I worked through the highest-risk automations. Duplicate logic came out. Old paths were retired. The remaining workflows were rebuilt around the agreed model and documented in language the team could understand.
I kept the changes incremental. One part live and tested before moving to the next.
There is nothing impressive about replacing one confusing system with a newer confusing system.
What changed
The team could finally answer simple questions without a portal archaeology project.
They knew which number to use, who owned each part of the flow, and what would happen when a field changed. New work became safer because the system had a visible shape and decisions behind it.
The CRM was still a tool. It was no longer a mystery.
If your setup mostly works but nobody trusts it, send me the symptoms.
Parts of the work