Onboarding
What must be collected, configured, tested, and proven before a client is called managed.
Small MSP operating guides
SmallMSP helps solo and small-team MSPs decide what to define, document, verify, and charge for before the stack or the vendor pitch takes over.

Use these cornerstone guides to define the client, the security promise, and the price before expanding the stack.
Turn a new client from unknown environment into documented, monitored, supported account with clear decisions and exceptions.
Define the controls, evidence, and client boundaries a small MSP can actually operate each month.
Build a minimum viable price around responsibility, labor, tools, review work, risk buffer, discount boundaries, and the technician time your team must protect.
SmallMSP
What must be collected, configured, tested, and proven before a client is called managed.
How work enters the queue, who owns the next action, and when informal support breaks down.
Which minimum controls should be real before security becomes a sales promise.
Turn a signed agreement into access, backups, monitoring, documentation, and proof.
Keep tickets, alerts, callbacks, and owner memory from becoming the operating system.
Compare tools by support load, reporting, billing minimums, and weekly operation.
Define minimum controls that can be checked, reported, and maintained.
Protect margin by separating included service from project work and exceptions.
Use AI and automation where they reduce repetition without hiding accountability.
Handle a security finding during MSP transition without destroying evidence, guessing at blame, or contacting the previous provider without a clear client-approved purpose.
Evaluate a PSA by whether a real ticket reaches the right owner, complete time records, a correct invoice, and usable profitability evidence without hidden manual work.
Quote fixed-fee MSP projects from a defined outcome, an internal sell rate, realistic effort, direct costs, and a risk reserve—then keep recurring responsibility in a separate monthly agreement.
SmallMSP is meant to stay practical: fewer rankings, fewer generic checklists, and more operating judgment that small teams can actually use.