Human task
Lands in a technician’s inbox with instructions, context and the evidence it needs to be marked done.
“Image and ship laptop”
Process automation for managed service providers
APMP reads the procedures your team already wrote and turns them into governed workflows — run by your technicians, AI agents and the PSA, RMM and documentation tools you already use.
AI proposes. Your people approve. Nothing runs until you publish it.
Illustrative example
How it works
Extraction runs in the background, and you’re told when the draft is ready. You stay in control of every step it proposes.
Upload a PDF or Word file, paste text, pull it from your documentation system, or describe the process in plain language.
Each step gets a proposed type — human, agent, system or approval — with the source line it came from.
Reorder, rename, delete, or change a step’s type. Steps the AI wasn’t sure about are flagged so you check those first.
Finish the flow in the designer, publish a version, and launch it by hand, on a schedule, or from a ticket or alert.
One process, four kinds of work
Mix people, AI agents and system actions in a single workflow. Every step type looks the same everywhere — in the designer, the run timeline and the technician inbox.
Lands in a technician’s inbox with instructions, context and the evidence it needs to be marked done.
“Image and ship laptop”
Handed to an AI agent that works in the background and reports back, so the run picks up where it left off.
“Assign licences by role”
A direct action in your PSA, RMM or documentation system — no copy-paste between tabs.
“Create user account”
Pauses for sign-off from your team or the client. Clients approve from a secure link — no account needed.
“Manager approves finance access”
Governance
Automation you can’t account for isn’t something you can sell to clients. Every run leaves a record you can show them.
Steps can require evidence before they complete — a screenshot, an asset tag, a command result — kept with the run.
Chain approvers across your team and the client. Each approver has their own escalation clock, and never sees the others’ decisions.
Every process has a version history you can branch from. Runs already in flight finish on the version they started on.
Restart a failed run or resume from the failure. Steps that can’t be safely skipped are called out by name before anything re-executes.
Integrations
Three separate connections, each built for its own kind of tool. A ticket and an alert can both start a process, with equal standing.
Start processes from tickets, update them as steps complete, and link every run back to the ticket it serves.
Trigger remediation from an alert and run actions on managed devices, with the device shown alongside the run.
Import SOPs straight from where they live, so the process and its source document stay connected.
Gets better as it runs
APMP watches how processes actually run and suggests improvements. It never changes a published process on its own.
Security & tenancy
Built from the ground up for the MSP-to-client model, with isolation you can explain to a client’s security team.
Every process, run and record belongs to an MSP and a client. Tenant boundaries are enforced before any permission check.
Shared by default, with an opt-in dedicated database for clients whose contracts call for it.
Single sign-on and multi-factor authentication for your staff, fine-grained roles built from permissions, and a full audit trail.
Tell us about your team and the procedure you’d start with, and we’ll set up your first workflow together.
Prefer email? Write to contact@apmp.app