Cost That Does Not Scale With Your Adoption
We do not publish price lists, because a licence fee without your instance count, environments, integration scope and support tier attached would be a number you could not plan against. What we can be precise about is the structure — and it is deliberately designed so that growing usage does not grow your licence.
Licensing is fixed per instance
Not per seat and not per user. Your cost does not increase as member, employer, claimant or staff numbers grow — so a successful rollout does not become a bigger invoice.
Hosting scales with actual usage
Infrastructure is charged at cost and sized by real demand rather than provisioned for peak year-round. Eagers Automotive absorbs up to 20× Saturday transaction spikes through autoscaling — containers moving from 5 to 35 units, the database to 300% of baseline — with no pre-provisioned peak capacity idling for the other six days.
New capability is an update, not a re-implementation
Improvements reach your existing instance through LTS versioning and RFC-based change management. And because every client runs the same underlying codebase, a module built for one client becomes optionally available to others — reaching you as an evolutionary update rather than a separate purchase.
One platform, not stacked module licences
CMS, marketing automation, CDP, email and AI are native capabilities of one platform rather than separately licensed products. That removes compounding module-by-module cost growth — and the need for certified specialist implementation partners for ongoing development.
The Components We Will Price for You
- Platform licence — fixed per Stack9 instance, independent of user counts.
- AWS infrastructure — on-charged at cost, scaling with actual usage across your DEV, UAT and Production environments.
- Email and communications — usage-based, against actual send volume.
- Base Support Package — SLA-backed support tiered by severity, delivered by the onshore team that built the platform.
- Development Credits — a pooled allocation for enhancements and new capability, drawn down against agreed work.
- Annual framework uplift — recommended and included under the MSA, so you are not funding a periodic re-platform.
On timeframes, so you can budget honestly: a new microsite is typically 2 to 10 days, which covers infrastructure and technical setup only — domain, SSL and SSO — with your team populating content in parallel. A first MVP portal migrated end to end runs to around six months. Each subsequent portal is estimated at 8 to 16 weeks, depending on content volume and integration complexity, and assumes the MVP established the template and methodology.
Tell Us the Shape and We Will Price It
Instance count, environments, the systems you need to integrate with, and the support tier you want. One vendor quotes the platform, the build and the support — there is no separate implementation partner to price alongside us.