Build a revenue and expense forecast straight from your accounting history. Joy reads the ledger, projects the next few periods off the trend, and states every assumption so you can defend the number.
Build a revenue and expense forecast for [the next four quarters] from our [NetSuite] history, and state the projected figures by period, the assumptions, growth rate, and sensitivity behind it.
An illustrative example. Your output will reflect your own sources, data, and prompts.
I read your last four quarters of actuals from the connected NetSuite ledger and projected the next four at the trailing trend rate. The brief below has the figures by period, the assumptions behind them, and how the total moves if growth runs faster or slower.
Your last four quarters of actuals show revenue climbing at an average of about 3.0% a quarter. Carrying that same trailing pace forward, the next four quarters project to $19.5M in revenue against $14.0M in operating expense, leaving roughly $5.5M in operating profit. Everything here extends the historical trend, so treat it as an outlook rather than a commitment.
Here is how the four projected quarters sit against the four most recent actuals. The trend line keeps rising because the projection simply extends the recent slope.
Quarterly revenue: four actuals, four projected
The projection carries revenue, operating expense, and the profit that falls out of the two, quarter by quarter.
| Quarter | Revenue | Operating expense | Operating profit |
|---|---|---|---|
| Q3 '26 | $4.66M | $3.36M | $1.30M |
| Q4 '26 | $4.80M | $3.46M | $1.34M |
| Q1 '27 | $4.94M | $3.56M | $1.38M |
| Q2 '27 | $5.09M | $3.66M | $1.43M |
| Total | $19.49M | $14.04M | $5.45M |
Three assumptions drive these numbers, and they are worth stating plainly so you can push on them.
Sensitivity is straightforward. A slower 1.5% quarterly pace pulls the four-quarter total to about $18.8M, roughly $0.7M below the projection, while a stronger 4.5% pace lifts it to about $20.2M. Hold growth where it is but let opex drift to 74% of sales and operating profit falls about $0.4M. Treat $19.5M as the middle of an $18.8M to $20.2M band rather than a single number.
Nothing here is written back to your accounting system. It is a read of the history and a projection off the trend, so you can pressure-test the assumptions before you commit a quarter to them.
Want me to rerun this at a slower growth rate to see the downside, or break the projection out by revenue line?
A forecast is only as good as the history behind it and the assumptions on top. Most of the work is plumbing: pulling actuals, lining up the periods, and deciding what growth rate to carry forward. That is the part that eats the morning and the part where a stale assumption sneaks in.
Point Joy at your accounting or ERP system through a read-only connector, or paste the period actuals directly. Revenue and operating expense by period are enough to start.
Tell Joy the horizon and the level, such as the next four quarters, consolidated or by revenue line. Say whether to carry the trend forward or use a growth rate you supply.
Joy returns the projected figures by period with a trend chart, the growth rate it used, and the assumptions spelled out, plus a short sensitivity read so you know the range around the number.
Adjust the growth rate, the expense share, or the horizon with a follow-up, then copy the projection into your model, board deck, or planning notes.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Joy carries your trailing growth rate forward period by period, so the forecast is grounded in what actually happened, not a number you typed into a cell.
Every projection names the growth rate, the expense share, and what it holds constant, so you can defend the forecast or challenge it in the same breath.
See the band around the number: what a slower or faster growth rate does to the total, so you present a range rather than a single point.
Connect to your accounting or ERP history through a read-only connector. Joy reads the ledger and never writes back to it.
Project each product or segment separately instead of the consolidated top line, so you see which line drives the growth.
Run the same projection on monthly actuals to see the shorter-horizon shape ahead of a cash review.
Ask for a conservative, base, and upside version side by side, each with its own growth assumption stated.
Project the cost base on its own to test where operating expense lands if it drifts off its historical share.
Joy reads your accounting or ERP history through a read-only connector, measures the trailing growth rate, and projects the next few periods off that trend. It returns the figures by period with a chart, the growth rate, and the assumptions it used, so the forecast is grounded in your actuals rather than a guess.
By default Joy carries your trailing period-over-period average forward, and it states that rate plainly. In the example, revenue grew about 3.0% a quarter, so the four-quarter projection lands near $19.5M. You can supply your own rate instead and Joy will rerun the projection.
It is a projection off history, not a prediction. A trend forecast is only as good as the assumption that the recent pace holds, which is why Joy states the assumptions and gives a sensitivity band. In the example the likely total of $19.5M sits inside an $18.8M to $20.2M range depending on the growth rate.
No. The connector is read-only. Joy reads the ledger history and returns a projection you can copy into your own model, deck, or planning notes. It does not post entries, change budgets, or write anything back to your accounting or ERP system.
Yes. Ask Joy to project each revenue line or segment separately and it will run the same trend projection per line, so you can see which part of the business drives the growth rather than only the consolidated top line.
Join the waitlist and be first to try this workflow when JoySuite launches.