Assumption testing
Every plan sits on unstated ifs. Testing means you write them, rank them by how much they would change the decision, and gather evidence on the top few.
use case
A plan can look robust while resting on two unverified sentences. Argumont extracts those sentences, classifies them, and keeps them inspectable.
People argue conclusions. The fight is usually in the assumptions. If gross margin depends on an unmeasured cost, that is the work.
User-confirmed numbers stay user-confirmed until something else supports them.
You leave knowing which assumptions are load-bearing, which are decorative, and what evidence would change the verdict.
Every plan sits on unstated ifs. Testing means you write them, rank them by how much they would change the decision, and gather evidence on the top few.
Most strategy documents mix five kinds of statement. Argumont labels them so an assumption cannot survive as a fact because it was formatted in bold.
Confidence should fall when evidence is thin, dates are old, or roles disagree. It should not rise because the slide is pretty or the room is aligned.
A use case is a job: challenge, compare, research, test. It is not the same as a decision type. Pricing can use several of these jobs.
Argumont challenges assumptions, researches evidence, compares competing approaches, and identifies the strongest decision.
Test the assumptions