Know the context
Resolve the person, club, consent, history, and active work before acting.
Architecture
Built for the interface you use today—and the one that replaces it tomorrow.
FitStack separates experiences from the governed context, domain rules, and workflows that make them useful. Your organization owns the durable layers.
The system
Four layers. One operational truth.
01
Experiences
Public web, HQ administration, club operations, member surfaces, mobile, voice, SMS, and email.
02
Operating intelligence
Agents, tools, deterministic workflows, evaluation, human handoff, and observability.
03
Shared context and services
Identity, consent, member history, clubs, leads, communications, agreements, and domain rules.
04
Client-owned foundation
Repository, data, infrastructure accounts, configuration, documentation, and deployment history.
Systems of recordPaymentsCommunicationsSchedulingSpecialist services
Operating agents
A shared agent core with channel-specific behavior.
Voice, SMS, email, and web interactions use common identity, history, policy, and tools while respecting the constraints of each channel.
Use bounded tools
Read availability, create records, update workflows, and send links through governed actions.
Follow policy
Apply deterministic routing, communication rules, failure paths, and human escalation.
Learn visibly
Record messages, outcomes, evaluation, and operational events for staff and analytics.
What you own
The complete operating foundation.
- The application and service repositories
- The data model and operational history
- Infrastructure and vendor accounts
- Agent instructions, tools, and evaluations
- Workflows, policies, and integration contracts
- Deployment automation and operating documentation
Engineering principles
Designed to stay understandable as it grows.
Domain-driven
Business rules live in focused services shared across applications and interfaces.
Event-aware
Reliable workflows coordinate long-running work, retries, timing, and outcomes.
Integration-first
External systems meet explicit boundaries instead of leaking across the platform.
Brand-isolated
Client experiences can diverge while reusable platform capabilities continue to improve.
Auditable
Consent, agent actions, operational events, and critical changes leave visible history.
Portable
Client-owned code and accounts preserve leverage across vendors, models, and delivery partners.
Build what comes next
Inspect the architecture against your operation.
Start with one member journey, the systems it crosses, and the context your organization needs to own.