Disclosure: I work at Skyfall Labs, an official Zoho Partner, so I have a commercial interest. The facts below are from Zoho's own help pages, linked at the end; advice is labelled as advice. Originally published on skyfallhq.net.
Agencies and consultancies often sign up for Zoho CRM, import a contact list and stop there, then wonder why it feels like a glorified address book. This post sets out what Zoho's own help pages say about the building blocks, and a suggested order for configuring them.
Start with the three core records
Zoho describes Accounts as "companies or departments you do business with", Contacts as "individuals (people) your company communicates with during business interactions", and Deals as "potential sales opportunities, connected to contacts and accounts". It explains that every deal is related to an account through an Account lookup field on the Deals module.
Practical advice: for a services firm, the account is usually the client company and the deal is a proposed engagement. Agree internally what counts as a deal (a scoped proposal, not every enquiry) before anyone starts entering them.
Define your sales stages
Zoho says each deal tracks the sales status and the estimated sales probability in each sales stage, and that a deal moves through the full process from a promising lead to being closed as won or lost.
Practical advice: write stages that match how your firm really wins work (for example enquiry, scoping call, proposal sent, negotiation) rather than keeping defaults nobody recognises. Stages people cannot map to their own routine are a common reason for stale pipelines.
Add a defined process with Blueprint
Zoho says a Blueprint "is designed to help you execute a business process in a well-defined, systematic manner". Its two building blocks are states and transitions: a state is the condition a record is in at a specific time, and a transition is a link between two states that sets conditions and actions a record must meet to move on. In a transition's During tab, each action can be marked mandatory or optional.
Zoho's edition guide lists Blueprint under the Professional edition, and says Free has no Blueprint. Confirm the current position on Zoho's Feature Availability table before planning around it.
Practical advice: use this for the one or two handoffs that most often go wrong, such as no proposal going out without a scope note, rather than trying to model the whole firm at once.
Connect delivery: the Zoho Projects link
Zoho's help page says the Zoho Projects integration is meant to make it easier to create and assign projects to CRM users after a deal is won. Projects can be created for Accounts, Contacts and Deals, either from a record's detail page or by linking an existing project. Tasks, milestones and bugs from Zoho Projects appear on CRM record pages, and tasks can be created from CRM and synced with Zoho Projects. Zoho's page does not state which CRM or Projects editions are required, so check yours.
Practical advice: decide up front who owns the handoff from sales to delivery, and which deal stage triggers project creation, so the link is used consistently.
A suggested order (practical advice)
This is a suggested sequence, not vendor documentation.
- Agree what an account, a contact and a deal mean in your firm, and who is allowed to create each.
- Set stages that match your real sales routine, then import clean data, not a raw spreadsheet dump.
- Add a Blueprint (if your edition includes it) for the single handoff that most often fails.
- Link delivery through Zoho Projects only once the sales side is being used consistently.
- Review after a month: which fields are empty, which stages are skipped, and what people work around.
