labs@atheron:~/industries/events-venues$ onsale --seats --scan --resale-cap

Event and venue apps

Your tickets, your buyers, your doors.

Your on-sale brings a month of traffic in ten minutes, your ticketing platform keeps the buyer's details, and your tickets resell at prices nobody agreed to. We build the ticketing, event apps and venue tools that keep the audience yours, from the first click to the scan at the door.

Start a project See the example projects

// what you are up against

The problems we hear most.

Ten minutes of on-sale

A popular on-sale brings more traffic in ten minutes than a quiet month, and that is exactly when a ticketing page gives way.

The buyer belongs to the platform

Third-party ticketing keeps the buyer's details and adds its own fees, so the venue knows little about who came.

Resale nobody agreed to

Tickets resell at many times face value on sites the promoter does not control, and genuine fans pay the difference.

Venue quotes by email

Private event enquiries are quoted by email over days, with dates held in a spreadsheet and deposits chased by phone.

// example projects

Systems we could build for you.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

Own ticketing with door scanning

Hypothetical. Not a client, not a result.

// The problem

A mid-sized concert hall sells through a third-party platform that keeps the buyers' details and adds fees, and its own site cannot hold an on-sale for a popular show.

// What we would build

The venue's own ticketing on its website and an iOS and Android app: seat maps, holds and presales, a queue that keeps an on-sale fair under load, and a scanning app for the doors that works when the network does not.

// What is in it

Seat maps, general admission, holds and presales
A fair queue for busy on-sales
Tickets in the app and in phone wallets
A door scanning app that keeps working offline
Your buyers' details in your own database
Hosting that scales for on-sales and shrinks after

// Stack

Next.js
React Native
PostgreSQL
Redis
Stripe
AWS

// estimate

Build: ≈ US$148,000 to US$226,000, delivered within 32 weeksCAD 210,800 to 322,400
Hosting: ≈ US$1,360 a monthCAD 1,940 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 9.4 to 16.4 weeks
Core features: 1.9 to 3.4 weeks
Full build: 1.4 to 1.9 weeks
First build on devices: 3.9 to 6.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week

How it is paid

Deposit 20%: CAD 42,160 to 64,480
Discovery 9.2%: CAD 19,393.60 to 29,660.80
Design approved 9.2%: CAD 19,393.60 to 29,660.80
Core features 7.6%: CAD 16,020.80 to 24,502.40
Full build 5%: CAD 10,540 to 16,120
First build on devices 20.1%: CAD 42,370.80 to 64,802.40
Testing and fixes 2.5%: CAD 5,270 to 8,060
Store submission 6.7%: CAD 14,123.60 to 21,600.80
Launch 9.7%: CAD 20,447.60 to 31,272.80
Holdback, 30 days after launch (10%): CAD 21,080 to 32,240

Start from this example

Example projectWeb appMobile app

Conference app with agenda and leads

Hypothetical. Not a client, not a result.

// The problem

A trade conference prints its agenda, exhibitors collect leads on paper, and attendees miss sessions because room changes are announced only at the door.

// What we would build

A conference web and mobile app designed for a busy hall: registration and badges, a personal agenda with room changes pushed live, exhibitor lead capture by badge scan, and sessions in the languages the audience speaks.

// What is in it

Registration, ticket types and badges with codes
A personal agenda with live room and time changes
Exhibitor lead capture by scanning badges
Speaker profiles and session feedback
Every screen in English and French, or more

// Stack

Next.js
React Native
PostgreSQL
Stripe
DigitalOcean

// estimate

Build: ≈ US$117,000 to US$179,000, delivered within 26 weeksCAD 166,200 to 254,200
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 5.9 to 10.4 weeks
Core features: 1.9 to 2.9 weeks
Full build: 0.9 to 1.9 weeks
First build on devices: 3.4 to 5.4 weeks
Testing and fixes: 0.4 to 0.9 weeks
Store submission: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week

How it is paid

Deposit 20%: CAD 33,240 to 50,840
Discovery 9.2%: CAD 15,290.40 to 23,386.40
Design approved 9.2%: CAD 15,290.40 to 23,386.40
Core features 7.6%: CAD 12,631.20 to 19,319.20
Full build 5%: CAD 8,310 to 12,710
First build on devices 20.1%: CAD 33,406.20 to 51,094.20
Testing and fixes 2.5%: CAD 4,155 to 6,355
Store submission 6.7%: CAD 11,135.40 to 17,031.40
Launch 9.7%: CAD 16,121.40 to 24,657.40
Holdback, 30 days after launch (10%): CAD 16,620 to 25,420

