Skip to content
AtheronLABS

You're visiting from the United States. Prices are shown in US dollars. Not right?

labs@atheron:~/industries/outdoor-recreation$ open --lifts --tee-sheet --rentals

Resort and course apps

Built for the busiest morning of your season.

Your season turns on a handful of busy days, your guests buy tickets, rentals and lessons in three places, and conditions change by the hour. We build the guest apps, booking systems and operations tools that keep a hill, a course or a park running, connected to the ticketing and point of sale you already use.

Start a projectSee the example projects

// what you are up against

The problems we hear most.

01

A season of peak days

A powder morning or a sunny Saturday brings more traffic in an hour than a quiet week, and that is exactly when an old booking site slows down.

02

Three systems for one visit

Tickets, rentals, lessons and food are sold in separate systems, so a guest queues three times and nobody sees the whole visit.

03

Conditions that change hourly

Lift status, trail grooming, course closures and weather change through the day, and guests hear about them late or not at all.

04

Too small for a pass alone

An independent hill or course cannot offer a season pass that competes with the big resort groups on its own.

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

Guest app with passes and conditions

Hypothetical. Not a client, not a result.

// The problem

A ski hill sells tickets, rentals and lessons on separate pages, posts conditions on social media, and guests still queue at the window for everything.

// What we would build

An iOS and Android guest app and a matching website for tickets, passes, rentals and lessons in one basket, with live lift and trail status and alerts, connected to the hill's ticketing and point of sale.

// What is in it

  • Tickets, passes, rentals and lessons in one basket
  • Pass reloads and direct-to-lift where your gates allow
  • Live lift, trail and grooming status from operations
  • Alerts for openings, closures and weather holds
  • Every screen in English and French, and more if you need them
  • Connected to your ticketing and point of sale

// Stack

  • Next.js
  • React Native
  • PostgreSQL
  • Stripe
  • Ticketing and point of sale interfaces
  • AWS

// estimate

Build
≈ US$134,000 to US$205,000, delivered within 30 weeksCAD 191,000 to 292,000
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
Design approved
9.4 to 15.9 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.9 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 38,200 to 58,400
Discovery 9.2%
CAD 17,572 to 26,864
Design approved 9.2%
CAD 17,572 to 26,864
Core features 7.6%
CAD 14,516 to 22,192
Full build 5%
CAD 9,550 to 14,600
First build on devices 20.1%
CAD 38,391 to 58,692
Testing and fixes 2.5%
CAD 4,775 to 7,300
Store submission 6.7%
CAD 12,797 to 19,564
Launch 9.7%
CAD 18,527 to 28,324
Holdback, 30 days after launch (10%)
CAD 19,100 to 29,200
Start from this example
Example projectWeb app

Tee-time and member booking

Hypothetical. Not a client, not a result.

// The problem

A golf club takes tee times by phone and a dated booking page, members complain that public golfers get the best times, and the pro shop rebuilds the sheet every morning.

// What we would build

A tee-time booking site designed around the club: member and public windows, guest passes, group bookings and deposits, and a tee sheet the pro shop runs from one screen.

// What is in it

  • Member and public booking windows you set
  • Guest passes, groups and tournaments with deposits
  • A tee sheet the pro shop runs from one screen
  • Weather holds and reminders sent to players
  • Pages designed in your club's look

// Stack

  • Next.js
  • PostgreSQL
  • Stripe
  • DigitalOcean

// estimate

Build
≈ US$65,000 to US$99,400, delivered within 18 weeksCAD 92,600 to 141,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
4.9 to 7.9 weeks
Core features
1.9 to 3.4 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,520 to 28,320
Discovery 7.7%
CAD 7,130.20 to 10,903.20
Design approved 7.7%
CAD 7,130.20 to 10,903.20
Core features 23.3%
CAD 21,575.80 to 32,992.80
Full build 15.5%
CAD 14,353 to 21,948
Testing and fixes 7.7%
CAD 7,130.20 to 10,903.20
Launch 8.1%
CAD 7,500.60 to 11,469.60
Holdback, 30 days after launch (10%)
CAD 9,260 to 14,160
Start from this example
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
Example projectWeb appBlockchain

Shared pass across independent hills

Hypothetical. Not a client, not a result.

// The problem

Five independent ski hills in a region each sell a pass that few guests buy, and none of them wants a rival to hold the shared pass and its money.

// What we would build

One pass across the member hills, with each visit recorded on a private permissioned ledger every hill runs a node of, so a guest skis at any member hill and each hill is paid its share from the same record. If one association runs the pass and the hills trust it, a database is simpler, and we will build that.

// What is in it

  • One pass and one guest account across every member hill
  • Visits recorded at each hill's gates
  • Revenue shares worked out from the shared record
  • No hill can add or change visits alone
  • Rules for joining and sharing agreed by the members

// Stack

  • Next.js
  • PostgreSQL
  • Hyperledger Besu (private, permissioned)
  • Access gate interfaces
  • DigitalOcean

// estimate

