Skip to content
Guide

Use B4Math as a disciplined decision workflow.

Start with a public rehearsal, inspect the evidence and uncertainty behind the result, then save private history when repeated decisions make that useful.

Run a decision rehearsal
01

Quickstart

  1. Open the decision rehearsal.
  2. Start with the loaded example or describe one real decision.
  3. Confirm the current state, proposed change, audience, goal, constraints, horizon, and success metric.
  4. Run the rehearsal and read the conditional recommendation first.
  5. Inspect assumptions, evidence gaps, customer reactions, scenario ranges, and the next test.
02

Write a strong decision brief

Name the current state, proposed move, target customer, market, timing, objective, constraint, success metric, and evidence already available.

Raise Pro from $99 to $129 for seed-stage B2B SaaS teams in September. Protect current renewals and proceed only if five of 15 qualified accounts commit to an annual plan.
03

Distinguish facts from assumptions

State which inputs come from your team, which come from observed customers or operating data, which are model assumptions, and which important facts are missing. Weak evidence should narrow the claim, not increase the precision.

04

Read the decision memo in order

Start with the recommendation and why. Then inspect evidence quality, plausible range, strongest supporting factor, main downside, sensitive assumptions, reversal conditions, missing evidence, next test, rollout boundary, and stop conditions.

05

Save only when history is useful

Public rehearsals do not require an account. Signed-in workspace users can save, reopen, rename, duplicate, and delete only their own decision records.

06

Validate important decisions in the real world

Scenario ranges are conditional decision support, not promises. Use customer interviews, experiments, financial review, legal review, operating data, and observed outcomes before committing material resources.