Prepared for Star Alpine · September 2026
Your lodge.
Your next chapter.
A simpler way for members to book. A clearer way for the committee to run the season. Thoughtfully built around one lodge at Mount Buller.
One lodge.
A better season.
01 / The difference it can make
More time enjoying the lodge.
For members
A booking should feel like the start of a holiday.
From checking availability and asking what is left.
To choosing dates, seeing the price and managing a stay on their phone.
For the booking officer
A clearer picture. Fewer loose ends.
From chasing details across messages and spreadsheets.
To one view of rooms, bookings, arrivals and payment status.
For the committee
A system the next committee can inherit.
From knowledge held by a few people.
To agreed rules, useful records and a documented way to run the season.
These are intended improvements, not measured savings. We will validate the fit with the booking officer and members before launch.
02 / Your investment
A clear build price.
A modest annual care plan.
The first release
$8,600+ GST · one-off
Built around your lodge.
Design refinement, the agreed core booking system, setup, testing, a clean data import and committee training.
See exactly what is included ↓From go-live
$620+ GST · per year
Care beyond opening day.
Scheduled maintenance and security reviews, backup checks and a small annual support allowance.
See the care and support details ↓Paid as the work progresses.
Proposed milestones, confirmed in the final scope.
- $3,44040% · scope agreed and project starts
- $3,44040% · agreed core ready for committee testing
- $1,72020% · acceptance and launch handover
All amounts are AUD. Build instalments exclude GST. Annual care is billed in advance from go-live, with renewal confirmed each year. The build price covers the focused scope below, subject to confirming the lodge's rules and inspecting its data before work starts.
What other running costs should the lodge allow for?
Allow an indicative A$80–150 per month, plus applicable tax, for hosting, the database, backups and basic email delivery. This is a planning allowance, not a fixed provider quote. Service accounts are held and paid for by the lodge; actual costs depend on usage, exchange rates and the chosen services.
That makes annual care plus this service allowance approximately A$1,580–2,420 before tax. Payment processing, SMS, domain renewal and any specialist services are additional. The build plus the first year of care and estimated services is approximately A$10,180–11,020 before tax.
We will agree the provider costs before enabling paid services. Current starting plans provide a reference: Vercel Pro and Supabase Pro. The final service selection is part of setup.
03 / Looked after, with clear boundaries
A named person.
A plan for ongoing care.
Sonder Sites remains your point of contact. The annual plan supports a small, stable lodge system, with larger work discussed and approved separately.
Maintain & review
Quarterly scheduled checks of dependencies, security notices and backup status, with routine compatible patches. Allowance: up to two hours of maintenance work per year.
Help when you need it
Up to two additional hours per year for committee questions, minor settings or content changes and troubleshooting. Unused hours do not roll over. Further work is quoted before it starts.
Know what to expect
Email support during Monday–Friday, 9am–5pm Melbourne time, excluding Victorian public holidays. Target initial response: within two business days. Urgent issues are prioritised during these hours.
The A$620 plan includes four hours in total across maintenance and support. Response targets are not resolution guarantees. It does not include 24/7 monitoring or on-call cover, major upgrades, incident recovery, new features or third-party charges. Work beyond the allowance is separately approved; we will advise if a security issue requires additional work.
Security belongs in the build, too.
The first release includes protected member and committee access, role-based permissions, encrypted connections, booking-conflict checks and a tested backup/restore process. These are delivery requirements to verify before real bookings begin. The public demo uses simulated access and data.
04 / A focused first release
The essentials, done properly.
The A$8,600 build adapts the existing prototype into the core system below. The wider demo shows possibilities for later stages as well as the first release.
Member experience
Secure member sign-in, household details, upcoming stays and a nights balance using one agreed entitlement model.
Bookings & beds
Shared room-and-bed availability, temporary holds, confirmation and protection against two people booking the same bed.
Prices & payment
One agreed seasonal member/guest price schedule, one standard hosted payment provider and payment-status tracking. Card fees are separate.
Committee desk
Manage bookings and cancellations, allocate beds manually, view arrivals and occupancy, export core records and record key officer actions.
Lodge essentials
Your supplied logo, verified room inventory and lodge guide, adapted within the existing design. One lodge, one agreed rule set.
A supported start
One clean import pack for members, future bookings and opening balances, one rehearsal, one committee training session and 30 days of fixes for defects in the agreed build.
Explore in the demo · Quote separately to implement
Room to grow, when it is useful.
Booking ballots and automated allocation, advanced credit and levy accounting, season repricing, lock or door-code integrations, customised 3D plans, accounting integrations, marketing campaigns, off-season group payments and custom analytics are later-stage options.
The first release uses officer-managed allocations. If ballots are essential for opening day, we will agree an additional scope before proceeding. Historical data cleanup, manual data entry, extra migration sources and major rule changes are also outside the build price.
Ownership, handover and keeping the scope clear
The lodge owns its data and receives access to its service accounts, exports and project code at final handover. Third-party software and reusable components retain their existing licences. Handover includes operating notes so a future committee or provider can take over.
Before development, we will document one agreed set of membership, pricing, guest and cancellation rules, the import format, acceptance checks and responsibilities. Scope changes are priced and approved before work starts. The final service agreement will confirm these details and the care arrangement.
The lodge supplies accurate content, a clean export in the agreed template, payment-provider access and a nominated decision-maker. The committee signs off imported balances and bookings before cutover.
05 / The summer build window
The path to June 2027.
A focused build with time to test, train and make the switch carefully. Timing depends on agreed scope, access to the current system and prompt committee decisions.
- 01
Sep–Oct 2026
Agree the lodge's rules
Confirm the core member classes, beds, prices, cancellation process and clean export format. Separate essential first-release requirements from optional later features.
Ready when: Signed-off scope, rules and commercial proposal.
- 02
Nov 2026–Feb 2027
Build one lodge properly
Adapt the prototype into the agreed secure member and committee system, shared booking database, nights model and one standard payment integration.
Ready when: Working core journeys with representative test data.
- 03
Mar–Apr 2027
Rehearse a whole season
Trial the agreed import and reconcile opening balances. Test simultaneous bookings, manual bed allocation, payment status, access permissions and recovery with the booking officer.
Ready when: Committee acceptance and a successful migration rehearsal.
- 04
May 2027
Make the switch with support
Train the committee, run a member pilot and schedule the final migration around the lodge's actual booking-round dates.
Ready when: Go/no-go approval, rollback plan and support arrangements.
June 2027 readiness target. Confirm the actual booking-opening date early. If the lodge needs an earlier launch, we will plan around that date before committing to the schedule.
No rush. Take a look around.
Try it. Picture your season.
Then let's have a chat.
Walk through the member and committee experiences, note what feels useful and anything your lodge does differently. When you are ready, reply to Tim and we can talk through the fit, the rules and the next step.
A proposal for discussion, subject to an agreed scope and service agreement. Exploring the demo does not place an order or create a real booking.