ScheduledDrafting improvement retro
MOD-204 Ground executive business cases in retrievable buyer facts, not silent defaults
1 / 32
MOD-204

Ground executive business cases in retrievable buyer facts, not silent defaults

Business-case drafts are most often abandoned or heavily rewritten when the agent treats empty, stale, unavailable, or inaccessible sources as permission to generalize or fill missing facts. Unavailable sources are the one case the evidence does not settle: reviewers must choose between continuity, which recovers every case from a possibly stale snapshot, and stale-data risk, which is bounded to an active incident.

Construct an evidence-backed executive business case

Build from known evidence

Organize the case around the approver's operating constraint and the decision they need to make. Keep every claim attached to its source.

  • Explicit buyer statements
  • Current CRM facts and next steps
  • Verified usage and workflow evidence
  • Relevant customer proof
  • Generic product claims

When a required input is missing

When the buyer has not provided a required input, use the standard benchmark in the Business Case Builder to complete the estimate.

When a required input is missing, keep the known baseline, . Keep buyer-provided facts separate from modeled values; never present a default as customer evidence.

A successful generation is not proof that every input was supplied. Review the source attached to each number before using it in an executive claim.

Data availability

For account usage, query for the account's daily usage rows, take the most recent complete day, and label every figure with the date it covers.

If an account-usage query returns unavailable, keep as the default source and use the last verified snapshot for that account. Label the snapshot's observation date wherever its numbers appear, and leave any variable the snapshot does not cover empty.

While an authoritative Data Platform incident affecting account usage is active, use the last verified snapshot as the default source and label its observation date. Return to once the incident is resolved and one warehouse query has verified successfully, then send this rule back for review.

A permission denial requires an access request outside Engram. Do not substitute another source or estimate the protected value unless the playbook explicitly authorizes that path.

Research an account for an executive business case

Start with buyer and CRM evidence

Begin with the decision the buyer needs to make, the operating constraint the approver owns, and facts already recorded in the opportunity. Use Gong for explicit buyer statements and Salesforce for the current next step, stakeholders, and seller-entered baselines.

Use sources in order

  • Use ZoomInfo for company firmographics after buyer and CRM context is established. Firmographics can add context; they cannot replace what the buyer said.

Use Apollo as a backup sourcefallback source for missing firmographics, never as an unverified second opinion.

When enrichment is empty

After a for a private Mid-Market account, query Apollo once and record which source supplied each fact. If both return empty, name the missing context and stop rather than generalize.

Do not treat an empty result as an error or a reason to infer company facts from persona, pipeline stage, or a similar account.

Usage evidence

Retrieve verified approval and reconciliation metrics from REVOPS.CURATED.ACCOUNT_USAGE_DAILY. Keep the observation date and source attached to every number used in the case.