Sales & CRM

How to forecast quarterly revenue as Small Law and Accounting Practices

Sales & CRMFor Small Law and Accounting Practices3 apps12 steps~24 min to set up

At a six-attorney firm or four-CPA practice, 'forecasting quarterly revenue' means one partner pulling Clio billing reports into Excel on a Sunday night, cross-referencing QuickBooks for collected versus billed, scrolling through Outlook threads to remember which retainers are renewing, and guessing at utilization rates because three associates haven't submitted their time yet. The number you land on is already stale before you share it. You have no clean view of pipeline — what's likely to close, which client matters are winding down, which retainers are at risk of non-renewal. The forecast lives in one person's head, and that person is already billing 180 hours a month.

Build this on Starch → See the apps used

Sales & CRMFor Small Law and Accounting Practices3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live quarterly revenue forecast that pulls collected revenue, outstanding invoices, and retainer renewals from QuickBooks and your practice management tool — updated on a schedule, not rebuilt by hand each time.

A scenario model that shows you what happens to the quarter if two retainers don't renew, a major matter closes early, or you add a lateral hire mid-quarter — so you're making decisions with numbers, not instincts.

A partner-facing dashboard that breaks revenue by practice area, attorney, and matter type, with a clean separation between billed, collected, and forecasted — the number you'd want before a Monday morning partner meeting.

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Scenario Analysis Investor Reporting CRM

Data sources & config

Starch syncs your QuickBooks data on a schedule — invoices, payments, vendors, and journal entries refresh automatically and power the forecast and scenario models. Connect Outlook from Starch's integration catalog; the agent queries it live when the CRM needs email thread context or last-contact dates. Google Calendar or Outlook Calendar syncs on a schedule to surface matter-related appointments and upcoming deadlines that inform utilization assumptions.

Prompts to copy

Build me a quarterly revenue forecast dashboard that pulls QuickBooks invoices and payments by client and matter type, separates billed from collected, and shows a rolling 90-day projection based on open matters and active retainers.

