011 in 4 customers, on average
Coverage drift
Customers paying for EDR don't have it deployed. Customers without backup are silently exposed. Nobody finds out until renewal — or a breach.
Currently onboarding design partners · 25–300 customer MSPsOne platform.
One platform.
Every agent your MSP needs.
mymsp.io | Control Center is the operations layer your MSP runs from. Multi-tenant. AI-native. Pre-wired into Autotask, Datto RMM, IT Glue, Microsoft, Xero, and the vendor portals you already use. Watching everything, every day — so the gaps, the drift, and the inbox sprawl stop costing you margin.
Already invited? Set up your tenant →
- Customers analysed
- 282
- Coverage gaps surfaced
- 54
- Spreadsheets needed
- 0
from the first production deployment · Phase 1.B
Speaks fluently to your stack
- AutotaskPSA
- Datto RMMRMM
- IT GlueDocs
- Microsoft 365Tenant
- AzureCloud
- XeroAccounting
- MYOBAccounting
- 3CXPhone
- HuntressEDR
- DropsuiteBackup
- Cisco UmbrellaDNS
- SentinelOneEDR
- Pax8Marketplace
- Ingram MicroDistributor
- Dicker DataDistributor
More vendors land every release. The connector pattern is generic — most new EDR, RMM, or backup vendors are a config job, not a rewrite.
Why this exists
Your back office is held together by spreadsheets, junior staff, and luck.
Every MSP we've spoken to has the same three quiet problems. None are on a PSA roadmap, none have a single SaaS tool that solves them, and all silently drain margin until someone notices. mymsp.io | Control Center closes them — automatically, every day, with full audit trails.
025–9% margin leak
License drift
Vendor portals say one number, your PSA says another, your invoice says a third. Reconciliation is monthly, painful, and almost always behind.
0320+ hours / week
Inbox sprawl
support@ takes hours to triage. Supplier invoices vanish into a tech's inbox and get re-keyed by hand. Forwarding chains lose the real customer.
The platform
One platform. Many specialised agents.
Each one does a job a person used to do.
mymsp.io | Control Center isn't a chatbot, a dashboard, or a flow editor you have to learn. It's a runtime for purpose-built agents that already know your stack and ship pre-wired for the work that doesn't fit anywhere else.
mymsp.runtime
v1.0-betacoverage-gap-agentrunning
vendor-license-reconbuilding
support-mailbox-handlerbuilding
accounts-mailbox-handlerbuilding
your-custom-agent—
15
connectors
282
customers
live
status
$ mymsp runs --tail
[ok] coverage-gap-agent · 282 customers analysed · 54 gaps surfaced · 0 errors
[ok] coverage-gap-agent · 282 customers analysed · 54 gaps surfaced · 0 errors
- 01
Pre-wired, not pre-empty
Agents ship knowing your PSA's data model, your RMM's site structure, your accounting system's chart of accounts. No flow-builder learning curve. Connect, review, run.
- 02
Multi-tenant from day one
Every customer is isolated. Per-tenant overrides for vendor mappings, signatures, and rules — surfaced in a review UI, learned over time, never silently overwritten.
- 03
Auditable by default
Every agent action records the data it saw, the decision it made, and the evidence trail — linked to the underlying Langfuse run. Trust is built before authority is delegated.
- 04
Customer identity preserved
Forwarding relays don't collapse the real sender. Tickets, invoices, and replies stay attached to the customer who actually sent them — no exceptions.
The agents
Each agent owns one job — and runs it across every customer, every day.
The first agents we shipped focus on the back-office work that quietly costs the most margin. More are on the way as the platform expands.
- 01Live
Coverage-Gap Agent
Compares every customer's contracted services against what's actually deployed. Surfaces the gaps your team would never have time to find by hand.
- ▸PSA contracts ↔ RMM device telemetry ↔ vendor portal seat counts.
- ▸Flags both directions — under-served (risk) and over-billed (margin).
- ▸Per-tenant overrides for naming, mapping, and edge cases.
282customers analysed54gaps surfaced - 02Building
Vendor-License Reconciliation
Pulls real seat counts from your vendor portals and reconciles against what your PSA thinks you're billing. Drift surfaces, every month, automatically.
- ▸One mapping per vendor — auto-derived, refined in a review UI.
- ▸Catches over-billing (clawback risk) and under-billing (lost revenue) symmetrically.
- ▸Drops clean reconciliation entries into your PSA — no spreadsheet round-trip.
Lives in: Huntress · Dropsuite · Cisco Umbrella · SentinelOne · Microsoft 365 · Pax8 - 03Building
Smart Support Mailbox
support@ stops being a triage queue. Inbound emails are classified, the real customer is resolved through forwarding chains, and tickets land in your PSA against the right contact with the right context.
- ▸Original sender preserved through every forwarding relay — tickets attached to who actually emailed.
- ▸Smart matching against open tickets, recent customer history, and device telemetry.
- ▸Reply drafts in your tone for technicians to review and send — no auto-send to customers.
Lives in: Microsoft 365 · Autotask · IT Glue - 04Building
Smart Invoice Mailbox
accounts@ stops being a re-keying job. Supplier invoices are classified, line items extracted, matched against your active vendor licenses, and pushed as draft bills to your accounting system behind a one-click approval.
- ▸Vendor identified, line items extracted by OCR + LLM — clean entries into Xero or MYOB.
- ▸Cross-checked against vendor-portal active license counts before approval — over-billing surfaces immediately.
- ▸Wholly separate from support@ — invoicing routes to accounts, not your service desk.
Lives in: Microsoft 365 · Xero · MYOB · Autotask
More agents on the roadmap — onboarding, off-boarding, board-pack generation, security-posture review. Tell us which one would change your week.
How it works
Connect your stack. Review the first runs. Hand over the keys.
- STEP 01
Connect
OAuth or API-key into Autotask, Datto RMM, IT Glue, Microsoft 365, Xero, and the vendor portals you actually use. mymsp.io | Control Center auto-derives default mappings from each upstream API — nothing to hand-write.
- STEP 02
Review
Every default mapping surfaces in a review UI before any agent acts. You override edge cases — a renamed site, a custom service line — and the platform learns and persists per tenant.
- STEP 03
Run
Agents run on schedule or on event. Outputs land where your team already works — in the PSA, in your accounting system, in your inbox — with full audit trails behind every action.
Pricing
Priced the way an MSP owner already thinks — per Active Customer, per month.
A small platform fee for the runtime, a per-customer rate that scales with your book, and metered AI usage that keeps the heaviest months honest. No per-tech tax.
You only pay for customers we worked for. Dormant ones are free.
Pioneer
For our first 20 design partners.
$0/mo platform
+ $10 per Active Customer / mo
- ●All agents · all features
- ●Generous AI credit allowance
- ●Permanent rate lock for life of contract
- ●Direct line to engineering
Starter
Up to ~25 customers.
$399/mo platform
+ $20 per Active Customer / mo
- ●Coverage-Gap + License Recon
- ●5,000 AI credits / month
- ●Self-serve onboarding
- ●Community support
Growth
25–100 customers · the sweet spot.
$799/mo platform
+ $15 per Active Customer / mo
- ●Full agent suite
- ●15,000 AI credits / month
- ●Slack Connect support
- ●Guided onboarding
Scale
100–300 customers.
$1,499/mo platform
+ $10 per Active Customer / mo
- ●Custom agent development
- ●50,000 AI credits / month
- ●White-label / co-brand
- ●Priority support · CSM
Roll-ups and 300+ customer estates: enterprise terms, dedicated infrastructure, custom integrations. Talk to us.
What counts as an Active Customer?
You only pay for customers we actually worked for.
A customer is Active in a month if any one of these happened — and Dormant (free) if none did.
- 1
A billable PSA contract was active for them
Any day in the month is enough. If you billed them, we bill you.
- 2
You did ticket work for them
Ticket created, updated, or a note added. One touch is enough.
- 3
Their RMM devices reported in
At least one device check-in, alert, or patch event. Decommissioned devices don't count.
- 4
We handled a backup or security event
Backup job ran, incident managed, or any connected security signal processed.
Tally
We count on the 1st of each month, for the month that just ended.
Live count
Your dashboard shows a running count all month. The invoice is never a surprise.
Auditable
Every Active count on your invoice points to a specific record — contract, ticket, device, or event.
A quick worked example
You have 50 customers in your PSA. 45 have active billable contracts. 3 are project / break-fix customers who had a ticket touch this month. 2 are old prospects with no contract, no tickets, no devices.
→ 48 Active Customers this month. The 2 dormants are free.
Common questions
- What about a customer onboarded on the 28th?
- Active that month. There's no pro-rate — one day with a qualifying trigger is enough.
- What about a customer who churned on the 3rd?
- Active that month (last month of service). Dormant next month, unless any of the four triggers still fires.
- Do internal / $0 contracts count?
- No. Trigger 1 requires at least one billable service line. Internal / non-billable contracts are excluded.
- Does a customer portal login count?
- No. Portal and identity activity are not triggers. Only the four service-work signals above.
- Can I manually exclude a customer (e.g. our own org, charity work)?
- No manual exclude toggle. The definition decides. If a customer shouldn't be counted, archive the company in your PSA or stop syncing their orphan devices — the count reflects reality.
- Does a customer with two triggers count twice?
- No. They count once. The triggers are an OR, not additive.
This is the full definition. The same wording appears in your in-product billing dashboard, on every invoice, and in your tenant agreement — one source of truth, everywhere it matters.
Get on the waitlist
We're onboarding our first design partners now.
If you run a 25–300 customer MSP on Autotask or a similar PSA, we'd like to hear from you. The Pioneer program is capped at 20 partners and locks in early-bird pricing for life.