A CRM that works is built around the handful of decisions your team makes every day. Those decisions are which lead to call, which deal is stalling and which customer needs attention. Design it in this order: map the customer journey, then define the pipeline stages and what moves a deal from one to the next. Keep required fields to the few that drive a report. Automate the handoffs, lock down access by role, and roll it out to a small group before everyone. Most CRMs fail because nobody uses them, not because a feature is missing. If entering data takes longer than the rep’s old spreadsheet, the data stops coming in and every dashboard built on it is wrong.

What should you design before choosing software?

Start with the journey, not the vendor. On paper, list every stage a customer passes through, from first inquiry to repeat business. For each stage, write down who owns it and what event moves the customer to the next one. “Proposal sent” is a stage. “Warm” is not, because two people will never agree on what it means.

Our own pipeline as a production company has seven stages: inquiry, discovery call, treatment/proposal, contract signed, pre-production, delivery, follow-up for the next project. Every exit criterion is something you can check: a call that happened, a PDF that was sent, a signature that came back. This step usually takes one or two working sessions, and skipping it is how teams end up with 40 custom fields and no usable forecast.

How many fields and stages should a CRM have?

As few as your reports actually need. A useful test: if no report, automation or routing rule reads a field, delete it. Each required field adds a few seconds to every entry. Multiply that by every record a rep touches in a week and it decides whether people keep using the system.

• Pipeline stages: 5–8 for most B2B sales cycles. With more than that, reps skip stages and your conversion numbers turn into fiction.
• Required fields at creation: name, contact method, source, owner. Ask for everything else when it becomes relevant, such as budget at the proposal stage.
• Picklists over free text wherever you plan to filter or report. “Referral”, “referal” and “Referral – Dan” end up as three separate sources.

What makes a CRM interface usable?

The same principles as any software interface. The Nielsen Norman Group’s ten usability heuristics work well as a review checklist. Two matter most in a CRM: recognition rather than recall (show the deal’s next step on the record, don’t make reps remember it) and error prevention (catch duplicate contacts when they’re entered, not afterward).

Build each role’s default view around its one main job. Sales sees “my open deals by next activity date.” Account managers see “clients with no contact in 60 days.” Leadership sees forecast against target. If your team includes anyone using screen readers or keyboard-only navigation, check custom layouts and embedded forms against WCAG 2.2. Custom-built CRM front ends often fail on contrast and focus order.

What should you automate first?

Automate handoffs and reminders before you automate anything a customer will see. Start with the jobs that are low-risk and pay off quickly:

• Assign new inquiries to an owner automatically, by region, service line or round-robin.
• Create a follow-up task when a deal sits in a stage longer than your normal cycle.
• Hand over to delivery when a deal closes. For us, a signed contract creates the project record and alerts the producer.

Customer-facing sequences like drip emails and nurture campaigns come later, and the rules for them have tightened. Since February 2024, Gmail and Yahoo require bulk senders to authenticate their domain and offer one-click unsubscribe. Google’s requirements are in its email sender guidelines. In the US, commercial email must also meet the FTC’s CAN-SPAM requirements. An automated sequence that ignores these rules ends up in spam and drags down delivery for your one-to-one email from the same domain.

What security and compliance does a CRM need?

Your CRM is probably the largest store of personal data your company holds, so configure it with that in mind:

• Role-based access: reps see their own accounts, and exports are limited to admins. Bulk export is the most common way customer data leaves a company.
• Multi-factor authentication for every user, with no exceptions for executives.
• Audit logs switched on and actually reviewed, at minimum after anyone leaves the company.
• Retention rules that delete or anonymise dead leads after a set period.

Which regulations apply depends on who your customers are and where they live. If you hold data on people in the EU, the GDPR requires a lawful basis for processing and the ability to honour access and erasure requests. California residents have similar rights under the CCPA/CPRA. HIPAA applies only if you are a covered entity or business associate handling protected health information. Most marketing CRMs aren’t, and those that are need a signed business associate agreement with the vendor. For a framework that isn’t tied to one law, the NIST Privacy Framework is free and practical.

A breach costs real money. IBM’s Cost of a Data Breach report put the global average at $4.45 million in 2023 and $4.88 million in 2024, with US figures far higher. Use the current edition rather than older numbers, which still get quoted.

What goes wrong in practice?

These are the failures we see most, in our own system and in clients’ systems that we connect video and campaign tracking to:

• Over-customisation in month one. Teams build for every edge case before they’ve seen the real data. Run the standard setup for 60–90 days, then customise based on what’s actually breaking.
• Lost lead sources. Web forms without UTM parameters dump everything into “direct”, so you can’t tell whether a video campaign produced pipeline. Fix this before you launch.
• Duplicate records from importing several old spreadsheets. Clean the data before migration. Expect it to take longer than the CRM setup itself.
• No owner. A CRM without a named admin who has a few hours a week for it falls apart within a year.

What does it cost and how long does it take?

Cost depends far more on setup and migration than on licence fees. Per-seat prices from HubSpot, Salesforce, Zoho and Microsoft Dynamics 365 run from roughly $15–25 per user per month on entry tiers to over $100 on tiers with advanced automation and forecasting. Pricing changes often, so check the vendor’s current page. A small team on a standard setup can be running in two to six weeks. A custom build with integrations to accounting, project management and marketing tools usually takes three to six months. The size and quality of your existing data is the biggest variable in both cost and timeline.

What has changed in CRM recently?

Some claims about CRM that still circulate are out of date:

• “$8.71 ROI per dollar” comes from a 2014 Nucleus Research study. It’s over a decade old and was produced before current pricing and AI features existed. Measure your own return in pipeline velocity and win rate instead.
• AI is now built in, not an add-on. Salesforce (Agentforce), HubSpot (Breeze) and Microsoft (Copilot in Dynamics 365) all ship tools that summarise records, draft emails and score leads. They only work if the underlying data is clean, which brings you back to field and stage design.
• Email automation now operates under stricter deliverability rules (see the sender requirements above) than when most drip-campaign advice was written.

Next step: before you look at vendors, spend an hour writing down your stages, their exit criteria and the five reports leadership actually reads. Then delete every planned field that doesn’t feed one of those reports. That short document is your CRM spec.