ICP Architect
Build a comprehensive Ideal Customer Profile through an interactive discovery process. This skill asks questions, pressure-tests assumptions, and produces a reference-ready docs/icp.md that other skills in the playbook can consume.
Activation
When the user triggers this skill, follow the steps below in order. Do NOT skip the discovery interview. Do NOT produce output before gathering all answers.
Step 0 — Check for Existing ICP
Use Read to check if docs/icp.md already exists in the current working directory.
- If it exists: Read the file, present a summary to the user, and ask: "You already have an ICP on file. Do you want to (A) refine it, (B) start fresh, or (C) add a new segment?"
- If refine: Load the existing content as context. During the discovery interview, pre-fill answers from the existing file and only ask about gaps or changes.
- If start fresh: Proceed with the full interview from scratch. The old file will be overwritten at the end.
- If add segment: Skip to Step 2 (ICP Segmentation) and ask only the questions needed to define the new segment and its personas. Append to the existing file.
- If it does not exist: Proceed to Step 1.
Step 1 — Discovery Interview (Interactive)
Present these questions to the user all at once in a numbered list. Tell the user they can answer inline (numbered) or paste a block of text and you will extract the answers.
Ask exactly these questions:
I need to understand your business before building your ICP. Answer these 10 questions — be as specific as possible. One-word answers are fine where they fit; paragraphs are fine where they don't.
1. What does your product do? (one sentence)
2. Who is your current best customer? Why are they your best?
3. What's your ACV or typical deal size range?
4. How long is your typical sales cycle? (days/weeks/months)
5. Who signs the check? (job title, not a person's name)
6. What's the trigger event that makes someone start looking for your solution?
7. What were they doing before your product? (the "old way" — spreadsheets, manual process, a competitor, nothing?)
8. What happens if they do nothing? (cost of inaction — lost revenue, compliance risk, wasted time?)
9. What's your unfair advantage vs. the next best alternative?
10. (Optional) Paste 3-5 LinkedIn profile URLs of your best customers. I'll extract patterns from their titles, industries, and company sizes.
Rules for this step:
- Wait for the user to respond before proceeding. Do NOT generate placeholder answers.
- If any critical answer is vague (especially questions 1, 2, 5, 6), ask a focused follow-up before moving on. At most 2 follow-up rounds.
- If the user provides LinkedIn URLs (question 10), use
WebSearchto look up those profiles and extract: job title, company size, industry, and any patterns across the set.
Step 2 — ICP Segmentation
From the user's answers, define 2-3 ICP segments. Present them to the user in a table for validation before going deeper.
For each segment, define:
| Field | Description |
|---|---|
| Segment name | Short label (e.g., "Mid-Market SaaS", "Enterprise Financial Services") |
| Company stage | Seed / Series A / Series B / Growth / Enterprise |
| Company size | Employee count range and/or revenue range |
| Industries | 2-5 specific verticals |
| Budget range | What they typically spend on solutions like this |
| Sales cycle | Expected length for this segment |
| Decision maker(s) | Title(s) of the person who signs or champions |
| Core problem | One sentence describing why they buy |
| Pain points | 3-5 specific, concrete pains (not generic fluff) |
Rules for this step:
- Ground every segment in the user's actual answers. Do not invent segments that contradict what the user told you.
- If the user's answers suggest only 1 clear segment, define that one plus a plausible adjacent segment and ask if it resonates.
- After presenting the segments, ask: "Do these segments look right? Should I adjust, merge, or add any?"
- Wait for confirmation before proceeding to Step 3.
Step 3 — Persona Deep-Dive
For each confirmed ICP segment, build 1-2 personas. Each persona is a fictional archetype representing a real buyer.
For each persona, define:
| Field | Description |
|---|---|
| Archetype name | A memorable label (e.g., "The Overwhelmed VP of Ops", "The Data-Driven CRO") |
| Job title | Exact title(s) this persona holds |
| Reports to | Who they report to (affects how they justify purchases) |
| Company context | What kind of company they work at (size, stage, situation) |
| Daily frustrations | 3-5 things that make their job hard right now |
| Goals & success metrics | What they are measured on / what "good" looks like for them |
| Buying behavior | How they research solutions (Google, Reddit, peer referrals, analyst reports, etc.) |
| Trust triggers | What makes them believe a vendor (case studies, free trials, peer recommendations, etc.) |
| Red flags | What makes them walk away (long contracts, no integrations, pushy sales, etc.) |
| Language patterns | 5-10 actual phrases they use to describe their problem — the words they type into Google, say on sales calls, or post on Reddit. These should sound like real speech, not marketing copy. |
Rules for this step:
- Language patterns are the most important field. Get these right. They drive content, ads, and outreach messaging downstream.
- Present personas to the user and ask for corrections before proceeding.
Step 4 — Community & Channel Discovery
For each persona, identify where they spend time online and offline. Use WebSearch to validate every community you suggest. Do not guess subreddit names or Slack community names -- verify they exist.
For each persona, produce:
Online Communities
| Channel Type | Specific Communities |
|---|---|
| Subreddits | 5-8 subreddits (use WebSearch: search reddit.com {topic} {persona role} to find active, relevant subs). Include subscriber count if available. |
| LinkedIn groups & hashtags | 3-5 groups, 5-8 hashtags |
| Slack / Discord communities | 2-4 (use WebSearch to find open communities in the persona's space) |
| Newsletters | 3-5 newsletters they likely subscribe to |
| Podcasts | 3-5 podcasts relevant to their role and problems |
| Events / Conferences | 2-4 industry events (in-person or virtual) |
| Thought leaders | 5-8 people this persona follows or respects (with LinkedIn or Twitter handles where findable) |
Rules for this step:
- Every subreddit must be verified via WebSearch. If a search returns no evidence the subreddit exists and is active, drop it and find one that does.
- Prefer communities with actual activity (posts in the last 30 days, >1K members for subreddits) over theoretical matches.
- Include at least 1-2 non-obvious or "hidden gem" communities per persona -- places competitors are unlikely to be watching.
Step 5 — Buying Signals Mapping
Define 8-12 signals that indicate a company or person matching the ICP is in a buying window.
For each signal:
| Field | Options / Description |
|---|---|
| Signal | What happened (e.g., "Posted a job listing for their first RevOps hire") |
| Where to find it | LinkedIn, job boards, press releases, G2 reviews, Reddit, SEC filings, tech stack tools, etc. |
| Signal strength | Strong (high intent, act now) / Moderate (worth monitoring) / Weak (early awareness) |
| Recommended action | What to do when you spot this signal (e.g., "Send a personalized cold email referencing the hire", "Add to nurture sequence", "Flag for SDR review") |
Rules for this step:
- At least 3 signals must be "Strong."
- Signals should be observable and actionable -- not vague ("they seem interested"). Every signal must answer: where exactly would I