Buying committee personas
The people who influence a midsize+ purchase, what each one wants, what makes them say no, and the proof that moves them. Plays and objection files refer to these names.
Summary
A midsize+ deal usually needs a champion (developer, architect or business owner), an economic buyer (engineering manager, CTO/VP Eng or department head), and gatekeepers (IT/security, procurement, legal). Message each one differently, and give the champion material they can forward to the others.
Details
| Persona | Goals | Typical objections | Proof they need |
|---|---|---|---|
| Developer / architect | Ship fast, clean APIs, good docs, works with their framework, no surprises in production | “Will it fit our stack?”, “Is the API stable?”, “How good is support when we’re stuck?” | Docs, code samples, live demos, GitHub examples, release cadence, support response times |
| Engineering manager | Hit delivery dates, reduce build-versus-buy risk, keep the team productive | “Will this slow us down?”, “What’s the learning curve?”, “Who maintains it?” | Time-to-first-result, migration guides, onboarding and support options, total cost compared with building in-house |
| CTO / VP Engineering | Platform choices that scale, vendor risk, standardization across teams | “Lock-in?”, “Vendor viability?”, “Roadmap?” | Company track record, roadmap signals, deployment flexibility, enterprise agreement options, references at similar scale |
| IT / security | Protect data, pass audits, control access, keep systems patched | “Where is data stored?”, “SSO?”, “Pen tests?”, “Can we self-host?” | Security/trust page, compliance attestations, SSO/SCIM, on-prem or private-cloud option, vulnerability policy, security questionnaire answers |
| Procurement | Predictable cost, standard terms, compliant vendor onboarding | “Cost at scale?”, “Renewal terms?”, “Can we pay by PO/invoice?” | Public pricing model, enterprise quote path, standard agreement, DPA, vendor forms, invoicing options |
| Business owner: BI and analytics | Self-service insights, embedded analytics for customers, governed data | “Will users adopt it?”, “Does it connect to our data?” | Data connector list, dashboard demos, embedding examples, governance and row-level security |
| Business owner: CX and support | Lower cost per ticket, faster resolution, better CSAT, safe AI | “Will AI give wrong answers?”, “How hard is it to switch?” | AI guardrails, resolution-rate reporting, migration help, integrations |
| Business owner: operations | Efficient workflows, fewer manual steps, auditability | “Does it fit our process?”, “Can we automate it?” | Workflow and integration demos, API, audit trails |
| Business owner: legal | Enforceable agreements, compliance with e-signature and privacy law, risk control | “Is it legally binding?”, “Audit trail?”, “Data residency?” | Legal-validity statements, audit trail samples, compliance pages, data-residency options |
How to use this table
- Ads and video: pick one persona per ad and one claim per ad. See YouTube ad messaging.
- Website: every persona should find their proof within two clicks of the product home page. See the website buyer-fit audit.
- Objection files: each objection in
_reference/objections/<slug>.mdnames the persona who raises it, using the names in bold above. - Sales: map the committee in discovery and confirm who signs. See competitive selling.
Product emphasis
| Product | Usual champion | Usual economic buyer |
|---|---|---|
| Essential Studio | Developer / architect | Engineering manager |
| Bold BI | Business owner: BI, or developer (embedded) | CTO / VP Eng or BI lead |
| Bold Reports | Developer / architect, BI owner | Engineering manager |
| BoldSign | Operations, legal, or developer (API) | Operations or department head |
| BoldDesk | Business owner: CX and support | Head of support or CX |
| BoldCreate | Engineering manager or developer / architect | CTO / VP Eng (TBD: confirm) |
| BoldDocServer | IT / security (SharePoint admin) | Head of IT or infrastructure |
TODO: add a real example of a buying committee map from a recent midsize+ deal (sanitized).
Sources
- Team experience and the build spec’s persona list. Validate with win/loss notes at the next review.
Used by
- ICP for midsize and enterprise buyers
- Every file in
_reference/objections/and_reference/positioning/ - YouTube ad messaging
- Competitive selling