CRM Software Examples: Three Minimum‑Viable HubSpot Setup Patterns for UK SMEs

If you run a 10–100 person SME, your real CRM question is usually not “Which CRM vendor?” but “What is the minimum viable way to structure HubSpot so my team actually uses it?”

This article answers one narrow decision:

Which minimum‑viable CRM setup fits this team: a deal‑pipeline‑led, shared‑service‑led or individual‑inbox‑led pattern, and how do we prove it works in a trial?

You get three synthetic but concrete HubSpot blueprints, not three vendors and not AI revenue promises. Each pattern comes with:

• Core records (deals, tickets, contacts).
• Stage and owner rules.
• Relevant plan and permission notes.
• A simple acceptance test you can run inside a trial.

If you later want to add AI lead generation on top of whichever pattern you choose, see our separate 30‑day plan in this guide.

Required tools and prerequisites for a fair CRM pattern trial

You can only judge these CRM software examples fairly if a few basics are in place.

1. A HubSpot account with pipeline access
   HubSpot’s documentation states that object pipelines (including deal and ticket pipelines) are available for “all products and plans”, although managing lead object pipelines requires Professional or Enterprise and managing custom object pipelines requires Enterprise [HubSpot, Set up and manage object pipelines]. For these patterns we only rely on standard deal and ticket pipelines.

2. Permission and seat awareness

   • To manage pipelines, users need appropriate property/settings permissions [HubSpot, pipelines].
   • Connecting channels to Help Desk requires Service Hub Professional or Enterprise and Account Access permissions; tickets in Help Desk can only be automatically routed to users with assigned seats [HubSpot, connect channels to help desk].
   • Connecting an individual work email is available on all products and plans, but users with a View‑Only seat cannot connect their individual emails [HubSpot, connect an individual work email].

3. A basic process sketch
   For each pattern you try, write down:

   • Entry criteria: when something enters the pipeline, inbox or help desk.
   • Stages or labels each record can pass through.
   • Who is responsible at each stage.

4. One named process owner
   Someone who can decide stage definitions, accept or reject test results, and own clean‑up after your trial.

Definition: Minimum‑viable CRM setup: the simplest combination of records, stages and ownership that lets your team track work, without unnecessary pipelines, fields or queues.

If you are unsure where CRM sits in your wider bottlenecks, you can use the free Value Driver Tree to see which workflows are currently draining margin before you commit to any pattern.

The four structural options you actually have

For a 10–100 person SME, your structural choice is usually between three HubSpot patterns and the status quo of doing nothing structured.

The rest of this article assumes you are moving from the manual pattern to one of the three HubSpot‑based ones. We will build and test each pattern separately, using small, illustrative record sets.

Definition: Deal pipeline: a sequence of stages that show where a potential sale (deal) is in your process, implemented using HubSpot deal pipelines [HubSpot, pipelines].

Pattern 1: Deal‑pipeline‑led CRM setup (sales‑first)

A deal‑pipeline‑led pattern treats deals as the primary record. Each deal represents a sales opportunity moving through stages. For many B2B SMEs with a clear sales motion, this is the cleanest starting point.

Applicable HubSpot capabilities

HubSpot explains that pipelines “help visualise your processes through stages, which are steps that signal where a record is in a process”, and that you can “create deal pipelines to track revenue” [HubSpot, pipelines]. Pipeline functionality for standard objects such as deals is available across all products and plans, with limits depending on subscription level.

For this pattern we rely only on:

• A single deal pipeline with a small set of stages.
• Board view to visualise deals.
• Manual ownership assignment.

Definition: Record owner: the user currently responsible for progressing a CRM record. In HubSpot, this is typically stored in an “Owner” property on deals, tickets or contacts.

Illustrative fixture: one simple B2B sales pipeline

Below is an illustrative mini‑dataset you can recreate in a HubSpot trial. Names and numbers are fictional.

• Pipeline name: New Business – Standard
• Stages: New enquiry → Qualified → Proposal sent → Verbal yes → Closed won → Closed lost

Illustrative records to create:

• Deal D‑1001 – "Website redesign – Acme Ltd" – Stage: New enquiry – Owner: Alice.
• Deal D‑1002 – "Retainer – Bright Retail" – Stage: Qualified – Owner: Bob.
• Deal D‑1003 – "Audit – City Finance" – Stage: Proposal sent – Owner: Alice.

Ownership and handoff rules

Keep rules deliberately simple:

• Rule 1: New deals are created in New enquiry and owned by the person who first spoke to the prospect.
• Rule 2: Only the current owner moves a deal forward between stages; a sales manager can move deals backwards after review.
• Rule 3: Any deal moved to Closed lost must have a “Loss reason” property filled.

