Overview
This prompt aims to help B2B startups define a precise Ideal Customer Profile for effective targeting. Startups will benefit by optimizing their sales efforts and resources on high-potential clients.
Prompt Overview
Purpose: This ICP dossier helps identify high-probability targets for your cybersecurity compliance automation software.
Audience: Focus on SaaS companies in Fintech with specific revenue, employee count, and geographic criteria.
Distinctive Feature: Target firms must utilize cloud technologies and have recently experienced significant growth or leadership changes.
Outcome: By using this checklist, you can streamline your sales efforts and maximize conversion rates with ideal prospects.
Quick Specs
- Media: Text
- Use case: Analysis, Classification & Categorization, Content Strategy
- Industry: B2B Sales, Vertical SaaS (Industry-Specific)
- Techniques: Plan-Then-Solve, Role/Persona Prompting, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
# Role
Act as a B2B Growth Strategist and Account-Based Marketing (ABM) Expert. You understand that “selling to everyone is selling to anyone.” Your goal is to define a hyper-specific Ideal Customer Profile (ICP) for my B2B startup so I can focus my limited sales resources on the highest-probability targets.
# Task
Construct a detailed ICP dossier for my startup. Do not just list “Small Businesses.” I need specific firmographic, technographic, and behavioral signals that indicate a company is ready to buy now.
# Context
My Solution: [INPUT: Solution, e.g., “Cybersecurity compliance automation software.”]
Broad Market: [INPUT: Broad Market, e.g., “SaaS companies in Fintech.”]
# Output Instructions
Create an ICP Profile with these 4 distinct layers:
1. Firmographics (The “Who”):
Revenue Range: (e.g., $5M – $20M ARR).
Employee Count: (e.g., 50-200 employees).
Geography: (e.g., North America only).
2. Technographics (The “What”):
Tech Stack: What tools must they already be using? (e.g., “Must be on AWS,” “Must use Slack”).
Maturity: Are they cloud-native or legacy?
3. Trigger Events (The “When”):
Buying Signals: What specific event just happened that makes them need this today? (e.g., “Just raised Series B funding,” “Just hired a new CTO,” “Recently announced expansion to Europe”).
4. The Anti-ICP (Who to Ignore):
Red Flags: Which companies look like good fits but will actually waste my time? (e.g., “Early-stage startups with
Screenshot Examples
How to Use This Prompt
- Copy the prompt into your preferred text editor.
- Replace placeholders with your specific solution and broad market.
- Define each layer of the ICP as instructed.
- Format the output as a “Targeting Checklist.”
- Create a Boolean Search String for LinkedIn Sales Navigator.
Tips for Best Results
- Firmographics: Target companies with $5M – $20M ARR, 50-200 employees, located in North America.
- Technographics: Focus on companies using AWS and Slack, preferably cloud-native with no legacy systems.
- Trigger Events: Look for firms that have recently raised Series B funding, hired a new CTO, or announced expansion to Europe.
- The Anti-ICP: Avoid early-stage startups with <$1M revenue and companies that have established in-house security teams.
FAQ
- What is the ideal revenue range for target companies?
The ideal revenue range is $5M – $20M ARR. - How many employees should the target companies have?
Target companies should have 50-200 employees. - Which geographic area should we focus on?
Focus on companies located in North America only. - What are key buying signals for these companies?
Look for companies that just raised Series B funding or hired a new CTO.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (December 2025): Initial release.
