Panel Marketplace, Persona Chat, or Causal Experiment: Choose by the Decision
A panel marketplace, a synthetic persona chat, and a controlled causal experiment answer different research questions. Choose a panel marketplace when the study requires recruited respondents. Use persona chat to develop hypotheses. Use a causal experiment when the business must determine which action changes buyer choice before committing budget.
Naming where a method breaks lets a team catch the misuse before it reaches budget. The costly error is asking exploratory output to carry a pricing, messaging, or positioning decision. If the method never compared actions under controlled conditions, it cannot isolate what caused the result.
Match the tool to the evidence required
A panel marketplace supplies recruited respondents to research applications through an API, as described in its respondent-sourcing documentation. That is a fieldwork capability. It does not turn a survey into a causal experiment.
| Research layer | Question it can answer | Appropriate use | What it cannot establish alone |
|---|---|---|---|
| Panel marketplace | What do recruited respondents report? | Tracking studies, syndicated research, or workflows that require a respondent-supply API | Which action caused a difference in buyer behavior |
| Synthetic persona chat | What hypotheses or reactions should the team examine? | Early exploration and question development | Whether one action changes an outcome relative to another |
| Controlled causal experiment | Which product, price, message, or position changes buyer choice? | Decisions that require a cause-and-effect comparison before budget or roadmap commitment | Ongoing respondent recruitment or per-completed-interview fieldwork |
What is the substitution risk?
Persona chat can surface language, reactions, and hypotheses worth testing. The boundary appears when a team treats those outputs as evidence that one proposed action will outperform another. A conversation is not a designed comparison, and a directional response is not an estimate of causal effect.
The same boundary applies to ordinary fieldwork. Recruiting real people improves the relevance of the respondent source, but respondent identity does not determine study design. A survey can involve real people and still fail to isolate the effect of a price, claim, or launch message.
When the evidence does not match the decision, the contradiction arrives after spend is committed. The larger cost is not the research spend but acting on a signal that was never designed to answer the business question.
How do you build one causal question through the stack?
Start with the action the business can take. For example: choose price A or price B, lead with claim A or claim B, or launch position A or position B. Then define the buyer choice that would distinguish the alternatives.
Subconscious runs controlled discrete-choice experiments to isolate which action changes buyer decisions. Its studies draw on a person-level audience graph covering 800 million real people. A scale number stated without its limits reads as marketing. That is an audience-reach claim, not a claim that 800 million people are available for recruitment.
When the stakes warrant human evidence, the same causal question can move to real-human testing without changing the study's decision logic. A capability holds up under scrutiny only when its description also states what it excludes. That does not convert the platform into a panel marketplace, guarantee market performance, or replace the judgment of research teams.
Keep fieldwork in the design when it belongs there
A research stack still needs a panel marketplace when:
- A tracking study or syndicated research product depends on repeated fielding with recruited respondents.
- An existing research application needs a respondent-supply API, following a workflow such as the provider's documented demand integration.
- The methodology or stakeholder requirement calls for recruited human fieldwork.
Stating what a method will not do is what lets a buyer check the claim against its actual scope. A causal experiment does not replace that layer: Subconscious does not operate a panel marketplace, sell fieldwork by the completed interview, or replace human research operations and agency relationships.
How do you route the study by its decision?
Need recruited respondent supply: choose the fieldwork layer. Need candidate hypotheses: use exploration. Need to choose which action changes buyer behavior: design a causal comparison and decide whether real-human validation is necessary.
Review the research approach to assess the method. When the decision and alternatives are defined, scope the study.