SMB Pulse

Can I afford a second roaster?

Know what a second roaster costs each month, fully loaded, and whether the cash outlook carries it from the planned start date.

Pick a use case and follow its guide

Can I afford a second roaster?

0 of 3 steps done

Sign in to try the demo
  1. Step 1. Open Operations, then hiring.afford_role. Type Second roaster in role. Enter the pay range in hourly_low and hourly_high, each with its Currency, for example 24.00 and 27.00 USD; type the hours in weekly_hours, for example 40; the start date in start_date, for example 2026-11-01; and the monthly benefits in benefits_monthly, for example 650.00 USD. Press Add one_off_costs, type Hiring and equipment in label, the amount in amount (for example 1500.00) and USD in its Currency. Leave basis at top and press Call hiring.afford_role. Under ANSWERED, rate_used is the top of the range. base_monthly is the monthly pay, employer_tax_monthly the employer tax at employer_tax_rate (labelled assumed when the business profile holds no rate), and benefits_monthly the benefits you entered. fully_loaded_monthly adds them up. In months, the start month also carries the one-off costs; every later month is the fully loaded figure. The answer's scenario_id names this scenario for the next steps. This call saves the scenario, its inputs and its figures, and nothing else. Open hiring.afford_role

  2. Step 2. On the same answer, read outlook, the business's cash outlook with the hire added from its start date. hire_outflows lists the one-off cost and the hire's payroll dates and amounts. The tightest week of the start month is shown twice, side by side: start_month_without_hire and start_month_with_hire, each with its low-band balance, set against the cash_buffer. breach_introduced says whether the hire pushes that week below the buffer. The nearest tight week is shown without_hire and with_hire too, so you can see a shortfall that is there whatever you decide. Break-even gives break_even_revenue_monthly at the blended_margin_pct, and how many units a month of the best seller the hire needs. Open hiring.afford_role

  3. Step 3. Open Operations, then hiring.explain_affordability. Paste the scenario_id from the first step into scenario_id and press Run hiring.explain_affordability. The run turns SUCCEEDED in under a minute. Under OK, verdict_sentence says in one sentence whether the start month's tightest week stays above the buffer with the hire, with both low-band balances. considerations holds exactly two things to consider, each built from the scenario's own figures, such as a tight week that is below the buffer whatever is decided, the fully loaded monthly cost with its one-off costs, or the revenue the hire must cover. The cash advisor chooses which two and points at the figures, and the app fills them, so the choice and the wording change from run to run and the figures do not. held_reason is null. Nothing is stored and nothing is sent. Open hiring.explain_affordability

Did it fit your work?