Build
≈ US$121,000 to US$185,000, delivered within 25 weeksCAD 172,300 to 263,400
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
Architecture
0.4 weeks
Design approved
3.9 to 6.9 weeks
Core features
1.4 to 2.4 weeks
Full build
0.9 to 1.9 weeks
Devnet
2.9 to 4.9 weeks
Testing and fixes
0.4 weeks
Testnet
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

Interface access from your access gate vendor
1 to 4 weeks

How it is paid

Deposit 20%
CAD 34,460 to 52,680
Discovery 2.5%
CAD 4,307.50 to 6,585.00
Architecture 6.7%
CAD 11,544.10 to 17,647.80
Design approved 2.5%
CAD 4,307.50 to 6,585.00
Core features 7.5%
CAD 12,922.50 to 19,755.00
Full build 5%
CAD 8,615 to 13,170
Devnet 20.2%
CAD 34,804.60 to 53,206.80
Testing and fixes 2.5%
CAD 4,307.50 to 6,585.00
Testnet 13.4%
CAD 23,088.20 to 35,295.60
Launch 2.5%
CAD 4,307.50 to 6,585.00
Mainnet 7.2%
CAD 12,405.60 to 18,964.80
Holdback, 30 days after launch (10%)
CAD 17,230 to 26,340
Start from this example
Example projectWeb app

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
Start from this example
Example projectWeb appAIFrontier model

Guest and conditions assistant

Hypothetical. Not a client, not a result.

// The problem

A resort's guest services answer the same questions about lifts, parking, rentals and lessons all day by phone and chat, and the answers change as conditions do.

// What we would build

An assistant on the website and app that answers from the resort's own information and today's live conditions, changes rentals and lessons through the resort's systems, and hands to guest services with the conversation attached. It uses a frontier model through its API: resort information is public and guests write in several languages.

// What is in it

  • Answers from your guest guide and today's conditions
  • Rental and lesson changes through your systems
  • Replies in the guest's language
  • Handoff to guest services with the conversation
  • No card details in the conversation

// Stack

  • Frontier model API
  • Next.js
  • PostgreSQL with pgvector
  • Ticketing interface
  • AWS

// estimate

Build
≈ US$87,000 to US$133,000, delivered within 21 weeksCAD 123,900 to 189,400
Hosting
≈ US$558 a monthCAD 795 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.

AI route
Frontier model
Model running cost
≈ US$383 a monthCAD 545 a month

Timeline by milestone

Discovery
2.9 to 3.4 weeks
Specification and evaluation plan
0.4 weeks
Design approved
2.4 to 3.4 weeks
Core features
1.4 to 1.9 weeks
Full build
0.9 to 1.4 weeks
Working pilot
3.9 to 6.4 weeks
Testing and fixes
0.9 to 1.9 weeks
Launch
0.9 to 1.4 weeks
Production
0.9 to 1.4 weeks

How it is paid

Deposit 20%
CAD 24,780 to 37,880
Discovery 2%
CAD 2,478 to 3,788
Specification and evaluation plan 10.2%
CAD 12,637.80 to 19,318.80
Design approved 2%
CAD 2,478 to 3,788
Core features 6.2%
CAD 7,681.80 to 11,742.80
Full build 4.1%
CAD 5,079.90 to 7,765.40
Working pilot 30.7%
CAD 38,037.30 to 58,145.80
Testing and fixes 2%
CAD 2,478 to 3,788
Launch 2%
CAD 2,478 to 3,788
Production 10.8%
CAD 13,381.20 to 20,455.20
Holdback, 30 days after launch (10%)
CAD 12,390 to 18,940
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

Resort booking apps

Guest apps and booking for ski hills, golf courses and outdoor operators: tickets, passes, rentals and lessons in one basket, live conditions, and a tee sheet the pro shop runs from one screen.

Read more

~/ai

Resort guest assistant

A guest assistant on a frontier model that answers from a resort's own information and live conditions, changes rentals and lessons through its systems, and hands to guest services when it should.

Read more

~/chains

Shared season passes

One season pass across independent ski hills or courses, with visits recorded on a private permissioned ledger each member runs a node of, so guests ride anywhere and each member is paid its share.

Read more

~/cloud

Peak-day hosting

Taking over and running ski resort and attraction ticketing: fixes for what fails under load, cloud hosting that scales up for peak mornings and down overnight, monitoring, backups and load tests before the season.

Read more

~/data

Resort ops data

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

Read more

~/automate

Gate and till integrations

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

Read more

// questions

What buyers in this industry ask us.

Do you work with small, independent hills and courses?

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

Can you work with our ticketing or tee sheet vendor?

Yes. We work through their interface and agree the boundary with them early.

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.

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

~/hospitality

Hospitality and travel

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

See the examples

~/equipment-rental

Equipment rental

Counter and yard systems with GPS and barcode tracking, booking portals with deposits for your customers, damage photo models, re-rent records shared between rental companies and off-rent bots, synced with QuickBooks Online.

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 projectBook a call
Software for ski resorts, golf courses and outdoor operators | Atheron Network Labs