Pilot
One department, one workflow
Prove the return on a single workflow before you commit to a rollout. Baseline, in-flow guidance, and an ROI readout you can take into a budget conversation.
Pilot
One workflow in scope, in a single department
Baseline measured before guidance is switched on
In-flow guidance: the approved tool and proven prompts at the moment of work
ROI reported on adoption and task-level change
Workflow context only, never content. PII redaction on by default
Security packet for your review team
Email support
Team
Several departments, multiple workflows
Expand past the pilot workflow with the baseline carried forward, and add the spend controls that keep the AI portfolio accountable.
Everything in Pilot, plus:
Multiple workflows across several departments
ROI reported on adoption, task-level change, and quality
Spend control centre: tiers and limits set by team
SSO, plus a shared success plan
Enterprise
Company-wide, unlimited workflows
Full governance across every AI tool in the building, with the controls and review support procurement will ask for.
Everything in Team, plus:
Unlimited workflows, deployed company-wide
All four ROI layers: adoption, task, quality, business impact
PII redaction controls and policy guardrails you configure
Full security review support, a named manager, and an SLA
How pricing works
The price follows scope
Four things move the number: seats receiving guidance, connected AI tools, workflows in scope, and your deployment and security requirements.
Most pilots are instrumented in weeks, not quarters, starting on one workflow with a clean baseline.
After the pilot you expand to more workflows and departments with the baseline carried forward, so the before-and-after stays defensible.
What a pilot includes →
Pricing FAQ
Why isn’t pricing published?
What does a pilot include?
How fast is time to value?
What happens after the pilot?
Who counts as a seat?
What data does Modo need?
Do you offer a self-serve trial?
Can we see a security packet before we start?