CRM setup for a small business: pipeline, owners and follow-ups
Set up your first CRM workflow with clear stages, linked records, task ownership and go-live checks. Use a fictional six-enquiry example and downloadable setup worksheets.
In this guide
- How do you set up a CRM for a small business?
- Separate the person, company, enquiry and sale
- Define stages with entry and exit conditions
- Choose the fields the team will actually maintain
- Reconcile the first pipeline with a six-enquiry example
- Check task ownership and access together
- Start manually, then test one automation
- Roll out in an order you can verify
- What should pass before the team goes live?
- Download the setup pack and review the first release
How do you set up a CRM for a small business?
Agree one sales process, define its stages and outcomes, choose the essential fields, assign record and follow-up owners, then configure a small sample. Check access, daily work, reporting and export before moving the whole team. Add automation only after the manual process works.
A useful first release lets a colleague answer three questions: who is responsible, what happens next, and when? The setup example below is for a fictional B2B service business. Adapt its rules to your process; it is a proposed configuration brief, not a completed HubSpot or Pipedrive implementation.
If the product is still undecided, start with choosing a CRM for a small business. If you are moving existing records, keep the migration and reconciliation work alongside the configuration.
Separate the person, company, enquiry and sale
Write down what each record represents before adding custom fields. The person is an individual contact; the company is the organisation; an enquiry needs assessment; a deal represents a particular sales opportunity. One existing customer can have another opportunity without becoming a new person.
Pipedrive distinguishes leads from deals: unqualified opportunities can stay in Leads Inbox, while deals enter a pipeline. Its record model also allows several open deals for one contact. Do not translate a generic word such as “lead” into an identically named object in every CRM without checking its meaning.
For this example, Q01 stays in intake until the agreed qualification rule is met. D01 and D03 share company O01 and person C01, but represent different purchases. Combining those deals would lose a legitimate opportunity; creating another C01 for each purchase would fragment the customer history.
Define stages with entry and exit conditions
| Stage / outcome | Enter when | Move on when |
|---|---|---|
| Discovery — Open stage | A relevant enquiry has an owner and an agreed discovery conversation. | A scoped, priced proposal is sent, or an explicit win/loss is recorded. |
| Proposal sent — Open stage | A priced proposal has actually been sent to the buyer. | The buyer is actively deciding, or an explicit win/loss is recorded. |
| Decision — Open stage | The buyer is reviewing terms, approval or a buying decision. | An agreed acceptance or rejection is recorded. |
| Won — Closed outcome | The business’s agreed acceptance condition has been met. | Create the agreed delivery handover; keep delivery status separate. |
| Lost — Closed outcome | The opportunity is explicitly declined or otherwise closed as lost. | Record the reason and any permitted future review separately. |
This example has three open stages and two closed outcomes. In HubSpot, map the outcomes to Won and Lost deal stages; its pipeline documentation says both are needed for correct sales reporting. Pipedrive tracks deals through pipeline stages until won or lost; use the product’s outcome controls rather than assuming the board layout is identical.
Keep “call the buyer” as an action here. Completing a call does not mean a proposal was sent. A separate pipeline may be justified when the actual selling process has different stages; a second salesperson alone does not establish that need. HubSpot requires a paid subscription for an additional custom pipeline, so check the retained account before designing several.
Stage probabilities are assumptions used in weighted reporting, not proof of future revenue. Start by reconciling the ordinary open amounts. If you use a weighted view, record how its probabilities were chosen and review them against your own outcomes.
Choose the fields the team will actually maintain
- Identity and links: stable record IDs, the relevant person and company, and a distinct opportunity reference.
- Responsibility: the deal owner and a separate next-action owner where another colleague must act.
- Progress: the agreed stage or closed outcome, supported by its entry condition.
- Commercial scope: amount, currency and expected decision date when known. Keep an unknown amount distinguishable from a genuine zero.
- Next action: a useful verb, due date and enough context for another person to continue.
- Outcome: the win condition or loss reason, plus the required delivery handover.
Choose standard fields where they express the requirement correctly. Add a custom field only when its meaning, permitted values and maintainer are clear. Agree which fields must exist at creation and which become necessary later. Check enforcement in the actual edition and entry route: a written rule, a manual form requirement and an integration validation are different controls.
Store interaction history as linked activity or notes where appropriate. A growing paragraph in a single “latest update” field can overwrite the context the next owner needs.
Reconcile the first pipeline with a six-enquiry example
These are fictional service opportunities, all valued in GBP where known. Due days are relative to the start of the exercise. Amounts describe possible sales, not CRM licence costs, recognised revenue or a forecast.
| Record / links | Position | Deal / intake owner | Amount | Next action / owner |
|---|---|---|---|---|
| Q01 · O05 / C05 | Intake | Intake | Unknown | Confirm need and suitability · Intake · day 2 |
| D01 · O01 / C01 | Discovery | Sales A | £4,800 | Discuss scope · Sales A · day 2 |
| D02 · O02 / C02 | Proposal sent | Sales B | £7,200 | Review proposal with buyer · Sales B · day 4 |
| D03 · O01 / C01 | Decision | Sales A | £3,000 | Confirm buying decision · Sales A · day 3 |
| D04 · O03 / C03 | Won | Sales B | £6,000 | Introduce delivery owner · Delivery A · day 3 |
| D05 · O04 / C04 | Lost | Sales A | £2,000 | No new action agreed; reason: timing |
The snapshot has five deals: 3 open totalling £15,000, one won at £6,000 and one lost at £2,000. Q01 is an unqualified enquiry with an unknown amount and stays outside deal totals. The £23,000 sum of all five deal values is not the open pipeline.
D04 remains owned by Sales B as a sales record while Delivery A owns the next handover action. Winning the sale does not mean the service has been delivered. Preserve that distinction when configuring reports and notifications.
Check task ownership and access together
A deal owner and the person responsible for its next task can differ. When responsibility changes, inspect both assignments and the due date. Do not assume that changing the deal owner automatically transfers every existing activity.
HubSpot tasks have their own assignee, due date and record associations. An unassociated task can appear in the user’s task list while being absent from the customer record timeline. Open the intended deal and verify that the follow-up is linked there.
Pipedrive’s activity guidance warns that an assigned activity may be hidden when the user lacks access to its linked deal or contact. Test the receiving role, including required linked records; an administrator seeing the task does not prove the colleague can use it.
Write down the intended access for sales, delivery and administration. Use a controlled test role to check both an allowed handover and a record outside that role’s scope. Record the actual product, plan and result before rollout.
Start manually, then test one automation
First create and complete the follow-up yourself. Once its owner, record link and due-date rule are clear, consider one bounded automation: for example, create a proposal-review task when an eligible deal enters Proposal sent.
Specify what happens if that event repeats, the deal moves backwards and forwards, the task already exists, or the owner is unavailable. Decide whether an existing task should be reused, updated or left alone. An activity on every record update can create several reminders for one promised conversation.
HubSpot documents workflow trigger tests and action simulation for qualifying Professional and Enterprise subscriptions. A trigger match alone does not establish that a previously enrolled record will run again; re-enrolment settings matter. Check the available tool and permissions in your retained plan. A simulation also does not prove that an external system received the intended update.
For D02, the proposed acceptance condition is one intended proposal-review task after the triggering event and its duplicate are examined. This article supplies the exercise, not a claim that either CRM has passed it. Use controlled records and recipients; review the execution history and resulting records before enabling the rule for normal enquiries.
Roll out in an order you can verify
- Agree the brief: name the process owner, required users, first workflow and retained edition.
- Configure the structure: record types, stages, outcome meanings, essential fields and visibility.
- Rehearse a small sample: create the fictional records, follow the relationships and reconcile the starting report.
- Exercise daily work: capture an enquiry, record a conversation, assign the next action and complete a handover on desktop and phone.
- Connect and automate selectively: inspect the exact account, direction, field mapping and duplicate-event behaviour for each connection.
- Approve the first release: resolve failed mandatory checks, brief the team, agree the data cutover and name the support owner.
This is a sequence, not a promise to complete implementation in a fixed number of days. Existing data, email connections, integrations and training determine the work. Keep subscription, setup, migration and ongoing administration as separate items in the software budget.
What should pass before the team goes live?
| Check | Exercise | Expected evidence |
|---|---|---|
| T01 | Create Q01 as an unqualified enquiry, then qualify it using the agreed rule. | One enquiry is linked to the right person/company. Its conversion route is recorded; no second active opportunity is created accidentally. |
| T02 | Complete a discovery call on D01 without agreeing a proposal. | The activity is completed; D01 stays in Discovery. A completed call alone does not satisfy the stage exit rule. |
| T03 | Review D01 and D03, which share O01 and C01. | Both legitimate opportunities remain distinct, while the same company and person records are reused. |
| T04 | Hand D02 to a permitted second sales role and inspect its follow-up. | The deal owner, task owner, due date and access are checked separately. The receiving role can see the required linked history. |
| T05 | Use D02 for a controlled proposal-follow-up rule, then repeat the same triggering event. | The intended single follow-up is retained. Any duplicate action or unexpected re-enrolment is documented before release. |
| T06 | Close D04 as won and D05 as lost using the agreed outcome conditions. | Neither is counted as open. D04 has a Delivery A handover; D05 has a loss reason. A win does not mark delivery complete. |
| T07 | As the proposed restricted role, attempt to open a record outside its agreed scope. | Access matches the agreed policy. Required linked records remain usable for the receiving role; an admin-only test is insufficient. |
| T08 | On a phone, find D02, read the last interaction and locate its next action. | The assigned person can find the correct deal, action and due date in the retained product arrangement. |
| T09 | Review the opening report and export the authorised sample. | Five deals: three open totalling GBP 15000, one won at GBP 6000, one lost at GBP 2000. Q01 stays outside deal totals; IDs and links reconcile. |
Record an observed result, evidence, tester and decision for each check. Keep a failed mandatory requirement visible. These are proposed acceptance exercises; the downloads deliberately leave observations blank. No live CRM account, customer message, import or automation was used to produce this example.
Download the setup pack and review the first release
Download the stage and outcome blueprint ↓
Download the six-enquiry example ↓
Download the go-live worksheet ↓
Read the setup-pack instructions ↓
The files are an editorial brief, not ready-made HubSpot or Pipedrive import templates. Map them to the actual objects and required fields in your chosen system. The blueprint leaves your final configuration blank; the worksheet leaves test results blank until you observe them.
After rollout, review open opportunities without a responsible owner, missing next actions, stale decision dates and disputed stage definitions. Choose a review cadence your team can maintain. Record your own baseline before claiming improved follow-up or conversion.
Compare HubSpot CRM and Pipedrive, explore the CRM directory, or return to the small-business buying guide and migration checklist for the adjacent decisions.
Frequently asked questions
What should I configure first in a small-business CRM?
Define the sales process, record meanings, stages and outcomes, essential fields, owners and next actions. Rehearse a small sample and check daily work, access and reporting before rolling out to the whole team.
How many sales pipeline stages does a small business need?
Use the stages required to distinguish meaningful progress in your own process. The fictional service example has three open stages and two closed outcomes; this is a worked design, not a universal ideal or an identical board layout for every CRM.
Should every new enquiry become a deal?
Follow an explicit qualification rule. Pipedrive can hold unqualified opportunities in Leads Inbox before conversion to a deal. Check the record meanings and route in the chosen CRM rather than treating every product’s lead label as equivalent.
Can one contact have more than one sales opportunity?
Yes. Pipedrive supports multiple open deals for a contact. In the fictional example, D01 and D03 share person C01 and company O01 but represent distinct purchases; merging them would lose an opportunity.
Does assigning a follow-up task guarantee the user can see it?
No. Check the task owner, record association and access. Pipedrive warns that access to the linked deal or contact can affect activity visibility. Test the receiving role rather than relying on the administrator’s view.
When should I automate CRM follow-ups?
Once the manual process and its ownership are clear. Define the triggering event, record links, due-date rule and repeated-event behaviour, then test controlled cases and inspect the resulting records before general rollout.