Best first use case
The team that already depends on folders for client, project, matter, or deal chronology.
Deployment
Roll MailLedger out across Microsoft 365 with less guesswork.
This page is for admins, billing owners, and team leads who need a clean path from first evaluation to controlled Outlook rollout.
Billing path
Keep self-serve for one mailbox or centralize billing once the workflow is proven.
Adoption
MailLedger stays inside Outlook, so people learn it in the workflow they already use.
Rollout shape
Start small, prove value fast, expand with control.
The clean rollout path is not a giant migration. It is one working Outlook record flow, then one team, then the next.
Pick the first mailbox group
Start with one team, shared mailbox cluster, or handoff-heavy workflow instead of trying to prove the whole tenant at once.
Confirm billing ownership
Decide whether MailLedger stays self-serve per mailbox or moves under one billing-owner path before rollout expands.
Pre-answer IT questions
Security, permissions, and Outlook compatibility should be settled before users are asked to adopt anything.
Launch on real folders
The first success case should use the client, project, matter, or deal folders people already trust today.
Admin checklist
What to line up before the rollout call.
- Choose the first team or workflow MailLedger should cover.
- Confirm who owns Microsoft 365 add-in deployment.
- Confirm who owns billing and renewals.
- Pick the first folder structure that has to work on day one.
- Share pricing, security, and rollout pages before the first deployment call.
Use this with
Pricing, security, and rollout.
Contact rollout
Tell us how you want MailLedger deployed.
Share the basics below and the rollout request will be emailed directly to Antonio for follow-up.