Stop guessing what
your customers
will do.

1. 1

   Start from + new, then choose Identify the best customer for my product.

2. 2

   Add a focus area such as best customer fit, pain intensity, purchase intent, or trust.

3. 3

   Choose how Populous should handle target customers:

   • Use I need to decide between specific target customers when you already have candidate segments.
   • Use I want Populous to figure out who the best target is when you want discovery from a broader starting point.
4. 4

   If comparing known segments, describe or load each population separately. For example:

   Population 1: Seed-stage founders building AI workflow products.
   
   Population 2: Mid-market operations leaders at B2B SaaS companies.
   
   Population 3: Growth marketers responsible for conversion experiments.

5. 5

   Pick the evidence source:

   • By asking questions for fast text-based signal.
   • By having people look at an image or document if you have a page, deck, mockup, or one-pager.
   • By having people use my website if the live experience is part of the decision.
6. 6

   Add context about the product, market assumption, current message, pricing, and launch goal.

7. 7

   The report should identify which customer looks strongest, why they stand out, what objections remain, and which customer to use in the next test.

Use this when the product is fixed and the open question is who cares most. The output is directional signal from simulated customers, not a market-size estimate.

1. 1

   Start from + new, then choose Identify the best product for my customer.

2. 2

   Add a focus area such as willingness to pay, positioning clarity, purchase intent, trust, or which workflow matters most.

3. 3

   Describe or load the customer population you want to hold constant. For example:

   Customer population: Operations leaders at B2B SaaS companies who care about implementation risk, team adoption, and measurable workflow efficiency.

4. 4

   Choose By asking questions.

5. 5

   Add context that frames the decision. For example:

   Decision: Should we lead with implementation speed or model accuracy?
   
   Current assumption: operations leaders care most about reducing manual work.
   
   Constraint: do not overclaim automation reliability.

6. 6

   Add supporting links, notes, or documents only if they clarify the decision.

7. 7

   The report should show what customers understood, what created trust, what created resistance, and what next test or product move is most justified.

Use this when the team has a clear customer but needs fast signal before choosing a product, pricing, positioning, or launch direction. Avoid claiming a definitive answer; frame the result as a better next decision.

1. 1

   Start from + new, then choose Identify the best product for my customer.

2. 2

   Add a focus area such as message clarity, believability, pricing clarity, trust, or launch readiness.

3. 3

   Describe or load the customer population that should react to the asset.

4. 4

   Choose By having people look at an image or document.

5. 5

   Upload the assets respondents should react to and label each one clearly:

   Asset 1: Current homepage hero.
   
   Asset 2: Revised time-to-value positioning.
   
   Asset 3: Pricing page draft.

6. 6

   Choose whether Populous can generate variants:

   • Use Yes, generate variants too when you want improved alternatives.
   • Use No, use only what I upload when the mission should critique existing materials only.
7. 7

   Add context about the audience, desired action, known weak spots, and what the asset must not overclaim.

8. 8

   The report should show which claims created belief, what confused people, what proof was missing, and which version or rewrite to test next.

Use this when the page, deck, mockup, pricing table, launch asset, or one-pager is the thing being judged. Simulated reactions help sharpen it before real-world exposure.

1. 1

   Start from + new, then choose Identify the best product for my customer.

2. 2

   Add a focus area such as conversion friction, activation, trust, ease of use, or clarity.

3. 3

   Describe or load the customer population that should use the flow.

4. 4

   Choose By having people use my website.

5. 5

   Add the live starting URL. For example:

   Starting URL: https://example.com/pricing

6. 6

   If the flow requires authentication, use Log in to this URL so Populous can use the current session for agent browsing.

7. 7

   Add context about the intended task, success criteria, known concerns, pages users may need to visit, and what the current flow should accomplish.

8. 8

   The report should show where simulated users hesitated, what they looked for, what language or UI created confusion, what proof was missing, and what to change before real users hit the same friction.

Use this when the live experience matters more than a static concept. Simulated users show where the flow creates friction; use that signal to guide product changes, not replace live analytics.