InsightsCRM Integration & Setup

CRM technical specification template: the document structure

A ready CRM technical specification template: seven document sections, what to write in each and how to check it before handing it to a vendor

Vitalii Kopach8 min

This is a document outline you fill in yourself. The seven sections below can be copied into a plain text file and written in your own words: a technical specification formalises not the names of buttons in the software but the real operational processes of the company, the rules for moving a lead between stages, and the requirements for data. Why skipping this step is expensive is set out in CRM technical specification; the service, with its scope and timeline, is on the CRM selection and requirements page. A filled-in version is shown in the CRM specification example by section.

The rule the template is filled in by

Write what happens today and mark what you want separately. A document that mixes the actual process with the intended one is later read as a description of a system that does not exist yet, and the wrong thing gets configured.

The second rule: every statement has to be checkable. "The manager handles an enquiry quickly" cannot be checked; "an enquiry from the website is assigned an owner within one working hour" can.

Section 1. Why the company needs a CRM

One paragraph and three to five bullet points. What actually hurts now: contacts scattered across spreadsheets, personal notes and phone logs; deal logic held in individual employees’ heads; the owner unable to see where clients are lost. Write your own list, because it is what will define a finished job.

Separately: is this a first CRM or a move from an existing system. Those are different volumes of work.

Section 2. Business processes

A diagrammatic and descriptive representation of how a lead reaches the company, who handles it, which stages a deal passes on the way to payment, and what happens after the sale.

For each process, write down:

  1. The name of the process and the event that starts it.
  2. The actual steps, in order.
  3. The person responsible for each step.
  4. The data needed to carry the step out.
  5. The condition for moving to the next step.
  6. What happens when the condition is not met.

A minimum set of processes for a company that sells through managers: handling a new enquiry, running a deal to payment, handing the order to delivery, repeat work with a client, and handling a refusal.

Section 3. Roles and permissions

The list of job roles that work in the system and what each of them may do. A typical set: inbound representative, key account executive, sales director, accounting.

For each role, record three things separately:

  1. What they see: the whole database, their own records only, their own area only.
  2. What they edit: their own deals, other people’s deals, reference data and settings.
  3. What they export: nothing, their own records, the whole database.

The right to export the database is a line of its own on purpose: it is the most expensive access mistake and it is rarely stated in advance.

Section 4. Pipelines and stages

The list of deal stages for every pipeline. Each stage has a clear criterion for advancement rather than a manager’s impression.

For each stage, write down:

  1. A name that denotes a completed action, not a vague process.
  2. The criterion for advancement: an attached proposal document, say, or a confirmed deal valuation.
  3. Who owns the deal at this stage.
  4. The normal time a deal spends on the stage.
  5. What is done with a deal that is stuck on it.

Check the stage names separately. If one manager logs any conversation as a qualified lead while another does so only after clarifying the need, the report counts different things under one name.

Section 5. The customer record and its mandatory fields

The list of fields, determined by the agreed process and by the principle of data minimisation. Initial enquiries normally record only basic contact details, while commercial and invoicing credentials are added at the contract stage.

A table that is convenient to fill in:

FieldMandatory from stageWho fills itWhich decision needs it
Client contactNew enquiryInbound representativeReplying to the client
Enquiry sourceNew enquirySystem or managerAssessing channels
Deal valueProposal sentManagerForecast and priority
Reason for refusalClosed without paymentManagerWork on recurring refusals
Invoicing detailsContract preparationManager or accountingIssuing the invoice

Every mandatory field needs an answer in the last column. A field without one is removed: it is precisely the over-full form that keeps part of the information in parallel private notes.

Section 6. The integration map

The list of lead sources and external services the system has to exchange data with. Sources: website forms, telephony, messengers, email. External services: accounting software, delivery services.

For each integration, record:

  1. The direction of exchange: into the CRM, out of it, or both ways.
  2. The list of fields that travel.
  3. What the key is, by which two records are treated as the same client.
  4. How often the exchange runs.
  5. What happens when an exchange fails, and who finds out.

The point about the key is not a formality: without it an integration creates a second record instead of updating the first.

Section 7. Acceptance criteria and schedule

A finished specification is the basis for the contract with a vendor or an internal technical team. So the document ends not with a wish list but with a check.

  1. Exactly how a test enquiry will be traced from the website form to a created deal.
  2. Which reports have to open with real data at the point of acceptance.
  3. Who on the client side accepts the work, and against which items.
  4. The schedule and the people responsible on the client side.
  5. What counts as a small correction inside the work, and what counts as a new task.

The check before you hand it over

Go through seven questions. If any answer is no, the document is not ready.

  • Are the stage names stated unambiguously?
  • Does every stage have a criterion for advancement?
  • Does every mandatory field have a reason for being mandatory?
  • Is the actual process described separately from the intended one?
  • Does every integration have a key for matching records?
  • Are the acceptance criteria defined?
  • Are the schedule and the responsible people on the client side defined?

Choosing the system once the specification exists

With requirements documented, choosing a platform becomes a technical decision rather than a reaction to advertising. The criteria: how far pipelines, records and automations can be configured with the system’s standard tools and no custom programming; whether there are ready integrations with the telephony, messengers and banking services you already use; and the total cost of ownership, meaning not only the monthly per-user licences but also connecting phone numbers, server storage and technical support.

We work with any CRM: the one you already run, or the one you choose after a selection exercise. The systems we work with most often are listed on the CRM direction page.

What paid work adds to this template

The template gives you the structure. The work gives you a filled-in and agreed document about your own processes. In the AKORDO catalogue the output is an analysis of current and future processes, a comparison and choice of a CRM that fits your process and budget, a list of roles, permissions, pipelines, data and required integrations, and an agreed technical specification with an implementation plan, stages and owners. The indicative timeline is 2 to 3 weeks, and it depends on how many business areas, how complex the roles and how many integrations are planned.

Questions about the template itself

Does it work if a CRM is already running?

Yes. Sections 2 and 4 then describe the actual process and the actual stages, and you mark the intended changes separately. The same document is what a migration from another platform needs.

How detailed should the process description be?

Detailed enough for an outsider to carry a step out without asking. If a step cannot be described without the phrase "depends on the situation", that is a place for a decision rather than for more text.

Who in the company should fill it in?

The process description comes from interviews with the sales managers and with the head of sales: the first group knows where time is lost and where handovers get confused, and the second knows which metrics they want to track in reports. One person writes the document, so that it has one logic.

What should we do with the completed template?

Hand it to a vendor or an internal team as the basis for the contract. If you would like to review the document together first, send an enquiry and bring it to a free AKORDO consultation. If sales need to be put in order before the CRM, start with the sales department audit checklist.