# CRM for a solo business | 121 CRM > A practical guide to CRM for a solo business, with working steps, a fictional example, review questions and clear limitations for UK small businesses. Begin by making the current ambiguity visible to the people who do the work. This guide helps a small team turn crm for a solo business into a specific, testable way of working rather than a vague intention. It uses a bounded customer journey, clear ownership and evidence people can review, keeping CRM for a solo business grounded in real work rather than treating it as another abstract CRM ambition. ## CRM for a solo business in a working decision Fictional example using Cedar Legal Admin; adapt the method to your own customers, responsibilities and configuration. ## Capabilities explained ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Users, roles and permissions Controls whether a user acts at agency or sub-account level and which supported areas they can access. **How it works:** Controls agency or sub-account configuration that determines access, packaging, governance or billing. **Why a business would use it:** Limits day-to-day access to the work a person actually needs to perform. **Limitations:** Availability and control depth depend on agency plan, role and current account configuration. **Human responsibility:** An authorised administrator must review, approve and audit material changes. ### Import and export Moves supported records through structured files, with mapping and validation needed before relying on the result. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Supports controlled migration and operational extracts when the data is prepared and reconciled. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. Bulk migration requires mapping and reconciliation; do not treat a completed import as proof of accuracy or reversibility. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ### Workflow builder Combines a start event with an ordered sequence of configurable actions. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Turns a repeatable customer process into a visible, reviewable flow. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ## Start with the decision behind CRM for a solo business The useful aim is to compare the decision against the work the business genuinely needs to perform. For CRM for a solo business, define what needs to change, who owns the choice and how the team will recognise a better customer or staff outcome. ### The question to answer Write this buying decision as a question an owner can answer. Here, the practical task is to turn crm for a solo business into a specific, testable way of working rather than a vague intention. Name the customer stage and the later action this buying decision should inform. ### Evidence to bring into the room Collect scored requirements, a representative demonstration and written commercial and configuration boundaries. Use a small current sample to test this buying decision, including one example that did not follow the expected path. ### A boundary people can recognise The main risk is that a persuasive demonstration can conceal configuration work, usage costs, weak export options or a feature that is not included commercially. State the stop, escalation or approval point for this buying decision in ordinary language and give it to a named person. ## A four-part method the team can test Try this method on a representative slice of this buying decision before changing every team or record. Each part of the CRM for a solo business trial should leave evidence that another person can inspect, challenge and repeat. ### 1. Write scenario tests Turn the requirement into ordinary, awkward and failed scenarios that a supplier must demonstrate with representative fictional data; keep the practical aim in view: turn crm for a solo business into a specific, testable way of working rather than a vague intention. ### 2. Inspect the whole task Watch capture, ownership, correction, reporting and export rather than accepting a polished view of one isolated feature; keep the practical aim in view: turn crm for a solo business into a specific, testable way of working rather than a vague intention. ### 3. Price the operating model Record setup, usage, connected-service, support, change and exit assumptions alongside the headline subscription figure; keep the practical aim in view: turn crm for a solo business into a specific, testable way of working rather than a vague intention. ### 4. Score the evidence Separate demonstrated behaviour, documented capability, commercial inclusion and unanswered questions before choosing a preferred option; keep the practical aim in view: turn crm for a solo business into a specific, testable way of working rather than a vague intention. ## How Cedar Legal Admin could apply the guide Cedar Legal Admin is a fictional professional-services team. The team tests CRM for a solo business on one bounded customer journey, using fictional data and the existing working practice as its comparison point. ### The starting question Cedar Legal Admin needs to turn crm for a solo business into a specific, testable way of working rather than a vague intention. The customer context needed for this buying decision exists today, but it is spread across records and individual knowledge, so another colleague cannot consistently explain the next decision. ### The bounded trial The team selects ten recent examples, applies the four-part method to this buying decision and records every exception. It changes only the minimum fields, ownership rules and prompts needed for this buying decision; one person can halt the trial if customer context is lost. ### The review conversation The owner checks whether the shortlisted option completes agreed scenarios without hidden manual work or unsupported assumptions. Staff compare the new route for this buying decision with the earlier practice, identify avoidable administration and show which awkward case still needs a person rather than another rule. ### The honest conclusion Capability, commercial inclusion and configured availability are different questions; verify all three for the intended customer account for this CRM for a solo business trial. The trial can show whether the method is clearer for Cedar Legal Admin; it cannot promise revenue, growth or a universal result. ## Limits, warning signs and review points The CRM for a solo business design needs another look when a scenario cannot be demonstrated, a cost remains conditional, an export is incomplete or the proposed owner cannot operate the process. Give this buying decision both a calendar review and an event-driven trigger so a once-useful configuration does not quietly become misleading. ### Treat workarounds as evidence If staff keep a private list, retype the same value or move this buying decision into chat, ask what the agreed method failed to represent. Fix that problem before layering another automated action over this buying decision. ### Challenge the apparent signal The CRM shows captured events under chosen definitions. Before drawing a conclusion from this buying decision, check missing activity, timing, duplicated records and whether the population still matches the decision. ### Reconfirm availability and dependencies Capability, commercial inclusion and configured availability are different questions; verify all three for the intended customer account for CRM for a solo business. Recheck the providers, permissions, retention and communication rules supporting this buying decision when the scope changes. ### Give somebody the stop decision The accountable owner must be able to pause this buying decision, correct the record and explain why an exception was handled differently. Responsibility for this buying decision cannot be delegated to a status or score. ## Frequently asked questions ### What decision should come first in CRM for a solo business? Start with the question that changes a customer action or handover: how will the team turn crm for a solo business into a specific, testable way of working rather than a vague intention? Give this buying decision an owner and test it against a few current examples before choosing more configuration. ### What evidence is useful for reviewing CRM for a solo business? Bring scored requirements, a representative demonstration and written commercial and configuration boundaries. Include a normal case, a missing-information case and an exception so the review of this buying decision does not describe only the ideal journey. ### Where should automation stop when handling CRM for a solo business? Stop where context, consent, fairness, professional responsibility or an unusual customer need changes the appropriate action for this buying decision. A person should own that point in this buying decision and be able to explain the decision. ### What should trigger another review of CRM for a solo business? Review this buying decision when a scenario cannot be demonstrated, a cost remains conditional, an export is incomplete or the proposed owner cannot operate the process. Also set a proportionate review date for this buying decision so quiet drift is found even when nobody raises an incident. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/crm-for-remote-team](https://121.direct/crm/guides/crm-for-remote-team) - [/crm/features/customer-management](https://121.direct/crm/features/customer-management) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.