Partner Enablement Account Brief
Arm a partner's reps with an account brief they can actually sell from — the account's stack, pain, and in-market signals, framed for the joint offer.
Partner - Enablement
An account brief the partner's reps can actually sell from
1
Joint account brief
Partner-rep ready
Profile + cloud footprint + why-now +
a joint-offer talk track.
Profile + cloud footprint + why-now +
a joint-offer talk track.
| Section | Content |
|---|---|
| Profile | Enterprise mfg (HG) |
| Cloud | Heavy AWS spend |
| Why now | Migration intent rising |
Why it lands
Partner reps often walk into joint accounts cold. This brief gives them the account's profile, cloud footprint, and a joint-offer talk track — so the partner's team shows up as prepared as yours, and the co-sell doesn't fall apart on their side.
Overview
Generate an account brief tailored for a partner's reps to use in a joint sales motion — the account's firmographic profile, installed stack, and in-market intent, framed around the joint offer — so the partner's team walks into the account as informed as yours.
Use cases
Equip the partner's team, not just yours
A joint motion fails when the partner's rep is unprepared. An account brief framed for the joint offer arms their team to carry their half of the conversation.
One brief, one story
Both teams working from the same data-grounded brief tells the account one coherent joint story instead of two disjointed pitches.
View workflow prompt
# Partner Enablement Account Brief
## Parameters
- `{{domain}}` *(required)* — The target account domain. Example: `siemens.com`
- `{{joint_offer}}` *(required)* — The joint offer the partner co-sells. Example: `AWS migration + our observability platform`
- `{{category}}` *(required)* — Category whose intent grounds the timing. Example: `cloud migration`
## Purpose
Build an account brief for {{domain}} that a partner's rep can sell from — profile, stack, cloud footprint, and {{category}} intent — framed around the {{joint_offer}} so the partner's team is as informed as yours walking in.
## Process
1. **Profile** — `company_firmographic` for size, industry, geo, corporate structure.
2. **Stack + cloud** — `company_technographic` + `company_cloud_spend` to map the relevant installed stack and cloud footprint the {{joint_offer}} targets.
3. **In-market** — `company_intent` for the {{category}} to ground the timing.
4. **Frame for the joint offer** — translate the account's situation into why the {{joint_offer}} fits now, in language the partner's rep can use.
5. **Talk track** — a short, joint-offer-specific talk track and the likely objections.
## Output Format
Markdown with:
- `# Partner Enablement Brief — {{domain}}`
- `## Account Profile` (cited)
- `## Stack + Cloud Footprint` (what the joint offer targets)
- `## Why Now` (in-market signal)
- `## Joint-Offer Talk Track` (+ likely objections)
- `## Citations`
## Quality Checklist
- Profile and footprint cite their HG tools
- The brief is framed for the joint offer, not just generic research
- Talk track is usable by a partner rep who doesn't know the account
- No fabricated account details