FINNS Member+ · Discovery
Welcome to the discovery hub for FINNS Member+ — the participation partnership between FINNS and SOTA. The world's best beach club, every day of the year: turning 1.5 million great days into guests who never stop paying attention. This page gets both teams aligned on who your members are, the journey they take, the systems we connect to and the scope we build — before a single screen is designed. We've done our homework on FINNSPass, Insider One, your live CDP rollout and the Member+ proposal, so most of it arrives pre-filled — your job is mostly to correct us, then hit Acknowledge at the bottom of each section.
How to use this page
Who should be involved at FINNS
You know your business better than anyone. Ideal contributors:
- Project sponsor / director — owns the outcome
- Marketing & membership lead — owns the member experience
- Operations / venue GM — owns the floor reality
- IT & systems lead — owns POS, bookings, data
- Finance / legal — owns prizes, permits, payments
- A front-line team member — the person who'll use it daily
The SOTA core team
The same team from the proposal — and the same people who'll be in the workshop room:
- Tom — Managing Director
- Drew — Head of Partnerships
- Cuan — Chief Product Officer
- Kain — Software Engineering Director
- Ethan — Senior DevOps Engineer
Engineering by the Q1 Group — 14+ years of mission-critical systems, 35+ government & enterprise clients, 100% in-house senior engineers, security independently validated by Deloitte + KPMG.
The process from here
We follow a four-phase flow — discovery first, then creative (all visual elements designed), then technical (brought to life), then review and testing.
Company & contacts
The basics of the FINNS organisation and the people involved in this project. We've pre-filled what's public — please correct and complete.
The organisation
Key people Pre-filled from your CDP project teamEmails needed
Drafted from your CDP project org chart — correct roles, add emails, and add anyone we've missed.
Product vision
One page that everyone — FINNS leadership, floor staff, and the SOTA build team — can agree on. We've drafted each block from what we know so far; edit freely. This board gets locked in at Workshop 1.
Positioning & pitch
Two quick exercises borrowed from product strategy. They feel simple — that's the point. If the sentence reads true to you, we've understood the project.
The elevator pitch SOTA draft — edit each blank
The classic template: For [target customers] who are dissatisfied with [the current alternative], our product is a [category] that provides [key capability]. Unlike [the alternative], our product [what it does].
The news release — dated launch day (optional, but powerful)
Imagine the platform just launched and it worked. What's the headline? Working backwards from the announcement is the fastest way to surface what success actually looks like.
The real people
Three groups will live in this platform daily. For each, we capture who they are and — crucially — the implications: what the product must therefore be. We've drafted these; sharpen them with what only you know.
Member journey
Six stages, from a guest hearing about FINNS to bringing their friends back. We've pre-filled the today column from your four journey maps (booker, walk-in, walk-in-then-bed, operational PoV) and drafted the with SOTA column on top — correct either freely.
Your world today
Before proposing anything, here's the FINNS digital ecosystem as we've mapped it from your project documentation. If this picture is right, you never have to explain your stack to us in a meeting. If it's wrong anywhere, fix it in the box at the bottom.
The map
Compiled from your CMO 1st Milestone Reporting (CDP, Middleware, LiteCard) and CDP Implementation & Use Cases (FINNSPass, Pain Points, Native App) documents, May 2026.
What else we've taken on board
- Pass mechanics — timed daily offers by pass type & gender, unlocked 5pm/9pm (fired 4:55/8:45); walk-ins must redeem offer 1 to activate the rest; CLAIMED state on the pass
- Your four journey maps — booker, walk-in, walk-in-then-bed, and the operational point of view (we've pre-filled the Member Journey tab from them)
- Pain points, all three layers — legacy on-prem sync, wallet push limits, identifying walk-ins vs bookers in venue, redemption abuse, points-vs-offers undecided
- The rollout is done — we treat the CDP, middleware, LiteCard and floating app as live and in production; Member+ designs on top of them as they run today
- The native app debate — advantages vs challenges both documented; no decision forced
- The targets — spend per head and long-term loyalty value
Correct the record Needs FINNS input
Where SOTA fits
SOTA doesn't replace anything on the previous tab. FINNSPass stays your identity and wallet rail, Insider One stays your CDP and the source of truth. SOTA plugs in as the participation layer — the layer nobody else in your stack owns — powering FINNS Member+. Phase one runs on membership: join, draws, presales and billing through SOTA. The phase-two options then wire participation into spend itself — entries and points earned automatically from purchases.
Phase one — membership in motion Pre-selected
Live fast, touching nothing on the venue floor: join, bill, draw, delight.
Phase two — wired into spend Phase two — tick to enable
The upgrade: entries and points earned automatically from purchases — no new staff steps, riding the streams you already run.
The revenue engine: full price, more entries Phase two — tick to enable
SOTA is a revenue engine, not a marketing toy. Phase one's dashboard pings with joins, draw entries and QR claims. With the phase-two purchase stream on, these two mechanics switch on too:
Entry boosts instead of discounts
A daybed that rarely sells on a Tuesday between 2–3pm doesn't need a discount — it needs a reason. Sell it at full price with 5× entries into the live trade promotion for that window. Price integrity stays intact (no training guests to wait for markdowns at the World's Best Beach Club), slow inventory moves, and the promotion does the persuading. Time-boxed boosts launch from the dashboard in minutes — happy-hour mechanics without ever touching the price.
A dashboard that pings
With the spend stream on, every qualifying purchase pings the dashboard in real time — entries earned, on what, against which promotion. Your team watches uptake live during a boost window; guests feel the counter move on their phone; and the same event stream can ping the floor team's Google Chat when a boost opens or a big multiplier lands — exactly the alert pattern your ops team already uses.
The promotion dashboard
The screen your team opens every morning:
- Active promotions & trade promotions — status, dates, prize pool
- Live entry numbers — total, today, by segment (pass type, walk-in vs booker, nationality)
- Conversion — entries per 100 guests, incremental spend per promotion
- Compliance view — entry logs and draw audit trail, export-ready for permits
- Screenshot-ready summaries — made for milestone reporting
What SOTA does not change
- FINNSPass — same QR, same wallet pass, unchanged for free-tier guests; Member+ sits alongside it as the paid upgrade, always a few taps away
- Insider One — remains the CDP; SOTA consumes its events and audiences, and can feed entry data back as segments
- The middleware program — we ride the stream, we don't touch OPERA or Simphony
- Your live rollout — CDP, middleware, LiteCard and the floating app are in production; SOTA connects to them exactly as they run today
- The native app debate — guest views are mobile web + wallet; a native app remains a later option, not a prerequisite
Your steer Needs FINNS input
Member+ build scope
The proposal on the table is FINNS Member+: the free FINNS Pass for everyone, a paid Member+ tier on top, and the participation engine underneath. We've split it deliberately: a lean phase-one core that delivers the essence fast, and phase-two options that add richer integrations when you want them. Untick, tick, tell us what's missing — this becomes the integration map and the sequenced rollout plan our scoping workshop signs off.
What's in the first delivery?
Phase one is pre-selected — it's the essence of Member+ and it ships regardless. Phase two is one flick away: use this switch, or simply tick any phase-two option below, and the whole page lights up to show where it lands. Flip back to phase one and the phase-two selections clear again.
Phase one — the essence of Member+ In scope
The lean core that delivers the proposal: a paid membership worth having, draws worth watching, and billing through SOTA. Everything here ships first.
Phase one — core integrations Pre-selected
Analytically minimal: three integrations make Member+ run. Nothing on the venue floor is touched.
Phase two — select what you want Phase two — flip the switch or tick to include
Available just by selecting it — flip the switch above or tick any option and the rest of the page shows where it lands. Each adds real integration scope, which is exactly why it isn't forced into phase one.
Delivery, governance & operations
Shape the scope Needs FINNS input
Programs & mechanics
SOTA's engines, and where each one sits for FINNS. Tick what interests you and set a rough priority — this is exactly the "phase one to wishlist" conversation, started early so Workshop 2 can focus on sequencing rather than definitions.
Campaign-based promotions with live entry counts and auditable draws. At launch, entries come from membership and staff-scanned QR claims; the phase-two spend stream upgrades them to entries-per-purchase, time-boxed entry boosts on slow inventory, and retail trade promos with brand partners.
Always-on — qualifying purchases can win on the spot. Your digital-scratch-card concept, productised: one-time or daily-timed, abuse-safe. A natural phase-two extension once the POS entry stream is on.
The heart of the proposal: free FINNS Pass for everyone, paid Member+ on top — recurring revenue, the member dashboard, member pricing & reserved inventory in CTG, queue-skip, presales. Tiers stay alive between trips (and your "locals hidden tier" idea fits right in).
A live points balance earned on every purchase, redeemed in venue — landing with the phase-two POS integration. It answers your points-vs-offers debate with both: points for redemption, entries for draws.
Members recruit members — "bring your crew" mechanics with tracked rewards. Cheap acquisition from your happiest guests.
Your own idea list, made runnable: bar tour / zone check-in QRs (Pool Bar, Lagoon, Main Stage, Sunset Deck, Party Bar), squad goals, leaderboards, day-to-night journeys, cross-venue streaks — each becomes a promotion rule with bonus entries.
The proposal's signature moment: Golden Hour draws with a countdown on every dashboard, winner moments staged on the floor ("bottle winner — Chris"), and a live "winning right now" feed. Theatre that makes the draw publicly credible.
Prizes that would move your guests SOTA draft — edit
The prize strategy shapes the mechanics, the budget and the permits. Drafted from your gamification notes — what feels right?
The away game — keeping attention after checkout
Most of your guests fly home. That's not the end of the relationship — it's where the trade promotion takes over. The pass in their wallet keeps a live promotion in their pocket:
- Entries keep working after the flight home — the balance they earned in venue counts toward draws that close weeks later, so checking the promotion becomes a reason to keep the pass (and the membership) active
- Flagship "come back" draws — prizes built around the return: the trip back, the bed, the bar tab — spoken in FINNS language, not travel-agency language
- Trade promotions as content — draw announcements, winner moments and live draws at the club give members abroad a reason to open the pass, the emails and the socials
- Tiers that bridge trips — status, streaks and your "exactly one year ago you were here" anniversary trigger carry entries, not just discounts; win-back messages get a scoreboard
- Presales & squads for the away crowd — member-only NYE first access, and pooled group entries that let the crew back home fund the next trip together
Systems & integrations
The platform is at its best when participation is automatic — spend at the till, entries appear. This tab maps what you run today and when SOTA connects to each system. Correct anything we've misread; "not sure" is a completely fine note.
Your current systems Pre-filled from your docs
Named from your CDP project documentation — correct anything we've misread, and fill the two flagged gaps. The chips show when SOTA connects to each system, and the ticks match: phase-one connections arrive ticked (payments, LiteCard, the light Insider sync); phase-two rows arrive unticked — each description says what connecting it would add.
Data & ownership
Hosting & infrastructure
Your platform runs in its own dedicated AWS environment — not shared with any other SOTA client. We've pre-selected the setup we recommend for FINNS and written down why, so your IT and legal teams can sanity-check the reasoning rather than the jargon.
Hosting region
Our standard SOTA deployment For your IT team's review
Serverless-first, dedicated to FINNS, scaled automatically for event spikes:
- CloudFront + S3 — global CDN front-end (fast for members abroad)
- API Gateway + Lambda — serverless API, scales with NYE-level spikes
- RDS (Multi-AZ) — managed database with synchronous standby
- Cognito — member & staff authentication, MFA for admin
- CloudWatch — monitoring & alerting, 24/7
- Certificate Manager — TLS everywhere, always
Compliance & prizes
Prize promotions and memberships in Indonesia come with real rules — permits, taxes, privacy. We build the platform so compliance is designed-in, and we coordinate with your counsel. This tab maps who owns what. We're your platform partner, not your lawyers — but we've done this dance before and we'll make it easy.
The checklist
Free prize draws in Indonesia generally require a permit from the Ministry of Social Affairs (Kemensos). The platform is built to produce the records a permit requires (entry logs, draw audit trails, winner publication).
Indonesian prize winnings attract withholding tax. We need a policy: does FINNS gross-up prizes (winner pays nothing) or does the winner bear the tax? Finance should own this one.
Consent capture, privacy notice, retention and cross-border transfer rules are built into the platform. Hosting in Jakarta (see previous tab) simplifies this considerably.
Clear T&Cs, disclosed odds/mechanics and auditable draws protect the brand as much as the law. SOTA drafts these with your input; live draws make winner moments public and credible.
A beach club skews adult; alcohol-adjacent promotions should be 18+/21+ by design. Confirm the age gate the brand wants.
Reporting & KPIs
What does success look like on a dashboard, and whose dashboard is it? We've drafted the KPIs we'd propose for a FINNS launch — edit, delete, add.
Proposed KPIs SOTA draft — edit me
Scale, timeline & testing
Ballpark numbers are perfect — they size the infrastructure and shape the rollout plan. We'd rather engineer for your honest guess than a wish.
Scale
Timeline & rollout
Member communications
Tick the channels members should hear from FINNS on. In Indonesia, WhatsApp isn't optional — it's the default.
Outcome priorities
Rate each outcome from 1 (flexible) to 5 (non-negotiable). There's no right answer — but if everything is a 5, nothing is. This ten-minute exercise saves the hardest conversations for later by having them now, calmly.
| Outcome | 1 flexible | 2 | 3 | 4 | 5 non-negotiable |
|---|---|---|---|---|---|
| Stakeholder satisfaction | |||||
| Deliver on time | |||||
| Deliver on budget | |||||
| Scope — everything planned ships | |||||
| Quality — polish & reliability | |||||
| Team satisfaction — both sides enjoy the ride |
Your questions
List any questions you have here — commercial, technical, operational — and we'll answer every one in writing before the first workshop.
What would you like to ask us? Needs FINNS input
Anything at all — commercial, technical, operational. Nothing is too small.
Review & submit
Here's where each section stands — completeness and whether your team has acknowledged it. Click any row to jump back. You don't need 100% — submit whenever the important things are in, and we'll handle the gaps together.