# CRM Guides for UK Small Businesses | 121 CRM > Practical guides to choosing, planning, implementing and improving a CRM for a UK small business, written without inflated promises. These guides help a UK small business define CRM needs, prepare data, plan implementation and design responsible follow-up. They are useful without a purchase and avoid borrowed statistics or inflated outcomes. ## Eight questions, eight practical guides 121 methodology and practical guidance. Product availability and service commitments remain separately scoped. ## 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. ### Pipelines Defines an ordered sales process through which opportunities can be reviewed and moved. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Makes the sales process visible so follow-up is based on stage rather than memory. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### 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. ### 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. ## Choose the guide that matches the decision in front of you. The library covers eight durable jobs with clear boundaries rather than publishing overlapping articles for every keyword variation. ### What is a CRM? Understand contacts, conversations, opportunities, tasks and follow-up — and what a CRM does not decide for you. ### Implementation checklist Prepare goals, owners, data, permissions, workflows, tests, training and acceptance before go-live. ### Migration checklist Plan discovery, cleaning, mapping, samples, reconciliation, cutover and fallback for an actual source. ## Design the customer-facing work, not only the software setup. The workflow guides cover pipeline stages, reminders, follow-up and reputation with clear human and platform boundaries. ### Pipeline and follow-up Define stages, ownership, next actions and bounded automation around real customer decisions. ### Appointments and reputation Plan reminders, changes, fair review requests and responses around customer choice and platform rules. ### CRM or spreadsheet Compare shared visibility and control, then move only when the operating need is clear. ## Treat each checklist as a conversation prompt, not a universal recipe. The right answer depends on the business, customer journey, current systems, data and responsibilities. ### Write down decisions Record owners, evidence, open questions and acceptance rather than relying on remembered workshop conclusions. ### Test representative cases Use fictional or controlled samples including duplicates, missing information, exceptions and failures. ### Return after go-live Review whether the process remains useful, proportionate and understood as the business changes. ## Frequently asked questions ### Are these guides specific to 121 CRM? They use the 121 operating approach but most planning questions are useful for assessing or improving another CRM as well. ### Do the checklists replace legal, privacy or professional advice? No. They identify operating questions and boundaries. Obtain appropriate specialist review where the workflow, data or sector requires it. ### Do I need to subscribe before using a guide? No. The guidance is public and intended to help you make a better decision whether or not you choose 121 CRM. ## Related CRM pages - [/crm](https://121.direct/crm) - [/crm/guides/what-is-a-crm](https://121.direct/crm/guides/what-is-a-crm) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.