How to set up a Blueprint in Zoho CRM (with a worked example)

What a Blueprint is made of

• States: the stages a record moves through, usually based on a picklist such as Deal Stage or Lead Status
• Transitions: the buttons that move a record from one state to the next
• Before: who can see the transition and under what conditions
• During: fields, notes, attachments or checklists the user must complete
• After: actions that run once the transition is done, such as emails, field updates, tasks or Deluge functions

Design on paper first

Draw the process as boxes and arrows with the people who actually do the work. For each arrow, write down who is allowed to take that step, what information must be captured, and what should happen next. Most Blueprint problems come from skipping this step and building straight in the editor.

The worked example as a transition table

Worked example: a B2B deal process

• Qualification to Needs Analysis: salesperson must enter budget range and decision date
• Needs Analysis to Proposal: requires an uploaded requirement document
• Proposal to Negotiation: discount above 10% triggers a manager approval
• Negotiation to Closed Won: requires PO number; after the transition, a sales order is created in Zoho Books and the delivery team gets a task
• Any state to Closed Lost: a loss reason picklist is mandatory

Build it in Zoho CRM

Go to Setup, Process Management, Blueprint. Choose the module, layout and the field that defines states. Drag the states onto the canvas, connect them with transitions, then configure Before, During and After for each transition. Publish only after testing with a test user who has the same role as your sales team.

Common mistakes

• Too many mandatory fields, which makes users avoid the CRM
• No path back for records that move forward by mistake
• Forgetting that a Blueprint locks the stage field, so imports and other workflows may fail
• Building one Blueprint for every product line instead of separate layouts
• Not explaining the new process to the team before switching it on

When to ask for help

Simple Blueprints can be built in an afternoon. Processes with approvals, parallel transitions, Deluge functions or links to Zoho Books and Zoho Projects are where a Zoho partner saves time. Flowpeak builds Blueprints as part of Zoho CRM implementation and workflow automation projects.

Blueprint vs workflow rules vs approval processes

Testing checklist before you publish

• Log in as a user with the sales role, not as an admin
• Move a test record through every transition, including the backward ones
• Check each mandatory field blocks the move when empty
• Confirm emails, tasks and functions fire once, not twice
• Check reports still show stage history correctly
• Ask two real users to try it for a day before switching it on for everyone

Tips that improve adoption

• Keep each transition to three or four required inputs
• Use checklists for steps people forget, not for every step
• Write the transition button names as actions: "Send proposal", "Mark won"
• Show managers a stage-duration report so the Blueprint has a visible payoff
• Review the Blueprint after 30 days and remove friction nobody needs

Frequently asked questions