Every MSP says responsive. One in fifty proves it.
The scenario:
Every MSP website says the same four things: responsive, proactive, trusted, tailored. Prospects have read those words on nine sites before yours.
What stops the scroll is a number. Average response time last quarter. Tickets resolved first-touch. Client retention rate. Real figures, dated, updated, with the method shown. Numbers do the work adjectives have stopped doing.
The prompts:
Your AI tool of choice.
STEP 1 - Choose the numbers
You are building a public proof-of-performance page for an MSP.
Context:
Metrics we track today: [response times, resolution rates, retention, satisfaction, uptime]
What our ideal client cares most about: [speed, security, stability, communication]
What we honestly do well: [strengths with rough numbers]
Choose the five metrics to publish: each one a client-outcome measure, honestly strong, and hard for a competitor to fake. For each, define the exact method: what counts, the period, the update frequency. Reject any metric needing a footnote to look good.
-
STEP 2 - Build the page
Write the proof page content: each metric with its figure, the plain-English line explaining what it means for a client, the method note building trust (“measured across all tickets, updated monthly”), and one short client quote per metric where available. Headline the page with the strongest number, not a slogan.
-
STEP 3 - Keep it honest
Build the update routine: the monthly 20-minute refresh, who owns it, the rule for a metric moving the wrong way (publish it anyway, with the note on what we are doing, because a dip explained builds more trust than a graph frozen in a good month), and the reuse plan: the numbers in proposals, review decks, and outreach signatures.