Create three scenarios for Q3 revenue: baseline (all retainers renew, current matter load), downside (two largest retainers don't renew), and upside (we close the pending estate litigation matter in July). Pull actual revenue data from QuickBooks as the starting point.

Build me a CRM that tracks client relationships by practice area, matter status, retainer renewal date, and last partner contact — and flags any active client I haven't billed or contacted in 45 days.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect QuickBooks as a scheduled-sync provider. Starch pulls your invoices, payments, clients, and journal entries on a recurring schedule — no manual exports, no copy-pasting into Excel.

2 Start with the Scenario Analysis app from the Starch App Store. It uses your actual QuickBooks revenue and expense data as the baseline so your scenarios start from real numbers, not last year's budget.

3 Tell Starch: 'Build three Q3 revenue scenarios — baseline with all retainers renewing, downside with our two largest retainers not renewing, and upside assuming the pending business acquisition matter closes in August.' Starch builds the model and shows each scenario's projected collected revenue, burn, and cushion side-by-side.

4 Customize the scenario inputs to match how your practice actually works — hourly rates by practice area, typical matter duration, retainer renewal probability by client tier. Describe these in plain language and Starch adjusts the model.

5 Connect Outlook from Starch's integration catalog. The agent queries it live to pull last-contact dates and thread context into your client view — so you can see which clients haven't heard from a partner recently alongside their billing status.

6 Use the CRM app to build a client pipeline view organized by matter status (active, closing, proposal stage) and retainer renewal date. Tell Starch: 'Show me all clients with retainers renewing in the next 60 days, sorted by annual value, with a flag if no partner has contacted them in the last 30 days.'

7 Sync Google Calendar or Outlook Calendar so Starch can factor scheduled client meetings and court dates into utilization assumptions — matters with heavy calendar activity in the quarter are more likely to generate billings than matters that have gone quiet.

8 Set up a weekly automation: every Monday morning, Starch pulls the latest QuickBooks payment data, checks for any invoices that moved from outstanding to collected, and updates the forecast. You get a Slack or email summary of where the quarter stands without touching a spreadsheet.

9 Use the Investor Reporting app — or fork it for partner reporting — to generate a monthly practice performance summary: collected revenue, realization rate by practice area, outstanding AR, and how the quarter is tracking against forecast. Describe the format you want and Starch drafts it.

10 Once the scenario model is running, add a 'retainer risk' flag: tell Starch to highlight any client whose collected revenue this quarter is more than 20% below the same quarter last year. These are the retention conversations to have before the quarter closes.

11 Share the dashboard with your managing partner or office manager directly — they get a live view of the forecast without emailing you for the latest version of the spreadsheet.

12 At quarter-end, tell Starch: 'Compare actual collected revenue against each of the three scenarios we built in July and summarize where we landed and why.' Use that as the foundation for the next quarter's planning conversation.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q3 2026 Forecast — Four-CPA Practice

Sample numbers from a real run

Active retainer clients (8)	184,000
Project-based engagements in progress (12)	97,000
Outstanding AR from Q2 work (collectible)	43,000
Proposals in discussion (50% probability)	31,000
Downside: two retainers at risk of non-renewal	-48,000

It's early July. The managing partner at a four-CPA firm wants to know if Q3 is on track before committing to hiring a junior associate in August. Starch has been syncing QuickBooks data on a schedule all year. The baseline scenario shows $281,000 in expected Q3 collections — $184,000 from retainer clients, $97,000 from active project engagements, and $43,000 in collectible AR from Q2 work that's still outstanding. The downside scenario strips out two retainers — a $28,000/quarter real estate developer who's been slow to respond to renewal conversations, and a $20,000/quarter family office that just brought their bookkeeping in-house — landing at $233,000. The CRM flags both clients as 'no partner contact in 38 days.' The managing partner sends personal outreach to both that afternoon. The associate hire decision gets deferred to the downside-case number: if Q3 collects below $245,000, hold the hire. Starch sends a Slack message every Monday with the updated collection total. No Sunday-night Excel.

Measurement

How you'll know it's working

Realization rate by practice area (billed hours collected vs. billed hours invoiced)

Outstanding AR aging — invoices over 60 days as a percentage of quarterly revenue

Retainer renewal rate — percentage of retainer clients renewing quarter-over-quarter

Utilization rate by attorney or CPA — billable hours as a percentage of available hours

Collected revenue vs. forecast variance — actual Q3 collections versus the scenario that matched market conditions

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Clio Manage reporting + Excel

Clio's built-in reports show billed hours and invoice status, but you're still exporting CSVs and building the forecast model manually in Excel every quarter — the data is there, the assembly isn't.

QuickBooks reporting alone

QuickBooks gives you collected revenue and AR aging, but has no concept of matter pipeline, retainer renewal risk, or scenario modeling — it tells you what happened, not what's likely to happen next.

Karbon or TaxDome

Karbon and TaxDome are strong for workflow and deadline management, but neither builds a revenue forecast model or lets you compare scenarios — you'd still need a separate spreadsheet for the financial planning piece.

Hiring a fractional CFO

A fractional CFO can build a sophisticated model, but at $2,000–$5,000/month for a small practice, you're paying for a person to do work that Starch can automate — and the model doesn't update itself between check-ins.

FreshBooks or Xero standalone

Both are reachable from Starch's integration catalog and solid for invoicing, but like QuickBooks they're accounting tools, not forecasting surfaces — the scenario modeling and pipeline view have to be built on top.

On Starch RECOMMENDED

One platform — scenario planning, investor reporting, crm all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch connect to Clio Manage directly?

Clio isn't currently listed as a scheduled-sync provider with a dedicated data pipeline. If Clio has a web interface you log into, Starch can automate it through browser automation — no API needed. For the financial forecasting workflow, the most reliable path is connecting QuickBooks (scheduled sync) as the revenue data source, since that's where your collected payments and invoices actually live regardless of which practice management tool you use.

QuickBooks is already connected to my billing system — does Starch see the same data?

Yes. Starch syncs your QuickBooks data on a schedule — invoices, payments, vendors, and journal entries. Whatever has been posted to QuickBooks is available in Starch. One honest limit: QuickBooks report views like the P&L summary are temporarily unavailable due to a connector issue, but entity-level data (individual invoices, payments, bills) syncs normally and is sufficient for building a revenue forecast.

Can Starch pull unbilled time from our timekeeping system into the forecast?

If your timekeeping system is web-accessible, Starch can automate it through browser automation — no API required. If it exports to QuickBooks or syncs data there, Starch already sees it. Describe what you want: 'Include unbilled hours from this week as a probability-weighted forecast addition' — and Starch builds the logic. The more data lands in QuickBooks, the cleaner the model.

Is this actually useful for a four-person CPA practice, or is it built for tech startups?

The Scenario Analysis and CRM apps were built for operator founders broadly — not just venture-backed startups. A CPA practice with eight retainer clients and variable project revenue is exactly the use case: known recurring base, uncertain project pipeline, and occasional lumpy client losses that can blow up a quarter. The scenario model works the same way whether your revenue driver is MRR or quarterly retainer renewals.

Is Starch SOC 2 certified? We handle client financial data.

Starch is not SOC 2 Type II certified today. That's worth knowing before connecting systems that hold client confidential financial information. If your firm's data policy requires SOC 2 before connecting accounting data, that's a real constraint — and we'd rather you know it upfront than find out later.

How long does it take to set this up versus just doing it in Excel?

Connecting QuickBooks and describing the forecast structure to Starch takes an hour or two the first time. The payoff is that it doesn't have to be rebuilt each quarter — Starch updates the model as new QuickBooks data syncs in. The Sunday-night-rebuild problem is what you're solving, not the initial build time.