Commercial packaging

Four levers, not three bundles

Four things are priced separately: the platform you subscribe to, the work to get it deployed, the support relationship around it, and the scope you add as adoption grows. Bundling those together produces impressive contracts and terrible delivery, so we do not.

Platform

The recurring subscription: Canopy, Roots underneath it, and whichever modules are in scope. Priced on organizational reach rather than on how much you use it.

Implementation

Getting your data connected and described correctly. Priced separately because it varies enormously with your sources, definitions and governance — it is not the same job twice.

Success

The ongoing relationship: who you get, how often, and how fast we respond when something breaks. An explicit commitment rather than an implied one.

Expansion

Domains, data sources, environments and modules. Added as adoption grows, without reopening the whole agreement.

What every edition includes

Trust is the product, so none of it is a premium feature. There is no cheaper edition of DeepGarden that produces less defensible answers.

Ask, Views and Evidence
Governed, read-only querying
Query validation before execution
Access controls enforced before a question is planned
A production Roots environment
Standard monitoring and security

Platform

Editions differ by how much of the organization is in scope, how much configuration control you hold, and which modules are included — never by how defensible the answers are.

Canopy Core

One department, one defined use case

Narrower, not cheaper. Everything that makes an answer defensible is here — this tier is about how much of the organization is in scope, not how much you can trust the result.

Business coverage: One domain or use case
Data sources: Two or three standard sources
Users: Around 25–75 active
Roots: DeepGarden-managed
Ask: Included
Views: Standard tables, charts and summaries
Evidence: Full query receipts and citations
Studio: Limited administrative controls
Signals: Basic usage reporting
Flows: Limited scheduled reporting
Environments: One production environment
Support: Standard
Account management: Pooled customer success

What the relationship looks like

Structured onboarding
Administrator training
Quarterly success review
Email and ticket support with standard response targets
Configuration changes through a defined request process
No custom engineering included

Scope this edition

Where most customers land

Canopy Scale

Several teams, or one significant business function

Broad enough to matter across a function without promising an organization-wide transformation. This is where most customers land.

Business coverage: Two to four domains or major use cases
Data sources: Around five to ten
Users: Around 100–500 active
Roots: Shared management
Ask: Advanced cross-source questioning
Views: Advanced and shared Views
Evidence: Expanded audit and retention controls
Studio: Included
Signals: Foundational capabilities
Flows: Scheduled briefings and alerts
Environments: Development and production
Security: SSO and enhanced access controls
Support: Enhanced
Account management: Named CSM

What the relationship looks like

Named customer success manager
Monthly success and adoption meeting
Quarterly executive review
Usage, adoption and metric-coverage reporting
Administrator office hours
Faster incident response
Annual technical health review
Limited configuration capacity

Scope this edition

Canopy Enterprise

Cross-enterprise, embedded, or business-critical

Greater scale, governance, responsiveness and partnership. Enterprise does not mean unlimited customization — that is what Managed Intelligence is for.

Business coverage: Multiple domains and business units
Data sources: Contracted enterprise scope
Users: Broad internal or external deployment
Roots: Full enterprise governance
Ask: Organization-wide querying
Views: Full generative UI and embedded experiences
Evidence: Enterprise audit, retention and compliance controls
Studio: Full Studio
Signals: Full Signals
Flows: Full automation layer
Environments: Development, test and production
Security: SCIM, private networking, advanced encryption
APIs: Included or contracted separately
Support: Mission-critical
Account management: Named CSM and technical account manager

What the relationship looks like

Named CSM, named technical account manager and an executive sponsor
Monthly operating reviews and quarterly executive business reviews
Proactive system monitoring and architecture reviews
Adoption and value-realization planning
Priority escalation with severity-one commitments
Joint roadmap planning

Scope this edition

Implementation

Priced separately because it is not the same job twice. Three clean warehouse tables and a health plan with claims, enrolment, benefit data and PHI controls are different engagements, and pretending otherwise means one of us absorbs the difference.

Standard implementation

Usually paired with Canopy Core

One domain, a small number of clean sources, and a defined use case to prove out.

Roughly six to ten weeks

Use-case discovery
One domain model
Two or three supported connections
Initial metric catalog
Permission configuration and query validation
User acceptance testing
Administrator training and launch support

Advanced implementation

Usually paired with Canopy Scale

