Cairo
Cairo Labs

Synthetic Audiences: Build Panels Without Hiding Assumptions

Design synthetic audience segments around explicit contexts, document panel composition, and avoid confusing simulated coverage with population representation.

Synthetic audiences are collections of AI-generated profiles organized to explore a question across different assumed contexts. Their composition is a design choice, not evidence of how a real population is distributed. A panel can cover contrasting situations without representing a market.

The essential work is deciding which differences matter, documenting why they matter, and keeping panel membership separate from prevalence claims. Otherwise, an audience report can make arbitrary profile choices look like customer knowledge.

Define the population before designing segments

Write a population statement identifying the people relevant to the decision. Include their relationship to the product, encounter context, and necessary exclusions. “Small businesses” leaves too much unspecified. “People evaluating appointment software for independently operated service businesses” provides a more useful boundary.

Distinguish that population from the synthetic panel. The population is the real group you hope to understand. The panel is an assumed arrangement used for exploration. They are different objects even when their labels sound similar.

Nielsen Norman Group cautions that synthetic users cannot replace real-user research and may produce shallow or idealized accounts. Detailed segment descriptions should remain provisional. Generated detail does not establish that a segment exists as described.

For individual responses, start with the synthetic users guide. Here, the focus is panel composition.

Segment by decision-relevant differences

Begin with a reason context might affect interpretation. Purchasing authority, budget, prior category knowledge, and urgency can create different questions about the same offer. Demographics may be relevant but should not automatically determine motivation or ability.

For each axis, write a causal proposal: “Approval responsibility may change the need for procurement information.” This is a hypothesis to examine. It is more actionable than assigning an age bracket and assuming a predictable attitude toward technology.

Keep the axes manageable. Crossing every demographic, socioeconomic, and psychometric attribute creates combinations without necessarily adding useful coverage. Start with contrasts needed for the decision and record what you leave out.

Segmentation planCairo Labs

Separate context from population claims

Define each contrast and its reason before generating profiles.

AxisPossible contrastReason to examine
AuthorityRecommender versus approverDifferent evidence requirements
ExperienceNew versus experienced buyerDifferent terminology needs
ResourcesFixed versus flexible budgetDifferent cost questions
TimingExploring versus urgent needDifferent information priorities
Illustrative design choices, not validated market segments.

Document composition without implying representation

A panel specification states included contexts, profiles allocated to each, and the allocation rationale. Equal allocations can make contrasts easier to inspect; they do not imply equal market shares. An intentionally overrepresented edge context can be useful without being common.

If credible population data exists, identify its source, date, and scope before using it. Do not fill missing shares with generated estimates. Even externally grounded proportions do not make generated responses equivalent to sampled human responses.

Maintain an exclusions register. A panel might omit people purchasing through intermediaries or operating under unusual procurement rules. State gaps rather than inventing experiences for missing groups. Some gaps require direct recruitment, not additional simulation.

In Cairo, demographic, socioeconomic, and psychometric synthetic profiles support exploration from a URL or idea. Audience views and reports organize generated material. The researcher still owns assumptions connecting profiles to a population.

See Cairo and Rosetta for product context, and the audience evaluation framework for technical assessment. Panel design does not evaluate the underlying system.

Hypothetical example: a bookkeeping-service panel

Hypothetical example, not a reported result: A service wants to examine whether its website explains who it is for. The intended population is owners and financial decision-makers considering outsourced bookkeeping for small service businesses.

It creates three contexts: an owner managing books personally, an operations lead recommending a provider, and an owner replacing a provider. These describe different decisions. The team attaches no unsupported market shares.

The panel gives equal coverage to each context, labeled analytical balance rather than a population estimate. Each includes variation in accounting familiarity, but familiarity is not inferred from age or income.

All profiles receive the same task: identify the service boundary, find customer responsibilities, and explain what remains needed before contacting the provider. The task stops before a real inquiry.

Suppose a generated response asks whether historical cleanup is included. That becomes a content question, not evidence of how many prospects need cleanup or which segment is more concerned.

Next, actual evaluators can assess whether the contexts fit their buying situations. The team revises its design if the original contrasts prove unhelpful. This is a way to improve a research instrument without pretending the initial instrument discovered its own population.

Interpret differences without inventing prevalence

Compare contexts against the same question. Distinguish page-supported content, profile-dependent interpretation, and unsupported inference. A difference may warrant investigation, but profile attributes may not have caused it.

If several profiles mention a concern, describe recurrence within the configured exercise. Do not translate it into “most buyers care about this.” Repetition can reflect shared model assumptions, not independent perspectives.

Reporting boundariesCairo Labs

What a panel summary can support

Keep statements tied to the configured exercise.

Report elementAppropriate interpretationAvoid
Included contextsScope of explorationMarket coverage claim
Repeated concernCandidate research topicCustomer percentage
Missing contextKnown design gapAssumption of no need
Segment contrastQuestion for follow-upProven group difference
Coverage and recurrence do not establish real population prevalence.

Apply the audience decision checklist

  • Define the real population separately from the synthetic panel.
  • Give every segmentation axis a decision-relevant rationale.
  • Label sourced attributes, assumptions, and unknowns.
  • Explain allocation without unsupported market shares.
  • Make excluded contexts and recruitment needs visible.
  • Use consistent materials and task boundaries.
  • Treat findings as hypotheses until checked with relevant people.

The core limitation is not merely imperfect demographic coverage. Generated panels lack the independent lived experiences that make real research informative. Adding profiles cannot guarantee missing experience appears.

Use segmentation to make assumptions visible and disagreement investigable. The synthetic persona design guide explains how to specify individual profiles without turning panel-level assumptions into stereotypes.

Next step: Explore your public page or product idea in Cairo, define one question and an audience, and use the simulated report to plan what to investigate next.

References

  1. Nielsen Norman Group: Synthetic Users — If, When, and How ↗