A Simple CRM for a Small Business: Contacts, Leads and the Next Action
A small business CRM should let your team answer four questions. Who is this contact? What work are we discussing? Who owes the next action? When is it due? Build that working record first, before you add dashboards or automatic sequences.
The method works in a lightweight CRM or in a well-kept worksheet. What matters is that requests stay visible, and that another authorised person can pick up the work when the usual owner is away.
This guide defines a practical starting structure, stage rules, a daily review and a safe way to bring existing records into it.
Keep contacts, leads and tasks separate
A contact identifies a person or organisation. A lead represents a particular request or possible job. A task is an action somebody needs to complete.
One contact can have several leads, and each lead can have several tasks over time. Keeping them separate prevents a common problem: marking a customer as finished because one job ended, or losing an older quotation when a new request arrives.
| Record | Example in a fictional equipment-hire business |
|---|---|
| Contact | A venue manager responsible for event requests |
| Lead one | Hire request for a particular event date |
| Lead two | A separate request for a later training session |
| Task | Confirm equipment availability for lead one |
| Note | Internal context relevant to the assessed request |
| Message | Information actually sent to or received from the customer |
An internal note is not a message. Keep the difference obvious, so a private working comment can never be sent to the customer by accident.
Start with a small contact record
Record the name, relevant organisation, appropriate contact route, source and necessary context. Include country or timezone where it helps handling, without collecting information just because another database happens to have it.
Handle shared email addresses with care. Two people may use the same company inbox, and one person may use several addresses. A matching email is a clue to a duplicate, not proof that two records are the same person.
Record communication objections and relevant permissions separately from ordinary contact details. Having an address in the CRM does not by itself establish permission for a marketing sequence.
Give each lead a specific subject
A useful title names the job or decision: "equipment for the June workshop", "replacement signage assessment" or "annual maintenance quotation". A title with only the contact's name gets confusing as the relationship grows.
Keep the customer's original request accessible to the people authorised to read it. Use controlled service/area fields where helpful, but do not replace the original context with an internal score.
Suggested lead fields are service or need, relevant area, source where known, owner, stage, next action, due date and waiting-on state. Add quoted value only when it serves a clear business purpose and its status is understood.
Use stages with observable meanings
| Stage | Working definition | Common mistake to avoid |
|---|---|---|
| New | A genuine request has been received and needs handling | Every imported contact becomes an open lead |
| Contacted | A meaningful contact action has been recorded | Assuming a sent email proves it was read |
| In progress | Assessment, quotation or an active decision is underway | A lead stays here without an owner or next step |
| Won | The business's defined acceptance point has been reached | A quote sent is labelled a sale |
| Lost/closed | The request ended under a recorded reason | Silence is automatically interpreted as rejection |
Choose a precise Won definition for your business. Accepted quotation, paid deposit and completed job are different milestones. If you need to observe several of them, keep the appropriate status or linked job record rather than changing the meaning of Won each month.
A stage is a summary. It should not substitute for the next action.
Make the next action concrete
Write tasks as actions someone can perform: confirm the access window, send the revised scope, check the supplier's reply. "Follow up" is usually too vague unless the task also says what decision you are chasing.
Give each task one responsible person and a due date or time. Where a date is sufficient, use the business's local calendar. A timed customer commitment needs the relevant timezone and an actual agreed instant.
Track waiting-on separately. A lead can be waiting for a customer while the team has an internal task to review it next week. That does not require an automatic email on that date.
Build a useful daily view
A small daily review can focus on:
- New genuine enquiries without an owner.
- Tasks due or overdue.
- Open leads with no next action.
- Replies that change a pending task.
- Delivery problems or uncertain outbound messages.
- Requests ready to close with a clear reason.
The view should help people make decisions, not reward them for opening records. Complete each item, reschedule it with a reason, assign it or close it deliberately.
Keep an absence arrangement. An inbox or CRM owned by one person becomes a single point of failure when that person is away. Access should be authorised and limited to the work the covering person needs.
A worked record through the pipeline
This example is fictional. A venue manager asks the equipment-hire business about chairs and presentation equipment for an event.
The team creates a contact record and a lead for that event, then assigns a task to confirm availability. The initial request remains visible; the task contains the actual next action and due time.
After the team replies, the lead becomes Contacted under its chosen definition. When a scope and quotation are being prepared, it moves to In progress. The contact is not duplicated when the manager asks a follow-up question.
A separate later event receives a new lead linked to the same contact. Its dates and decisions remain separate. Winning the first event does not close the second.
If the customer declines the first quote, the lead closes with the actual reason where known. If they simply stop replying, the team records no response under its closure policy rather than inventing a competitor or price objection.
Import existing records cautiously
Prepare the source file and decide what it contains: contacts, open requests or both. Map the fields deliberately, preview the result and inspect duplicate suggestions before committing.
Start with a manageable representative sample. Include shared email addresses, international numbers, missing optional information and existing records that should be updated rather than duplicated.
| Import decision | Useful check |
|---|---|
| Create contact | Is this a distinct person/organisation record? |
| Update existing contact | Which field is newer and supported? |
| Keep separate | Is a shared email hiding distinct people? |
| Create an open lead | Does a real unresolved request exist? |
| Preserve objection | Will the import keep the existing stop state? |
| Exclude a field | Is the information unnecessary or inappropriate for this CRM? |
An import should not automatically send messages, create public listings or enrol people in follow-ups. Those are separate actions requiring their own authority and purpose.
Use notes to preserve decisions
Record important decisions, uncertainties and commitments in plain language. Include enough context for another authorised person to understand the next step.
Avoid unnecessary sensitive detail, speculation or comments that would be hard to justify if the record were reviewed. Keep formal documents and message history in their appropriate protected location rather than duplicating everything into notes.
When facts change, add the correction and preserve the necessary history. An older quotation should not silently become the current agreement because someone edited a number in a contact card.
Automate reminders before customer messages
An internal reminder can improve reliability without changing the customer's communication experience. Establish that workflow first: a due task reaches the responsible owner and can be completed or rescheduled.
External automation needs more checks: current request state, recipient/channel suitability, message purpose, permission, replies, objections and delivery uncertainty. A CRM makes those checks possible; it does not supply them automatically.
The follow-up guide provides a restrained communication sequence and stop conditions. W3C's form guidance is also a useful reference when choosing how much information to request from a customer initially. Focused form design
Review the pipeline weekly
Look at aged open leads, recurring missing information and reasons work was closed. Review the source and service mix only with clear definitions and enough context.
Do not judge the team by raw contact counts or the size of an unqualified pipeline. A record with a possible amount is not booked revenue, and a lead that has been open for months is not necessarily a live opportunity.
Use the qualification guide to establish fit and the marketing economics guide to connect observed outcomes with cost. Keep those analyses separate from the operational duty to answer each genuine request.
Choose software by the workflow it can support
Test contact/lead separation, clear task ownership, search, permissions, import preview, duplicate review and data export. Check what the product means by sent, delivered, replied and won.
Use a real representative request to assess the tool. An attractive dashboard should not outweigh an unclear record or an inability to recover the business's data.
A good starting CRM has enough structure to keep customer work dependable, and few enough moving parts that the team can maintain it. Add to it when a recurring problem shows you need to.