How Does a CRM Actually Work?

Someone fills in the get a quote form on a solar installer's website at nine on a Sunday evening. Eleven days later they sign for a four kilowatt system with battery storage. A CRM is the thing that connects those two moments. Here is what happens in between, mechanically, without the marketing language.

The core object is a record

Everything in a CRM hangs off one kind of object, usually called a lead or a contact. A record is a set of fields plus everything attached to it: notes, logged activities, files, and a history of what has changed. When people say a CRM is one place for your leads, the record is what they mean. One per person or enquiry, and every action happens on it.

Fields hold the facts

Fields are the structured part of the record. A typical lead carries:

• Name and contact details
• Source: how the lead arrived, a website form, a phone call, a referral, a named campaign
• Status: where the lead sits in your process right now
• Owner: the single person responsible for it
• A free-text notes area for anything that does not belong in a field

The reason to use fields rather than a paragraph of prose is that the system can count and filter them. Show me every website lead from last week that still has no owner is a question you can only ask if source, date and owner are all fields.

How a lead gets in

Records are created three ways. Someone types one in by hand from a call or a business card. A list is imported in bulk, usually from a spreadsheet. Or a web form creates them automatically: you build the form, place it on your site, and every submission becomes a record with the fields filled in and the source set to the page it came from. The automatic route is the one that matters most, because it is the only one where nobody has to remember to log the lead.

The pipeline is an ordered list of stages

A pipeline is simply your statuses written in the order a lead passes through them, for example New, Contacted, Quote sent, Negotiating, Won, Lost. Most CRMs draw this as a board with a column per stage and each lead as a card you move along. Nothing complicated sits behind the move: you are changing one field, status, and the board is just a picture of that field. The benefit is that anyone can read the state of the pipeline at a glance, forty in New, six in Quote sent, a pile-up in Negotiating that needs a look.

Assignment puts a name on the lead

When a record is created, the CRM sets an owner. That can happen in a few ways: whoever entered it becomes the owner, an administrator allocates it, or the system hands it out on its own. A common automatic method is round-robin, where new leads are dealt out one at a time across the active team so the workload stays even and nothing lands nowhere. Once a lead has an owner it appears in that person's list and their overdue view, which is what turns the follow-up into one person's job.

The activity log records what happened

Every meaningful action on a lead is written to a timeline: a call logged, a note added, the status moved from Contacted to Quote sent, the owner changed. This is the history, and its job is to answer what is the story with this lead without anyone relying on memory. When the first owner is on leave and a colleague picks up the solar enquiry, the log tells them the customer asked about battery capacity, was quoted on the ninth, and wanted to talk it over with their partner first.

Reminders schedule the next step

A CRM lets you attach a future action to a lead: call back on the fourteenth. When the fourteenth arrives, that lead shows up in a due or overdue list. This is the part that replaces remembering. It is deliberately plain: a date, a short description, and a view that gathers everything now due. The discipline it imposes is that a lead is never finished for now unless it has a next date on it.

Reports read the records back as numbers

Because the facts live in fields, the CRM can add them up. The reports that earn their keep early are:

• Volume by source: which channels actually produce leads, not just clicks
• Conversion by stage: where leads stall or fall out of the pipeline
• Activity by owner: who is working their list and who is swamped
• Response time: how long between a lead arriving and the first contact

None of these need building if the data is being entered. They are just a reading of the same records the team works in all day.

What the software does not do for you

A CRM does not qualify a lead, write the follow-up email, or set the price. It will not chase anyone on its own. What it does is hold the state of every lead and put the next action in front of the right person at the right time. The judgement stays with you; the system makes sure nothing is dropped while you use it.

Following the solar enquiry through

Put the parts together. The Sunday-night submission creates a record: name, phone, interested in solar and battery, source website pricing page. Round-robin gives it to the installer next in the rotation. It sits in their list as a new lead with no contact yet.

Monday morning they call, log the call, move the status to Contacted, and set a reminder to send a quote by Wednesday. Wednesday the quote goes out, the status moves to Quote sent, a reminder is set for the following Monday. The customer emails a question about roof orientation; it is added as a note. The follow-up call happens on the Monday, the customer confirms, the status moves to Won, and the record now holds the entire eleven-day sequence for anyone who needs it later.

That is the whole mechanism: a record, some fields, an ordered list of statuses, an owner, a log, a reminder, and reports that read it all back. Every CRM presents this differently, but underneath it is the same small set of parts doing the same small set of jobs.