How to Plan and Manage Business Events Without a Planner

Three weeks before the event, the owner of a 14-person agency we worked with realized her registration spreadsheet did not match her ticketing platform's export. Forty-six tickets sold. Fifty-one rows in the spreadsheet. Five names she did not recognize. Two of them turned out to be staff who registered themselves and forgot. The other three were people who paid via a Venmo screenshot her assistant accepted in March.

This is what running a business event without a dedicated planner actually looks like. It is not glamorous, it is not catastrophic, and it does not require a $50,000 agency to fix. What it requires is treating an event the way you would treat any operational project: a clear scope, a budget, a stack that does not lose data, and a 90-day runway that turns chaos into a checklist.

This post is for the SMB owner, nonprofit director, or small-team operator running a workshop for 20 customers, a conference for 300, a fundraiser for 150, or a holiday party for the whole team. Budgets between $5,000 and $100,000. No professional planner, no events team, no inherited playbook. The goal: run the event, capture the data, follow up, and tie it back to revenue.

There is a moment in every first-time event-runner's journey where they open a tab, type "event registration software," and breathe out. Eventbrite. Done. It sells tickets. It emails confirmations. It scans QR codes at the door. What more does an event need?

Quite a bit, actually. Ticket sales is one piece of a 12-piece puzzle, and the other 11 pieces are where most first-time events lose money, attendees, and the chance to convert the people who showed up into repeat customers.

A dedicated ticketing tool handles the transaction. It does not handle the CRM record, the sponsor invoice, the day-of badge print, the post-event survey, or the email sequence that turns a $50 ticket buyer into a $5,000 customer six months later. When those live in seven different tools, your registration data ends up trapped in one of them, and the operational work of pulling it together for follow-up becomes the reason follow-up never happens.

Before we get to budget percentages and software stacks, here is the actual scope of work for any event in the 20-500 attendee range. Skip any of these and you create a gap that either an attendee or an accountant will find.

If you are running your first event, the question is not whether you can afford it. The question is what your dollar should be doing. The percentages below come from operator interviews and industry surveys across 2024-2025; they hold reasonably well for events between $5,000 and $100,000 in total spend.

Two notes on the table above. First, the F&B service charge is the single most common underestimate we see — a $50/person catering quote becomes $61/person after a 22% service charge, before tax. Build the gross-up into the line item from day one. Second, contingency is not a luxury. Skipping it is how a $40,000 event ends up costing $44,000 and the founder is calling it a loss when it was actually a planning gap.

Pricing strategy at small-event scale follows a fairly predictable pattern: tier the price, anchor early, leave room for late buyers, and manage the waitlist as carefully as the seat chart.

The cleanest tier structure for an SMB event is three tiers spread roughly 25-40% apart, with explicit deadlines that the registration page enforces automatically.

A common mistake is leaving early bird open until the day before the event. The point of the tier is to generate a forcing function, not to offer a discount in perpetuity. Set the deadline, let it expire, and resist the urge to extend it even when conversions slow. Extending kills the urgency for the next event.

Group rates work because a single buyer making a 5-seat decision is much higher-value than five individual buyers making separate decisions. A typical structure: 10-15% off for groups of 3-5, 20-25% off for groups of 6-10, custom pricing above that. Build the group discount as an automatic code applied at the cart, not a manual back-and-forth.

For B2B tickets where a company is paying via PO or wire instead of credit card, you need an invoicing flow. Most small events lose 10-20% of potential B2B revenue because the registration page only accepts credit cards and the buyer's procurement process does not. A short "request an invoice" path that generates a real invoice (net 30, with payment terms and a PO number field) is one of the highest-leverage additions to the registration flow.

Set a refund window — typically full refund up to 30 days out, 50% refund up to 14 days out, no refund inside 14 days but free transfer to another attendee. Publish it on the registration page. Stick to it. The transfer option matters because it lets a buyer who can no longer attend solve their own problem without going through your inbox.

Waitlist management is its own discipline. When the event hits capacity, the waitlist should auto-open and capture the same data as the registration form. Then when refunds open seats back up, the waitlist gets a notification with a short window to convert (24-48 hours), after which the seat releases back to the next person. Manual waitlist juggling becomes the bottleneck of the event by day-of if you skip the automation.

This is the part that separates an event that pays for itself once from an event that pays for itself for two years.

Every person who registers — whether they show up or not — becomes a CRM contact. Tag them with the event, the ticket tier, their company, their role, and any dietary or accessibility data you captured. Then, after the event, layer on behavior signals: did they check in (showed up), did they engage (attended a specific session, visited a sponsor booth, scanned at a partner table), did they buy (took the post-event offer, booked a follow-up call).

The segments those signals produce are gold. "Customers who attended and went to the product session" is a different audience than "customers who registered but no-showed." The first gets a thank-you plus an upgrade offer. The second gets a recording link with a "sorry we missed you" frame. Both are higher-converting than the generic blast.

The trap is letting the registration data sit inside the ticketing platform and never flow into your CRM. If your follow-up requires exporting a CSV from Eventbrite and importing it into HubSpot the day after the event, the follow-up will not happen. The data flow has to be automatic.

Most first-time event-runners overspend on marketing and underspend on day-of ops. The result is a great-looking event that has a 25-minute check-in line, runs over by 45 minutes because nobody is calling time, and ends without anyone collecting sponsor lead data. The fix is not more staff — it is a few specific systems that small events consistently underbuild.

