MSPs are the primary market we built aidizen for. You support 10–50 client tenants, each with helpdesk volume that's mostly repetitive, and each with their own audit-and-compliance posture. aidizen ships a separate, per-client Aid — a first-class citizen in that client's enterprise, with its own identity, audit trail and scope — and gives your techs back the time they spend on license-and-group churn.
Every client tenant gets its own container, secrets, and audit. You can run 50 Aids and each one is its own blast radius. No shared multi-tenant database touching any client's credentials.
Sam at one client, Robin at the next, Alex at a third. Each Aid is a first-class citizen in that client's enterprise — same name conventions, same email domain, same Teams presence as everyone else in the directory.
Every action lands in the client's own M365 audit log. Their compliance team reviews their log, the way they already do. You aren't asked to forward a third-party "AI activity" report.
Aids are free across your entire fleet — 1 client, 50 clients, same price (zero). You can bake the value into your client MRR; we don't take a cut. We earn revenue separately when you bring us project work.
15 minutes at the client + 5 minutes on our side. No portal projects. No client-side install. Your techs can deploy a new Aid in a coffee break.
The Aid handles the well-defined work. Anything genuinely unusual escalates to your team — by design. You stay the relationship; the Aid handles the toil.
A typical MSP tech spends 6–10 minutes on a license/group/password ticket — clarify, switch to the admin portal, do the change, log it. aidizen handles those in 5 seconds. On a typical 200-seat client, that's a few hours a week of high-frequency toil you stop billing your techs against.
200-seat client, typical week
| Request type | Volume | Handled by Sam |
|---|---|---|
| License grants / changes | ~12 | ~100% |
| Group add / remove | ~18 | ~100% |
| Password / MFA resets | ~14 | ~95% |
| Distribution list / shared mailbox | ~6 | ~90% |
| Directory lookups | ~25 | ~100% |
| Novel / unclear | ~5 | Escalate |
Illustrative — real volumes vary. We'll size it against your fleet during the walkthrough.
Rename a client's Aid (Sam → Robin) without breaking history. Audit linkage stays consistent.
App secrets and tokens rotate on a schedule. One operator command, zero client involvement.
Enable/disable tools per client. Some clients want license + group only; some want the full catalog.
One command tears the container down, revokes tokens, and disables the Aid identity. We retain nothing.
peasyCloud regions for data-residency clients. EU container for EU clients, US for US.
MSP-tier support: a real human, a real Slack channel, an SLA that maps to your client SLAs.
30 minutes. We'll size your fleet, walk the onboarding script, and show the audit shape your clients will see.