Setting Up a Basic CRM for a Five-Person Team

A basic customer relationship management system for five people should answer three questions without requiring a meeting: who is responsible for a customer enquiry, what has been agreed, and what needs to happen next? If those facts live in different inboxes and private spreadsheets, the team has a continuity problem. An expensive system cannot repair vague responsibilities, but a modest, properly configured CRM can give employees a shared record of contact history and genuine next actions. Start with the team's work, not a vendor's most impressive dashboard.

This guide covers setting up a simple CRM for a five-person UK service or property business. It focuses on records, ownership, pipeline definitions, permissions and safe handovers. A CRM is not automatically an accounting ledger, booking authority or complete customer-support system. Each business must decide which application controls those separate outcomes. The steps below are an operational framework, not a claim that a named vendor will deliver a particular revenue increase.

1. Agree what a customer record represents

Begin with a meeting involving the people who receive, respond to and fulfil enquiries. Decide what should count as a contact, an organisation, a lead and an active opportunity. A buyer asking about several properties may be one person with multiple enquiries; creating a different person record for each viewing makes history difficult to follow. A business client may have several employees contacting the team on behalf of one organisation. Record these relationships in terms employees can explain to someone covering their work.

Set rules for creating, merging and closing records. The correct answer is not to store every piece of personal information the business can find. The UK's Information Commissioner's Office explains data minimisation and accuracy as distinct principles: collect what is necessary and keep it correct. A basic contact name and reply address may be appropriate for a first enquiry; detailed personal or financial information requires a specific, justified purpose. Decide what belongs elsewhere and which system remains authoritative if customer details change.

2. Keep the first screen deliberately small

Choose a few fields that support real decisions: the customer's agreed contact route, enquiry subject, responsible employee, current status, last meaningful interaction and next action. A property team may also need a reference to the relevant property or service, without copying confidential property documents into every contact record. Create mandatory fields only where the information can reasonably be known at the stage of entry. Forcing a salesperson to enter a fictional budget before a first conversation pollutes the database and the reports built upon it.

Make descriptions practical. Define what qualifies as an enquiry source, how to record a referral and when a preference has been confirmed rather than assumed. Limit free-text notes containing unnecessary sensitive data. Establish who can correct a mistaken address and how the correction is reflected in connected applications. With five employees, small inconsistencies accumulate quickly because each colleague sees different cases; a concise data dictionary and a few realistic examples can prevent repeated arguments about fields.

3. Define pipeline stages using evidence

A stage should communicate a meaningful state, not just activity. For example, an enquiry may be new, assigned, qualified, awaiting an approved quotation, under negotiation, won or closed without proceeding. The exact labels depend on the business; fewer well-defined stages are usually easier to maintain than an elaborate pipeline imported from another industry. Describe the evidence needed to move forward and who can approve a consequential change. A draft quotation is not an issued offer, and a positive conversation is not a signed agreement.

Microsoft's Dynamics 365 Sales documentation illustrates the distinction between a lead and an opportunity. Its lead qualification process can create or associate account, contact and opportunity records, with behaviour depending on configuration. Its opportunity stages represent a different part of sales progress. These are useful product-specific examples, not rules requiring every five-person CRM to copy Microsoft's default pipeline. Test how the selected product records a lost opportunity and how it can later reopen a genuinely new enquiry without erasing history.

4. Assign one accountable owner and a visible next step

Five people may share duties, but each active record needs a clearly responsible colleague at any given point. Ownership answers who makes sure the next step happens; it does not mean that person must complete every task. Record a short, actionable next step such as checking a specific document with the customer or arranging a follow-up after an approved date. A reminder that simply says 'follow up' cannot tell a covering employee what the customer is waiting for. Include dependencies and uncertainty without turning the CRM into a repository of unnecessary personal commentary.

Test a handover by asking a colleague unfamiliar with three live enquiries to identify each current status, outstanding commitment and responsible person. If the answer requires access to someone's private inbox, decide whether the CRM needs a better note, a controlled email link or a revised process. Avoid automatically copying entire private email conversations into the system. Staff should be able to find the business context whilst confidential information remains restricted to those with an appropriate reason to read it.

5. Control duplicates, consent and access before importing history

Import a small, representative sample first. Include a returning customer, two similar names, an organisation with multiple contacts and a contact who has changed their email address. Check whether the selected CRM proposes to merge records and who reviews the decision. Incorrect merging can reveal one person's information to another or cause an employee to act on the wrong case. Establish a review method for ambiguous matches rather than relying entirely on automated deduplication.

Use named accounts and role-appropriate permissions. One employee may need to see their enquiries without accessing all commercial negotiations or administrators' configuration. Test what happens when a colleague leaves: the business should retain legitimate records while revoking their access and any connected sessions. Review customer contact preferences separately from the mere existence of a CRM record. Being in a database does not itself establish permission to receive electronic marketing. ICO guidance on minimisation, accuracy, purpose and security provides relevant UK principles for assessing the actual use.

6. Connect only the tools that serve a defined workflow

A website form can create an enquiry; a calendar can display an approved meeting; a document service can hold the final quotation. Each connection introduces a question about source of truth. If a contact changes their telephone number in two products, which application governs the result? If a customer cancels a meeting, will an old reminder continue to be sent? Map the direction of each necessary transfer and verify the destination's actual status before telling a customer that a booking or refund was completed.

Start with one integration that removes repeated entry. Use limited permissions and a company-controlled connection rather than an employee's unmanaged personal account. Test duplicate submissions, delayed updates and a missing required field. A successful API request may mean only that the destination received a message. When the result is material, check whether the authoritative record was actually created or changed and surface exceptions to a responsible person. More integrations should be added only when a clear benefit outweighs their maintenance burden.

7. Build views that help staff work, not merely impress managers

The first reports should address daily operations: new enquiries without owners, active opportunities without a next action, and cases waiting for approval or customer evidence. A manager may also need to review how long work stays in a particular stage. Such measures depend on consistent status definitions and records that staff actually update. A dashboard with beautiful charts is misleading when 'won' includes unaccepted quotes or when closed work disappears before complaints are resolved.

Use records from the trial to challenge every measure. Ask what the numerator and denominator mean, when data were updated and what has been excluded. Avoid fabricated conversion benchmarks, unverified revenue forecasts or scoring based on demographics that have no legitimate operational purpose. A five-person team gains more from a short review of blocked work than from reports nobody understands. Add a measure only if a named person will use it to make an identifiable decision.

8. Run a handover pilot and document the exit route

Choose several representative journeys: a new enquiry, a returning customer, a changed owner, an enquiry that should close without a sale, and a duplicate that needs review. Ask different employees to work through them and inspect the same record. Check whether an unauthorised user can access restricted information and whether the CRM preserves the original history when correcting a mistake. An acceptance decision should explain what passed, what needs correction and who owns the remaining work.

Before adopting the product, export sample contacts, activities and links to associated opportunities. A CSV of names may not preserve conversation context or decisions. Document ownership of administrator accounts, pricing of the actual team and the procedure for leaving the vendor. The right CRM is the one that keeps customer commitments understandable without making five colleagues spend their days feeding an elaborate database. Begin with a handful of trusted records, consistent ownership and a verifiable next action; grow only when real use demonstrates why more complexity is necessary.

Evidence: Microsoft Learn: create or edit leads, vendor-specific example of records and relationships; Microsoft Learn: qualify leads, vendor-specific opportunity creation behaviour; ICO small-organisation data-protection principles, UK. These sources support the described distinctions, not a guarantee of business performance.