When you map the 12 pieces of an event to actual software, you do not need 12 tools. Most of the work consolidates into about seven jobs, and several of those jobs share the same underlying data (the attendee record, the financial record, the email engagement). The trap is treating each job as an isolated tool purchase. The trap is also what creates the data-trapped-in-Eventbrite problem.

The reason this matters is not the consolidated subscription. It is the data flow. A registration in Bookings creates a CRM record. The Marketing app reads that CRM record to send the right email at the right time. The check-in app reads the same CRM record on day-of. The post-event survey, sent by Forms, writes back to the same CRM record. The Invoicing app reconciles the financials against the same registrations. The Customer Portal serves the attendee resources to the same authenticated user.

When those connections are automatic, the operational work of running an event collapses to about 15-20% of what it is when each tool is a separate vendor. Compare that to the alternative: Eventbrite for tickets, HubSpot for CRM, Mailchimp for email, QuickBooks for invoicing, Typeform for surveys, Square for walk-up, Notion for the attendee resource page, and a CSV-export-and-merge workflow holding it all together. Every export is a place where a contact gets dropped or a tag gets lost.

Here is the template that works for the 20-500 attendee, $5k-100k budget range. It is opinionated — there are events that work on a 6-month runway and there are events that come together in 4 weeks of nights and weekends. But 90 days is the right default for a first-time or first-few-times event-runner with a day job.

Lock the venue, the date, the headline (one sentence describing what the event is and who it is for), and the rough budget. Open a save-the-date list — not full registration, just an email capture page with the date, location, and a short pitch. The save-the-date list does two things: it pressure-tests demand before you commit to harder spend, and it gives you a warm audience the day registration opens.

At this point your event has a landing page (even a Notion page is fine), a date, a venue contract, and a goal. No tickets are on sale yet.

Early-bird tickets go live. The save-the-date list gets an email first, ahead of any public announcement, with the early-bird link and a 48-hour exclusivity window. Then the public announcement goes out.

The registration page is now live, the ticket tiers are configured with their deadlines, the refund and transfer policy is published, and the first 2-3 emails in the sequence (welcome, what to expect, save the date for sessions) are scheduled. Sponsors get pitched in parallel — sponsor commitments need to land before day 30 to have time for logo collection and booth coordination.

Standard ticket pricing is live. Sponsor commitments are closing. Speakers are confirmed. The agenda is a real document with timestamps. The run-of-show draft is shared with the venue, the A/V vendor, and the catering lead.

This is also the deadline for any vendor decisions that have lead time: A/V quotes are signed, catering headcount is locked (or a final-count date is on the calendar), photographer is booked, security and insurance are confirmed if needed.

Attendees get the detailed prep email. Address, parking instructions, transit options, hotel block reminders if you arranged one, agenda link, what to bring, what is provided, dietary confirmations, accessibility info, dress code if relevant.

Late tier pricing kicks in. The waitlist starts converting. A second email goes out to non-registered prospects with a "last call" frame. Internally, the run-of-show is final and the day-of staff have their assignments.

The day before the event is a rehearsal, not a build-day. Build-day was day 2. Day 1 is walking the venue with the A/V vendor, testing the check-in flow with three test registrations, confirming the sponsor lead-capture process with each sponsor lead, doing a sound check, and confirming all timing with the MC and speakers.

The day-of email goes out the morning of the event: directions, arrival window, and one specific 'do this when you arrive' instruction (find the check-in table, grab a badge, head to the lobby).

Within 24 hours: thank-you email to all attendees with a survey link, photos if you have them, and the link to the recording or session resources if applicable. Sponsor lead lists go out within 48 hours.

Within 7 days: financial reconciliation. Revenue minus all invoiced expenses. The number you compare against the event goal. The number that tells you whether to run it again next year.

Within 14-30 days: the follow-up offer or nurture sequence. Customers who attended and engaged with the product session get a sales touch. General attendees get added to a nurture audience. No-shows get the recording with a softer follow-up frame.

Concretely, here is how a Deelo-based event setup looks on day 60 through day 14. A buyer hits the registration page, picks a ticket tier in Bookings, pays through Stripe, and lands in the CRM as a contact tagged with the event, the tier, and the timestamp. Marketing reads that tag and starts the registered-attendees email sequence automatically — confirmation, week-out reminder, day-of logistics, post-event thank-you.

If the buyer is registering a group of five, Invoicing generates a single invoice with the company on it, marks the seats as group-purchased, and creates five contact records linked to the same parent company in CRM. If a sponsor signs up, Invoicing generates a net-30 invoice and the sponsor's commitments live as a checklist on the CRM record.

Forms hosts the pre-event intake (dietary, accessibility, t-shirt size, optional session preference). On the day of the event, the check-in app reads the same CRM, prints badges via the connected printer, and accepts walk-up payments through the POS app. The day-after survey goes out through Marketing, tagged responses write back to the contact record, and the financial reconciliation reads the same payments ledger that processed every ticket.

No CSV exports. No "which tool was that contact in." No manual merge between the ticketing data and the CRM. The follow-up that turns event attendees into customers actually happens, because the data has been ready for it since registration.

Running a business event without a planner is not about being a hero or saving money. It is about treating the event as a project with the same operational discipline you would apply to a product launch or a quarterly campaign. A 90-day runway, a budget that names every category, a stack that does not lose data between tools, and a follow-up plan that starts the day after the event. Do those four things and the event pays for itself in attendee data and pipeline long after the venue invoice has been paid.