Where Stack9 Fits: Three Ways Teams Put It to Work
Same platform, three different shapes of problem — a multi-brand dealer group, a membership organisation, and a financial-services back office. Each maps to a different combination of Stack9 Core and Stack9 Experience capabilities.
Multi-Brand Automotive Dealer Group
A dealer group operates several dealership brands across different regions. Each dealership needs its own pages, campaigns, and lead forms — and its own team managing them day to day — without the group standing up a separate marketing stack per brand.
At the same time, the group wants a shared design system and shared back-end so a change to a common component, or a group-wide compliance update, doesn’t have to be repeated five times.
How Stack9 Maps to It
One Marketing Tenant, one Business Unit per dealership — each with its own pages, campaigns, forms, and files.
Learn moreShared Core Slices for the common design system, with per-brand Business Unit Forks where a dealership genuinely needs to diverge.
Learn moreCampaigns and journeys run and report per Business Unit, scoped to each brand’s own audience.
Learn moreUnified subscriber profiles keep lead and customer data addressable across the group while campaigns stay scoped per brand.
Learn moreOne tenant, one shared component library, one Business Unit per dealership.
Membership Organisation (Association / Club)
A membership association needs a self-service portal where members can update details, renew, and manage their own records — plus regular email and marketing communication to keep members engaged.
Behind the scenes, staff need forms and workflows that route into back-office processes: renewal reminders, event registrations, and approvals that shouldn’t require manual re-entry.
How Stack9 Maps to It
Member entities, self-service portal screens, and automations for renewals and status changes.
Learn moreRenewal reminders, welcome sequences, and event communications sent to the member base.
Learn moreOngoing engagement journeys for members, segmented by membership tier or activity.
Learn moreForms and webhooks push submissions — event sign-ups, applications — into back-office workflows the moment they happen.
Learn moreA member portal on Core, engagement on Experience, forms and webhooks tying the two together.
Financial Services / Operations Back Office
An operations team needs a domain-specific application to run case files, approvals, and records that don’t map to any off-the-shelf CRM — with a query library for reporting and workflow automations for the steps that repeat every time.
Some of that work needs to reach customers directly — a status page, a document, a transactional email — and increasingly, internal teams want their own AI assistants to be able to look up and act on operations data without a bespoke integration.
How Stack9 Maps to It
Domain entities, a query library for reporting, and workflow automations for case handling.
Learn moreDocument templates and a central library for the files generated and stored through a case’s lifecycle.
Learn moreTransactional email and customer-facing pages served from the Stack9 Experience side.
Learn moreInstance MCP exposes chosen query-library queries and automations as tools an internal AI assistant can call, under the same permissions as the REST API.
Learn moreCore runs the back office, Experience faces the customer, MCP faces internal AI assistants.
None of These Are Edge Cases
They're the same pattern in three industries: a domain-specific application on Stack9 Core, pre-integrated marketing and communications on Stack9 Experience, and as much or as little of each as the problem actually needs.