Handoffs happen at agreed stages, for example notifying delivery when a deal moves to Proposal sent. At first, treat that notification as a manual step, not automation.

Definition: Board view: a Kanban‑style visualisation of a pipeline where each column is a stage and each card is a record, referenced by HubSpot in the context of managing records in a pipeline [HubSpot, pipelines].

Acceptance test: can you track three live deals today?

This illustrative acceptance test checks whether your team can reliably track three example deals in one day.

Steps (illustrative):

1. Create the three illustrative deals above in your pipeline.
2. Ask Alice to move D‑1001 from New enquiry to Qualified and update value and expected close date.
3. Ask Bob to move D‑1002 from Qualified to Proposal sent and add a short note with the next action.
4. Ask your sales manager to move D‑1003 from Proposal sent to Closed lost, adding a loss reason.

Pass conditions:

• All three deals are visible in board view with correct stages and owners.
• The manager can answer “Which deals might close this month?” using the pipeline alone.
• No one is confused about who owns each deal or what the next step is.

If these do not hold, the pattern may still be right, but your stage definitions or ownership rules need tightening.

Pattern 2: Shared‑service‑led CRM setup (support‑first)

A shared‑service‑led pattern makes tickets in a central workspace the primary record. This suits SMEs with a support desk, customer success or client services team handling a shared inbox.

Applicable HubSpot capabilities

HubSpot’s Help Desk tool is part of Service Hub Professional and Enterprise. Documentation states that you can “connect chat, email, form, calling, and Facebook Messenger channels to the help desk tool, which consolidates your support process into a single workspace” [HubSpot, help desk].

Key points for this pattern from the same article:

• Help Desk is available with Service Hub Professional or Enterprise.
• You need Account Access permissions to connect channels.
• During set‑up you choose a Ticket pipeline, Ticket stage and Ticket priority for new incoming tickets.
• Tickets can only be automatically routed to users with assigned seats [HubSpot, help desk].

Definition: Help Desk: HubSpot’s consolidated workspace for managing tickets created from connected channels such as team email, chat, forms and supported messaging apps [HubSpot, help desk].

Illustrative fixture: shared support email into a ticket pipeline

This illustrative setup assumes you have a shared support email like support@yourcompany.co.uk.

• Ticket pipeline: Support – General
• Stages: New → In progress → Waiting on customer → Resolved → Closed

Illustrative records to simulate:

• T‑2001 – "Invoice query – March" – from client A → becomes a ticket in New.
• T‑2002 – "Website down" – from client B → becomes a ticket in New.
• T‑2003 – "Change of contact details" – from client C → becomes a ticket in New.

Ownership, routing and handoff rules

Using the documented defaults and assignment options [HubSpot, help desk]:

• Rule 1: All new emails create tickets in Support – General with stage New and medium priority.
• Rule 2: Auto‑assign tickets round‑robin between two support agents who both have seats.
• Rule 3: Only the assigned owner may move a ticket to Resolved.
• Rule 4: A team lead reviews tickets in Resolved once per day and moves them to Closed.

The ticket’s stage and owner history are your handoff evidence.

Definition: Ticket pipeline: a set of stages representing the lifecycle of a support or service request, implemented using HubSpot ticket pipelines.

Acceptance test: do three emails become owned tickets?

This illustrative test checks whether your support pattern actually creates and routes tickets as expected.

Steps (illustrative):

1. Confirm you have Service Hub Professional or Enterprise and appropriate permissions on one admin user.
2. Connect your team email support@… as a channel to Help Desk, following HubSpot’s documented steps.
3. On “Set up ticket defaults”, select:
   • Ticket pipeline: Support – General.
   • Ticket stage: New.
   • Ticket priority: Medium.
4. Choose an assignment option that auto‑assigns tickets to two agents with seats.
5. From three different external email addresses, send the three illustrative enquiries to support@….
6. In Help Desk, verify:
   • Three tickets exist in pipeline Support – General, stage New.
   • Each has been assigned automatically to an available agent.
   • Email conversations appear within the ticket record.
7. Ask each agent to reply from Help Desk and move their ticket through In progress to Resolved.

Pass conditions:

• New emails reliably become tickets with the defaults you set.
• No ticket remains unassigned unless you intentionally allow it.
• Agents can work from Help Desk without hunting through personal inboxes.

If auto‑assignment fails because of seat limits, the pattern may still fit, but you must accept manual assignment or adjust licences.

Pattern 3: Individual‑inbox‑led CRM setup (relationship‑first)

An individual‑inbox‑led pattern accepts that most work still happens in personal email. The CRM’s main job is to log and send one‑to‑one emails from contact or deal records, while ownership and stages remain lightweight.

This can suit partner‑led consultancies or professional services where each senior person manages their own small portfolio of relationships.