Several domains, more complex semantic modeling, and change management for a wider group of users.

Roughly ten to sixteen weeks

Multiple use cases or domains
More complex semantic modeling
Five to ten data connections
Custom metric definitions
Historical query and documentation ingestion
Development and production environments
Workflow configuration and broader acceptance testing
Change-management support and departmental training

Enterprise transformation

Usually paired with Canopy Enterprise

Multiple business units and a real data architecture. Milestone-based and run in phases rather than as one delivery.

Several months, in defined phases

Multiple business units and complex data architecture
Custom connectors
Enterprise identity and networking
Extensive domain-model development
Compliance and security reviews
Data-quality remediation
Executive and departmental workshops
Embedded or external-facing deployment
Formal change-management programme

Success plans

An explicit commitment rather than an implied one: who you get, how often you see them, and how fast we move when something breaks. Support fixes the product; success drives adoption. They are not the same job.

Standard Success

Included with the subscription

Everything you need to run the platform, with pooled coverage rather than a named person.

Support portal and documentation
Structured onboarding handoff
Quarterly adoption review
Pooled customer-success contact
Business-hours support with standard response targets

Partnered Success

Most Scale customers

A named person who knows your setup, on a monthly cadence, with prioritized support behind them.

Named customer success manager
Monthly operating review
Quarterly executive review
Adoption plan with usage and value reporting
Administrator office hours and training sessions
Prioritized support
Annual health review

Strategic Success

Enterprise deployments

A team rather than a contact, working to a joint plan, with the fastest response commitments we offer.

Named CSM, named technical account manager and executive sponsor
Weekly or biweekly working cadence
Joint success plan and business-value reporting
Proactive monitoring and architecture reviews
Key-event support
Roadmap workshops
Mission-critical escalation with the fastest severity-one response

Expansion

Scope grows in defined units, so adding a domain or a source does not mean reopening the whole agreement.

Additional standard data source
Custom connector
Additional business domain
Additional environment
Signals
Flows
Embedded, customer-facing deployment
Premium support
Managed Intelligence retainer
Advanced security and deployment options

What actually moves in a negotiation

If the number does not work, we change the scope rather than discounting the same thing. It is a more honest conversation and it leaves you with a contract that still means something at renewal.

Launch with one domain instead of three
Reduce the number of connected sources
Defer Signals to phase two
Take Standard Success rather than Partnered
Remove a custom connector
Phase Studio access
Reduce implementation scope
Adjust the environment count

Proof of Value

DeepGarden needs real data and real definitions to show you anything worth seeing, so the way in is a fixed-scope engagement rather than a login. Part of the fee is credited against a first-year subscription signed within an agreed window.

Eight to twelve weeks
One defined business problem, one domain
One or two data sources
A small user group
Success criteria agreed before we start
Executive readout at completion
No production SLA
No unlimited customization

Managed Intelligence

A monthly retainer for teams who want us to act as their data function rather than their vendor. Sold as defined delivery capacity — never as unlimited customization.

Defined monthly capacity against a prioritized backlog
New metric and domain-model development
New Views and custom Flows
Prompt and query optimization
Data-quality investigation
Monthly executive briefing
Analyst support

Predictable capacity, not a token meter

Raw model tokens are a terrible unit for a customer to be billed in: nobody can forecast them, they do not track the value of an answer, and an apparently simple question can cost far more than a complicated one. Contracts are written against a monthly allowance of verified analytical responses, with fair-use and workload-complexity provisions. We monitor the underlying cost; you should not have to.

What every order form makes explicit

Most bad vendor relationships come from four ambiguities. We resolve all of them in writing before anyone signs.

Configuration versus customization

Configuration uses capabilities DeepGarden already has, and is included. Customization requires engineering or product work, and goes on a separate statement of work.

Support versus professional services

Support fixes the product when something is broken. It does not cover building new analytics, connectors or customer-specific workflows — that is Managed Intelligence or an SOW.

Included scope, stated explicitly

Every order form names the exact data sources, domains, environments, business units, user population, implementation deliverables, training sessions and support cadence.

Change control

Anything outside that scope needs a written request, an impact estimate, pricing, a timeline and your approval before work starts.

Get a quote that reflects your scope.

Tell us the scope you have in mind and we will come back with a number, and with what we would cut first if it needs to be smaller.

Book a demo