Twelve Decisions, Not Twelve Features.

When a company hires a Zoho implementation partner, the proposal usually lists features. Lead management. Pipeline. Workflows. Reports. Integrations. It reads like a product brochure, and it should not, because the product already has those features. What you are buying is a set of decisions about how your business will run inside them. We count twelve. They come in an order, each one depends on the ones before it, and each one is made by a named person, some by us and most by you. This video is the list, so you can hold any proposal, including ours, against it.

Everything on screen is a mock demo of Zoho CRM with sample data. Six minutes, twelve decisions. The first three decisions are about nouns. One: what is a customer? A company, a person, a site, a household? Zoho CRM ships with accounts and contacts, and whether a dental group with nine locations is one account or nine is a decision that changes every report afterwards. Two: what is a deal? A single sale, a renewal, a project, a load? The deal record and its stages have to describe the thing you actually sell, and most companies sell two or three different things.

Three: what do we not track here? The decision to keep inventory in the inventory system and support tickets in the help desk, and connect them, rather than pull everything into the sales system, is made now or paid for later. These three are yours. We ask the questions; you answer them. These three take the longest and cost the least, which is why they get skipped. A configurator cannot make them for you, and a good partner will not try; they will ask until the room agrees, and write the answer down where the next decision can read it.

Four: where do records come in, and what happens to a bad one at each door? The web form, the import, the connections from other systems. Each gets a required-field list and a duplicate rule. Here is the form's duplicate check, which is the decision that a returning visitor updates a record rather than creating a second one. Five: who owns what? Assignment rules decide which rep gets which lead, by territory, by product, by round robin. The rule is ours to write; the policy is yours to state. Six: what has to be true before a deal moves?

That is the sales process written as a Blueprint, and it is the decision most companies have never made out loud. We run a workshop for it, because the answer is in four people's heads and they disagree. Seven: who sees what? Profiles and roles. Zoho ships two profiles. A company of thirty needs four or five, and the decision about whether support may see deal amounts is a business decision that we write down and you sign. Eight: what does the system do without being asked? Workflows: when a deal closes, create the onboarding project; when a lead sits untouched for five days, tell the manager.

Each one is a small policy. The list is short at first and should stay short. Nine: what has to wait for a person? Approval processes: discounts, refunds, stage moves past a threshold. This is the same control that governs an agent later, so it is worth getting right the first time. These three are written by us from decisions you make in one afternoon. Ten: what comes across from the old system, and what is left behind? Every migration we have done started with a list that was too long.

The decision is which records, how far back, and who signs off that the imported customer list is the customer list. Eleven: which systems connect, in which direction, and which one is right when they disagree? The accounting system, the help desk, the inventory system, the website. Each connection is a decision about the system of record, and it is the decision that is hardest to undo. Twelve: what does each person actually see when they log in? That is the custom skin: one permissions-driven navigation, built with Zoho's own customisation tools, so a rep, a dispatcher and an owner each move through their own workflow without knowing which Zoho application is underneath.

It is the last decision because it depends on all the others. Decision eleven is the one we would defend hardest if a client wanted to cut the engagement short. A connection built with no decision about which system is right is a connection that will quietly make the decision for you, record by record, until the two systems are both wrong in different ways. Here are the twelve on one page, with the column that matters: who decides. Eight of the twelve are yours. Four are ours, and those four are configuration, which is the part the brochure was selling.

Hold a proposal against this page. If it has a line for every feature and no workshop for decisions one, two, six and eleven, it is a configuration quote, and the eight decisions will be made by default, by whoever configures first. If it schedules the decisions before the configuration that depends on them, it is an implementation. We have a separate video on the kinds of partner who sell each. This page is how you tell which one you are reading. An implementation is a list of decisions, not a list of features, and the list does not change much from one company to the next.

What changes is whether anyone makes them on purpose. We are CodeStringers, a Zoho authorised consulting partner. The link below is a no-risk discovery: we walk the twelve with you, and you pay only if you proceed.