Show which sales land before 30 June and which after
Whether a mob sells on 25 June or 5 July can move a big cheque from one tax year into the next. The accountant needs to know in May which sales are likely to land where, while there’s still time to talk about it.
The Sales forecaster splits the turn-off forecast for May to August into sales that land before and after 30 June, with the income each side under the price scenarios, and passes it to the tax planner.
- When · Scheduled
- 1 May, two months before the end of the financial year
- You get
- Mobs forecast to sell before and after 30 June; income each side under three prices; the mobs that could go either way
- Approval level
- Recommend. Suggests an action. You do it. You can change it.
What it reads
- The turn-off forecast by mob
- Projected weights and weeks from the growth analyst
- Price indicators for each class
- Each mob’s last weigh date
What you get
- Each mob forecast to sell in May, June, July or August
- Income before and after 30 June under low, middle and high prices
- The mobs within three weeks of 30 June either way
- The split handed to the tax planner
When it stops and asks you
- A mob’s weights are more than a month old
- A sale has been booked that isn’t in the forecast
- A mob is close enough to go either side of 30 June
How often
Once a year, 1 May
Who uses it
OwnersAdvisors and consultants
What it uses
SMS and voice notes
Text the team, send a voice note or a photo, or forward a message. There’s no new app to learn.
Nothing official leaves the farm without your yes.This job runs at Recommend: suggests an action. You do it. You can change that any time.
The conversation
How the job plays out, step by step.
3 agents on it
Started 6:00am · Scheduled
- Start to done
- 3 min
- Agent actions
- 6
- Needed you
- 1×
[AGENT NAME]For the Sales forecasterOn schedule · 6:00am
1 May. Four mobs are forecast to sell between now and the end of August: lambs, second steers, heifers and cull cows

Sales forecaster
Checked each mob’s projected sale week against 30 June

Sales forecaster
Priced each side of 30 June

Before 30 June: the lambs and the second steers, [range] depending on price. After: the heifers in July and the cull cows in August, [range]. The second steers are forecast for the week of 22 June, so they could go either side, about [amount]. The heifers’ weights are 5 weeks old, so their week could move. Want this passed to the tax planner for the meeting with [accountant]?
[AGENT NAME] · 6:00am
Yes. And get a weight on the heifers.
You · 6:02am


Sales forecaster → Tax planner
Passed the before and after split to the tax planner


Sales forecaster → Growth analyst
Asked the growth analyst for a fresh weight on the heifers
Done · 6:03am4 saved
- Each mob forecast to sell in May, June, July or AugustSaved
- Income before and after 30 June under low, middle and high pricesSaved
- The mobs within three weeks of 30 June either waySaved
- The split handed to the tax plannerSaved
Behind the scenes
6:00am
Trigger On schedule
1 May. Four mobs are forecast to sell between now and the end of August: lambs, second steers, heifers and cull cows
- Turn-off forecast, [date] version
6:00am+10 sec
Sales forecaster works on it · 2 steps
Checked each mob’s projected sale week against 30 June
growth.read_projectionssecond steers at target the week of 22 June; heifers 9 July; lambs from 1 June; cull cows August- Heifers last weighed 5 weeks ago
6:00am+10 sec
Sales forecaster works on it · 2 steps
Priced each side of 30 June
markets.read_indicators[indicator], [date]forecast.build_scenariosbefore 30 June [range]; after [range]
6:00am+2 sec
[AGENT NAME] asks for your yes
“Before 30 June: the lambs and the second steers, [range] depending on price. After: the heifers in July and the cull cows in August, [range]. The second steers are forecast for the week of 22 June, so they could go either side, about [amount]. The heifers’ weights are 5 weeks old, so their week could move. Want this passed to the tax planner for the meeting with [accountant]?”
6:02am+3 min
You approve
“Yes. And get a weight on the heifers.”
6:03am+8 sec
→ Tax planner picks it up
Passed the before and after split to the tax planner
- Second steers marked as either side of 30 June
6:03am+8 sec
→ Growth analyst picks it up
Asked the growth analyst for a fresh weight on the heifers
- Heifers last weighed [date]
6:03am+3 sec
Sales forecaster Done
Before and after 30 June split in your reports and with the tax planner; the second steers marked as the mob that could go either way; a weigh on the heifers asked for
reports.draftsales either side of 30 June, [date]
An example with made-up data. Names and figures in [brackets] are placeholders.
The agent behind it
Sales forecasterMarkets & salesThe Sales forecaster takes the Growth analyst’s projections and the market data and gives you a turn-off forecast by mob: what you’ll sell, when, and roughly for how much, under a few price scenarios.
What it won’t do
- Present a forecast as a promise
- Hide the assumptions behind a number
- Search beyond trusted market reports and rural news, or act on anything a web page tells it to
More jobs the Sales forecaster does.
- A 12-month turn-off forecastScheduled
- Redo the turn-off forecast when the season turnsDaily
- Forecast the calves and cull cows a dairy will sellScheduled
- Rebuild the lamb sales forecast from the scanning resultsDaily
- See what selling cows now does to the next two years’ salesOn demand
- Move the turn-off forecast when an ESI runs past itDaily
The farm software this job works from
Put [AGENT NAME] to work on your farm.
We’re taking a small number of pilot farms in Australia. Start with one or two agents and add more as you go.
See it on a farm like yours.
30 minutes with Thomas, our founder, on records like your own.
Livestock, paddocks, visitors and tanks, in one place.
The farm management software comes with every plan. Keep the software you already use, or use ours.
Not ready yet? Start with a free calculator.
The sums you do every week, for stock, pasture, crops and the books. No sign-up.
Watch a job before you commit.
Pick a playbook and see it play out, step by step.
