Sales & CRM

How to qualify inbound leads as Event Agency Founders

Sales & CRMFor Event Agency Founders2 apps11 steps~22 min to set up

Your inquiry form — whether it's a contact page, a HoneyBook intake form, or a Dubsado questionnaire — fires off a lead notification that lands in Gmail alongside 80 other messages. You tab between your inbox, a Google Sheet tracking 'status' with colors you invented six months ago, and your brain trying to remember whether that March corporate gala lead ever got a follow-up. Half the time you write a proposal for a lead who was never serious; the other half you let a warm lead go cold because you were heads-down on a live event. There's no automatic first response, no qualification score, no way to see at a glance which inquiries are worth your next two hours.

Build this on Starch → See the apps used

Sales & CRMFor Event Agency Founders2 apps11 steps~22 min to set up

Outcome

What you'll set up

A lead CRM shaped around your agency's actual qualification criteria — event type, headcount, venue flexibility, budget range, decision timeline — not a generic deal pipeline built for a SaaS sales team

An Email Agent that drafts a personalized first-response to every new inquiry in your voice and sets a follow-up reminder if the lead goes quiet after 48 hours

A live view of every open inquiry, its qualification score, last contact date, and outstanding proposal — so you can triage your morning in two minutes instead of twenty

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 Email Agent

Data sources & config

Starch syncs your Gmail data on a schedule so the Email Agent reads incoming inquiries and thread history without you forwarding anything. The CRM connects to Gmail through the same scheduled sync to attach email threads to the right lead record automatically. If your inquiry form lives in HoneyBook or Dubsado, Starch automates data capture from those tools through your browser — no API needed — and drops new leads directly into your CRM pipeline.

Prompts to copy

Build me a CRM for my event agency. Each lead should have: event type (corporate, social, nonprofit), estimated headcount, target venue (flexible vs. client has a venue), estimated budget range, event date, decision-maker name and title, source (referral, website, Instagram, Cvent marketplace), and a qualification stage (New Inquiry, Qualified, Proposal Sent, Contract Out, Booked, Lost). I want to be able to ask 'which leads over $15k haven't had contact in five days?' and get a straight answer.

Set up the Email Agent to watch my Gmail for new event inquiry messages. When one arrives, draft a first-response that confirms receipt, asks for the three things I still need to qualify them (event date, headcount, and whether they have a venue in mind), and matches my tone — warm but efficient. If I haven't replied to a lead within 24 hours, remind me. If the lead hasn't responded to my follow-up in 48 hours, draft a short check-in note for me to review.

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

Walkthrough

Step-by-step

1 Connect Gmail to Starch — Starch syncs your Gmail data on a schedule, giving the CRM and Email Agent visibility into every inquiry thread from day one.

