ICP Intelligence report
Buyer Group Analyzer: your result
This answer uses a made-up example company. Change the details above and press Run to see your own result.
Buyer Group Analyzer
For account executives and founders selling to a buying committee. The decision: who else must agree before this deal can close?
Who else must say yes before this deal closes? Give what you sell, the deal size, the company size, your usual champion and the roles you know. Buyer Group Analyzer places each role as economic buyer, evaluator, reviewer or user, with its concern, a message angle and the question that confirms it.
Map your deal across five buying group roles treated as hypotheses to confirm: Champion, Economic Buyer, Technical Evaluator, End User, and Potential Blocker. For each role, get a validation question, acceptance condition check and message angle, plus a multi-threading checklist and role-specific discovery questions in Buyer Group Analyzer.
This sample is a made-up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Role: Finance Controller
Evidence: Role hypothesis only. Title supplied; contact and decision evidence unconfirmed.
Validation question: Who is the named person, and what did they do to advocate internally? Record the observed action and date.
Check to own: The account owner should ask Finance Controller to name the acceptance condition for spend management software before the next buyer meeting, then record the supporting evidence and who can approve it.
Message angle: Lead with days to close the books: show the effect on their own numbers, with the kind of proof this sector trusts (close time or reconciliation effort before and after for one entity, signed off by the finance controller).
See the full example answer or run it with your own details.
ICP Intelligence report
This answer uses a made-up example company. Change the details above and press Run to see your own result.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 89 tools and skills
About this example. Darwinbox is a real company. It has not reviewed this page, and Helix GTM Consulting has no relationship with it. Darwinbox sells an HR platform covering recruiting, onboarding, payroll and employee administration (TechCrunch, 5 March 2025). Every input below is illustrative, written by Helix to show how the tool works. None of it is Darwinbox's data, and the output is an exercise result, not Darwinbox's strategy.
We ran Buyer Group Analyzer on 19 November 2026 through the ICP Intelligence MCP endpoint (server version 1.2.28); the excerpt is cut word for word from its answer.
Exercise output from illustrative inputs. It is not Darwinbox's data, result or strategy.
Role: CFO
Evidence: Role hypothesis only. Title supplied; contact and decision evidence unconfirmed.
Validation question: Who can approve the spend for this purchase, and what source confirms that authority?
Check to own: The account owner should ask CFO to name the acceptance condition for HR software (HCM): recruiting, onboarding, payroll and employee administration before the next buyer meeting, then record the supporting evidence and who can approve it.
Generated on 12 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
ICP Intelligence report
Budget authority: Who can approve the spend for this purchase, and what source confirms that authority?
Role titles are hypotheses until contact and role evidence are supplied. A typical role alone does not confirm a champion.
Sector: read from your inputs as fintech, spend and expense. Business model: software subscription (from your answer).
The deal size and company size are shown for context: the roles below come from your champion, your stakeholders and the sector, not from the deal size.
Role: Finance Controller
Evidence: Role hypothesis only. Title supplied; contact and decision evidence unconfirmed.
Validation question: Who is the named person, and what did they do to advocate internally? Record the observed action and date.
Check to own: The account owner should ask Finance Controller to name the acceptance condition for spend management software before the next buyer meeting, then record the supporting evidence and who can approve it.
Message angle: Lead with days to close the books: show the effect on their own numbers, with the kind of proof this sector trusts (close time or reconciliation effort before and after for one entity, signed off by the finance controller).
Strategy:
Role: Chief Financial Officer (usual in fintech, spend and expense; none of your stakeholders fits this role)
Evidence: Role hypothesis only. Suggested from sector or role context; no contact evidence supplied.
Validation question: Who can approve the spend for this purchase, and what source confirms that authority?
Check to own: The account owner should ask Chief Financial Officer (usual in fintech, spend and expense; none of your stakeholders fits this role) to name the acceptance condition for spend management software before the next buyer meeting, then record the supporting evidence and who can approve it.
Message angle: Tie the spend to days to close the books and to the risk of staying as they are, and bring proof from a buyer like them.
Strategy:
Role: Head of IT (usual in fintech, spend and expense; none of your stakeholders fits this role)
Evidence: Role hypothesis only. Suggested from sector or role context; no contact evidence supplied.
Validation question: Who owns technical acceptance, and where are their agreed criteria recorded?
Check to own: The account owner should ask Head of IT (usual in fintech, spend and expense; none of your stakeholders fits this role) to name the acceptance condition for spend management software before the next buyer meeting, then record the supporting evidence and who can approve it.
How to answer: Show the gap between the ERP module and the daily workflow (approvals, receipts, cards, posting) using one month of the buyer's own transactions.
Strategy:
Role: Head of Accounts Payable (usual in fintech, spend and expense; none of your stakeholders fits this role)
Evidence: Role hypothesis only. Suggested from sector or role context; no contact evidence supplied.
Validation question: Who will use this in daily work, and which observed task confirms their involvement?
Check to own: The account owner should ask Head of Accounts Payable (usual in fintech, spend and expense; none of your stakeholders fits this role) to name the acceptance condition for spend management software before the next buyer meeting, then record the supporting evidence and who can approve it.
How to answer: Show the daily workflow through their eyes and agree a small pilot with the people who will use it.
Strategy:
Role: Internal Audit Lead (usual in fintech, spend and expense; none of your stakeholders fits this role)
Evidence: Role hypothesis only. Suggested from sector or role context; no contact evidence supplied.
Validation question: Who must review this purchase, and which policy or decision confirms their role?
Check to own: The account owner should ask Internal Audit Lead (usual in fintech, spend and expense; none of your stakeholders fits this role) to name the acceptance condition for spend management software before the next buyer meeting, then record the supporting evidence and who can approve it.
How to answer: Prepare the answers before they are asked: data residency, access controls, audit logs, certifications you actually hold.
Strategy:
┌──────────────────────────┐
│ ECONOMIC BUYER │
│ Chief Financial Officer │
└─────────────┬────────────┘
│ approves
┌─────────────▼────────────┐
influences │ CHAMPION │ influences
┌─────────│ Finance Controller │──────────┐
│ └─────────────┬────────────┘ │
▼ │ ▼
┌──────────────────────────┐ advocates for ┌──────────────────────────┐
│ TECHNICAL │◄───────────────────│ USER │
│ Head of IT │ validates │ Head of Accounts Payable │
└──────────────────────────┘ └──────────────────────────┘
│ │
│ ┌──────────────────────────┐ │
└────────►│ BLOCKER │◄─────────┘
reviews │ Internal Audit Lead │ reviews
└──────────────────────────┘
Track your coverage of the buying group:
| Role | Identified | Contacted | Meeting Held | Aligned |
|---|---|---|---|---|
| Champion | ☐ | ☐ | ☐ | ☐ |
| Economic Buyer | ☐ | ☐ | ☐ | ☐ |
| Technical | ☐ | ☐ | ☐ | ☐ |
| End User | ☐ | ☐ | ☐ | ☐ |
| Blocker | ☐ | ☐ | ☐ | ☐ |
Goal: Minimum 3 of 5 roles engaged before proposal (Example figure: replace with your own)
Next Step: Use TAM SAM SOM Calculator to size your market
Suggested timings, lengths and counts: adjust them to your own.
For a spend management software company in India: This is a contact and approval hypothesis for spend management software. A title in the supplied contacts does not establish authority, advocacy or access. Evidence that could change this conclusion: direct confirmation of approval authority, the buying steps and the acceptance condition for $24,000 ACV.
Proposed owners. Confirm the named person before acting.
Founder: For a spend management software company in India, ask Finance Controller to describe the problem in their own words before endorsing the purchase story; keep their observation separate from a role inferred from a title.
CEO: For a spend management software company in India, confirm who can approve $24,000 ACV and what approval they require before committing delivery resources; do not assign that power from a job title.
CMO: For a spend management software company in India, collect one stated acceptance concern from the supplied contacts before preparing committee material; mark any missing concern as unconfirmed.
CRO: For a spend management software company in India, ask Finance Controller to arrange contact with the actual approver before the next deal review; record whether the introduction and approval path are confirmed.
Demand generation head: For a spend management software company in India, distinguish the supplied contacts from confirmed buying roles before adding similar titles to a target list; validate the proposed role with the account owner.
Region context: Which region applies: India, Southeast Asia, Middle East, UK, Western Europe or North America? Add it to your description and rerun.
How the answer is laid out, using the sections the tool prints. The Economic Buyer approves.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
The tool maps the five roles in your buying committee (Champion, Economic Buyer, Technical Evaluator, End User, and Potential Blocker), prints an Influence Map, a Multi-Threading Checklist, and Role-Specific Discovery Questions. Every role title is explicitly marked as a Role hypothesis only (champion unconfirmed, budget authority unconfirmed) until you record a named contact, their observed advocacy or sign-off authority, and their specific acceptance condition. Your deal size and target company size are shown for context; the roles and questions come from your champion input, known stakeholders, and sector.
Run the analyzer again for a specific live deal once you know the exact stakeholder titles in the account, or whenever you launch a product into a new sector with a different buying committee. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
No. Every role taken from a title is a hypothesis. The answer opens with the first unconfirmed decision role and the question that confirms it, such as who can approve the spend and what source confirms that authority.
Enter the confirmed budget owner. A confirmed fact overrides the order the tool would otherwise suggest from titles.
Buyer Group Analyzer maps a deal's whole buying group from the roles you know. Identify Champions, on the IMPACT site, starts from your product and problem and suggests who inside the buyer is most likely to push for you.
Add ICP Intelligence once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use ICP Intelligence's Buyer Group Analyzer tool. product category: spend management software; deal size: $24,000 ACV; target company size: 300-3000 employees; typical champion: Finance Controller. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
It applies fixed rules in the ICP Intelligence code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
ICP Intelligence home · All Helix GTM tools · Tools by GTM job
MCP tool name: buyer_group_analyzer. REST: POST https://icp-intelligence.gtmhelix.com/api/tools/buyer_group_analyzer with this JSON body (see How it works):
{
"input": {
"product_category": "spend management software",
"deal_size": "$24,000 ACV",
"target_company_size": "300-3000 employees",
"typical_champion": "Finance Controller"
}
}
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh