Starter Content

A library of opinionated defaults for a typical MSP. Add whichever packs are useful - on a brand new install or on one that has been running for years.

Nothing here is overwritten or deleted. Anything already present under the same name is skipped, so a pack can be added again later to pick up entries you removed by mistake, and adding twice never produces duplicates. Everything added is editable and deletable afterwards like any other record.

$pack_details) { $pack_status = $starter_content_status[$pack]; ?>
Content In library Already here Will be added


Add first, or these come in without them.
Nothing to add

Ticket templates bring their task lists with them. Products are filed under income categories and priced as starting points only - hardware and resold licensing come in at zero because they are quoted per deal.

Demo Data

A fictional book of business for demos, training and screenshots - clients with the people, equipment, documentation, tickets and billing a typical MSP would be carrying for them, plus the bank accounts, operating costs and transfers on your own side of the books. It is generated across the last two years and dated relative to today, so the dashboard, ticket queue, aging, profit and loss and every other report have real history behind them rather than a single flat month.

This is sample data, not configuration. Every demo client carries the Demo Data client tag and everything created hangs off one of them, so removing it takes the whole lot back out again. Contacts use addresses on the reserved .example domain, which cannot receive mail, and the demo agreements are created with email notification switched off.

This install already has client(s) of its own. Demo data is meant for a demo or training install - it will sit alongside your real clients in every list, report and total until it is removed.

Add the Categories and Tags packs above first, or the demo tickets, invoices and tags come in bare.

demo client(s) are here: