Stop customising your CRM before you've used it
Every CRM rollout has the same arc. Week one: excitement. Week two: customisation. Week three: the customisations start contradicting each other. Week six: nobody can remember why there’s a custom field called “Sector (OLD) 2”.
I’ve watched businesses spend their first month with GoHighLevel building a bespoke replica of a sales process they never actually followed — instead of running the boring default-ish version for a fortnight and learning where it genuinely pinches.
Customisation feels like progress
It isn’t, not yet. Custom fields and renamed stages are guesses about what you’ll need to know. Until real leads have flowed through, you don’t know which questions matter — you know which questions you think matter, based on a process that existed mostly in people’s heads.
The moves that pay off in month one:
- Run the default pipeline with minimal edits. Rename stages to your customer states, sure. Don’t build seven pipelines and forty custom fields on day one.
- Log what you wish you knew. When someone says “we should track that”, write it on a list instead of creating a custom field. Most of the list dies within a fortnight, which is the point — the surviving items are real needs.
- Automate the boring bits first: instant reply, appointment reminders, review requests. These need no bespoke design and pay for the platform immediately.
The tell that you’re over-customising
You’re three custom fields deep on “lead source subcategory” and your team is still asking new customers “sorry, who am I speaking to?” in the second email. If the basics aren’t automatic, the bespoke layer is decoration on an unfinished house.
Another tell: two fields that mean the same thing. “Estimated value” and “Est. job value” both exist, populated by different workflows, and the sales report uses one of them while the owner reads the other. That’s how dashboards lie.
When to customise
After roughly a month of real usage, customise from evidence:
- The list of “things we wish we knew” that survived → custom fields.
- The stages contacts actually pile up in → that’s where a follow-up workflow is missing.
- The questions the team asks every call → make them form fields so they’re captured at source, not transcribed later.
Customise from the shape of your real pipeline, not the shape of your imagined one. The CRM will tell you what it needs — you just have to use it plainly for a few weeks first.
Boring first. Bespoke later. Every time.