MSP Documentation Software
Document each client's sites, cloud tenant and apps on one diagram, and keep owners, contracts and vault references behind every system.
Free forever on the Personal plan
Client documentation: an example
One team per client
Each client's diagrams, documents and connections kept apart, with their own engineers.
One structure for all
An organisation template gives every client's documentation the same tabs and sections.
Vault entries, not passwords
Records name the vault entry, so credentials stay in your password manager.
The basics
What is MSP client documentation?
MSP client documentation is the record a managed service provider keeps for each client: sites and networks, cloud tenants, applications and their suppliers, devices, contracts, contacts and the procedures for when things fail. It is what lets any engineer pick up any client's ticket.
Good IT documentation shortens tickets, cuts escalations and makes onboarding new engineers quicker. Poor documentation shows up as repeat questions, guessed passwords and a single engineer who knows how a client works.
In Blueprintr each client's estate is a diagram, and every system on it opens a stratum with its owner, contract, renewal date, vault entry and failure notes, so engineers start from the picture and click for the detail.
Why Blueprintr
Documentation every engineer can work from
One picture per client, with the record behind each system.
A team for each client
On the Team plan, give each client a team with its own engineers and blueprints. Cloud connections and integrations belong to the team, so one client's access never reaches another's work.
Sites, tenants and apps
Draw offices, firewalls, Microsoft 365 and business apps with network, Azure, Entra and Microsoft 365 icons, or your own SVGs.
VellumThe record behind each system
Give every tile a stratum with its owner, contract, renewal date, vault entry and what to do when it fails.
StratumDiscovery inside the client
On Enterprise, Continuum Local runs an agent in the client's network, connects out over HTTPS and draws what its SNMP sweeps find. On Team, Continuum Cloud draws their AWS and Azure.
ContinuumThe same structure every time
Save a finished client blueprint as an organisation template, so the next client starts with the same tabs, sections and records.
Readable by the client too
Share a client's documentation privately with their own staff, so the people who pay for it can read it.
Blueprints
How to
How to document a client in Blueprintr
Set up the client
Create a team for the client, or a portfolio if you work alone, and add each engineer who supports them.
Draw the estate
Add the sites, cloud tenant, business apps and the services you run, grouped as the client is organised.
Add the records
Right-click each system and add a stratum with its owner, contract, renewal date and vault entry.
Make it a template
Save the blueprint as an organisation template so every new client starts the same way.
Keep it current
Update the record as part of each change ticket, then publish so the team sees the new version.
FAQ
Questions about client documentation
Can an MSP use Blueprintr for free?
You can document clients on the free Personal plan with portfolios, diagrams and strata. A team per client, roles, approval workflows, audit logs and Continuum Cloud are part of the Team plan, priced per seat.
How do I keep each client's documentation separate?
Give each client a team. Its blueprints, cloud connections and integrations belong to that team, and only its members can open private content, so engineers see the clients they support.
Should I store client passwords in the documentation?
No. Keep credentials in your password manager and record the vault entry name in the stratum. Anyone who opens the documentation then knows where to look, without the secret being copied around.
Can Blueprintr discover a client's network?
On Enterprise, Continuum Local sweeps the address ranges you allow over SNMP from an agent inside the client's network and draws the result. It connects out on port 443, so no inbound firewall rule is needed.
Can I import the documentation a client already has?
Yes, in part. draw.io files import on every plan. Word, PowerPoint, PDF and Markdown documents can be converted into blueprints with AI on the Team plan, up to 10 documents per import.
Can clients read their own documentation?
Yes. Share a private blueprint with named people at the client, or send an unlisted link, with a password on Premium and above.