LUFF
LUFF products & offerings Concept demo · Proposed pilot

LUFF Membership · Provisional label

A clear welcome.
A current answer.

Bring applications, dues, and member credentials into one dependable flow. Members open their pass on a phone. Staff know what to do when they arrive.

Try the member journey Discuss a membership pilot

For club owners, membership teams, and the people at the door.

Fictional club · Sample pass

Alex Morgan

Harbor Social Club · Social member

Member → staff → welcome

Your rules, carried through to the door.

A proposed offering, shown with fictional data. The platform is not yet built. LUFF Membership is a provisional label; brand and ownership remain open.

A fictional member journey

One member. From application to arrival.

Try the illustrative journey below. Approval, dues, and access stay separate, so a payment alone never decides who belongs.

  1. 01Apply
  2. 02Review
  3. 03Confirm dues
  4. 04Phone credential
  5. 05Staff check-in
Fictional data · Browser only

No real members, payments, or connected systems.

Switching clubs resets the sample journey.

Member view

Responsive web concept

Harbor Social Club

Alex Morgan

Social member

Review pending

Credential preview · Awaiting eligibility

Approval
Pending
Dues
Pending
Access area
Club lounge

DEMO-H014 · Fictional member

A real pilot would require a current server check. This picture cannot open a door.

Staff view

Role actions illustrated

Alex's membership

Staff approval + current annual dues

Reviewer

Application awaiting review

Billing staff

Sample dues record pending

Door staff · Club lounge

Review pending

The application needs an authorized review.

Manager

Try an access change

A door attendant would check entry; reviewers and managers would hold separate permissions. This demo simulates those roles.

Start by approving Alex's fictional application. You can also check the pending credential to see the staff decision.

Sample history & export 1 events

Fictional, browser-local history. Reset or refresh clears the journey.

  1. #01
    Applicant

    Fictional application received · Alex Morgan

Membership operations for adult clubs

From “are they a member?” to a clear next step.

The proposed pilot connects your membership team's decisions with the answer staff see at the door, and keeps a record of why it changed.

A repeatable foundation

Shared foundations.
Your way of working.

The proposed core holds the membership decisions. Configuration and scoped connections make it fit your club. Existing LUFF components still need a source and fit review.

01 / Reusable core · Proposed

Know who can decide.

Organizations, member records, staff roles, and a review workflow with clear approval authority.

Proposed capability

Pilot must test staff permissions and separation between organizations.

Keep access current.

Membership states, entitlements, dues reconciliation, and credential checks that reflect changes in eligibility.

Illustrated in this demo

This browser demo illustrates decision changes. Live verification and payment event handling still need implementation and testing.

Leave a useful history.

Check-in, suspension, reinstatement, exception records, and an export the club can keep.

Illustrated in this demo

This demo records fictional local events and exports them. Production audit, recovery, and data quality are unverified.

02 / Club configuration & connections

Your club's rules.

Branding, membership tiers, review steps, dues policy, guest rules, and access areas.

Proposed capability

Two fictional configurations are shown here. Real club policies need discovery and acceptance tests.

The systems you use.

Selected roster or CRM, billing and accounting records, message delivery, and credential formats through scoped connections.

Proposed capability

No integrations are connected. Access, compatibility, and effort must be confirmed separately.

An agreed way to run it.

Hosting, sign-in, privacy, retention, support, and handover responsibilities chosen with your team.

Proposed capability

Operating responsibilities and source components for reuse have not been verified.

A scoped pilot

Start with one club. Prove the everyday flow.

One adult club, an agreed member cohort, and one admission workflow. Define a useful result with the people who will run it.

Plan the first conversation

Review preview only. No inquiry is sent from this page.

  1. 01

    Map the working day.

    Agree who approves members, what confirms dues, what staff check, and which existing records we need.

  2. 02

    Test the difficult moments.

    Review suspension, copied credentials, lost phones, duplicate checks, payment corrections, and no connection against agreed expectations.

  3. 03

    Decide what earns a rollout.

    Measure staff effort and decision errors against your baseline. Review the evidence and a second fictional club configuration before expanding.

Discuss a membership pilot

Bring a workflow,
and the people who run it.

For a first conversation: the club's current process, its budget owner, the systems holding records and dues, and a small cohort to test with. No member roster or payment details are needed here.

Contact LUFF about a pilot

What we would agree first

Pilot scope, pricing, timing, and support would be agreed after discovery.

Phone web credentials are the proposed starting point. Wallet passes, NFC hardware, and unattended entry need separate review.

Portable identity and club-authorized transfer remain discovery questions. Global networking, resale, equity, escrow returns, and formal governance are outside this pilot.

Where the concept stands

This public demo illustrates a proposed workflow. A production pilot requires an agreed scope, operating tests, and reviewed terms.

  • Agree the brand, ownership, and rights.
  • Confirm one club, its operator, and pilot scope.
  • Review capability evidence, data responsibilities, and commercial terms.

The membership platform is not yet built. Brand and ownership remain unresolved.