How to preserve decision and scope evidence in B2B sales

In project-based B2B sales, disorder often comes from losing how a decision was formed, not from a missing proposal file. Scope items scatter across messages, people treat different outcomes as final, and the authority behind changes becomes unclear. Zoho CRM here carries evidence of the buyer's commercial decision, not a future delivery work plan.

During a scope discussion, a technical evaluator may consider one output included while the commercial party says it was never discussed. Both can be right from their own contact points, yet a proposal cannot restore clarity when the decision exists nowhere. A structure relates people, roles, commitments, prerequisites, and changes, then passes only verifiable signals.

An opportunity stage is not a delivery status

The opportunity record shows the state of a commercial decision, not the daily plan for work that may follow. When this boundary fails, sales reporting can treat ongoing engagements as open opportunities. Project teams may reuse forecasting fields for task tracking, making the stage describe internal progress instead of buyer intent.

In the Zoho structure, the commercial decision remains in the standard Deals module. Related evidence sits in four custom modules: Opportunity Stakeholders, Delivery Commitments, Starting Prerequisites, and Commercial Change Requests. Lookup fields connect records. A user field points to a user, while a lookup points to another module record, not roles.

Custom module capacity is 10 in Standard, 25 in Professional, 200 in Enterprise, and 500 in Ultimate. Custom and team modules consume the same allowance. Custom field limits per module are respectively 10, 155, 300, and 500. Free has neither custom modules nor custom fields, so the four-module structure cannot be implemented there.

Store decision roles as separate relationship records

The budget holder, technical evaluator, coordinator, and contract owner may be different people. Fixing these roles on a contact card mixes that person's positions across opportunities. An Opportunity Stakeholder record links a person to an opportunity and role. One person may hold several roles, while an outdated relationship can be set inactive instead of deleted.

Field names must use actual data types from the product's closed list. Role can be a Pick List, the person connection a Lookup, and the responsible user a User field. Approval Required is a Checkbox. A created field's type cannot change, although its name can. Removing it from layout consumes capacity.

A custom view showing missing decision roles only lists records meeting its criteria. It sends no notification, creates no task, assigns no owner, and produces no reminder. Automation does not move a record into a view; the record appears when it meets the criteria. The list exposes omission for review.

A delivery commitment is an acceptance unit

A delivery commitment defines the outcome promised to the other party and conditions required before that outcome can begin. It does not describe daily activities or resource planning. Each commitment is an acceptably bounded scope unit. An old commitment removed from scope is retained with a changed status and reason.

If commitments are placed in a Zoho subform, their fields cannot be used in custom view columns, layout or validation rules, Blueprint validation, webforms, imports, template merges, or workflow criteria and field updates. When a rule is needed, add an aggregate field; the trigger is its change, not row addition.

Enterprise permits two subforms per module, while Ultimate permits five. A layout can contain no more than 25 subform fields, and the combined row total across all subforms cannot exceed 200. Keeping commitments in a separate module removes these restrictions but consumes module capacity. The choice balances rules against capacity.

Uniqueness applies across the whole module

Zoho CRM does not enforce field uniqueness within a parent opportunity. The Commitment Key therefore combines the opportunity identifier and commitment code in one Text field. Marking the combined value as unique checks it across the entire module. A second record with the same key is prevented, not merely warned.

Most modules allow at most two unique fields. Leads, Contacts, custom modules, and Products allow three. Only Text, Email, Phone, Integer, Big Integer, and URL fields support uniqueness. Tasks, Calls, and Meetings have no unique fields. Matching is case-insensitive, so changing letter case does not create a separate key value.

A unique field cannot also be encrypted. Its technical purpose and data characteristics must therefore be settled before configuration. Because there is no “unique within this opportunity” scope, marking only the commitment code would prevent valid repetitions across different opportunities. The combined key converts the module-wide constraint into intended rule.

Base transitions on flags, not related-record counts

A Zoho Blueprint Before condition reads fields on the opportunity rather than counting related-list records. This design keeps three Deal fields: Decision Roles Complete and Active Change Exists as Checkboxes, plus Confirmed Commitment Count as an Integer. A custom function maintains all three, and transition visibility reads these values directly.

A rollup summary returns a related list's total record count or supported numeric and date aggregates, but not a conditional count. Enterprise allows 10 rollup fields per module and Ultimate allows 15. Values appear after saving. Confirmed commitments are therefore counted in the function-maintained Integer field, not a conditional rollup.

Blueprint defines eligible people and visibility criteria in Before, requested fields and items in During, and automation actions in After. During supports 4 fields in Professional, 10 in Enterprise, and 50 in Ultimate. Blueprint limits are respectively 3, 20, and 100. Workflow avoids the process field; a function maintains active-change.

The proposal is an output of the decision package

The proposal record links to the opportunity and represents document output of the decision package. Quotes are available in Professional, Enterprise, and Ultimate. A quote's product line is a subform, and line customization is limited to Enterprise and Ultimate. Up to 10 fields can be added. Decision evidence remains elsewhere.

The document does not replace Opportunity Stakeholder or Delivery Commitment records. The structure first records who decided in which role, which outcome was accepted, and which starting condition remains open. The proposal then becomes the commercial expression of that decision frame. When it changes, decisions remain traceable in dedicated records.

An opportunity may look closed when an email thread reveals that a price condition changed two weeks earlier. If the approver can only be inferred from the sender's signature, the evidence is incomplete. A price or condition change first creates a Commercial Change Request record. The proposal reflects that decision.

Test failure scenarios through external channels

A validation rule runs during manual record creation and editing. Field changes prevail during imports, workflow field updates, approval processes, Blueprint, and API updates. Conditional mandatory behavior is a layout rule's Set Mandatory Fields action. Layout rules do not run in imports, webforms, or lead conversion. API supports only Set Mandatory Field.

The setup requires Enterprise or Ultimate. Free lacks custom fields and modules. Standard offers 10 modules and 10 custom fields per module; roles and commitments stay on record, with flags marked manually. Professional enables Blueprint and Quotes. Enterprise enables subforms, rollups, and custom functions. Enterprise and Ultimate support quote-line customization.

Acceptance tests cover a missing-role opportunity, a commitment without acceptance authority, a reused Commitment Key, and a change against a closed opportunity. They test a rejected request reaching the record, an inactive commercial owner, and authority granted while a prerequisite remains open. External-channel defects remain visible in a data-quality view.

Zoho CRM