How much does an event ticketing app cost?

$2,500 fixed, agreed before work starts, covering design, build, payments, the scanner and 30 days of support. No per-ticket fee to me, ever — that is the entire point of owning it.

How does it compare to Eventbrite or similar?

You keep the fee and you keep the attendee list. Platforms charge per ticket and own the relationship with your audience. At a few hundred tickets a month the build pays for itself quickly; below that, a platform is genuinely the cheaper option and I will say so.

Does the door scanner work without internet?

Yes — valid tickets are cached before the doors open and check-ins sync when signal returns. Venues have bad reception and this is the feature that decides whether the night goes smoothly.

Can I run recurring or multi-day events?

Yes, including series, sessions and multi-day passes. Say what shape your programme is on the call so the model fits from day one.

Can attendees transfer or refund tickets themselves?

Yes, within rules you set — refund windows, transfer permissions, name changes. It removes most of the email traffic organisers spend their week on.

Who owns the code and the attendee data?

You do, both. Source code and design files at handover, and the attendee list in your own database rather than a platform's.

Ship It Live — $1,999 flat

Design + build + deploy · kickoff in 24h · limited slots

Book a 30-min call →

30 days · $2,500 · fixed

Ship It Live · events sprint

Sell tickets and scan them at the door, in 30 days.

Your events, your ticket fees, your attendee list. Scanning at the door included, because that is the bit that goes wrong at 8pm.

Book a 30-min call →

See the 30-day plan

4.93★ / 32 reviews 75+ shipped Kickoff in 24h

Quick answer

An event and ticketing platform can be designed, built and selling tickets in 30 days for a fixed $2,500, covering event listings, ticket types and pricing, checkout, QR tickets, door check-in and an organiser dashboard. It removes the per-ticket commission an external platform charges.

The plan

Day one to day 30, written down.

You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.

Days 1–3

Scope lock

Ticket types, pricing rules, capacity, and exactly how the door works on the night. The door is the part most ticketing builds under-think.

Days 4–12

Design

The buying flow first — it has to work on a phone, from a social link, in seconds — then the scanner and the organiser dashboard.

Days 13–24

Build

Listings, ticket inventory, checkout, QR generation and the scanner. Capacity and double-sell protection get real attention, because overselling is unrecoverable.

Days 25–28

Dry run

A full rehearsal: buy, receive, scan, refund, re-scan the same ticket. Including with bad signal, because venues have bad signal.

Days 29–30

Launch

Payments live, your first event published, and staff walked through the scanner before they need it.

What $2,500 gets you

Everything needed to launch — nothing padding the invoice.

Event listings with dates, venues, images and descriptions

Multiple ticket types, tiers, early-bird pricing and capacity limits

Checkout through Stripe, with discount and promoter codes

QR tickets delivered by email and saved to the phone

A door check-in scanner that works on a phone, offline included

An organiser dashboard: sales, capacity remaining, attendee list

Refunds, transfers and cancellations handled without emailing you

Source code, design files and 30 days of support at handover

Who books this

Built for

Organisers losing 5–10% of every ticket to a platform

Venues and promoters running a recurring programme

Communities and conferences with their own audience already

The honest part

When 30 days is the wrong answer.

A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.

Reserved seating with an interactive seat map for a large venue. Genuinely complex inventory, and worth building properly as its own project.

Secondary resale marketplaces, which bring fraud, identity and regulatory questions with them.

Access control hardware — turnstiles, RFID wristbands, printed-badge kiosks. The software can talk to them; specifying and supplying them is not this sprint.

Questions

Before you book

Yes, for general admission and tiered tickets with QR check-in. What does not fit is reserved seating maps and resale. The month covers everything from listing an event to scanning the last person through the door.

Other sprints

30 days · $2,500

Booking app in 30 days

An appointment and booking app — availability, payments, reminders and a staff calendar — designed, built and live in 30 days for a fixed $2,500.

30 days · $2,500

Marketplace app in 30 days

A two-sided marketplace app — listings, search, booking and payments — designed, built and live in 30 days for a fixed $2,500. Source code yours.

21 days · $1,999

Loyalty app in 21 days

A customer loyalty and rewards app — stamps or points, rewards, referrals and campaigns — designed, built and live in 21 days for a fixed $1,999.

30 days from now, this could be live.

A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.

Book the call

All sprints