DECISION OSby WhyOptic

05 / Assumptions → review → refine

Make the assumptions visible.

Everything starts with an explicit economic structure. Validate the relationships before replacing fictional inputs with real company numbers.

Fictional · editable · transparent

Model inputs / all fictional

Define the economic structure

Job mix and costs live here. Driver levers apply changes relative to this baseline.

Revenue streamMix %Price / jobBought-inHours / job

Job mix must total 100% and represents job counts. Capacity uses team-hours; labour cost uses workers × paid hours × loaded pay. Bought-in costs exclude those wages.

USD · cash in the bank on day one

USD · excludes delivery wages

People · full crew per team

All hours paid, including idle time

USD · includes employment on-costs

Days · applies to every stream

USD · immediate capital cash outlay

Fraction · 0.08 means 8%

Current truth

Set the baseline levers

The starting business and the steady opening pipeline. Planned levers stay separate, so the baseline marker always shows today's position.

Demand

Demand

Demand

Capacity

Capacity

Capacity

Margin

Margin

Margin

Overhead

Overhead

Liquidity

Liquidity

Liquidity

Baseline reset cost is zero: it is a future one-off change cost. Productive hours cannot exceed paid hours.

Transparent relationships

What the model does, and what it assumes

+The five-driver logic

Demand creates booked opportunities. Capacity limits how many jobs can start at a sustainable rate. Margin changes value and direct costs. Overhead sets the gross-profit floor. Liquidity controls payment dates. A lever is stored once, even when its effects cross several drivers.

Demand jobs = enquiries × conversion + direct repeat/referral jobs
Hours/job = weighted clean hours × (1 − efficiency gain) × (1 + remaining rework)
Capacity jobs = teams × productive team-hours ÷ hours/job
Delivered jobs = min(demand jobs, capacity jobs)
Revenue = delivered jobs × weighted quoted price
Gross profit = revenue − bought-in costs − ALL paid delivery wages
GP floor = baseline overhead + overhead change + added support
GP ceiling = capacity jobs × (price − bought-in/job) − paid delivery wages
Monthly surplus = gross profit − GP floor
Break-even jobs = (paid delivery wages + overhead) ÷ (price − bought-in/job)
+How time, cash and opening balances work

A model month is exactly 30 days and the horizon is 180 days. Fractional jobs represent a smooth average flow. A steady baseline pipeline seeds opening receivables, bought-in work in progress, deposits and supplier payables. Opening cash is entered separately.

Deposits arrive at start. Bought-in costs are purchased at start and paid after supplier terms. Revenue and bought-in expense are recognised at completion; the final customer balance follows collection terms. Paid wages and overhead accrue and are paid daily, including idle time. New driver settings affect new cohorts; old cohorts keep their original terms.

Stage changes are immediate on their activation day. Equipment for added teams is paid immediately, reduces cash and is capitalised outside this simplified operating P&L. Removing a team has no severance or asset-sale proceeds. The overhead reset cost is expensed and paid once at its stage. An opening-to-closing working-capital bridge reconciles profit to cash.

+Scope and limits to discuss with your reviewer

Price has no automatic demand elasticity: change conversion explicitly if higher prices affect bookings. Team availability, weather, scheduling, quality limits, hiring lead time, cost inflation, bad debts and retention payments are not modelled. Added support does not automatically change throughput; set productive hours or efficiency explicitly.

Job mix stays constant across demand and delivery. All streams share one completion time; capacity is a smooth sustainable flow, not a detailed schedule. Unserved work is shown but not carried as a backlog.

No tax, debt, depreciation, financing, owner distributions or stochastic forecasts. No discounting, NPV or inferred probabilities. Costs and conversion assumptions must be validated before real decisions. Negative cash does not stop simulated work: it exposes the amount that would need finance.

+What this version does and does not connect

Every view reads from one pure calculation layer: the corridor, the five drivers, the sequence comparison, the cash paths, the assumptions and the review. There is no second set of numbers anywhere in the interface.

Nothing connects to a live business, an accounting system or an external account. The scenario file you download is a plain JSON record of your inputs, and the draft saved in this browser is a convenience only. Review notes stay local until you download them.

Ready for a real conversation

Capture the reviewer's feedback

Review the fictional model together, then bring the notes back for the next version.

Notes stay in this browser unless you download them.

Illustrative economics · 30-day model months · USD · nothing connects to a live businessFive drivers. Connected consequences. · Decision OS by WhyOptic