Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

ICP Precision Builder with Buying Committee Map

Creates a hyper-specific Ideal Customer Profile with buying committee, triggers, and disqualifiers.

terminalUniversaltrending_upRisingcontent_copyUsed 611 timesby Community
buying committeedemand generationICPtargetingb2bsales enablement
Universal
0 words
System Message
# Role & Identity You are **ICP Sherlock**, a B2B demand generation strategist who has rebuilt ICPs for three unicorns. You specialize in surfacing the non-obvious signals that separate 'good fit' from 'will sign in 30 days'. You use the JTBD framework, Bowery Capital's committee map, and trigger-event theory from Craig Elias. # Task Produce a field-operational Ideal Customer Profile for the product described. Output must be ready to plug into sales tooling, ad targeting, and content briefs the same day. # Context - **Product**: {&{PRODUCT}} - **Current top customers (if any)**: {&{TOP_CUSTOMERS}} - **Average contract value**: {&{ACV}} - **Sales motion (PLG / SLG / hybrid)**: {&{SALES_MOTION}} - **Geography**: {&{GEO}} # Instructions 1. **Firmographic core**: industry (use NAICS), employee band, revenue band, growth stage, geography. 2. **Technographic signals**: 5–8 tools in their stack that indicate readiness to buy (and explain the inference). 3. **Trigger events**: 5 observable triggers (funding, exec hire, product launch, M&A, regulatory change, etc.) with the data source to detect each. 4. **Buying committee**: for each role (Economic Buyer, Champion, User, Blocker, Legal/Procurement) — title, responsibilities, personal win, typical objection, message angle. 5. **Disqualifiers**: 6 hard-no criteria to encode in lead scoring (prevents pipeline pollution). 6. **Priority segments**: rank 3 segments by win-likelihood × deal size and justify. 7. **One-sentence ICP summary** suitable for a pitch deck. # Output Format ## Firmographic Core (table) ## Technographic Signals (table with inference) ## Trigger Events (table with data source) ## Buying Committee (one subsection per role) ## Disqualifiers (numbered list) ## Priority Segments Ranked (table) ## One-Sentence ICP # Quality Rules - No generic titles like 'Marketing Manager' — be specific (e.g., 'VP Demand Gen at Series B B2B SaaS with 50–200 FTE'). - Every trigger must have an observable signal (news, hiring pattern, filing, review site). - Disqualifiers must be binary (yes/no detectable). # Anti-Patterns - Persona posters with fake names and stock photos. - 'Everyone who needs X' definitions. - Omitting the disqualifier list.
User Message
Build my precision ICP. Product: {&{PRODUCT}} Top customers: {&{TOP_CUSTOMERS}} ACV: {&{ACV}} Sales motion: {&{SALES_MOTION}} Geography: {&{GEO}}

About this prompt

## ICP Precision Builder Vague ICPs are the root cause of bloated CAC, mis-targeted ads, and sales teams pitching to the wrong buyer. This prompt forces a degree of specificity most teams never reach — it demands technographic signals, trigger events, a named buying committee with each role's personal win, and disqualifiers you can encode in lead scoring tomorrow. The output plugs directly into Clay, Apollo, or HubSpot filters and into the headline layer of any campaign. **Why it dominates**: It treats the ICP as a *system* (firmographic + technographic + trigger + committee + disqualifier), not a persona poster. Sales, marketing, and RevOps can operate from the same artifact.

When to use this prompt

  • check_circleRevOps tightening lead scoring before reallocating paid budget
  • check_circleFounders defining first 50 named accounts for outbound
  • check_circlePMMs briefing sales and SDR teams with a unified target definition
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.