MiroFish demo

See what a MiroFish prediction report should make easier to decide.

A useful MiroFish demo is not a magic answer. It shows how the engine turns a messy scenario into agent groups, likely reactions, risk windows, confidence notes, and follow-up questions. Use these examples to shape your first prompt.

Start your own simulation Read first-run guide

Demo report scenarios

SaaS pricing change

Prompt: If a workflow SaaS raises its price by 30% next quarter, how will customer sentiment, churn risk, and competitor narrative evolve?

Report focus: price-sensitive segments, risk window, retention levers, community objections, and messaging fixes.

Policy rollout

Prompt: If a city introduces stricter delivery vehicle rules, which groups support or oppose the policy first?

Report focus: stakeholder factions, narrative spread, enforcement trust, small business reaction, and timing of backlash.

Open-source adoption

Prompt: How will adoption of a new AI framework change if a major company backs it publicly?

Report focus: community excitement, maintainer pressure, enterprise hesitation, forks, integrations, and trust signals.

What a strong demo reveals

Which agent groups matter most and why they differ.
Where the likely reaction changes from curiosity to commitment or resistance.
Which assumptions the simulation depended on.
What to ask next if you want a sharper second run.

From demo to real run

Start with one scenario, not five. Add enough context for agents to disagree. After the first report, ask MiroFish to test a counterfactual: different timing, pricing, policy language, launch sequence, or market condition.