Sales & CRM

How to forecast quarterly revenue as Event Agency Founders

Sales & CRMFor Event Agency Founders2 apps12 steps~24 min to set up

You're trying to forecast Q3 revenue while juggling 14 open event files. Your 'pipeline' is a Google Sheet with columns like 'Proposal Sent?', 'Deposit Paid?', and a color-coded mess of follow-up dates. HoneyBook or Dubsado shows you invoices but not conversion probability. You don't know if you're on track for $380K this quarter or $290K until the last week of the quarter when it's too late to do anything about it. Aisle Planner has no concept of a revenue forecast. You're doing the math yourself in a spreadsheet tab labeled 'maybe Q3' and it's already out of date.

Build this on Starch → See the apps used

Sales & CRMFor Event Agency Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live event-agency pipeline CRM that tracks every lead, proposal, deposit, and signed contract — with close probability and expected revenue per event, so you can see your realistic Q3 number at any time without opening a spreadsheet

A quarterly revenue forecast that rolls up your pipeline data against your actual invoiced and collected amounts, updated automatically as deals move through stages

Scenario views that show what Q3 looks like if 60% of open proposals close versus 80%, so you can decide now whether to push harder on new inquiries or protect margin on the events already booked

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

CRM Scenario Analysis

Data sources & config

Connect Gmail from Starch's integration catalog — the agent queries your email threads live to attach vendor and client correspondence to the right deal. Connect Stripe so Starch syncs your invoices and payments on a schedule, giving the forecast real collected-revenue numbers rather than just pipeline estimates. If you use QuickBooks, Starch syncs that too on a schedule for a clean picture of what's actually been recognized. For leads coming from HoneyBook or Dubsado, Starch automates pulling inquiry data through your browser — no API needed.

Prompts to copy

Build me a CRM for my event agency. Stages are: Inquiry, Proposal Sent, Contract Out, Deposit Received, Fully Booked, Completed, Lost. Fields I need on each deal: event type (corporate, social, nonprofit), event date, estimated event budget, our fee, proposal sent date, contract signed date, deposit amount, deposit received date, lead source (referral, Instagram, venue partner, Cvent inquiry). I want to see a pipeline view sorted by event date and a revenue forecast view that shows expected fees this quarter grouped by stage.

Build me a scenario analysis for Q3 revenue. Baseline is my current pipeline from the CRM: $180K in proposals out, $95K in signed contracts, $42K in deposits collected. Show me three scenarios: (1) 50% of open proposals close, (2) 70% close, (3) 90% close. For each, show projected Q3 collected revenue, projected Q3 recognized revenue, and how many new inquiries I'd need to hit $400K if close rate is 50%.

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

Walkthrough

Step-by-step

1 Start with the CRM app from the Starch App Store. Tell Starch your pipeline stages, the fields that matter to your agency (event type, event date, your fee vs. client budget, lead source), and it builds the schema around how you actually sell — not how HubSpot thinks you should.

2 Import your existing leads and open proposals. If your current list is in a Google Sheet, connect Google Sheets from Starch's integration catalog and the agent pulls it in live. If it's in HoneyBook or Dubsado, Starch automates the export through your browser — no API needed.

3 Set close probability by stage. Tell Starch: 'Inquiry = 20%, Proposal Sent = 45%, Contract Out = 75%, Deposit Received = 95%.' The forecast view will weight your pipeline by these numbers automatically.

4 Connect Gmail from Starch's integration catalog so vendor quote threads, client revision emails, and deposit confirmation notes attach to the right deal record. Ask the CRM: 'Which open proposals haven't had any email activity in the last 10 days?' and get a real list.

5 Connect Stripe so Starch syncs your actual invoices and payments on a schedule. Now your forecast has two columns: pipeline-weighted expected revenue and real collected revenue — and you can see the gap clearly.

6 Ask the CRM a direct question: 'What is my probability-weighted revenue forecast for Q3 2026 by stage?' Starch runs the math across every open deal and returns a number you can actually stand behind.

7 Open the Scenario Analysis app and describe your three forecasting scenarios — conservative close rate, base case, and upside. Wire it to the same pipeline numbers so the scenarios start from your actual data, not a blank spreadsheet.

8 For each scenario, Starch shows you Q3 projected collected revenue, projected recognized revenue, and — if you want — how many new inquiries at your average fee size you'd need to close to hit a target number.

9 Set a recurring prompt: every Monday morning, Starch checks your pipeline for deals with no activity in 7 days, proposals more than 14 days old without a signed contract, and invoices past due — and Slacks you a digest. Connect Slack from Starch's integration catalog.

10 At the end of each month, ask Starch: 'Compare my Q3 forecast from four weeks ago to where I actually stand today. What closed, what stalled, and what's the new probability-weighted number?' Use this as your gut-check before you commit to new vendor contracts or staffing.

11 When a deal closes, tell Starch to move it to 'Fully Booked' — the forecast updates instantly. No manual spreadsheet math, no re-coloring cells at 11pm before a site visit.

