Deal Registration Context Brief
When a partner registers a deal, get the account context fast — fit, footprint, in-market signal — so you approve, prioritize, or question the registration with data.
Partner - Deal registration
Approve partner deal registrations on account quality, not just who's first
1
Registration brief
Context in seconds
Fit confirmed, footprint supports it,
in-market on the category. Approve.
Fit confirmed, footprint supports it,
in-market on the category. Approve.
| Check | Result |
|---|---|
| Size sanity | $150k realistic (HG) |
| Footprint | Supports the product |
| Intent | In-market - approve |
Why it lands
Channel teams approve registrations on first-come order with little context. This brief confirms in seconds that the account can transact at $150k, the stack fits the product, and the buyer's in-market — so the approval is informed, not reflexive.
Overview
For a partner-registered deal, produce a context brief that enriches the account with HG firmographic, technographic, and intent data — so the channel team approves or prioritizes the registration based on account quality, not just on who registered first.
Use cases
Informed registration decisions
Approving registrations blind rewards speed over quality. A fast account-context brief lets the channel team prioritize the registrations backed by real fit and intent.
Catch the unrealistic registration
A $150k deal registered against an account too small to transact it is a flag. Firmographic sanity-checking surfaces it before it clogs the joint pipeline.
View workflow prompt
# Deal Registration Context Brief
## Parameters
- `{{domain}}` *(required)* — The registered deal's account domain. Example: `boeing.com`
- `{{registration_context}}` *(required)* — Pasted registration details (partner, product, stated deal size, stated stage). Example: `Partner A registered; product: analytics platform; ~$150k; discovery`
- `{{category}}` *(required)* — Category whose intent validates the deal. Example: `data analytics`
## Purpose
Enrich the partner-registered deal at {{domain}} (per {{registration_context}}) with HG data so the channel team can approve, prioritize, or question the registration based on account fit, footprint, and {{category}} intent — not just registration order.
## Process
1. **Frame the registration** — restate {{registration_context}} (partner, product, size, stage).
2. **Account quality** — `company_firmographic` to confirm the account can transact at the stated size; flag mismatches.
3. **Footprint check** — `company_technographic` to see whether the account's stack supports the registered product's fit.
4. **In-market validation** — `company_intent`/`intent_category` for the {{category}} to confirm the buyer is actually researching (validates or questions a discovery-stage registration).
5. **Recommendation** — approve / prioritize / question, with the evidence; flag if the stated deal size looks unrealistic for the account.
## Output Format
Markdown with:
- `# Deal Registration Context — {{domain}}`
- `## Registration Snapshot` (from the input)
- `## Account Quality` (fit + size sanity, cited)
- `## Footprint + Intent` (does the deal make sense?)
- `## Recommendation` (approve / prioritize / question)
- `## Citations`
## Quality Checklist
- Account-size sanity cites `company_firmographic`
- In-market validation cites `company_intent`/`intent_category`
- Recommendation is evidence-backed, not registration-order-based
- Unrealistic stated deal sizes are flagged