Pilot Cohort Forming
MSP Operators
Your clients expect structured project delivery. Your PSA doesn't run projects. Now something does.
ConnectWise, Autotask, and Halo run tickets. Certio Stack is the MSP project management layer your PSA wasn't built for: high-stakes delivery work, with the evidence trail clients now expect.
// Free during the pilot. Direct line to the team building this. Priority on what ships next. Founding cohort only.
or check the cohort fit criteria ↓Current focus: M365 tenant migrations + consolidations. Intune, server, and network migrations on the roadmap.
Product concept · illustrative data
Tenant-to-tenant migration
Stage: Approve
Risk: Elevated
1
Discover
2
Plan
3
Approve
4
Execute
5
Verify
Approval required
2m ago · awaiting J. Mendez
Cutover wave 2: proceed to MX swap
Decision rationale: Mailbox sync validated (318 / 318), VIP exclusions confirmed (12), rollback window open until 03:30 UTC. DNS pre-stage signed off by infra lead.
Approve cutover
Hold
View checks
Evidence attached
3 / 3 captured
Pre-check report
DNS readiness
Pilot validation
Discovery complete
Plan reviewed
Approval required
Evidence captured
02 · The PSA gap
The work your PSA can't even start.
PSAs run service desks: tickets, time, contracts, billing. MSP project delivery needs a different shape, and the first thing to break is discovery: ad-hoc, unstructured, and impossible to inherit.
// exhibit a · discovery
The black hole between sales and execution.
screenshots/, script-output.txt, "ask Mike", notes-from-call-final-v3.docx
Certio runs discovery as structured, read-only collection: environment-aware, output-structured, landing a baseline snapshot with receipts the next engineer (or the next gate) can actually use. The operator-approved script library, where the collector proposes adaptations per environment, is the model the platform is building toward.
Built to recover hours of manual scoping per project, and to give every project a better starting point.
// dim · decisions
From notes to gates
status fields, free-text comments → approval gates with named owner + rationale
// dim · proof
From timestamps to receipts
time entries, ticket timestamps → evidence requirements attached to each stage
03 · Operating model
From discovery to done, with receipts.
Five stages. Each one produces the artifact the next stage actually needs, not a status field, not a Slack thread.
01 / Discover
Discover
Structured, read-only discovery lands a baseline snapshot with receipts: what was collected, when, and what is still unknown. Replaces screenshots and "ask Mike." The operator-approved script library with proposed next steps is the roadmap.
tenant intake · constraints captured
02 / Plan
Plan
Sequenced waves, cutover windows, rollback notes: generated, then reviewed. An hours estimate with confidence bands built from discovery data, not gut feel. The handoff isn't a spreadsheet.
waves · windows · rollback
03 / Approve
Approve
Named owner. Decision rationale. Timestamped record. Before the irreversible button gets clicked.
human gate required
04 / Execute
Execute
Execution stays with your team and your tooling. Certio's job is the cleared-to-go record: a verified plan, a named approval, and rollback criteria before anything irreversible runs.
your team executes · out of band
05 / Verify
Verify
Validation tied to the plan: what must be true after cutover, captured as evidence requirements at close. After-snapshot capture against baseline is planned. The "can you send proof?" email never has to happen.
client receipt ready
system outputs
hours estimate with confidence bands
runbook + unknowns list
client-ready evidence requirements
psa integration · planned
change tickets in ConnectWise, Autotask, Halo
engineer tasks delegated
project state mirrored
04 · Where it costs you
The four places it costs you, every quarter.
Not abstractions. Real hours, real escalations, real accounts at risk. These are the failures Certio is built to remove.
C / 01
The re-collection tax
Each new project starts from zero because the last one's discovery lives in someone else's screenshots. Days of work, repeated.
C / 02
Heroics tax
Every project depends on the one engineer who remembers how the last one went. They leave, the runbook leaves with them.
C / 03
Escalations during cutover
Mistakes surface live in front of executives and VIPs. The next QBR is no longer about value; it's about what went wrong.
C / 04
Closeouts that won't close
"Can you send proof?" emails. Rebuilt evidence packets. Contested final invoices that drag past 60 days.
05 · What it handles
Tools compute. LLMs judge. Humans approve.
Built for operator reality, not demo theater. Automation where it earns its place, humans where it matters. Fast is good. Fast + governed is better.
H / 01
Cutovers that don't slip
Sequenced waves, dependency awareness, named rollback windows. The cutover plan is a plan, not a wish.
H / 02
Automation with brakes
Your tools execute; people approve consequential moves first. The irreversible button never gets clicked without a name next to it.
H / 03
Receipts the client actually reads
Pre-checks, validations, decisions, evidence requirements: captured as one structured record. Branded, exportable closeout packets are planned.
H / 04
Runbooks that survive turnover
Standardized discovery, plan, approval, verify: same shape every project. Senior departures don't take the institutional memory with them.
Apply to the founding MSP cohort
Free during the pilot. Direct line to the team building this. Priority on what ships next. Founding cohort only.
06 · Operational assets
High-intent checklists MSP teams actually search for.
Practical migration guides for planning scope, controlling risk, and defending delivery decisions. Free for the founding cohort.
Microsoft 365 tenant-to-tenant migration checklist
Scope, sequencing, approvals, and validation checkpoints for cross-tenant moves, including pilot wave design, MX cutover guardrails, and post-cutover verification.
Updated 2026-05-07Open guide
Cross-tenant mailbox migration guide
Mailbox-specific planning, coexistence guardrails, and post-cutover validation priorities.
Updated 2026-05-07Open guide
Google Workspace to Microsoft 365 migration checklist
A structured plan for mail, calendar, contacts, and drive migration readiness.
Updated 2026-05-07Open guide
M365 tenant consolidation playbook
Phased consolidation strategy for M&A and multi-tenant operating simplification.
Updated 2026-05-07Open guide
MSP project governance checklist
Approval gates, rationale capture, and evidence trails for delivery trust.
Updated 2026-05-07Open guide
Post-migration validation playbook
Baseline + after-snapshot capture, validation tests, and the closeout evidence packet your client can read.
New 2026-05-07Open guide
Intune migration playbook
From device enrollment to compliance continuity. Founding cohort gets access first.
In developmentPreview
Server & network migration playbook
From server inventory to network cutover, with receipts. Founding cohort gets access first.
In developmentPreview
07 · Founding cohort fit
Who the founding cohort is for.
A small founding cohort. We're optimizing for operators who'll shape the platform, not just consume it.
F / 01
You run real migrations
3+ M365 tenant migrations or consolidations a quarter. Discovery, sequencing, and cutover risk are everyday problems, not edge cases.
F / 02
You answer to a client when it goes wrong
The escalation lands on your desk. Your service leaders need plans and decisions they can defend in front of execs.
F / 03
You're done being held together by heroics
One senior engineer holds the runbook in their head. You want a repeatable operating system before they take a vacation.
F / 04
You'll trade speed for governance, once
You want pace, but not the kind that costs you the account. You're ready to put approval gates in the cutover path.
08 · Honest qualification
Who this is not for.
Said up front to save us both time. If you see yourself in this list, Certio isn't the right tool for your team today.
- Teams shopping for another generic task tracker, Notion replacement, or spreadsheet upgrade.
- Organizations that want fully autonomous, no-human-gate execution.
- Service work that fits inside a single ticket. Certio is for projects, not tickets.
- Anyone shopping for a PSA replacement. Certio runs the project layer on top of your PSA, with PSA integrations planned, not a replacement.
09 · Operator reality check
Tickets aren't projects. Approvals aren't comments. Receipts aren't invoices.
Three categories your PSA was never going to be. Certio Stack is the project layer on top, built for the migrations, consolidations, and cutovers your clients actually escalate.
10 · FAQ
Common questions from MSP operators evaluating migration delivery platforms.
If your question isn't here, ask in the intake form below. Operator questions shape the cohort.
01 What is Microsoft 365 tenant-to-tenant migration?
Microsoft 365 tenant-to-tenant migration is the process of moving users, mailboxes, files, and collaboration workloads between separate Microsoft 365 tenants. Common triggers: mergers, acquisitions, divestitures, or consolidating subsidiary tenants into a parent. The work spans identity, mail, files, Teams, and policy, and the riskiest part is rarely the data move itself; it's the cutover sequencing and the receipts you owe the client when it's done.
02 How is cross-tenant mailbox migration different from full tenant migration?
Cross-tenant mailbox migration moves Exchange Online mail data and mailbox objects only. A full tenant migration also covers OneDrive, SharePoint, Teams, Intune-managed devices, identity (Entra ID), security policies, and shared configuration. Mailbox-only is faster and lower-risk; full tenant requires sequencing, dependency mapping, and an approval gate at every irreversible step. Both produce evidence trails the client expects to see at closeout.
03 How do MSP teams reduce risk in Google Workspace to Microsoft 365 migrations?
Top teams reduce GW→M365 migration risk with five practices: structured discovery (not screenshots), pilot waves with named exit criteria, explicit approval gates at each cutover, staged DNS/MX changes with rollback windows, and post-migration validation tied to user-impact outcomes, not just object counts. The shape is the same as any high-stakes migration: discover, plan, approve, execute, verify.
04 Why does governed delivery matter for migration projects?
Governed delivery answers the three questions every escalated cutover surfaces: who approved this, what's the rationale, and where is the evidence. PSAs answer 'who worked the ticket'; the project layer on top (Certio Stack and tools like it) answers 'who decided the cutover and why,' so service leaders can defend the call in front of execs and clients can read the receipts after.
05 How is Certio Stack different from ConnectWise, Autotask, or Halo PSA?
Certio Stack is the MSP project management layer that runs on top of ConnectWise, Autotask, or HaloPSA, not an alternative to them. PSAs run the service desk (tickets, time, contracts, billing). Certio runs the project layer (discovery, planning, approval gates, evidence, client receipts). The two are designed to work together: planned integrations with ConnectWise, Autotask, and HaloPSA will push change-management tickets, delegate engineer tasks, and mirror project state. You don't pick one or the other.
06 Does Certio Stack replace my PSA?
No. Certio Stack runs the project layer on top of your PSA: discovery, planning, approvals, evidence. Planned integrations with ConnectWise, Autotask, and HaloPSA will push change-management tickets, delegate engineer tasks, and mirror project state where your team already works. Your PSA keeps doing what it does best (tickets, time, billing). Certio runs the work on top.
07 Is Certio Stack project management software for MSPs?
Yes, but more specifically, it's the project management software for MSP delivery work that doesn't fit inside a service ticket: tenant migrations, consolidations, and other high-stakes client-facing projects. Generic PM tools (monday.com, ClickUp, Asana) treat every project the same. Certio is purpose-built for the shape of MSP project delivery, with structured discovery, approval gates with rationale, evidence trails, and planned integrations with the PSAs your team already uses.
08 What does the Certio Discovery actually do, and what does it run on?
Today, discovery is a structured, read-only collection from Microsoft Graph (usage reports, organization profile, domains, groups, Teams structure) plus Exchange Online configuration. It never changes the environment, and where evidence is sampled or incomplete the output says so instead of guessing. The result is a baseline snapshot that feeds the project plan and the hours estimate with confidence bands. The broader operator-approved script library, where the collector proposes next steps and adaptations per environment, is the designed model the platform is building toward.
09 How much control do operators have over the Certio Discovery, can it go rogue?
No. Discovery is read-only by design, and that boundary is enforced by the product's own test suite: the collection layer cannot execute changes against your environment. The operating model puts a human approval gate at every consequential step: the system suggests, the operator decides, and the record shows who approved what, when, and why. “Tools compute. LLMs judge. Humans approve.” is the design principle the platform is built around.
10 Can I use Certio Stack for projects beyond M365 migrations?
Yes, over time. The MVP focuses on M365 tenant migrations and consolidations because that's where the discovery, approval, and evidence requirements are densest. Intune migration, server migration, and network migration are next on the roadmap. Founding cohort members get priority access to each new workload as it ships.
11 What's included in the founding MSP cohort, and what does it cost?
Free during the pilot. Founding cohort members receive six things beyond the product: white-glove first Discovery, co-pilot on the first project, direct line to the team building Certio, priority on the Intune/server/network roadmap, and first access to white-label client receipts and partner referral terms, both planned for GA with details published before launch. Small founding cohort, applications reviewed in order received.
Apply to the founding MSP cohort
Free during the pilot. Direct line to the team building this. Priority on what ships next. Founding cohort only.
11 · Pilot intake
Tell us about your next project.
2-minute intake. If there's strong fit, we'll schedule a focused operator call. No generic sales sequence.
// what founding members receive
Six things, beyond the product.
- Free during the pilot. No price tag while we're building together.
- White-glove first Discovery. Read-only discovery run on a real client tenant with you.
- Co-pilot on your first project. Runbook, gates, and evidence, alongside your team.
- Direct line to the team building this. Slack/email for product feedback, escalations, roadmap.
- Priority on Intune, server, and network. Founders get next-workload access first.
- White-label receipts & referral economics. Branded client packets, partner upside at GA.
Small founding cohort · applications reviewed in order received