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