Your CRM has all the data. Does it tell your team what to do next?
Three questions a CRM should answer the moment you open it:
Who needs attention today?
What is holding an active deal back?
What should happen next?
If answering any of them means opening the inbox, a spreadsheet or a chat thread, the problem usually isn’t the CRM. It’s the workflow around it.
A well-designed setup quietly handles the background work: new leads get assigned, follow-ups are created, replies and meetings show up in the record, stale opportunities are surfaced, and deal stages move when real business events happen.
On three of my projects, that meant:
A hire company’s enquiry-to-invoice funnel across Pipedrive, PandaDoc and Xero, with the pipeline updating itself.
A move from ActiveCampaign to GoHighLevel, with contracts sent natively and a contract tool retired.
GoHighLevel conversation summaries saved to CRM Notes, so nobody re-reads a whole history before a follow-up.
A ten-minute test: for one day, have your team note every time they leave the CRM to find out what to do next. The lookups that repeat most are your first automations.
I build CRM and workflow automations for service businesses. Message me where your team leaves the CRM and I’ll tell you where I’d look first.
Where does your team leave the CRM to find out what to do next?
Some designers are waiting for flashy visuals to shine in their portfolio, but keep forgetting that the process is far more important.
Recently, I had a good opportunity
To focus on what matters for a client
The process.
The thing they can't find even with AI.
What AI can’t give a founder ↓
↳ Context: it hasn’t heard their last three customer calls
↳ A decision trail: why this positioning, and who signed off
↳ Consistency: the deck, the site and the outbound each get a different prompt, so each tells a different story
↳ One final version: nobody is sure which file is the real one
Most AI-built brands don’t fail on speed or creativity.
They fail on the structure around the output.
So I built that structure before the project starts.
Every client gets a private portal on day one ↓
→ A Loom walkthrough from me
→ About 20 onboarding questions on their business and customers
→ A brief drafted from their answers: AI drafts, they approve, then it locks
→ One page per phase, with its own comments
→ 3 revision rounds on the logo and the landing page
→ Start and end dates they can see
The point?
Visuals get you noticed.
Process gets you hired.
What does your portfolio show: the final visuals, or how you got there?
I'd split it by the lost reason instead of one timer. Price objections get a check-in at 30 days, timing objections get one on the date they mentioned, and everything else waits 90. Tagging the reason when the deal is marked Lost makes that easy to branch in GoHighLevel, and the follow-up feels personal instead of automated.