Start from this example

Example projectWeb app

Venue booking and quote portal

Hypothetical. Not a client, not a result.

// The problem

An event venue answers wedding and corporate enquiries by email, holds dates in a spreadsheet, and takes a week to send each quote.

// What we would build

A booking portal on the venue's site where planners check dates, build a quote from rooms, menus and extras, pay a deposit and sign, with a calendar and pipeline for the venue's team.

// What is in it

Live date availability for each room
Quotes built from rooms, menus and extras
Deposits and payment schedules online
Contracts and floor plans shared in the portal
A calendar and pipeline for your events team

// Stack

Next.js
PostgreSQL
Stripe
DigitalOcean

// estimate

Build: ≈ US$61,200 to US$93,500, delivered within 17 weeksCAD 87,100 to 133,200
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 4.9 to 7.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 1.4 to 1.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 20%: CAD 17,420 to 26,640
Discovery 7.7%: CAD 6,706.70 to 10,256.40
Design approved 7.7%: CAD 6,706.70 to 10,256.40
Core features 23.3%: CAD 20,294.30 to 31,035.60
Full build 15.5%: CAD 13,500.50 to 20,646.00
Testing and fixes 7.7%: CAD 6,706.70 to 10,256.40
Launch 8.1%: CAD 7,055.10 to 10,789.20
Holdback, 30 days after launch (10%): CAD 8,710 to 13,320

Start from this example

Example projectWeb appWeb3

Tickets with fair resale

Hypothetical. Not a client, not a result.

// The problem

A festival's tickets resell at many times face value on sites it does not control, and fans who buy there are sometimes turned away with copied tickets.

// What we would build

Tickets issued as tokens on a public chain, with resale only through the festival's own marketplace at a price cap the festival sets, and the scan at the gate checking the current holder. Fans pay by card and never need a wallet unless they want one. If you only need a resale cap, a database-backed marketplace does that more simply, and we will say so.

// What is in it

Tickets issued with a resale price cap you set
Resale only through your own marketplace
The gate scan checks the current holder
Card payments, with a wallet optional
Contracts audited before launch

// Stack

Next.js
Solidity
Base
Stripe
AWS

// estimate

Build: ≈ US$104,000 to US$159,000, delivered within 25 weeksCAD 148,100 to 226,500
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Specification: 0.4 weeks
Design approved: 3.9 to 6.9 weeks
Core features: 1.9 to 2.9 weeks
Full build: 0.9 to 1.9 weeks
Contracts and tests: 2.4 to 3.9 weeks
Testing and fixes: 0.4 weeks
Testnet deployment: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

An outside audit of the contracts, if you want one: 2 to 4 weeks

How it is paid

Deposit 20%: CAD 29,620 to 45,300
Discovery 3.5%: CAD 5,183.50 to 7,927.50
Specification 6.3%: CAD 9,330.30 to 14,269.50
Design approved 3.5%: CAD 5,183.50 to 7,927.50
Core features 10.5%: CAD 15,550.50 to 23,782.50
Full build 7%: CAD 10,367 to 15,855
Contracts and tests 19.1%: CAD 28,287.10 to 43,261.50
Testing and fixes 3.5%: CAD 5,183.50 to 7,927.50
Testnet deployment 6.3%: CAD 9,330.30 to 14,269.50
Launch 3.5%: CAD 5,183.50 to 7,927.50
Mainnet 6.8%: CAD 10,070.80 to 15,402.00
Holdback, 30 days after launch (10%): CAD 14,810 to 22,650

Start from this example

Example projectWeb app

Audience and sales dashboard

Hypothetical. Not a client, not a result.

// The problem

A promoter sees ticket sales in one system, bar sales in another and email results in a third, and plans next season's shows on instinct.

// What we would build

A dashboard that reads ticketing, the bar and the email platform into one model, so the promoter sees sales pace by show, who comes back, what they spend and which campaigns sell tickets.

// What is in it

Sales pace by show against past shows
Returning buyers and what they come to
Bar and merchandise spend per head
Campaign results against tickets sold
Exports for artists' teams and finance

// Stack

Next.js
PostgreSQL
dbt
Ticketing and point of sale interfaces
DigitalOcean

