Ticketing that holds on peak days
Hypothetical. Not a client, not a result.
// The problem
A resort's online ticketing slows to a crawl on powder mornings and holiday weekends, the agency that built it has moved on, and nobody on staff knows how it is hosted.
// What we would build
We take over the ticketing site, fix what breaks under load, move it to cloud hosting that grows on busy mornings and shrinks overnight, and run it for you with monitoring, backups and a plan for the next peak.
// What is in it
- A review of the code and hosting you have today
- Fixes for the parts that fail under load
- Hosting that scales up for peak mornings and down overnight
- Monitoring, alerts and backups you can see
- Load tested before the season opens
// Stack
- Next.js
- PostgreSQL
- AWS
- Terraform
- Grafana
// estimate
- Build
- ≈ US$65,900 to US$101,000, delivered within 17 weeksCAD 93,800 to 143,500
- 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
- 2.9 to 4.9 weeks
- Core features
- 2.4 to 3.9 weeks
- Full build
- 1.4 to 2.4 weeks
- Testing and fixes
- 0.9 to 1.4 weeks
- Launch
- 0.9 to 1.4 weeks
How it is paid
- Deposit 20%
- CAD 18,760 to 28,700
- Discovery 7.7%
- CAD 7,222.60 to 11,049.50
- Design approved 7.7%
- CAD 7,222.60 to 11,049.50
- Core features 23.3%
- CAD 21,855.40 to 33,435.50
- Full build 15.5%
- CAD 14,539.00 to 22,242.50
- Testing and fixes 7.7%
- CAD 7,222.60 to 11,049.50
- Launch 8.1%
- CAD 7,597.80 to 11,623.50
- Holdback, 30 days after launch (10%)
- CAD 9,380 to 14,350