Start with a focused project pack for one real migration plan. Broader subscriptions and usage credits should come after repeat value is proven.
Recommended next
Best first package for validating AssurePlan with one real migration project.
After pilot
For teams that need repeat reviews across multiple active migration plans.
Custom
For governed programs that need security review, procurement, and onboarding.
Keep the public page conservative while the product is still validating paid demand. The first commercial offer should be a project pack, with credits used only as a secondary usage guardrail.
| Decision | Pilot Pack | Team | Enterprise |
|---|---|---|---|
| Primary value metric | One governed migration project | Repeat assurance work | Program-level rollout |
| Best fit | First paid validation | Multiple PMs or repeat scans | Security and procurement-led adoption |
| Billing stance | Package price to validate willingness to pay | Subscription plus usage allowance | Custom contract |
| What to avoid now | Tiny credit packs as the main offer | Unlimited AI usage | Complex procurement before product proof |
Use it for cutover readiness, dependency review, business validation, rollback evidence, and steering committee preparation.
Project Assurance Workspace
Evidence-backed plans, reports, and assurance actions.