Arcadia is redefining what a community centre can be. Not a single-purpose leisure facility. Not a clinical mental health service. A genuinely integrated community hub where fitness, therapy, co-working, creative studios, youth programmes, crisis support, and social gathering coexist . Designed around the idea that wellbeing is not a separate intervention, it is what happens when communities are well-structured. Managing a network of these centres requires software that is just as unusual as the model itself.
Arcadia centres are community hubs built around a person-issue-context model of wellbeing. Rather than separating health from life, placing it in clinical settings people visit reluctantly, Arcadia integrates support into everyday community activity. You go to the centre for a fitness class, a co-working session, an after-school club, a music night. The mental health support is there if and when you need it, woven into the same space, without stigma and without a waiting list.
Each centre provides:
Beyond the centre buildings, Arcadia operates Sanctuaries (rural recovery spaces) and Retreats for skill-building and wellness getaways. The full ecosystem requires a management platform that can handle all of this without forcing a single, inflexible service model onto operations that are deliberately local and responsive.
No off-the-shelf platform is designed for a service organisation that simultaneously manages therapy bookings, co-working hot-desk reservations, walk-in crisis intake, after-school programme waitlists, volunteer rotas, and café table availability, across a network of centres with different local configurations.
Booking systems designed for gyms don't understand crisis support pathways. Membership platforms designed for co-working spaces don't understand multi-tier service access across health, leisure, and education. Community case management systems don't understand consortium partnership structures and equity distribution. The combination of service types that defines Arcadia is precisely the combination that no existing software has been designed for. That's . That is the challenge.
A unified booking layer across all service types (fitness classes, therapy sessions, co-working desks, workshop seats, event tickets, after-school programme enrolments) with service-appropriate configuration per type. A therapy slot has different booking rules, cancellation policies, and privacy requirements than a fitness class. The system accommodates both without forcing one template onto all.
Arcadia's inclusive-by-design model means membership cannot be purely transactional. Access tiers need to reflect economic circumstances, community contribution, referral pathways, and local authority arrangements. The platform needs to manage this complexity without bureaucratising the user experience for members who simply want to show up.
Walk-in support requires a distinct interface from booking-based services. Staff need to log interactions, record the level of support provided, note follow-up requirements, and flag escalations, without creating a clinical records system that triggers regulatory frameworks the centre is specifically trying to avoid. The three-tier crisis framework (on-site support, on-site refuge, referral to Sanctuary or Soteria partner) needs to be navigable in real time by a non-clinical coordinator.
Arcadia's model relies heavily on community volunteers, people who are themselves centre members taking on coordination, facilitation, or peer support roles. The platform needs to manage volunteer availability, matching, scheduling, and recognition without it feeling like a staffing system. The distinction between member and volunteer is porous by design.
Each centre operates through a three-sector partnership: private operators who fund and manage local ventures, public sector bodies who fund essential services, and third-sector organisations who supply community connectors and specialist support. The platform needs to manage equity relationships, consortium agreements, reporting obligations to each sector, and the distribution of outcomes data that demonstrates impact to funders. This is not standard CRM functionality.
Each Arcadia centre is locally responsive but collectively coordinated. National-level reporting on outcomes, impact metrics, consortium formation across multiple centres, and learning from each centre's experience. All of this requires a network layer above the individual centre interface. The platform needs to be both hyperlocal and network-wide simultaneously.
The Arcadia platform will be built on the engage.re graph architecture. The centre is a node. Services are nodes. Members, volunteers, staff, partners, and programmes are all nodes. The relationships between them (who is enrolled in what, who referred whom, which organisation holds what equity stake, which partner is responsible for which service) are all typed links with metadata. The entire Arcadia model, however complex, fits in five tables.
Because the platform owns its data model and carries no dependency on an external platform vendor, Arcadia can evolve the system as its model evolves, adding new service types, new partnership structures, and new locations, without rebuilding from scratch and without asking permission from a software provider.
ESRE Media runs its entire pipeline, partner network, and commission tracking on a system we built ourselves, on the same graph architecture. We are growing fast, and if you know organisations that need better digital systems, referral partners earn 15% on project delivery.
Find out how partnerships work