2 Open the CRM starter app and describe your qualification schema in plain language: event type, headcount, budget range, venue situation, decision timeline, and the pipeline stages your agency actually uses (not HubSpot's generic ones).

3 Tell Starch how your inquiry sources map to your business — referrals, your website contact form, Instagram DMs, or a listing on a venue's preferred vendor list — so every new lead is tagged at entry.

4 If you use HoneyBook, Dubsado, or a custom web form for intake, tell Starch to automate pulling new submissions into the CRM through your browser — it logs in, reads the new inquiry, and creates the CRM record with fields pre-populated.

5 Configure the Email Agent: paste in two or three examples of your best first-response emails so it learns your voice, then set the trigger — any new Gmail thread containing 'event inquiry,' 'venue availability,' or similar phrases you specify.

6 Set qualification rules directly in Starch: any lead with a budget under $5k or an event date less than six weeks out gets flagged for a quick manual review before the Email Agent drafts a response.

7 Ask the CRM: 'Show me all leads in New Inquiry status that haven't had outbound contact in three days' — use this as your morning triage view instead of scanning your inbox.

8 When a lead replies and gives you the missing details (headcount confirmed, budget range shared), update the CRM stage to Qualified and tell Starch to draft a tailored proposal outline based on the event specs in the record.

9 Move the lead to Proposal Sent when you send; Starch sets an automatic five-day follow-up reminder and drafts a 'just checking in' message for your review if no reply comes.

10 Track your close rate by source each month — ask Starch 'what percentage of Instagram leads booked in Q1 versus referrals?' — so you know where to point your next marketing dollar.

11 Any lead marked Lost gets a note field for your loss reason (budget, timing, competitor, ghosted) — ask Starch to summarize loss patterns quarterly so you can adjust your intake questions.

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

April 2026 inquiry week — corporate offsite season

Sample numbers from a real run

Tech company offsite — 120 pax, flexible venue	28,000
Nonprofit gala — 200 pax, client has venue	14,500
Birthday party — 40 pax, backyard	3,200
Law firm holiday dinner — 80 pax, TBD	9,800

Four inquiries hit your Gmail on Wednesday morning during load-in for a different event. The Email Agent catches all four, drafts first-response messages within minutes, and flags the $3,200 backyard birthday — below your $5k floor — for your manual review before sending. By the time you're back at your desk Thursday, the tech company ($28k) and the law firm ($9.8k) have both replied with headcount and date confirmations. Starch has already moved them to Qualified in the CRM and surfaced them at the top of your pipeline. The nonprofit ($14.5k) is still at New Inquiry; you ask Starch 'did they reply at all?' and get the full thread summary in a sentence — they asked about AV, no answer on budget yet. You instruct the Email Agent to send the 48-hour check-in draft. Total time spent on intake that week: about 25 minutes across four leads, instead of the two hours it would have taken toggling between Gmail and your spreadsheet.

Measurement

How you'll know it's working

Inquiry-to-proposal rate: percentage of new inquiries that get a proposal sent within five business days

Proposal-to-close rate: broken down by event type (corporate vs. social) and inquiry source (referral vs. web vs. venue listing)

Average response time to first inquiry: how fast a lead gets your first reply, in hours

Pipeline value by stage: total estimated revenue across Qualified, Proposal Sent, and Contract Out at any point in the month

Loss reason distribution: ghosted vs. budget vs. timing vs. competitor, tracked quarterly to refine intake and pricing

Comparison

What this replaces

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

HoneyBook or Dubsado

Great all-in-one for proposals and contracts, but the CRM pipeline is built around their stages, not yours — and there's no AI drafting first responses or flagging leads that have gone cold.

Google Sheets + Gmail labels

Free and familiar, but you're doing all the qualification logic in your head; there's no automated follow-up, no natural-language query, and the sheet drifts the moment you're slammed during event season.

HubSpot free tier

Solid deal pipeline, but the setup assumes a B2B sales team — you'll spend hours reconfiguring fields for event-specific data, and AI drafting is paywalled behind higher tiers.

Airtable CRM template

Flexible schema you can customize, but no email integration that actually reads your threads, no AI-drafted responses, and every automation you want requires you to build it manually.

On Starch RECOMMENDED

One platform — crm, email agent 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 inquiry form is in HoneyBook — can Starch actually pull those leads in automatically?

Yes. If HoneyBook doesn't have a direct API connection available in Starch's integration catalog, Starch automates it through your browser — no API needed. It logs into HoneyBook, reads new inquiry submissions, and creates the corresponding CRM record in Starch. You describe the field mapping once and it runs on a schedule.

Will the Email Agent actually sound like me, or will it send something generic that embarrasses me with a client?

You control the voice. Paste in three to five examples of your real first-response emails when you configure the Email Agent, and it uses those as the tone reference. Every draft goes to you for review before anything sends — nothing goes out automatically unless you explicitly set it to.

I work with a part-time assistant. Can they see the same lead pipeline?

Yes — your Starch workspace is shared. Your assistant can update lead stages, review Email Agent drafts, and pull the same pipeline views. You set what each person can edit.

Does Starch store my clients' contact data securely? I have corporate clients who ask about this.

Starch is not SOC 2 Type II certified yet — that's an honest limit worth knowing. If a corporate client requires SOC 2 compliance from every vendor in your stack, that's a conversation to have upfront. For most independent agencies and small corporate event teams, Starch's data handling is appropriate; it's the same question you'd ask about HubSpot or Dubsado.

What if a lead comes in through Instagram DM instead of email?

Instagram DMs don't have a direct API that Starch reads, but you can automate a browser-based workflow to check your Instagram inbox on a schedule and log new inquiry messages into the CRM. Alternatively, many agencies route Instagram leads through a link-in-bio form that hits Gmail — that path works natively with the Email Agent.

Can I track which leads came from a specific venue's preferred vendor list?

Yes — when you describe your CRM to Starch, include 'source' as a field with the specific values you care about (venue referral, wedding planner referral, website, Instagram, Cvent marketplace, etc.). You can then ask 'what's my close rate from The Foundry's preferred vendor list this year?' and get a direct answer from your own data.

I don't want to rebuild my whole process — can I start with just the email follow-up piece?

Yes. Start with just the Email Agent connected to Gmail. Get the first-response drafting and follow-up reminders working for a week. Once that's running, describe the CRM to Starch and it builds the pipeline around the lead data you've already been collecting. You don't have to set everything up at once.