What is a CRM?

What does CRM stand for?

CRM stands for Customer Relationship Management. It refers both to the business strategy of managing customer interactions and to the software that supports it. The term entered mainstream business vocabulary in the mid-1990s, was popularized by Siebel Systems and Salesforce, and is now the umbrella name for any database that holds your contacts, deals, activities, documents, and revenue events.

Where the term came from

The phrase "Customer Relationship Management" entered mainstream business vocabulary in the mid-1990s, when client-server databases became cheap enough that mid-sized companies could replace their Rolodexes with something searchable. Siebel Systems was the early category leader; Salesforce was founded in 1999 with the radical proposition that the CRM should live in the browser instead of on a sales rep's laptop. By 2010 "CRM" had become the umbrella term for every piece of revenue-facing software — pipeline tracking, marketing automation, customer support, e-signature, even billing in some definitions.

The vocabulary creep is part of why buying one is confusing. A founder asked "do you have a CRM?" might say yes because they use HubSpot for email blasts, even though their pipeline lives in a spreadsheet and their contracts live in Google Drive. None of those things talk to each other, which means none of them are actually doing the job of a CRM.

What a CRM actually does

A working CRM holds five kinds of objects and keeps them in sync. Contacts and companies — the people and organizations you sell to. Deals or opportunities — the open conversations with a dollar value and a stage. Activities — calls, emails, meetings, notes, and tasks. Documents — proposals, contracts, SOWs, and signed agreements. And revenue events — bookings, invoices, payments, churn.

Every one of those objects has a relationship to the others, and the value of a CRM is that you can pivot through them in a single query. "Show me every open deal over fifty thousand where we have not had a meeting in 21 days, grouped by sales rep, with the most recent contract version attached" is a one-line question in a CRM and an afternoon of spreadsheet work without one.

When founders actually need one

The trigger is rarely customer count and almost always "someone besides the founder is talking to customers." The moment a second teammate is emailing prospects, the founder loses the in-the-head context that was keeping the pipeline coherent, and a CRM becomes the cheapest way to rebuild that shared brain. Other common triggers: an investor asks for a pipeline forecast you cannot produce in twenty minutes, a customer complains you forgot something they told a teammate last quarter, or you miss a renewal because the renewal date lived in a Calendar event nobody thought to check.

At QUANT LAB

We build custom CRMs for teams whose sales process is their moat — agencies with complex retainer ladders, professional-services firms with multi-party deal teams, vertical SaaS companies whose pipeline shape does not match anything Salesforce ships out of the box. Our custom CRM development work usually starts with a two-week discovery phase where we map your current pipeline, identify the three or four custom fields that everyone reaches for, and decide whether to start from a blank database or fork an open-source base. The build itself is typically Next.js on the frontend, Postgres for the database, and Stripe wired in for billing.

If you already use Salesforce or HubSpot and the pain is that you cannot get them to do one specific thing your business depends on, we usually recommend extending instead of replacing — read our custom CRM vs Salesforce vs HubSpot comparison before deciding which path you are on.