Playbook 1 — Lead-to-Cash
The lead-to-cash playbook is the first and most common engagement for a Zoho consultant. It is also the playbook where the platform's breadth is simultaneously the greatest strength and the greatest trap. A poorly-scoped lead-to-cash implementation ends up with eight applications all pretending to be the source of truth for the same record.
The canonical stack is seven applications deep: Zoho Campaigns for email nurturing; Zoho Marketing Automation for multichannel journeys, lead scoring, and web tracking; Zoho SalesIQ for live-chat and visitor identification; Zoho CRM for the unified lead, deal, and account lifecycle; Zoho CPQ (an embedded module of CRM Enterprise/Ultimate) for configurable quoting and approval chains; Zoho Books or Zoho Billing for invoice issuance; and Zoho Payments or Zoho Checkout for card capture.
The governance contract
A lead record is born in Campaigns, Marketing Automation, SalesIQ, or a web form; is promoted to CRM on a scoring threshold; is qualified in CRM and converted to a Deal; a Quote is created via CPQ; on acceptance a Sales Order is generated; the Sales Order syncs to Books or Billing as an Invoice; Payments captures the money; and CRM's Deal stage advances to Closed-Won on receipt confirmation. Each handoff is a governance checkpoint. The consultant's job is to name the owner, the field of record, and the failure mode at each checkpoint — before writing a single workflow rule.
Anti-patterns
Three anti-patterns will kill a lead-to-cash programme. The first is dual-source-of-truth on the contact: allowing Campaigns and CRM to both edit the same email-opt-in flag, resulting in un-opted leads resurrecting on every sync. The second is silent CPQ divergence: creating quotes outside of CRM Quotes such that pricing tiers, discount approvals, and product catalogues fall out of step with the Books item master. The third is invoice orphaning: having Books create invoices that never link back to a CRM Deal because the Deal's Account was merged after the invoice was raised.
The figure
The figure below maps the five stages — Acquire, Qualify, Quote, Fulfil, Recognise — as a cross-application flow with governance checkpoints at each application boundary.
