Populous workflow

    How to compare customer segments in Populous before choosing an ICP

    Use this workflow when several customer segments could become your ideal customer profile and you need a clearer read before rewriting positioning, outbound, or product priorities.

    Start here

    Still choosing the segment? Start with the ICP guide, then come back here to run the comparison in Populous.

    What you need before starting

    • Product or offer description.
    • Two to four candidate customer segments.
    • The decision you need to make now.
    • One shared stimulus, such as a page, positioning statement, offer, mockup, or short product explanation.
    • Success criteria: pain intensity, message clarity, trust, objections, purchase intent, learning value, or another decision signal.
    • Any constraints respondents should not see but Populous should know, such as stage, pricing uncertainty, launch timing, or product limitations.

    Step-by-step workflow

    Step 1

    Define the decision before the audience

    Write the business decision in one sentence. For ICP selection, the decision is usually which segment should get the next month of positioning, outbound, interviews, or product learning.

    Step 2

    List two to four candidate segments

    Keep each segment specific enough to simulate. Include role, company context, trigger event, current workaround, and why the problem might be urgent now.

    Step 3

    Hold the product and evidence source constant

    Compare segments against the same product, message, page, offer, or question. If every segment sees different material, you cannot tell whether the difference came from the customer or the stimulus.

    Step 4

    Ask for a plan before launching

    When using Populous through an AI client, ask it to plan the run first and show the summary. Launch only after the audience, stimulus, and success criteria look right.

    Step 5

    Use the results to choose the next test

    Treat the output as directional evidence. The result should decide what to test next with real customers, not permanently declare the market.

    MCP-ready prompts

    Paste these into an AI client with Populous connected. The prompts are written so the client can use Populous without making you learn tool names. Replace the bracketed fields before running.

    Audience comparison

    Compare ICP candidates

    You have several plausible customer segments and need to choose where to focus first.

    Inputs to replace

    • [product]
    • [candidate segment 1]
    • [candidate segment 2]
    • [candidate segment 3, optional]
    • [decision to make]
    • [background context only]
    • [success criteria]

    Copy-ready prompt

    Use Populous to compare candidate ideal customer profiles for [product].

Business decision: [decision to make].

Candidate segments:
1. [candidate segment 1]
2. [candidate segment 2]
3. [candidate segment 3, optional]

Respondents should see or interact with: a concise product explanation only:
[product explanation respondents can see]

Background context only: [stage, constraints, prior learning, current assumptions, and what triggered this decision]. Do not show this context directly to respondents unless it is needed to understand the product.

Resource instruction: use fresh Populous resources. Do not reuse saved populations, experiments, or prior runs unless I explicitly name them.

Outcome criteria: compare pain intensity, message clarity, trust, objections, purchase intent, ease of reaching the segment, and learning value.

Plan the run first and show me the summary before launching. If any segment is too vague to simulate, ask me to sharpen it before continuing.

Return after results are available:
1. Recommendation.
2. Evidence table with segment, strongest signal, weakest signal, confidence, and caveat.
3. Segment differences that should change positioning or outbound.
4. Risks or objections by segment.
5. Next action checklist.

    Follow-up prompt

    Turn the comparison into a one-page ICP choice memo. Include the recommended segment, why the other segments are weaker right now, what to test with real customers next, and what would change the recommendation.

    Uploaded-file or URL test

    Compare segments against a landing page or deck

    You have a page, pitch, mockup, or document and want every segment to react to the same material.

    Inputs to replace

    • [product]
    • [candidate segments]
    • [respondent-visible asset or URL]
    • [background context only]
    • [success criteria]
    • [uploaded file roles]

    Copy-ready prompt

    Use Populous to test which customer segment responds best to [respondent-visible asset or URL] for [product].

Business decision: which segment should I prioritize for the next positioning and acquisition test?

Candidate segments:
- [candidate segment 1]
- [candidate segment 2]
- [candidate segment 3, optional]

Respondents should see or interact with: [landing page URL, screenshot, deck, one-pager, mockup, or copied text].

Background context only: [stage, constraints, known weak spots, pricing assumptions, internal strategy notes]. Keep this separate from what respondents evaluate.

