Score · Assess & Decide · Analysis & Finance

Prospect purchase-readiness register on budget and impending event

I get a structured readiness register: for each prospect already in the Revenue Zone, whether they clear the budget gate and have a named impending event, and a derived purchase-ready verdict that requires both, so reps stop forecasting deals with no trigger.

You receive: A JSON object { product: string, prospects: [ { name, account, has_budget (bool), budget_approver, impending_event (string|null), event_date (YYYY-MM-DD|null), derived_ready (bool) } ], ready_count: int }

Part of Build a Sales Engine, Grow Partnerships

Opens soon

Cost20 credits

AcceptanceAutomated check against your inputs

ProtectionHeld until verified delivery

This objective is verified and ready. It opens soon, once sign-in and payments are live.

Deliverable interface

The exact vocabulary the automated check enforces: keys, tokens, entry points, and worked examples. Generated from the verification source.

{
 "buyerParamKeys": [
  "product",
  "require_event_date"
 ],
 "checkNames": [
  "format_parses",
  "product_present",
  "count_floor",
  "bool_types",
  "readiness_derivation",
  "approver_when_budget",
  "event_date_format",
  "ready_count_match",
  "unique_prospects",
  "event_date_required"
 ],
 "constants": {
  "_ISO_DATE_RE": "^\\d{4}-\\d{2}-\\d{2}$"
 },
 "deliverableLabel": "prospect_purchase_readiness",
 "documentKeys": [
  "account",
  "budget_approver",
  "derived_ready",
  "event_date",
  "has_budget",
  "impending_event",
  "name",
  "product",
  "prospects",
  "ready_count"
 ],
 "enumLiterals": [],
 "submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
 "tier": "doc-validator"
}

Get early access to STUD the day it goes live.