Delaying a hire saves salary. It can also delay the revenue that hire was supposed to bring in. A decision that looks cheaper on the payroll line can leave the business worse off by December.
The answer depends on the connections between those numbers. Follow them and you can see which assumptions make the decision work.
That is one of the most useful things a financial model can do. It gives people a shared way to ask what happens next.
Follow the decision beyond the first number
Consider a sales hire with a monthly cost of $15,000 and expected monthly revenue of $40,000 at full productivity. Assume an 80% gross margin and a 3-month ramp: 1/3 of full productivity, then 2/3, then full productivity.
Compare starting in February with starting in May, through the same December end date. Keep everything else fixed and treat the sales output as additional company revenue.
| Effect of starting in May instead of February | Change through December |
|---|---|
| Hire cost | $45,000 less |
| Revenue | $120,000 less |
| Gross profit | $96,000 less |
| Operating income | $51,000 less |
Both hires finish the same ramp before December. The difference is equivalent to 3 months at full productivity. Under these assumptions, the later start saves $45,000 and gives up $96,000 of gross profit.
That is a reason to examine the sales assumption. The earlier start needs $56,250 of additional revenue within the year to cover its additional cost:
Additional revenue needed = $45,000 / 80% = $56,250If there isn't enough demand for the hire to produce that revenue, the forecast needs to change. Moving the start date around won't resolve that uncertainty.
Give people something specific to disagree about
A hiring discussion becomes more useful when the disagreement has a location in the model.
The sales lead might think the ramp takes 5 months. Finance might question whether the salesperson's expected revenue includes accounts another rep would have closed anyway. The founder might agree with the annual result but worry about paying salaries before customers pay their invoices.
Each objection changes a different part of the decision. You can test a longer ramp or remove transferred sales from the estimate of additional revenue. Adding customer payment dates to the cash forecast lets you examine whether the company can fund the plan.
Then compare the results against the same starting plan. You can see whether people disagree about the cost, the expected benefit or the ability to fund it.
The model gives the discussion a structure. The people closest to the work supply the evidence.
A formula makes a belief inspectable
People should be able to understand how their decisions affect the business around them.
There is an important limit. A model describes the relationships you put into it. It cannot establish that a product feature will improve retention just because someone connects those variables with a formula.
If the expected retention improvement is uncertain, give it a range and test the decision across that range. A plan that only works at the most optimistic end deserves a different conversation from a plan that works throughout it.
Good modeling makes uncertainty easier to discuss. It shows which belief you need to investigate and how much it matters to the result.
Work through the connections with Ari
In CFO.ai, Ari and the user work against the same business model. You can ask Ari to explore a change, inspect the assumptions behind it and correct them yourself.
Canvas blocks can give that discussion a visual form: a timeline for a hiring decision, or a chart showing how an outcome changes as an assumption moves. The view should help you follow the relevant relationships. It can only explain the dependencies represented in its model or disclosed simulation.
For the hiring example, the useful view would keep the start date close to the cost and expected output. It would also make clear that annual operating income doesn't answer whether the company can fund the hire's first few months.
That is the standard for a useful business model: after working with it, you can explain the decision more precisely. You know which assumption supports it and what new evidence would make you reconsider.
For more on connecting a hiring plan to expected output, read Build a capacity model that links headcount to revenue.
CFO.ai editorial adaptation of Siqi Chen's original Runway essay. Updated September 18, 2026.