A CRM requirements template, as usually downloaded, is a feature checklist: lead scoring, yes or no; mobile app, yes or no; two hundred rows. Every CRM on the market ticks most of them, and a partner can tick every one for Zoho CRM without learning a single thing about how your business runs. The template produces a configuration quote, the configuration is done, and six months later the system does not match the business because nobody asked the questions that would have told the partner what the business is.

This template asks those questions. There are thirty, in six groups, in the order a build needs them, and each one is a decision with an owner. Most of the owners are you. That is the point: a requirement is a decision the business has made, and a feature is a thing the software does whether or not the decision was made.

Group one: the nouns. Yours to answer.

These five questions name what your business is made of. Only you can answer them, and every later group is built on the answers.

  1. What is a customer? A company, a person, a site, a household, a parent with subsidiaries? The answer decides the account structure and every report that groups by customer afterwards.

  1. What is a deal? One sale, a renewal, a project, a subscription, a load? If you sell more than one kind of thing, say so now, because each kind is a pipeline with its own stages.

  1. What is a product or service line, and does a deal carry line items or a single amount? This decides whether quoting lives in the CRM.

  1. What do we deliberately not track here? Inventory, tickets, projects, invoices. Name the system that owns each and the CRM will connect to it instead of absorbing it badly.

  1. Which fields are facts and which are opinions? Revenue is a fact. Lead quality is an opinion. The facts get validation and the opinions get a date so you know how stale they are.

Group two: the doors. Yours to state, ours to build.

  1. Where do records come in? Web forms, imports, the inbox, the phone, the connected systems, hand entry. List every door.

  1. At each door, what is required before a record is allowed to exist? The minimum field set per door, because a form and an import have different minimums.

  1. What makes two records the same record? The duplicate rule, per module, stated as fields: email alone, or email plus company, or phone.

  1. What happens to a bad record at the door? Rejected, held for review, or created and flagged?

  1. Who owns a new record, by what rule? Territory, product, round robin, or the person who created it.

Group three: the process. Yours to decide, in a workshop.

  1. What are the stages of each pipeline, and what has to be true for a deal to leave each one? This is the sales process as a Blueprint, and it is the question most companies have never answered out loud.

  1. Which stage transitions need a document, an amount, a date or a contact to exist first?

  1. What can a rep do without asking, and what waits for a manager? Discounts above a percentage, stage moves past a threshold, changes to closed deals.

  1. What does the system do on its own? When a deal closes, when a lead sits untouched, when a renewal approaches. Each is a small policy; list them.

  1. What does lost mean, and what are the reasons? A closed list of lost reasons is the difference between a report and a guess.

Group four: the people. Yours to sign.

  1. Who are the kinds of user? Rep, manager, support, finance, owner, partner. Each is a profile.

  1. For each kind, what may they see, and what may they change? Deal amounts for support, other territories for reps, closed deals for anyone.

  1. Who approves what? The named approver per rule in question thirteen, by role not by name, so it survives a resignation.

  1. What does each kind of user see when they log in? The home screen, the views, the fields on the record. A rep and an owner should not open the same screen.

  1. Who administers the system after go-live, and how many hours a week is that person given? A CRM with no named administrator is a CRM that decays.

Group five: the connections. Yours to name, ours to design.

  1. Which systems stay, and which does the CRM replace? The accounting system, the help desk, the website, the phone system, the marketing tool, the inventory system.

  1. For each system that stays, which direction does data flow, and which system is right when the two disagree? One answer per connection. This is the decision that is hardest to undo.

  1. Which system issues the customer id, and how does the other receive it? Without this, every cross-system report puts one customer on two rows.

  1. What comes across from the old CRM, how far back, and who signs off that the imported list is the customer list?

  1. What is left behind, on purpose? Every migration list starts too long. Name what stays in the archive.

Group six: the surface and the measure. Shared.

  1. What are the five reports the owner reads weekly, by name, with the fields each needs? Reports designed after the build are reports the data cannot answer.

  1. What does the dashboard show a rep on Monday morning, and what does it show a manager?

  1. What happens on the mobile app, and what is deliberately desktop-only?

  1. What does go-live look like? All users on one day, or a pilot team first, and what is the criterion for the second wave?

  1. What will be true ninety days after go-live that is not true today, in one sentence, with a number? If this question has no answer, the build has no finish line.

How to use the thirty.

Answer the questions in groups one and three before you talk to a partner, in a room with the people who disagree about them, and write the answers down. Those are the decisions that no partner can make for you and that a configuration quote will silently make by default. Then hand the list to the partner, and read the proposal against it. A proposal that has a line for every feature and no workshop for questions one, two, eleven and twenty-two is a configuration quote. A proposal that schedules those questions before the configuration that depends on them is an implementation, and the difference is the subject of our guide to choosing a Zoho implementation partner.

The thirty are not exhaustive and they are not meant to be. They are the decisions that change what gets built. The two hundred tick boxes can wait, and most of them will turn out not to matter once the thirty are answered, because the general discipline of gathering requirements as decisions rather than features applies to a CRM exactly as it applies to custom software.

This list is the first workshop of our implementation, and you can run it without us. Discovery is no-risk: we sit in the room for the thirty, write the answers into a design, and you pay only if you go ahead.

Find out what one connected Zoho system would change in the way you run.

In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.

Book the no-risk discovery

More on the same problem:

Not yet on Zoho, or already there?

Start a Zoho One trial through our sign-up, or tag us as your Zoho partner for free consulting time every month.

Where we're not the right answer

We'll tell you if we're a fit. If we're not, we'll tell you that too.

  • Your current stack works and nobody wants to change it
  • You want licences resold at a discount and nothing else
  • Your internal team owns the operating model and is not handing it over
  • You want hours of configuration work and nothing run for you: that is on our services pages, and it is not a managed solution
How we start

Most of our best clients come to us with a feeling, not a plan.

"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.

Talk to us

Have a question about this?

Say who you are and ask. A person replies within one business day.

A new client, or thinking about becoming one
What are you looking for?
An agentic solution (AI OS) is licensed and sold with managed services. An integrated solution is built for a professional services fee. A Service is professional work, done by the hour, the month or the project. Not sure yet is a fine answer.

Agentic solutions (AI OS)

Integrated solutions

Services

Platforms You Use or Are Considering

Your details are never shared or sold.