InsightsCRM Integration & Setup

CRM specification example: section by section with ready wording

A filled-in CRM specification for a fictional B2B company: what each section looks like, which wording can be checked and where people most often go wrong

Vitalii Kopach7 min

An empty template shows which sections you need. An example shows what the filled-in text looks like. Below is a shortened specification for a fictional company that sells B2B services through managers. It is an illustration, not a document from a real AKORDO client: replace the stage, role and field names with your own. The CRM specification template gives the empty structure with notes on each section, and the article on the CRM specification explains why you need this document before choosing a system.

How to read the example

Each section has two blocks: what the specification says and why the wording works. The mark of a working specification is that every item can be checked after launch with a plain yes or no.

1. Goal and boundaries

In the specification: "The company replaces spreadsheets and managers' personal notes with a single database of clients and deals. All enquiries from the website, telephony and the messenger are recorded in the CRM. The head of sales sees deals by stage without asking a manager. This is the first CRM implementation, no migration from another system is needed."

Why it works: it names the problems that can be solved and says this is a new implementation. A complex integration with the accounting system is left out of scope, and the text says so directly: "Data exchange with the accounting system is not included, it is a separate stage."

2. Business process

In the specification: "Process 'New enquiry'. It starts when a client leaves a request on the website or calls. Step 1: the system creates a client card and a deal. Step 2: the responsible first-line manager contacts the client within one working hour. Step 3: the manager fills in the need and the source. Condition to move on: the need is filled in. If the condition is not met within a working day, the deal appears in the head of sales' report."

Why it works: there is a trigger event, an owner, a transition condition and a consequence of not meeting it. The other processes are described the same way: managing a deal through to payment, handing over for delivery, repeat work with a client, refusal.

3. Roles and permissions

RoleSeesEditsExports
First-line managerOwn recordsOwn dealsNothing
Key account managerOwn areaOwn dealsOwn records
Head of salesThe whole databaseDepartment deals and reference listsThe whole database
AccountingDeals with an invoiceBilling detailsNothing

Why it works: the export right has its own column. It is the most expensive access mistake and is rarely written down in advance.

4. Pipeline and stages

In the specification: "Pipeline 'Service sales'. Stages: New enquiry, Need clarified, Proposal sent, Approval, Invoice issued, Paid, Closed without payment. A move to 'Proposal sent' is possible only if the proposal file is attached and the amount is filled in. A deal that stays at a stage longer than the agreed time appears in the head of sales' report."

Why it works: stage names describe a completed action, and the move depends on an objective condition. The manager does not decide by mood, so the report counts the same things.

5. Client card and fields

FieldWhen it is requiredWhich decision it supports
ContactNew enquiryReplying to the client
Enquiry sourceNew enquiryAssessing channels
Deal amountProposal sentForecast and priority
Reason for refusalClosed without paymentWorking with repeat refusals
Billing detailsContract preparationIssuing an invoice

Why it works: every required field has a reason. A field for which no decision can be named does not make it into the specification.

6. Integrations

In the specification: "Website form: into the CRM, creates a card and a deal, passes name, phone, email and the page of the request. Telephony: both ways, the call is attached to the card, the matching key is the phone number. Messenger: into the CRM, the conversation is stored in the card. If an exchange fails, the head of sales sees the error."

Why it works: each integration states the direction, the fields, the key and who finds out about a failure. The matching key stops the system from creating a second record instead of updating the first.

7. Acceptance criteria

In the specification: "A test request from the website form creates a card and a deal at the 'New enquiry' stage with the correct source. A call to the test number is attached to the card. The 'Deals by stage' report opens with real data. The head of sales accepts the work against this list. Anything not on the list is a new task, not a fix."

Why it works: acceptance is tied to scenarios that can be run, and the line between a fix and a new task is written down before the work starts.

Common mistakes in a specification

  1. It describes the desired system instead of the actual process. Mark the desired state separately.
  2. It uses wording like "fast" and "convenient" that cannot be checked.
  3. It names stages without transition criteria.
  4. It lists an integration without a record-matching key.
  5. It has no acceptance criteria, so nobody can declare the work done.

What to do with this example next

Copy the structure into your own document and replace the fictional processes with real ones. If you want a ready, agreed document built on your processes, the AKORDO catalogue lists business analysis and a specification at $400-800 and 2-3 weeks. CRM licences are paid separately. The service is described on the page CRM selection and specification, and the article on how much CRM implementation costs gives the wider budget picture.

Questions about the example

Can I use this example as a ready specification?

No. It illustrates the structure. Processes, roles, stages and fields have to reflect how you actually work, otherwise the system gets configured for a fictional company.

How detailed should a specification be?

Detailed enough for an outside specialist to complete a step without asking. If an item cannot be described without the phrase "it depends", that is a place for a separate decision.

Who writes the specification?

One person fills in the document so it has one logic, and the source material comes from conversations with managers and the head of sales.

Want to check your document? Book a free AKORDO consultation.