12 At quarter end, run the full reconciliation: 'Show me every deal that was in my Q3 pipeline on July 1, what stage it was at, what I forecasted it to close for, and what it actually closed for (or why it was lost).' That's your baseline for calibrating Q4 close-rate assumptions.

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 — Meridian Events Co. (July pipeline review)

Sample numbers from a real run

Signed contracts (Deposit Received stage)	94,000
Contracts out, awaiting signature (Contract Out stage @ 75%)	41,250
Proposals sent, not yet contracted (Proposal Sent stage @ 45%)	29,700
New inquiries, no proposal yet (Inquiry stage @ 20%)	8,600
Total probability-weighted Q3 forecast	173,550

It's July 8th. Meridian Events Co. has 11 open deals in the pipeline. Three corporate retreats are fully signed with deposits in — $94K that's essentially certain. Two more contracts are out to client legal teams, together worth $55K in fees; at 75% probability those add $41K to the forecast. Four proposals went out in June totaling $66K in fees; at 45% close rate that's $29.7K. Two fresh inquiries from a venue partner referral sit at 20%, contributing $8.6K. Total probability-weighted Q3 forecast: $173,550. The target is $200K. The Scenario Analysis shows that if close rate on the proposals jumps to 65% — historically accurate for referral-sourced leads — the forecast hits $189K, still $11K short. Starch's output: you need one more signed contract or a new referral inquiry at your average $18K fee to get there. That's a concrete action, not a feeling.

Measurement

How you'll know it's working

Probability-weighted pipeline value by quarter (broken out by stage)

Proposal-to-contract conversion rate by lead source (referral vs. venue partner vs. inbound)

Average days from proposal sent to contract signed (pipeline velocity)

Collected revenue vs. forecasted revenue gap at month-end

Revenue concentration risk — percentage of quarterly forecast sitting in any single event

Comparison

What this replaces

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

Google Sheets forecast tab

Free and familiar, but you're updating it manually after every conversation with a client, it breaks when someone edits the wrong cell, and it has no idea what's in your Gmail or Stripe.

HoneyBook or Dubsado

Good for proposals and contracts, but their pipeline and revenue forecasting views are too shallow for a multi-event quarter — they show invoiced amounts, not probability-weighted pipeline, and you can't ask them questions in plain language.

HubSpot Sales Hub

Genuinely powerful pipeline forecasting, but the configuration overhead is real, the cost scales fast past the free tier, and it knows nothing about your event dates, vendor quotes, or the way your agency actually tracks a deal.

Aisle Planner

Purpose-built for event logistics and client portals, but has no revenue forecasting capability — you'd still be running a separate spreadsheet for the pipeline math.

On Starch RECOMMENDED

One platform — crm, scenario planning 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

My pipeline lives in HoneyBook right now. Can Starch pull it in without me re-entering everything?

Yes. HoneyBook doesn't have a public API that Starch syncs on a schedule, but Starch automates the export through your browser — no API needed. You log in once, Starch pulls your open proposals and client records, and they land in your CRM. After that, you'll want to keep the CRM as your primary source of truth for pipeline data and use HoneyBook mainly for client-facing proposals and contracts.

Will Starch actually understand event-agency-specific fields like 'event date' or 'venue partner referral'? Or will I have to map everything to generic CRM fields?

That's the point of describing it in your own words. Tell Starch your stages, your field names, and how you think about a deal — 'event date,' 'our fee vs. client budget,' 'lead source: venue partner' — and it builds the schema around your language. You're not mapping your business into someone else's pipeline template.

My revenue is lumpy — one $80K corporate summit can be 40% of the quarter. Does the forecast handle that?

Yes, and Starch can flag it explicitly. Ask: 'What percentage of my Q3 forecast is concentrated in any single event?' or 'Show me my Q3 pipeline excluding the Hartwell Summit — what does the rest of the quarter look like?' Revenue concentration is a real risk for event agencies, and this is exactly the kind of question the forecast is built to answer.

I use QuickBooks to track what's actually been invoiced and paid. Can that feed into the forecast?

Yes. Starch syncs your QuickBooks invoices, payments, and bills on a schedule — entity-level data comes through normally. One honest note: QuickBooks report views like P&L and Transaction List are temporarily unavailable due to a connector issue, but the underlying invoice and payment data syncs fine, which is what the revenue forecast actually needs.

Is my client data safe? Event agencies handle a lot of private client information.

Starch is not SOC 2 Type II certified yet — that's the honest answer. If you're working with enterprise corporate clients who have strict vendor security review requirements, that's worth knowing upfront. For most independent event agencies handling typical client data, the security posture is solid, but we won't pretend a certification exists that doesn't.

What if I want to forecast by event type — corporate vs. social vs. nonprofit — instead of just by quarter?

Just ask. 'Break down my Q3 probability-weighted forecast by event type' is a valid question the CRM can answer if you've been tracking event type as a field. This is why the setup step matters — if you tell Starch to capture event type from day one, every downstream analysis can slice on it.