Pricing And Packaging
How TrialStack packages the same structured platform foundation into focused, governed, and multi-study operating models.
Start with the operating model
flowchart LR
Foundation["Structured platform foundation"] --> Scope["Scope of use"]
Scope --> Governance["Governance depth"]
Governance --> Support["Implementation and support model"]
TrialStack pricing is built around operational depth, governance depth, and implementation burden, not around selling standards, generic AI, or disconnected feature bundles.
Every plan starts from the same core product architecture:
- structured trial records and connected context
- standards-aware protocol structure
- AI-assisted drafting inside governed product workflows
- visible history and supported export surfaces where the product already supports them
The step-up is how much controlled study-startup work the team needs to run through that foundation.
Commercial snapshot
- every tier includes a
7-day free trial - teams can pay
monthly or annually - annual billing saves
about 17% - the public buying posture is
cancel anytime,no setup fee, andno migration required - monthly token capacity scales by plan:
500K,2M, and8M included - support and security posture step up with the package, not just raw volume
The three packaging questions
Ask three questions when choosing a plan:
- Is this one active study or a broader portfolio?
- Is the team using TrialStack as a focused drafting workspace or as the governed operating surface for study-definition work?
- Does the rollout need starter setup, governed workflow design, or broader organizational implementation and support?
Plan intent
| Plan | Best fit | Why it exists |
|---|---|---|
| Ignite | Academic teams, early biotech groups, and focused study teams | Gives one study team a structured place to draft and coordinate without pretending it already needs the full governed operating model |
| Accelerate | Serious study teams, CTUs, academic CROs, and sponsors running one study or a small portfolio | Makes governed study-definition work, controlled review, reusable workflows, and downstream readiness the default way the team operates |
| Scale | Multi-study sponsors, CROs, CTU programs, and broader enterprise delivery groups | Adds program governance, organizational controls, implementation depth, and SLA-backed support accountability |
Current package snapshot
| Plan | Public price | Capacity | Support |
|---|---|---|---|
| Ignite | €500 / month | 1 active trial, 3 users, 500K tokens / month | Email support |
| Accelerate | €2,500 / month | 3 active trials, 8 users, 2M tokens / month | Email + business-hours phone |
| Scale | €10,000+ / month | 10+ / custom active trials, Unlimited users, 8M included tokens / month | Email + priority phone |
Limit snapshot
| Area | Ignite | Accelerate | Scale |
|---|---|---|---|
| Evidence Packs | 3 active, 3 templates | 15 active, 10 templates | 50 active, Unlimited templates |
| Documents | 12 active, 8 templates | 40 active, 25 templates | 150 active, 50 templates |
| Insights | 3 active | 15 active | 50 active |
| Revisions | 10 active, 1 template | 40 active, 5 templates | 150 active, 15 templates |
| Connections | systems 8, contacts 25, interventions 10, organizations 10, personas 10, sites 5 | systems 20, contacts 100, interventions 25, organizations 30, personas 30, sites 40 | systems 40, contacts 500, interventions 100, organizations 100, personas 100, sites 200 |
| Tools | configurable skills No, rules 5, concurrent runs 2 | configurable skills Yes, rules 15, concurrent runs 5 | configurable skills Yes, rules 50, concurrent runs 10 |
| Security | SAML No, RBAC No, HIPAA BAA No, SCIM No, 2FA Yes | SAML No, RBAC Yes, HIPAA BAA Optional add-on, SCIM No, 2FA Yes | SAML Yes, RBAC Yes, HIPAA BAA Yes, SCIM Yes, 2FA Yes |
What stays foundational across all plans
The following are part of the platform model and should not be treated as premium buzzwords:
- structured trial architecture
- standards-aware protocol structure
- connected study context
- AI-assisted drafting with human review
- versioned records and visible change history
- supported standards-based export surfaces where configured
What changes when teams move up
flowchart TD
A["Ignite"] --> B["Accelerate"]
B --> C["Scale"]
A --> A1["Focused study workspace"]
B --> B1["Governed study-definition operations"]
C --> C1["Program governance and implementation depth"]
The real pricing fence is governance and operating depth:
Igniteis for standards-aware structured authoring and AI-assisted document generation inside a focused study scope.Accelerateis where TrialStack becomes the governed study-definition and startup system for serious study work.Scaleis for multi-study organizations that need broader control, organizational governance, and implementation/support accountability.
Capability fences that matter
The most important plan differences are not generic feature volume. They are operational consequences.
Ignite: bounded capacity for one active trial, small-team collaboration, starter templates, and standard supportAccelerate: more active capacity plus persona engagement feedback, feasibility review, configurable skills, RBAC, and stronger support expectationsScale: enterprise limits, identity controls such as SAML and SCIM, included HIPAA BAA support, and priority response expectations
Current tier fences
Ignite: one active trial, three users, 500K monthly tokens, bounded limits across connected records, and email supportAccelerate: everything in Ignite plus three active trials, eight users, 2M monthly tokens, persona engagement feedback, feasibility review, configurable skills, RBAC, and business-hours phone supportScale: everything in Accelerate plus 10+ or custom active trials, unlimited users, 8M included monthly tokens, SAML, SCIM, included HIPAA BAA, and priority response commitments
Standards framing
Use standards to explain product logic, not to decorate pricing.
ICH M11andCeSHarPare relevant when the conversation is about structured protocol organization and consistency.CDISC USDMis relevant when the conversation is about structured downstream representation and exchange readiness where supported.ICH Good Clinical Practice E6(R3)is relevant only when the conversation is about role clarity, review discipline, oversight, rationale capture, verification rigor, and governed change.
TrialStack can support more structured and controlled ways of working, but customer SOPs, validation, sign-off, and regulatory responsibilities remain with the customer.
Upgrade triggers
Move from Ignite to Accelerate when:
- more than one function must review and author in the same governed flow
- one trial and three users stop matching the team shape
- the team needs persona engagement feedback, feasibility review, configurable skills, or RBAC
- document, evidence, insight, revision, or connection limits are becoming the real blocker
- TrialStack becomes the study team’s operational source of truth
Move from Accelerate to Scale when:
- several studies must run under one governance model
- rollout requires enterprise identity controls such as SAML or SCIM
- HIPAA BAA must be included rather than treated as an optional add-on
- active capacity across templates, records, runs, or connected entities is outgrowing the mid-tier limits
- support expectations become SLA-backed and program-level rather than study-team level