The North · Sales Knowledge Center

Automation and Systems

CRM Setup

CRM stands for Customer Relationship Management. A CRM keeps track of every person or company a business has ever contacted, is talking to, or has sold to.

$25k$80k6 to 10 weeks
Plain English

CRM stands for Customer Relationship Management. It's the system where a company tracks every prospect and customer , their contact info, what conversations have happened, where they are in the sales process, and what needs to happen next. Most companies either don't have one, have one that's a mess, or have one that nobody uses. We either build it from scratch or clean up what they have , and configure it around how their team actually sells, not how a software company thinks they should sell.

What it is

CRM stands for Customer Relationship Management. A CRM is a piece of software that keeps track of every person or company that a business has ever contacted, is currently talking to, or has sold to. It stores their contact information, records every email, phone call, and meeting that has happened with them, and shows where they are in the process of becoming a customer. Think about how a business works without a CRM. Leads come in through a website contact form and the details get emailed to someone. That person copies the information into a spreadsheet. The spreadsheet gets passed around via email. Two salespeople accidentally reach out to the same prospect on the same day. A hot lead does not get followed up because the salesperson forgot it was in the spreadsheet. The CEO asks how much revenue the company expects next month and nobody can give a confident answer. A CRM solves all of this. Every lead is captured automatically. Every interaction is logged. Every deal has a stage showing exactly how close it is to closing. The CEO can see the full pipeline at any moment. Salespeople know exactly who to follow up with and when. Nothing falls through the cracks.

What problems it solves

The most common CRM problems we see are: the company has no CRM and is running sales out of email and spreadsheets, the company has a CRM but nobody uses it because it was not set up in a way that matches how the team actually sells, the company has a CRM but the data in it is unreliable because entries are incomplete or inconsistent, or the CRM exists but is not connected to anything else, so leads still have to be manually entered and reports still have to be manually compiled.

What we deliver

HubSpot setup and implementation

HubSpot is one of the most popular CRM platforms in the world. It is particularly well-suited for small and mid-sized businesses and for companies with marketing teams, because it combines the CRM with marketing tools, email, and reporting in one platform. We implement HubSpot by configuring the pipeline stages to match the company's actual sales process, setting up contact properties to capture the right information, building automated workflows for lead routing and follow-up, connecting it to the website and other tools, and training the team on how to use it.

Salesforce setup and implementation

Salesforce is the most widely used CRM for larger companies and enterprise organizations. It is more powerful and more customizable than most other CRMs, but also more complex to implement correctly. We implement Salesforce by designing a data model that matches the business's structure, building the workflows and automations the team needs, connecting it to other systems in the stack, and ensuring the configuration is maintainable and documented so it does not become a black box that only one person understands.

GoHighLevel build and setup

GoHighLevel is a CRM platform that is particularly popular with marketing agencies, coaches, consultants, and service businesses. It combines CRM functionality with email, SMS, phone, booking calendars, pipeline management, and website hosting in one platform. We build and configure GoHighLevel systems for clients who want to consolidate many tools into one platform.

CRM migration and data transfer

A migration is the process of moving data from one CRM to another. Companies do this when they outgrow their current platform, when they are consolidating tools, or when their current CRM has become so messy that starting fresh on a new platform makes more sense than cleaning up the old one. Migrations are technically complex and carry significant risk if not done carefully, because improperly migrated data can corrupt records and cause problems that take months to untangle.

When not to recommend this

A company with no defined sales process is a bad fit for CRM implementation. A CRM structures and tracks a sales process. If the process does not exist yet, the CRM will just reflect the chaos more visibly. The sales process needs to be defined first, even if it is simple.

Operator brief

Generate a dense, AI-written operator playbook for this service: executive overview, business problems solved, technical foundations, stakeholder positioning, sequencing, delivery reality, financial logic, objection matrix, failure modes, AI coach notes.

Problem solved

Their CRM exists but no one trusts the data in it. Their sales team doesn't use the CRM — deals live in spreadsheets and email. They can't forecast revenue because their pipeline is inaccurate. They have attribution data but nowhere clean to send it. They're scaling headcount and need a system that scales with them.

Business outcome

A trusted single source of truth that the sales team actually uses, leadership can forecast from, and downstream systems (attribution, lifecycle) can rely on.

Best fit

Companies with a defined sales process, a named internal CRM owner, and budget for both setup and ongoing adoption support.

Triggers
  • Hiring sales leadership
  • Adopting attribution
  • Lifecycle automation planned
  • Forecast inaccuracy
  • Multiple disconnected sources of truth
Bad-fit conditions
  • No defined sales process — you can't systematize chaos
  • The person who will own the CRM post-implementation doesn't exist yet
  • Pre-product-market-fit — process will change monthly
  • Budget covers setup but not ongoing support — adoption will decay
  • We just need somewhere to store contacts — that's a spreadsheet problem, not a CRM problem
Dependency warnings
  • Do not recommend before sales process is defined or in scope
  • Do not migrate if data hygiene is unsalvageable — start clean instead
Discovery questions
  • What CRM are you using today? How much of your team actually uses it consistently?
  • If I asked your best salesperson to show me your pipeline right now, would it be accurate?
  • How do leads currently get into your CRM? Is it manual entry or automated?
  • Can you forecast next quarter's revenue from your current system? What's your confidence level?
  • What does a deal look like from first contact to closed — every stage, every handoff?
  • Who currently owns your CRM? Is there someone whose job it is to maintain it?
Qualification criteria
  • Executive sponsor
  • Internal admin or willingness to hire
  • Defined sales process exists or is in scope
  • Willingness to enforce data hygiene
Deliverables
  • Custom data model
  • Lead routing rules
  • Lifecycle stage definitions
  • Reporting suite
  • Admin documentation
KPIs
  • Data completeness rate
  • Lead-to-MQL conversion
  • Forecast accuracy
  • Sales adoption rate
Risk factors
  • No executive sponsor
  • No agreement on stages
  • Sales team will not adopt
Positioning angles
  • CEO: You'll be able to call your quarter before it ends — because you'll finally trust what's in the pipeline.
  • VP Sales: Your team will actually use this. It'll be built around how they sell, not how someone thinks they should sell.
  • RevOps: Clean data, proper stage definitions, automated lead routing, and reports you can actually act on.
  • CMO: Attribution can finally flow into a CRM that's accurate enough to tell you what's working.
Common delivery failures
  • Biggest blocker: client sales process is undefined or inconsistent across reps
  • CRM migrations are high-risk — data mapping from the old system must be done carefully
  • Adoption is the hardest part — a perfect CRM no one uses is worth nothing
  • No named CRM admin on the client side before the engagement starts
  • Leadership approves CRM scope without getting sales team buy-in first
SOP flow
  • Audit
  • Data model design
  • Migration plan
  • Build & test
  • Train & launch
  • Optimization
Delivery team
  • Engineering
  • Strategy
  • Automation
Cross-sell
  • funnel-optimization
  • website-development
Upsells
  • attribution-modeling
  • lifecycle-automation
  • workflow-automation
Next services
attribution-modeling
lifecycle-automation
workflow-automation
Proposal language

A CRM that earns the trust of every team that touches it — operationally, analytically, and strategically.

Technical notes

HubSpot, Salesforce, or Pipedrive depending on scale. Native fields preferred over custom objects unless justified.

You are reading a detail page within Service Library. This page is part of Module 5 of 13 in the New Account Manager Track. Back to Service Library