Field notes
A CRM built for everyone is a CRM built for no one
Different teams, one system, forty fields nobody reads. How role-based views, conditional fields and automated admin turn a CRM people tolerate into one they’ll want to use - with HubSpot examples.
A CRM people use is built around each role instead of as one giant form for everybody. Role-based views, conditional fields and automated admin turn forty fields nobody reads into the few each person needs, and HubSpot gives you the tools to do it.
On this page
Most CRMs are built once, for nobody in particular, and then everyone is told to use it. Marketing gets a screen full of sales fields. Sales gets asked for data only success needs. Everyone sees everything, so everyone tunes most of it out.
A CRM built for everyone gets used by no one. More training won’t fix it. You fix it by designing the thing around the people who live in it.
Different teams should see different systems
The same CRM should not look the same to every team. HubSpot lets you decide who sees which objects and which properties - and you should use all of it. Marketing doesn’t need the renewal date. Success doesn’t need the original ad campaign. An SDR staring at forty fields, thirty of which are somebody else’s job, just works slower for it. Build each team a view that shows their objects and their fields and nothing else. The record underneath stays the same; each team gets its own lens on it.
Conditional fields: show it when it matters, not before
A field that’s empty because it isn’t relevant yet is just noise with a label. Half a form greyed out doesn’t look optional. It looks like you forgot something. Conditional, dependent fields fix that: the field appears when the object reaches the stage where it means something, and stays hidden until then. Ask for the closed-lost reason when a deal is lost, not while it’s still open. Ask for the churn reason at renewal, not at onboarding. The person filling it in sees only what this moment needs, and that focus is something you build into the form.
Automate the admin nobody wants to do
CRM data goes stale for a dull reason: people don’t fill it in because they hate it, and they hate it because it feels like paperwork with no payoff to them. So automate the parts you can. Stamp the source, set the lifecycle stage from the trigger that changed it, roll the last-activity date without anyone touching it. Every property a workflow can fill is one a human doesn’t have to dread, and it still lands in the record. That’s what the properties are for: the context every future analysis and every plan is built on. A blank field isn’t harmless either. It leaves a question you can’t answer later.
Handovers need a protocol, not a prayer
The moment a lead becomes a deal, or a deal becomes a customer, is where data goes to die. The SDR knows things the AE never hears, and the AE knows things success never sees. Without a defined handover, what must be filled in and who signs off, each transition drops half the context. So write the protocol. A deal can’t move to the AE until these fields exist. A customer can’t reach success until the handover notes are in. Make it a gate the system enforces. A courtesy note in Slack won’t hold.
None of it works unless everyone uses it the same way
You can design the most thoughtful CRM in the world and it still fails if three people use it three ways. Everyone in the cycle has to share one definition of what a stage means and what “done” looks like, and then commit to working inside it. A predictable system is the only kind you can improve, which is the whole reason to bother agreeing. When everyone works the same way one inconsistency stands out at once, and when everyone works their own way the whole thing looks broken and nothing is fixable.
People only flag what doesn’t make sense once they’re in the system using it, which is the case for making it worth being in. Design it for the person in front of it, take the admin off their hands, and agree on the rules together. Then the data is a by-product of people doing their job rather than a tax on top of it.
Agreeing those rules together, on your live data, with the people who have to live with them, is what a working session is for, not a slide deck about adoption.