Skip to content
Digitizing CRM· Part 7 of 7

A 90-Day Plan to Roll Out CRM in Your Business

Short answer

A CRM can go live in 90 days in 3 blocks of 30: records, then channels and leads, then service and consent. The seventh and final part of Digitizing CRM gathers the exercises of the six earlier parts into one plan, splits the owner's decisions from the sales or service lead's, and sets a date to switch off the side lists.

Origami Team

Editorial Team · · 7 min read

Share on WhatsApp
Like what we publish? Pin Origami as a preferred source on Google.Add as a preferred source on Google
A 90-Day Plan to Roll Out CRM in Your Business

Rolling out a CRM in 90 days is realistic if you split the work into 3 blocks of 30 days in the right order: first clean and merge the customer records and set who sees what, then bring every channel into one inbox and every open lead into a pipeline, then add service tickets and consent records before you switch off the side lists. This seventh and final part of Digitizing CRM gathers the exercises from the six earlier parts into one plan, and states which decisions belong to the owner and which belong to the sales or service lead. If you have not chosen a system yet, start with our guide to choosing a CRM for a Saudi business, then come back to this plan, because it works with whichever system you pick.

Before day one: three decisions for the owner

The plan does not start with software but with decisions only the owner or general manager can make. If they are postponed, the plan stalls halfway:

  • Who owns the project: one named person, usually the sales or customer service lead, with dedicated time every week and the authority to ask any salesperson or branch for their customer lists.
  • The cut-off date: the day the system becomes the only place for customer data; after it, no new customer lives only in a salesperson's phone or a side spreadsheet. Set the date now and announce it, even if it falls at the end of the 90 days.
  • Who sees and who exports: the short list of names allowed to see every customer and to export lists. Customer data is personal data, and Article 19 of the Personal Data Protection Law requires the controller to take the organizational, administrative and technical measures that protect it, including when it is transferred.

Everything else is an operational decision for the project owner and their team: field formats, stage names, ticket categories and message templates.

Days 1 to 30: one customer record and its permissions

Everything after this block reads from the customer record, so it comes first. Repeat the exercises of the first two parts at full size, not on a sample:

  • Week one: the exercise from part one on your last 20 inquiries, to see where customers get lost today, plus a list of every phone, file, group and notebook that holds customer data.
  • Weeks two and three: gather every list into one file, then merge duplicates as in part two: one record per customer with a name, a number, the relationship owner and the source. Every conflict between two copies is settled before the move, not after.
  • Week four: load the clean records into the system, apply the permissions the owner approved, and lock the old files as read-only.

The cleaning method itself is in our article on cleaning data before the move from the Excel-to-system series. Test one thing before closing the block: Article 4 of the law gives customers the right to know, to access their data, to obtain a copy, to correct it and to request its destruction when it is no longer needed. Ask yourself how long it would take to answer such a request from the new record; if the answer is minutes, the record is ready.

Days 31 to 60: one inbox and a pipeline for open leads

Once the record is trusted, daily activity is attached to it:

  • The inbox: the door list from the part three exercise becomes your connection list. Every WhatsApp number, landline, website form and email address feeds one list, and every inquiry gets an owner, a status and a reply deadline your business sets and then measures.
  • The company number: customer conversations move to numbers the business owns, so a customer does not leave with an employee who leaves.
  • The pipeline: the open opportunities from the part four exercise go into the system at their stage, each with a dated next step. Any opportunity without one is either given a step or closed as lost with its reason.
  • The hand-off to the quote: a won opportunity ends in a quote or sales order. The money side is covered in our sales-to-cash series, so here you only agree where the hand-off happens and who receives it.

Here the sales lead decides the stage names and routing rules, while the owner decides one thing: which inquiries and opportunities a manager must see, such as large customers or a lead with no reply after the deadline.

Days 61 to 90: service tickets and consent, then switch off the side lists

The last block covers the customer after the sale, and ends by switching off the old habits:

  • Service tickets: the complaint categories from the part five exercise become the ticket categories, every ticket gets an owner, a priority and a target time, and it closes only on the customer's confirmation.
  • Consent: the part six exercise on your broadcast lists becomes consent fields in every record, with status, date, source, purpose and channel. Article 25 of the law requires the recipient's consent before advertising material is sent to their personal contact details, and a clear way to stop receiving it.
  • Switching off the side lists: on the cut-off date, every broadcast group and customer file outside the system is archived as read-only, and any customer who arrives through an old door is added to the system, not to the side list.

The month after the switch needs close follow-up, as we explained in the first thirty days after the move: repeat the exercises of parts 1, 3 and 5 and compare the figures with what you measured at the start.

Who decides what

DecisionWho makes it
The project owner, the cut-off date and who sees and exports customer dataThe owner or general manager
Fields of the customer record and how duplicates are mergedThe sales or service lead
Pipeline stages, routing rules and reply deadlinesThe sales lead
Ticket categories, priorities and target timesThe customer service lead
Message templates, their purposes and the consent each one needsThe project owner, with your lawyer where unsure
Exceptions above a manager's authority, such as a large customer's escalationThe owner or general manager

The Origami view

We are a technology company that builds custom systems, apps and integrations, and when we build a customer relationship system we follow this same order: the record first, then the inbox and the pipeline, then tickets and consent. A system built on top of duplicate and scattered records only moves the problem to a nicer screen.

We start from the exercises of the six parts themselves rather than a ready-made feature list, because they show where your customers really get lost, then we build what is missing and connect the channels and the systems you already use. That is how we build our services around how a business works, while legal questions are settled by the text of the law, SDAIA or a lawyer.

Conclusion: the end of the series

Digitizing the customer relationship is not buying software, it is an order of work: one record everyone knows, then every channel in one inbox and every lead in a pipeline, then tickets that close with the customer's confirmation and messages that go only to those who agreed. This part completes the series, and you can return to any part in the knowledge hub when you reach its stage in the plan.

Sources

This article explains the mechanism and is not legal advice; confirm your case with SDAIA or a lawyer.

  • #Make the Most of Tech
  • #Digitizing CRM: From First Inquiry to Repeat Customer
  • #CRM
  • #Customer Service

Frequently asked questions

How long does it take to roll out a CRM in a small or mid-size business?

This plan splits it into 90 days in 3 blocks of 30: the customer record and its permissions, then one inbox and the pipeline, then service tickets and consent. The real duration depends on how many scattered lists you have and the state of their data, so start with the exercises of the first parts to size the work.

Where do I start a CRM rollout?

With the customer record, not the software: gather every list from phones, files and groups, merge duplicates into one record per customer, and decide who sees the data and who exports it. Everything after it, the inbox, the pipeline and the tickets, reads from that record.

Which decisions must the owner make personally?

Three before day one: who owns the project, the date the side lists are switched off, and who sees and exports customer data. Then exceptions above a manager's authority, such as escalating a large customer. Stages, categories and reply deadlines are decisions for the sales or service lead.

When do I switch off the old WhatsApp groups and customer files?

On the cut-off date the owner announces at the start, after records, channels, tickets and consent have moved into the system. The old lists are archived as read-only, and any customer who arrives through an old door is added to the system.

Have a project in mind?

We build custom systems, apps and websites for your business. Tell us your idea and we will give you a straight answer on it.

See our services

Newsletter

New articles and series, in your inbox.

Follow Origami in Google

Pin Origami as a preferred source and our articles will surface first for you in Google Search and Top Stories.

Add as a preferred source on Google