What Is a CRM? A Sales Pipeline Guide for Small Businesses

A CRM (customer relationship management) system is a shared record of everyone you sell to: the companies, the people you talk to there, the deals in progress, every call and meeting, and the quotes you sent. For a small or mid-size business, the point is that everyone on the team sees the same history and knows the next step, instead of piecing it together from inboxes, chat threads and a spreadsheet only one person understands.

What a CRM does for a small team

A CRM is more than a contact list. A useful one does four jobs:

• One record per customer. Contact details, open deals, past quotes, notes and support requests sit on the same card.
• A visible pipeline. Every open deal sits in a stage, so you can see what is stuck and what is about to close.
• Follow-ups that don't slip. Each deal has a dated next step and an owner.
• Reports you can trust. Structured data lets you measure conversion, time to close and activity without counting by hand.

Typical signs you have outgrown spreadsheets: two people call the same prospect in the same week, nobody knows which quotes are still open, or a salesperson leaves and their pipeline leaves with them.

The core flow: companies, contacts, deals, quotes

Most B2B CRMs are built around four linked records:

1. Company: the organisation you sell to.
2. Contact: a person, usually at a company. If you also sell to consumers, a contact should be able to exist without a company.
3. Deal (or opportunity): a specific potential sale with a value, an owner, an expected close date and a stage.
4. Quote: the priced offer you send for a deal, built from your products or services.

Keep them separate: one company can have several contacts and several deals at once, such as a new project and a renewal. On a single spreadsheet row, new information overwrites the old.

How to design pipeline stages

Stages should describe what has actually happened with the buyer, not what the salesperson hopes:

• Give each stage an exit criterion. A deal moves forward only when something verifiable happens.
• Keep the list short. If two stages always happen together, merge them.
• Treat won and lost as outcomes. Record a reason for every lost deal; after a few months those reasons tell you more than any dashboard.
• Assign a probability to each stage if you want a weighted forecast, and compare it with real results regularly.
• Use separate pipelines for separate processes. New business, renewals and partner deals rarely follow the same steps.

An example pipeline for a small B2B service company:

Stage	Move the deal forward when…
New	You know who they are and what they need
Qualified	Budget, decision-maker and timing are confirmed
Meeting / demo	The meeting took place and next steps are agreed
Quote sent	A priced quote is in the customer's hands
Negotiation	The customer came back with questions or changes
Won / Lost	Signed, or a clear no with a recorded reason

Activities and follow-ups

A pipeline only moves when someone acts. Log calls, meetings, emails and notes against the company and the deal, so anyone can pick up the conversation, and give every open deal a next activity with a due date. For a weekly review, two lists are enough to start: open deals with no next step, and overdue tasks.

Quotes from a product catalog

Typing prices by hand invites mistakes. A catalog with product names, units, prices and tax rates lets you build a quote line by line in a few clicks. Two habits make quotes reliable:

• Freeze a quote once it's sent. If you raise a price next month, the quote a customer already holds must not change.
• Give every quote a validity date and a status: draft, sent, accepted, rejected or expired. Then "which quotes are open?" has an exact answer.

Roles and permissions

Not everyone needs to see everything. Split permissions by job: who can change pipeline settings, who can delete records, who can export data. Exporting deserves its own permission, because that is how customer lists leave a company.

Reports that matter

Start with a handful and review them weekly: open pipeline by stage, stage-to-stage conversion and win rate, average time to close, activities per person, and lost reasons.

Moving from spreadsheets to a CRM

1. Decide the fields first. Keep only what you actually use.
2. Clean and de-duplicate. Merge duplicate companies, standardise phone formats, drop dead leads.
3. Load in order: companies, then contacts, then only the deals that are still open.
4. Map your old statuses to the new stages before you move anything.
5. Pick a cut-over date. After it, the spreadsheet is read-only.
6. Work real deals from the first week and fix gaps as you find them.

How VOLTR does it

The VOLTR CRM follows the same flow: company → contact → deal → quote. A contact doesn't have to belong to a company, so individual customers are managed in the same module.

• You define your pipelines and stages. A stage's type (open, won, lost) is kept separate from its name, so renaming stages never breaks reports. Each stage can carry a probability.
• Activities (notes, calls, meetings, emails, tasks) have a due date and an owner, and one activity can be linked to a company, a deal and a call at the same time.
• Quotes are built from a product catalog. Quote lines copy the product's name and price, a sent quote can't be edited, and expired quotes are flagged automatically.
• Support tickets live in the same module, with first-response and resolution times stored separately.
• Permissions are split by job: companies, contacts, deals, activities, quotes, tickets, pipeline settings and reports. Exporting a report to CSV is a separate permission, and table columns can be hidden by role (see security).
• Custom fields can be added to contacts, companies, deals and tickets.
• Reports cover the pipeline, conversion, time to close, tickets and activities.
• With the ERP module, a finance account can be linked to the CRM company, so sales and collections are tracked on one platform.

Frequently asked questions

Is a CRM worth it for a team of three?

Yes, if more than one person talks to customers or if deals take more than one conversation to close. The value comes from shared history and dated follow-ups, not from team size.

How many pipeline stages should we have?

As few as you can verify. If you can't name the event that moves a deal from one stage to the next, you probably don't need that stage.

Why shouldn't a sent quote change?

Because the customer is holding it. Even if your prices change later, the record must still show what was offered at the time.

Ready to try it with your own pipeline? Open a free VOLTR account and add CRM from the Subscription section in the app. Module prices, or how to request a quote, are on the pricing page.