Next WrldFeatured case · Next Wrld product
AION / WELLNESSAION Wellness — The operating system for modern fitness businesses.
A platform connecting members, memberships, payments, access and cash operations across the daily work of gyms.
Strategy · Product · UX/UI · Software Engineering · Cloud
01 · Operational fragmentation
Everything happens in the same day. The information often lives in different places.
A member arrives at reception. The team finds their record, checks the membership, decides whether they can enter and records a payment when needed. At the end of the day, those movements need to match the cash close.
When each step depends on a separate record, a simple request turns into searches, checks and repeated data entry.
02 · Product opportunity
Turn related tasks into a coherent operation.
AION organizes work around the decisions teams make every day. Four principles guided the product from domain model to interface.
Keep members, memberships, payments, access and cash activity in the same context.
Shorten frequent searches and steps at reception and in administration.
Show validity, expirations, activity and payments where decisions happen.
Support isolated organizations on a shared product foundation.
Records, statuses, payments and closeouts checked as separate parts of the day.
An operational sequence with shared context and recorded movements.
AION · CONNECTED OPERATIONS03 · Understand and model
We first defined how operational decisions relate to one another.
We designed the complete journey: identify the member, interpret the plan, record a renewal through payment, make an access decision and retain the movement for daily close.
Currencies, payment methods, document types and access policies are configurable so the model can support each organization’s operation.
04 · Product walkthrough
The product follows the work from the front desk.
The member list brings search and status together. From the same operation, the team can assign or renew a membership by recording a payment, including split methods or configured currencies.
FindSearch using the member information available.
ResolvePlan, validity and status visible in context.
RecordThe payment retains its link to the membership.
05 · Connected experience
Every movement contributes to a shared view of the operation.
Access records check-ins according to membership status and configured policy. Payments flow into the overview and daily cash close. The dashboard brings together today’s revenue, activity, active members, signups and expirations without rebuilding the picture by hand.
Search brings together the information needed to respond without checking parallel records.
The decision applies configured validity, grace period and cooldown, then retains the check-in.
Daily movements become information the team can act on.
Recorded payments organize cash review by method and currency.
06 · Multi-organization product
AION shares one product foundation while keeping each organization’s operating context isolated.
AION runs as a multi-tenant SaaS. Members, users, settings and operational movements belong to the organization that manages them.
- Members
- Operations
- Users
- Settings
Isolated data context
- Members
- Operations
- Users
- Settings
Isolated data context
- Members
- Operations
- Users
- Settings
Isolated data context
The visual scope covers organization-level isolation; multi-location operation is outside this representation.
07 · System thinking
The interface is the visible layer of connected decisions.
We designed experience, workflows, rules and data as parts of the same product, so an action at reception retains its meaning through the overview and daily close.
ExperienceReception · administration · daily decisions
Product workflowsMembers · memberships · payments · access · cash
Business logicValidity · usage · currencies · policies · permissions
Data & infrastructureIsolation · persistence · files · deployment
08 · Technology by responsibility
Each technical decision supports a concrete product responsibility.
The architecture combines an SPA with a modular-monolith backend. That boundary keeps the domain cohesive and allows modules to evolve without distributing complexity too early.
Operational workflows, interface state and visualization.
Contracts, validation and role-based permissions.
Cohesive rules, migrations and transactional data.
Storage for optional member photos.
Built to evolve
The foundation can support new capabilities when the product validates them.
- Automation
- Analytics
- Integrations
- Intelligence
- New modules
09 · End-to-end involvement
Next Wrld stays with the product from the operational question through its evolution.
In AION, we work across strategy, product definition, experience, architecture, frontend, backend, data and infrastructure. The decisions stay connected throughout one process.
- 01Discover
Understand the operation and its decisions.
- 02Shape
Define product, scope and model.
- 03Build
Design and implement the workflows.
- 04Launch
Bring the system into operation.
- 05Evolve
Learn from use and decide what follows.
10 · Concrete result
A daily operation with shared context.
Teams can find members, manage plans and memberships, record payments, resolve access, review check-ins and complete daily cash review within the same product.
The dashboard organizes the current state through today’s revenue, activity, active members, signups, expirations, seven-day series and payment breakdowns.
AION connects how the business operates with how the product is built. That continuity defines Next Wrld’s work: strategy, product, experience, engineering and cloud under one shared responsibility.
Operational diagnostic
Turn a critical part of your operation into a system.
Let’s review one concrete process and decide where it makes sense to simplify, connect or build.
← Back to case studies