How to sell tickets for a small event: a practical launch guide

To sell tickets for a small event, you need a clear event page, a price that works for your costs, a tested checkout and a way to reach the people who may come. The ticketing service handles bookings; you still need to bring the audience.

This guide is for an organizer running a small show, talk, workshop or independent conference. It focuses on getting one real event ready, rather than building a large marketing campaign.

Download the free launch checklist

Keep the editable text checklist with your event plan. No email is needed.

1. Make the event details clear

Write the event name, date, start and end time, venue and the reason to attend. Say who it is for. A buyer should be able to tell whether the event fits them before they reach the ticket picker.

Include practical details that change the decision: age restrictions, what is included, what to bring, and how people reach the venue. Do not hide a change of venue or a required item in the confirmation email.

Use one public event URL when you share the event. If details change, update that page so older messages still lead to the current information.

2. Choose a price that works for your event

List your costs before copying another event's ticket price. Include the room, performers or speakers, materials and other costs you expect. Then choose a realistic paid attendance, not just the room's maximum capacity.

Use the ticket price calculator to compare attendance scenarios. The Stripe fee calculator estimates standard processing for the account country and card type you select; its assumptions and exclusions are listed on the page.

Separate buyer-paid fees from organizer costs. If buyers cover a platform's booking fee, removing that fee does not automatically save you the same amount. An annual subscription may be a new organizer cost even when the buyer's total falls.

3. Choose the ticketing workflow you need

For a small event, start with the basics: capacity, ticket types, payment, confirmation, attendee lookup and check-in. Check whether a buyer can book more than one place and whether you can export the records you need.

A marketplace may offer discovery alongside ticketing. A standalone shop is a different choice: it gives you an event link to share with your own list, community and partners. Neither choice removes the need for a plan to reach suitable people.

CrabGate is built for rooms with their own audience, as well as independent conferences and workshops. It costs $99 a year with no CrabGate per-ticket fee; Stripe processing fees still apply. Ticket payments go to the organizer's own Stripe account.

Before choosing, read the product limits and the current pricing page. Features such as reserved seating, memberships or automatic repeating schedules should be checked directly, not assumed from a general ticketing description.

4. Test the buying journey before sharing

Open the event page on a phone. Check the date, ticket options, total shown before payment and confirmation instructions. Look for text that wraps badly or a button that is hard to use.

Use the platform's supported test process. Confirm how it distinguishes test payments from real ones before making a test purchase. On CrabGate, the setup call includes a test order so you can see what buyers receive.

Check one place and a multi-place order. Open the confirmation email, find the event details and make sure a person can present the right ticket at the door. If a friend books for someone else, the payer's name should not leave staff guessing who is attending.

Make sure you can find the order again. Decide who handles a buyer's question and how that person gets the correct booking reference.

5. Share one link with the right audience

Start with people who already know the room, organizer or subject. Explain the event in one short message: what it is, who it is for, when it happens and where to buy a ticket.

Ask relevant partners to share the same event URL. A speaker, workshop tutor or local community may reach suitable people; a large unrelated audience may not. Give each partner accurate details they can use without rewriting the whole page.

Check sales against your realistic attendance plan. If people open the page but do not buy, first check the event offer, price and checkout. Posting more often will not fix unclear details or a broken buying step.

Keep messages useful. Tell people about a genuine deadline, changed detail or practical reason to attend. Do not invent a countdown or claim that tickets are almost gone when they are not.

6. Prepare the door before event day

Decide who checks people in and what they should do when a ticket cannot be found. Share the correct staff access, charge the phone and check the venue connection before arrivals begin. Do not assume a tool works offline unless that behavior is supported and tested.

On CrabGate, the Door Link is the phone check-in entry point. Staff should know when to scan a ticket and how to look up an attendee. Agree who handles a duplicate scan, a changed name or a booking question rather than leaving those decisions to the queue.

Keep a contact route for the person responsible for orders. If you prepare an attendee export as part of your backup plan, protect it and share it only with the people who need it.

Before you announce the event

• The date, location and ticket total are clear.
• The capacity counts places rather than orders.
• The buying journey and confirmation have been checked.
• The event link works from the messages you will share.
• Door staff have the correct access and know the exception process.

For a paid workshop, use the workshop registration template to plan the buyer and attendee details you need.