// estimate

Build: ≈ US$30,600 to US$46,800, delivered within 13 weeksCAD 43,600 to 66,600
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.4 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 13,080 to 19,980
Discovery 6.6%: CAD 2,877.60 to 4,395.60
Design approved 6.6%: CAD 2,877.60 to 4,395.60
Core features 20%: CAD 8,720 to 13,320
Full build 13.3%: CAD 5,798.80 to 8,857.80
Testing and fixes 6.6%: CAD 2,877.60 to 4,395.60
Launch 6.9%: CAD 3,008.40 to 4,595.40
Holdback, 30 days after launch (10%): CAD 4,360 to 6,660

Start from this example

Example projectAPI

Event systems hub

Hypothetical. Not a client, not a result.

// The problem

A conference organiser copies registrations from the ticketing system into the CRM, the email platform, the badge printer and the accounting system, by hand, before every event.

// What we would build

An integration hub between ticketing, the CRM, the email platform and accounting, so a registration is entered once and reaches each system with the right fields, and a failure is flagged at once.

// What is in it

Registrations sent to your CRM and email platform
Badge data ready for printing
Sales and refunds posted to accounting
A log of every message, with alerts
Documented, so a new event tool is easy to add

// Stack

Node.js
PostgreSQL
OpenAPI
CRM and email interfaces
DigitalOcean

// estimate

Build: ≈ US$43,300 to US$66,200, delivered within 13 weeksCAD 61,600 to 94,200
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

API contract agreed: 2.9 to 3.9 weeks
Core resources built: 2.4 to 3.4 weeks
Security, gateway and connections: 1.4 to 2.4 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Launch and first callers: 0.9 to 1.4 weeks

How it is paid

Deposit 30%: CAD 18,480 to 28,260
API contract agreed 7.5%: CAD 4,620 to 7,065
Core resources built 22.5%: CAD 13,860 to 21,195
Security, gateway and connections 15%: CAD 9,240 to 14,130
Docs, SDKs and load tests 7.5%: CAD 4,620 to 7,065
Launch and first callers 7.5%: CAD 4,620 to 7,065
Holdback, 30 days after launch (10%): CAD 6,160 to 9,420

Start from this example

// by service

Go deeper on one kind of work.

Pages for the services we have the most to say about in this industry.

~/apps

Ticketing and event apps

Ticketing with seat maps and door scanning, conference apps with live agendas and lead capture, and venue booking portals with quotes and deposits, built for venues, promoters and organisers.

~/web3

Capped resale

Event tickets issued as tokens with a resale price cap, resold only through the organiser's own marketplace, with the gate scan checking the current holder and card payments for fans without a wallet.

~/cloud

On-sale hosting

Hosting and running event ticketing for busy on-sales: a fair queue, hosting that scales for the on-sale and shrinks after, load tests against your biggest show, and monitoring you can see.

~/data

Audience dashboards

A dashboard for promoters and venues that reads ticketing, bar and email results into one model, showing sales pace by show, returning buyers, spend per head and which campaigns sell tickets.

~/automate

Event system integrations

An integration hub for conference organisers and venues that joins ticketing, the CRM, the email platform and accounting, so each registration is entered once and reaches every system correctly.

// questions

What buyers in this industry ask us.

Do you work with small venues and single events?

Yes. A venue booking portal or a dashboard suits a single venue, and the estimator shows the range for your scope.

Can you work alongside our current ticketing platform?

Yes. Many projects start by connecting to it, and moving to your own ticketing can come later or never.

How do payments work?

A deposit to start, then payments at agreed milestones, with 10% held until 30 days after launch. The deposit is a smaller share on larger projects.

Who owns the code?

You do, once the work is paid for.

// other industries

Nearby industries.

~/media

Media and entertainment

Subscriber apps, assistants that search your archive, rights and royalty ledgers, and community bots for Discord and Telegram.

See the examples

~/hospitality

Hospitality and travel

Direct booking engines and guest apps, guest messaging agents, housekeeping apps and shared loyalty for independent hotels.

See the examples

~/sports-fitness

Sports and fitness

Member apps for gyms and studios, movement analysis models, fan bots for Discord and Telegram, and season tickets with fair resale.

See the examples

All industries

// where we work

Find your market.

We work from Kelowna with clients across Canada, the United States and further afield. Each market page covers working hours, hosting, the privacy law that applies, and prices in your currency.

Every market

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call