Interview
Ask source packet whether the strongest assumption is real.
Synthetic Customer Research
Use MiroFish when customer hypotheses before real validation needs more than a one-shot answer. MiroFish uses seed material, named actors, reaction rounds, and structured reports; treat every run as decision support, not a guaranteed prediction.
Operating facts
Scenario angle
For synthetic customer research, the 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
Run a synthetic customer research scenario. Use this 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
Ask source packet whether the strongest assumption is real.
Refresh facts that may have changed since the source packet was written.
Change one assumption around customer hypotheses before real validation and compare the new branch map with the original.
Evidence choice
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 running synthetic customer research so the report does not treat a weak claim as settled.
Why MiroFish
| 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
Synthetic Customer Research 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
The best next step after a synthetic customer research run 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
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.
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
Before using synthetic customer research 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
Prepare the decision boundary, source notes, actor roles, known objections, timing, and the signals that would change the result.
No. Use it to generate hypotheses, pressure points, and validation questions, then confirm important claims with real data or accountable review.
A structured report with reaction paths, weak assumptions, evidence gaps, and follow-up questions you can challenge.
Rerun after changing one important assumption, such as the actor list, timing window, evidence strength, or public message.
Next paths