Interview
Ask source packet whether the strongest assumption is real.
Synthetic Customer Research
Synthetic Customer Research for evidence-led scenario rehearsal
Use MiroFish when customer hypotheses before real validation depends on source packet, synthetic panel, and research handoff reacting differently. Bring seed material for source packet, run reaction rounds around synthetic panel, and review research handoff changes as decision support, not a guaranteed prediction.
Operating facts
Keep source packet and synthetic panel limits visible before opening the console.
Source packet workflowSeed material and graph context let source packet and synthetic panel react inside a bounded MiroFish world.
Synthetic panel boundaryTreat synthetic panel reactions as decision support, not as a guaranteed prediction.
Useful inputThe first useful run needs source packet, synthetic panel, research handoff, timing, constraints, and the strongest contrary signal.
Scenario readiness check
Check whether the source packet brief is ready for a MiroFish run around customer hypotheses before real validation.
Use this quick tool before opening the console for source packet and synthetic panel. A strong first run names research handoff, the pressure point, a review owner, and one outside validation move.
Preparation detail
Give source packet enough context to produce a useful disagreement.
For customer hypotheses before real validation, begin with the moment when source packet can change the path. Add what synthetic panel already knows, what research handoff might ignore, and which constraint would make the decision reversible. A narrow source packet brief helps the report produce disagreement you can inspect instead of a smooth synthetic panel story that feels confident but cannot guide the next action.
Use concrete material from source packet, synthetic panel, research handoff, timing, constraints, and the strongest contrary signal and label the parts that are still weak. If the source packet note is old, the synthetic panel move is speculative, the research handoff source is ambiguous, or the signal came from a small sample, say that directly. MiroFish can then keep strong evidence separate from convenient assumptions while it builds reaction rounds.
Before acting, compare the report with synthetic panel changing the interpretation of customer hypotheses before real validation and then check source packet against research handoff before treating the branch as useful. That outside check for research handoff should be small enough to complete quickly: one customer call, one support search, one analytics pull, one expert read, or one revised prompt with a single changed condition. The point of the first run is to improve judgment, not to outsource it.
MiroFish uses seed material from the brief to keep source packet, synthetic panel, and research handoff anchored to the same facts. For customer hypotheses before real validation, that means the report should show which claim each actor accepted, which claim each actor resisted, and which missing detail changed the branch. If the report cannot name those links, improve the input before spending attention on a larger run.
Notebook prompt: ask source packet what would make customer hypotheses before real validation feel urgent, ask synthetic panel what proof would be dismissed, and ask research handoff which missing fact would reverse the branch. Then record the exact source packet sentence in the report that changed your confidence. If no sentence changes confidence, the next move is not a bigger run; it is a better source packet, a narrower actor list, or a validation check outside the tool.
Scenario angle
The useful question is where customer hypotheses before real validation breaks.
This page is worth its own route because the reader needs a bounded rehearsal around source packet, synthetic panel, research handoff. Start by asking which role can change the story first, then keep that role visible through the report review.
First run
Copy a bounded brief into MiroFish.
Run this scenario with the source packet, the decision boundary, the actor roles, known objections, and the signals that would change the conclusion. Return reaction branches, weak assumptions, and one validation plan. Do not treat the report as a guaranteed outcome.
Validation plan
Turn output into real checks.
Evidence pull
Refresh facts that may have changed since the source packet was written.
Rerun
Change one assumption around customer hypotheses before real validation and compare the new branch map with the original.
Evidence choice
Pick source material that can be challenged later.
The first run should include source packet, synthetic panel, research handoff, timing, constraints, and the strongest contrary signal. If a source is old, ambiguous, or politically loaded, mark it before opening the console so the report does not treat a weak claim as settled.
Why MiroFish
Use a structured world instead of a loose answer.
| Need | General chat | MiroFish |
|---|---|---|
| Source packet behavior | One compressed explanation. | Named roles with incentives and memory. |
| Second-order effects | Often summarized too early. | Reaction rounds make synthetic panel changing the interpretation of customer hypotheses before real validation inspectable. |
| Review | Hard to trace after the answer. | Report, assumptions, and follow-up questions stay visible. |
Direct answer
Use this when the question depends on reactions, not only facts.
This workflow fits MiroFish when customer hypotheses before real validation could be changed by source packet, synthetic panel, or research handoff. The useful result is a branch map with weak assumptions and the next outside check, not a single confident verdict.
Outside check
Leave with one verification move, not a pile of guesses.
The best next step after the first report is to check source packet against research handoff before treating the branch as useful. That keeps the simulation useful without pretending it measured the real world.
Source packet
Bring the material that makes the run inspectable.
Start with source packet, synthetic panel, research handoff, timing, constraints, and the strongest contrary signal. MiroFish works better when each claim can be traced back to a source or an explicit assumption, especially when the run is about customer hypotheses before real validation.
Good packet
customer hypotheses before real validation; one time horizon; named roles; known constraints; and at least three signals to review after the first report.
Review owner
Name the person who can say the branch is weak.
Before using the output, assign one reviewer to challenge source packet, one to challenge synthetic panel, and one to decide whether research handoff changes the next action.
FAQ
Synthetic Customer Research FAQ
What should I prepare for synthetic customer research?
Prepare the decision boundary, source notes, actor roles, known objections, timing, and the signals that would change the result.
Can synthetic customer research replace real evidence?
No. Use it to generate hypotheses, pressure points, and validation questions, then confirm important claims with real data or accountable review.
What does MiroFish return?
A structured report with reaction paths, weak assumptions, evidence gaps, and follow-up questions you can challenge.
When should I rerun it?
Rerun after changing one important assumption, such as the actor list, timing window, evidence strength, or public message.
Next paths