Applicable HubSpot capabilities

HubSpot distinguishes individual work emails from team emails. Documentation states that you can “connect an individual work email to HubSpot to send one‑to‑one emails from the CRM, log emails to the CRM, send sequences emails, and use HubSpot sales tools in your email inbox”, and that an individual work email “is used for one‑to‑one communication and should be unique to you” [HubSpot, connect an individual work email].

It also notes:

• You can connect Gmail, Microsoft Outlook, Microsoft Exchange, or other email accounts using IMAP.
• Users with a View‑Only seat cannot connect their individual work emails [HubSpot, connect an individual work email].

Definition: Individual work email: a unique mailbox for one user, connected to HubSpot for one‑to‑one communication, email logging and use of CRM email tools [HubSpot, connect an individual work email].

Illustrative fixture: partner‑owned opportunities with email logging

In this illustrative setup:

• Each fee‑earner connects their individual work email.
• You create a simple two‑stage deal pipeline: Open and Closed.

Example records for partner "Priya":

• Contact C‑3001 – Jane Smith – jane.smith@acme.co.uk.
• Deal D‑3001 – "Advisory retainer – Acme" – Stage: Open – Owner: Priya – Associated with Jane.

Ownership and behaviour rules

Because ownership is clear at the contact or deal level and work is done via individual inboxes, the rules can be light:

• Rule 1: Whoever owns the key relationship owns the contact and any associated deals.
• Rule 2: Partners send and reply to emails from within HubSpot’s CRM record view, using their connected individual work email, so emails log automatically.
• Rule 3: When a deal is finished, the owner moves the deal from Open to Closed and adds a short summary note.

If a relationship passes from one partner to another, you change the owner on the contact and deals; past email remains logged.

Acceptance test: does logging work without changing habits?

This illustrative test checks whether partners are comfortable working from within HubSpot without changing their day‑to‑day email tools.

Steps (illustrative):

1. Ensure that each partner has a non‑View‑Only seat so they can connect their individual work email.
2. Ask one partner (for example Priya) to connect her work email following the documented workflow for her provider.
3. Create contact Jane Smith and deal D‑3001 as above.
4. From within the contact record, Priya sends a short test email to Jane.
5. When Jane replies, check that:
   • The reply appears on the contact’s timeline in HubSpot.
   • The email thread is visible from the associated deal.
6. Priya then moves D‑3001 from Open to Closed and adds a short summary note.

Pass conditions:

• Partners can keep using their usual provider (for example Outlook) while HubSpot logs the thread.
• Relationship context is available when viewing contacts or deals, without needing a shared inbox.
• There is no confusion between individual work email and team email usage.

If users find logging intrusive or key people cannot connect their inboxes due to seat limits, this pattern may not fit without licence changes.

Trade‑offs, risks and limitations of these HubSpot CRM patterns

None of these patterns is perfect. Each has limits you should recognise before committing.

1. Deal‑pipeline‑led pattern

   • Strength: Clear view of revenue opportunities and next steps.
   • Risk: If you over‑complicate stages, the board becomes noise. HubSpot notes that multiple pipelines are useful when processes truly differ, such as a direct‑to‑consumer sales process versus a wholesale process [HubSpot, pipelines]. Copying that complexity into a small SME can backfire.
   • Operational cost: Someone must own stage definitions and review stuck deals weekly.

2. Shared‑service‑led pattern

   • Strength: Centralised visibility of support, consistent handling of a shared inbox.
   • Risk: Requires Service Hub Professional or Enterprise, Account Access permissions and enough paid seats for auto‑assignment [HubSpot, help desk]. Under‑licencing leads to unassigned tickets or manual workarounds.
   • Operational cost: You need a queue owner watching New and Resolved stages every day.

3. Individual‑inbox‑led pattern

   • Strength: Minimal behaviour change for senior staff who live in email; easier adoption.
   • Risk: Weak central reporting if people never use stages; risk of mixing up personal and team email if boundaries are unclear. HubSpot explicitly expects individual work emails to be unique to one person [HubSpot, connect an individual work email].
   • Operational cost: You rely on individuals to keep deals updated; there is little structural enforcement.

Definition: Acceptance test: a small, pre‑defined set of actions and expected outcomes used to decide whether a system setup is acceptable for real‑world use.

Across all patterns, a recurring risk is drawing the wrong conclusion from a failed trial. A failed acceptance test means “this configuration does not yet work for us”, not “HubSpot cannot do this”. Documentation excerpts are partial; unknowns need checking against full docs or support.

When these CRM examples do NOT apply or can backfire

These three patterns assume a relatively straightforward SME structure and modest licence footprint. There are clear cases where you should be cautious.