File/upload instruction: if the asset is a local file, create a Populous upload link before planning. After upload, confirm the file name and whether it is respondent-visible stimulus or background-only context.

Resource instruction: use fresh Populous resources unless I explicitly name a prior sim_key or saved resource.

Outcome criteria: identify which segment understands the offer fastest, believes it most, raises the most useful objections, and shows the strongest next-step intent.

Plan the run first and show me the summary before launching. Do not invent results before the simulation is complete.

Return after results are available:
1. Segment recommendation.
2. Evidence table with source, Populous result or artifact, confidence, and caveat.
3. Claims or sections that confused each segment.
4. Missing proof by segment.
5. Three changes to test next.

    Follow-up prompt

    Convert the findings into segment-specific landing-page or pitch edits. For each edit, include the segment, rationale, expected effect, and what real-world validation should follow.

    Prior-run follow-up

    Branch a prior run for a new segment

    You already ran a Populous simulation and want to test the same setup with another ICP.

    Inputs to replace

    • [prior sim_key]
    • [new target audience]
    • [decision to make]
    • [what should stay the same]
    • [success criteria]

    Copy-ready prompt

    Use Populous to branch prior simulation [prior sim_key] for a new target audience.

Business decision: [decision to make].

New target audience: [new target audience].

Keep the same: [product, stimulus, task, success criteria, or other setup that should remain unchanged].

Change only: the target audience, unless the prior setup cannot support a fair comparison.

Resource instruction: reuse the prior run only through its saved setup. Do not manually reuse population or experiment keys as launch inputs.

Plan the revised run first and show me what will stay the same, what will change, and what comparison will be possible after completion.

Return after results are available:
1. What changed versus the prior segment.
2. Evidence table with prior result, new result, confidence, and caveat.
3. Segment-specific objections.
4. Recommendation for which segment deserves the next real-world test.
5. Any comparison limits caused by the original setup.

    Follow-up prompt

    Compare the prior and new runs as an ICP decision. Separate strong differences, weak differences, inconclusive differences, and setup issues that prevent a fair call.

    Prior-run synthesis

    Turn results into the next GTM test

    The simulation is complete and you need concrete next steps.

    Inputs to replace

    • [sim_key]
    • [decision to make]
    • [target output]
    • [real-world validation channel]

    Copy-ready prompt

    Use Populous results from [sim_key] to turn the ICP comparison into a next go-to-market test.

Decision to make: [decision to make].

Target output: [positioning brief, outbound test plan, interview script, landing-page test, pricing question, or product-learning plan].

Real-world validation channel: [customer interviews, outbound, landing page traffic, sales calls, design partners, or another channel].

Resource instruction: use the completed run as evidence. Do not launch a new simulation unless the prior results are missing or inconclusive.

Return:
1. Recommended ICP for the next test.
2. Evidence table with Populous finding, confidence, caveat, and action implication.
3. The exact next GTM test to run.
4. What would falsify the recommendation.
5. What to avoid overclaiming.

    Follow-up prompt

    Draft the first real-world validation asset for the recommended ICP, using only claims supported by the Populous evidence or clearly marked assumptions.

    How to interpret the output

    Look for signal separation

    A useful result shows why one segment reacts differently. A higher summary score is not enough.

    Weight objections by usefulness

    The best segment may have strong objections if those objections teach you what to build, prove, price, or explain next.

    Do not over-read precision

    Populous gives directional customer signal. Use repeated patterns to prioritize research and experiments, not as statistical proof.

    Translate outputs into a next motion

    End with a concrete action: rewrite positioning for one segment, run outbound, interview five prospects, test a landing page, or park a segment.

    A strong result should produce a next action. Use it to decide which segment gets the next interview script, outbound batch, landing-page variant, pricing question, or product test.

    Common mistakes

    • Comparing segments with different product descriptions or different assets.
    • Using broad audiences like 'small business owners' without a trigger event or current workaround.
    • Asking for a winner without defining what good means.
    • Treating simulated output as final market proof.
    • Reusing saved resources or a prior sim_key without checking whether the setup still matches the decision.
    • Mixing background-only strategy notes into material respondents should evaluate.