121 CRM guide · CRM pricing models

CRM pricing models: assess the choice before you commit.

This is an operating question, not a request for more CRM fields. This guide helps a small team compare time, setup, usage, support, change and exit costs against a realistic operating baseline. It uses a bounded customer journey, clear ownership and evidence people can review, keeping CRM pricing models grounded in real work rather than treating it as another abstract CRM ambition.

Subscribe to 121 CRM Seller, billing and cancellationExplore all practical guides

Customer Thread

CRM pricing models in a working decision

Illustrative example

Define the question
Write down what the team needs to improve or decide about CRM pricing models.
Observe the work
Use scored requirements, a representative demonstration and written commercial and configuration boundaries, not assumptions.
Agree the boundary
Record how CRM pricing models may be supported by the CRM and where a person must decide.
Human decision
Test and review
Check whether the shortlisted option completes agreed scenarios without hidden manual work or unsupported assumptions, then revise the method.

Fictional example using Northstar Joinery; adapt the method to your own customers, responsibilities and configuration.

Fictional working example

See CRM pricing models in context

This code-built CRM pricing models illustration shows how the decision could appear inside a working CRM, demonstrating information and responsibility rather than a fixed account configuration.

121 CRM · Control responsibilities

Control questionOwnerNext check

Who can export customer data?CustomerConfirm

Who changes workflow permissions?Agreed scopeRecord

What happens at account closure?SharedDefine

Which suppliers process data?SharedCheck

Illustrative exampleIllustrative governance pattern. It does not assert that a specific technical control or certification is in place.

CRM building blocks

Connect the advice to day-to-day CRM work.

These are the practical tools behind the guide, with enough context to decide where they can help and where people still need to take responsibility.

Capability 01

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 use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 02

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 use it: Limits day-to-day access to the work a person actually needs to perform.
Plan for: Availability and control depth depend on agency plan, role and current account configuration.
Your team owns: An authorised administrator must review, approve and audit material changes.

Capability 03

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 use it: Supports controlled migration and operational extracts when the data is prepared and reconciled.
Plan for: 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.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 04

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 use it: Turns a repeatable customer process into a visible, reviewable flow.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Start with the decision

Start with the decision behind CRM pricing models

The useful aim is to compare the decision against the work the business genuinely needs to perform. For CRM pricing models, 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 compare time, setup, usage, support, change and exit costs against a realistic operating baseline. 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.

Human review point

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 practical method

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 pricing models 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: compare time, setup, usage, support, change and exit costs against a realistic operating baseline.

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: compare time, setup, usage, support, change and exit costs against a realistic operating baseline.

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: compare time, setup, usage, support, change and exit costs against a realistic operating baseline.

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: compare time, setup, usage, support, change and exit costs against a realistic operating baseline.

Review the method

Make the next decision visible

Use the second view to inspect ownership, exceptions and the evidence the team should review before extending this buying decision.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Worked example

How Northstar Joinery could apply the guide

Northstar Joinery is a six-person joinery business. The team tests CRM pricing models on one bounded customer journey, using fictional data and the existing working practice as its comparison point.

The starting question

Northstar Joinery needs to compare time, setup, usage, support, change and exit costs against a realistic operating baseline. 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

Official product material can evidence a general capability, but it does not establish that the capability is enabled or included in a particular 121 customer account for this CRM pricing models trial. The trial can show whether the method is clearer for Northstar Joinery; it cannot promise revenue, growth or a universal result.

Limits and review

Limits, warning signs and review points

The CRM pricing models 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

Official product material can evidence a general capability, but it does not establish that the capability is enabled or included in a particular 121 customer account for CRM pricing models. Recheck the providers, permissions, retention and communication rules supporting this buying decision when the scope changes.

Human review point

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.

Questions about this page

Useful answers, without the sales fog.

1. What decision should come first in CRM pricing models?

Start with the question that changes a customer action or handover: how will the team compare time, setup, usage, support, change and exit costs against a realistic operating baseline? Give this buying decision an owner and test it against a few current examples before choosing more configuration.

2. What evidence is useful for reviewing CRM pricing models?

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.

3. Where should automation stop when handling CRM pricing models?

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.

4. What should trigger another review of CRM pricing models?

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.

Read all CRM questions

Continue the journey

Guides Free versus paid CRM Customer management

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing