labs@atheron:~/industries/outdoor-recreation/data$ query --warehouse --dashboards

Resort ops data

Visits, rentals and revenue through the day.

Staffing a lift line or a rental shop on yesterday's numbers wastes money or guests. A dashboard that reads every system through the day shows where people are, what they are buying and what tomorrow is likely to need.

Start a project See the example projects

// what matters here

What is different in this industry.

Every system in one view

Ticketing, rentals, lessons and food read into one model and compared on the same terms.

Through the day, not after it

Figures refresh during the day, so a manager can move staff while it still helps.

This season against last

Today compared with the same day last season, adjusted for the calendar.

Yours to keep

The data sits in a database you own, so you can take it anywhere.

// example projects

Priced examples for this service.

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 app

Operations dashboard

Hypothetical. Not a client, not a result.

// The problem

A resort's managers see ticket sales, rentals, lessons and food in four reports at the end of the day, so staffing and lift decisions are made on yesterday's numbers.

// What we would build

A live operations dashboard that reads ticketing, rentals, lessons and food into one model, so managers see visits, queues and revenue through the day and plan staff for tomorrow.

// What is in it

Visits, sales and revenue by hour, across every system
Rentals and lessons against what is booked
Today against the same day last season
Staffing plans from expected visits
Exports for finance and the board

// Stack

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

// estimate

Build: ≈ US$34,000 to US$52,000, delivered within 13 weeksCAD 48,400 to 74,000
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 14,520 to 22,200
Discovery 6.6%: CAD 3,194.40 to 4,884.00
Design approved 6.6%: CAD 3,194.40 to 4,884.00
Core features 20%: CAD 9,680 to 14,800
Full build 13.3%: CAD 6,437.20 to 9,842.00
Testing and fixes 6.6%: CAD 3,194.40 to 4,884.00
Launch 6.9%: CAD 3,339.60 to 5,106.00
Holdback, 30 days after launch (10%): CAD 4,840 to 7,400

Start from this example

Example projectAPI

Gates, tills and booking hub

Hypothetical. Not a client, not a result.

// The problem

A mountain park sells online, at the window and in the rental shop, and its access gates, tills and booking system each keep their own list of who has paid for what.

// What we would build

An integration hub between the booking system, the access gates, the tills and the accounting system, so a ticket bought anywhere opens the gate, appears in the rental shop and reaches the books once.

// What is in it

A purchase anywhere recognised at every gate and till
Rentals and lessons tied to the guest's ticket
Sales posted to your accounting system
A log of every message, with alerts when one fails
Built for the load of your busiest hour

// Stack

Node.js
PostgreSQL
OpenAPI
Access gate and point of sale interfaces
DigitalOcean

// estimate

Build: ≈ US$58,400 to US$89,300, delivered within 14 weeksCAD 83,100 to 127,100
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

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

Outside our hands, and added to the calendar

Interface access from your access gate vendor: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 16,620 to 25,420
API contract agreed 8.7%: CAD 7,229.70 to 11,057.70
Core resources built 26.2%: CAD 21,772.20 to 33,300.20
Security, gateway and connections 17.5%: CAD 14,542.50 to 22,242.50
Docs, SDKs and load tests 8.7%: CAD 7,229.70 to 11,057.70
Launch and first callers 8.9%: CAD 7,395.90 to 11,311.90
Holdback, 30 days after launch (10%): CAD 8,310 to 12,710

Start from this example

// questions

Questions we get about this.

Can the resort dashboard read our ticketing and rental systems?

Yes, through their interfaces or exports. We check each system before we quote.

Can a golf course use the operations dashboard too?

Yes. Rounds, carts, pro shop and food are read the same way as lifts and rentals.

Does the operations dashboard forecast visits?

It shows expected visits from bookings and past seasons. It is a planning aid, not a promise.

Back to the industry: Ski resorts, golf and outdoor recreation About the service: Data and analytics

// 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