1. You need complex custom objects or advanced data models
   HubSpot notes that an Enterprise subscription is required to manage custom object pipelines, and a Professional or Enterprise subscription is required to manage lead object pipelines [HubSpot, pipelines]. If your process genuinely revolves around non‑standard entities (for example, equipment, properties or multi‑party projects), these simple examples are too limited as a design.

2. Your workflows are compliance‑critical
   In heavily regulated sectors where every interaction must follow strict scripts and approvals, the lightweight acceptance tests here are insufficient. You will need more rigorous workflow design, risk analysis and governance. For that, start with our guide on AI as a control layer and then map CRM into that structure.

3. Your process is not defined at all
   If you cannot write down your own stages or ticket types, any pattern becomes a dumping ground. In that situation, first stabilise your manual process. Our workflow automation guide explains how to map a process before you automate or encode it in a CRM.

4. You expect CRM alone to fix lead quality or volume
   These patterns answer how to structure and test HubSpot, not how to generate or qualify leads. If your real issue is demand generation, use one of these patterns as plumbing, then apply the dedicated AI lead generation engine plan on top.

If any of these constraints fit you, treat this article as a sketchbook rather than a blueprint. Your next step is likely a more tailored architecture exercise, not just switching patterns.

Worked examples: three illustrative acceptance tests in practice

To make the patterns concrete, here are three short illustrative scenarios. All data and outcomes are fictional and intended purely as examples.

Example 1 – Deal‑pipeline‑led: qualifying three web leads in a day

Inputs (illustrative):

• Three new web enquiries arrive on Monday:
  "SEO project – Northshore Digital", "Ongoing PPC management – Lumen Retail", "One‑off audit – Greenfield Finance".

Steps (illustrative):

1. SDR Sam creates three deals in the New enquiry stage and logs a short note on each after initial contact.
2. Based on fit, Sam moves two deals to Qualified and leaves one in New enquiry pending more information.
3. The sales manager reviews the pipeline board and moves one Qualified deal to Proposal sent after confirming scope.

Acceptance check:

• At day‑end, every enquiry is either in Qualified or has a clear next step noted.
• The manager can answer “How many qualified deals did we get today?” from the pipeline alone.

If either fails, tighten the rules or stage definitions before scaling.

Example 2 – Shared‑service‑led: testing Help Desk auto‑routing

Inputs (illustrative):

• Two support agents, Emma and Tariq, each with Service Hub seats.
• One shared inbox support@… connected to Help Desk with round‑robin routing.

Steps (illustrative):

1. Three customers email support@… about a password reset, a billing error and a feature request.
2. Help Desk creates three tickets in the New stage and auto‑assigns them alternately to Emma and Tariq.
3. Each agent replies from Help Desk and moves their ticket through the appropriate stages.

Acceptance check:

• No ticket remains unassigned by the time agents log in.
• At least one ticket reaches Resolved with a clear resolution note the same day.

If auto‑assignment fails due to seat issues, you either increase seats or accept a manual assignment workflow.

Example 3 – Individual‑inbox‑led: logging high‑touch partner emails

Inputs (illustrative):

• Partner Olivia connects her individual work email (for example Outlook) to HubSpot.
• She has three key accounts she emails weekly.

Steps (illustrative):

1. Olivia sends her usual check‑in emails to each contact from inside their HubSpot contact records.
2. Over the week, each contact replies once.
3. On Friday, Olivia reviews each contact’s timeline: emails and replies are logged, and she adds tasks based on upcoming meetings.

Acceptance check:

• Olivia has a richer, single view of each relationship in HubSpot without feeling forced to abandon her normal email tool.

If she continues to ignore HubSpot and work entirely from her native inbox, an individual‑inbox‑led pattern is not delivering value yet; you may need stronger pipeline discipline instead.

What to explore next

If you want help turning one of these patterns into a concrete 6–12 week plan, you may find these pages useful:

• Understand how our automation projects are structured → AI Automation Services
• See how structured workflows play out in real businesses → Client Success Stories
• Learn who is behind SIMARA AI and how we work with SMEs → About SIMARA AI
• Ready to discuss your CRM pattern? → Contact SIMARA AI

Sources & Further Reading

• HubSpot Knowledge Base – Set up and manage object pipelines (accessed 21/10/2026)
• HubSpot Knowledge Base – Connect channels to help desk (Service Hub Professional & Enterprise, accessed 21/10/2026)
• HubSpot Knowledge Base – Connect an individual work email (accessed 21/10/2026)
• For layering AI on top of your CRM once it is stable: AI Sales Funnel Automation for UK SMEs

If you want a second pair of eyes on which pattern fits your team and how to test it without wasting weeks, you can Contact SIMARA AI for a structured review.