One screen for all your clients. One report for each.
Probecast watches the stores, sites and apps you run for clients — and every provider underneath them. When something breaks, you know which clients it touches before they call. Every month, each client gets an independent report under your brand — drafted for you, in their language.
Founding agencies: 10 places · Independently measured · Your brand, not ours
Twenty clients. Five tools. The full picture in one person's head.
An uptime monitor pings the sites. A spreadsheet tracks who has access to what. A doc template becomes the monthly report, rebuilt by hand, client by client. Alerts land in a shared channel nobody owns. It works until a client calls about an outage your team never saw — or asks you to prove what the retainer paid for.
Your agency is only as good as the last thing you missed.
The client finds out first.
The alert went to a channel nobody was watching. The first person to notice was the client's customer.
The report eats a week.
Twenty clients, five tools, copy-paste into slides. Every month, by the people you'd rather have building.
Your word against theirs.
The client says the site was down all weekend. Your monitor says it wasn't. Neither of you has a record the other trusts.
Nobody knows who changed what.
A monitor muted on a Friday. An alert rerouted. A contractor who still has access six months later.
Watch. Prove. Control.
Three jobs your agency does every month, on one screen.
Before they call.
Cross-client impact
One provider breaks. You know every client it touches.
When a shared provider degrades — a payment gateway, a host, an email API — Probecast lists it once, with every client that depends on it, ordered by how many it hits. Message them before they call you.
All healthy? One calm sentence, not a grid of zeros.
Incidents with context
When something breaks, the right person knows — with the client's name on it.
A monitor has to fail twice in a row before it's an incident, so nobody gets paged at 3 a.m. for a blip. The alert names the client, the dependency and the region and reaches your team on email, Slack, web push or a webhook.
SLA & error budget
The SLA you signed, tracked.
Set the target you promised each client. Probecast tracks it through the month and shows how much error budget is left — and warns you while there's still budget to protect, not after it's gone.
Don't ask clients to take your word for it.
An agency reporting on its own work is marking its own homework. Probecast is the third party in the room: it measures every client's stores, sites and apps from outside, around the clock — the monthly report is built from that record — not from anyone's spreadsheet. Your team adds the context. Nobody edits the numbers.
01
Measured from outside.
Checks run from multiple regions, independent of your servers and your client's. An incident only counts after two consecutive failures — no blip inflated, none hidden.
02
Nothing changes quietly.
A paused monitor, a maintenance window, a muted alert: every change lands in an append-only log, with a name and a time.
03
Frozen once finalised.
A finalised report can't be rewritten. Send the private link and your client reads it straight from the record — not from a file someone could edit.
Your brand on the cover. Independent measurement underneath.
The report that renews the retainer.
One page per client, per month: availability and SLA, every incident, traffic and revenue against last month and the support your team delivered. A short paragraph explains the month for a business owner, not an engineer — and your account manager can sign it off with a note in their own words.
Automatic when you want it. Personal when it matters.
Drafted on the 1st.
When the month closes, every client's report is ready: data pulled, support counted, the month written up.
Yours to shape — or not.
Send it as it is or adjust it first: template, sections, language and a note from the account manager.
Out the door.
PDF, a private link under your brand or straight to the client's inbox. Archived and frozen.
Monthly client report · September
Fashion Store
The month in words
September was steady. The store was reachable all but 29 minutes and that single window appears to have originated with your payment provider rather than the site itself. Traffic grew 12% and the spring campaign brought most of it.
Availability · day by day
Availability
99.97%SLA target 99.9%Traffic & revenue
48,200visitors · +12% · €23.4kSupport
34 tickets91% resolved · by priorityAccount manager's note
“We moved the checkout to the new gateway on the 22nd, so next month should read cleaner. I'd like 20 minutes to talk about the shipping API before Black Friday.”
ANA · YOUR AGENCY
Your brand, not ours.
Your name and logo on the document, the link and the email. Replies come to you.
In your client's language.
English, German, French, Spanish, Dutch or Brazilian Portuguese — numbers, dates and currency formatted to match.
Shaped per client.
Executive, Detailed or Minimal. A store gets revenue and support; a brochure site gets uptime and incidents.
An archive that stays true.
A finalised report is frozen. What you sent in March still says what March said.
If revenue isn't connected, the report says so. It never shows a zero that looks like a collapse.
PDF · A private link under your brand · Straight to the client's inbox
Time back
The monthly report shouldn't cost your team a week.
Uptime from one tool, tickets from another, revenue from a third. Screenshot, paste, format, check, send — then start again for the next client. Across a client list, that's days of skilled people every month spent copying numbers.
Probecast drafts every report on the 1st, so those days go back to work clients actually pay for: shipping fixes, improving their sites and the conversation that grows the account.
Your numbers
After about 10 minutes of review per report. Your estimate — change the numbers.
Uptime is half the retainer. The other half lives in your helpdesk.
Most care plans sell two things: a site that stays up and a team that answers. Probecast reads both. Connect HelpScout, Zendesk, Gorgias or Freshdesk — read-only — and each client's report shows the work behind the retainer: tickets handled by priority, the share resolved and, where the tool provides it, the average first response.
Counts and timings only — never a subject, a message or a customer's name. A test in our pipeline makes sure of it.
Your team, without handing over the keys.
Everyone sees their clients. Nobody sees more.
Invite your team, freelancers and contractors. Scope each person to the clients they work on, decide who sees revenue and keep anyone read-only who only needs to look. Credentials, integrations and alert rules stay with the owner.
Scoped means scoped: reports, archives and impact counts all shrink to that person's clients.
Who changed what and when. On the record.
Every change is logged with the person who made it and the time. Filter by person, client, type or period; export it as CSV. Nobody can edit it — the database itself refuses. When an alert didn't fire, you'll know in a minute whether it was the stack or the settings.
Your client's store runs on someone else's APIs. The call still comes to you.
Payments, shipping, email, hosting. The failures that hurt aren't the loud outages: a provider slows down without going down, a webhook stops delivering, a nightly sync dies without a sound. The status looks green while the business leaks — and when the client notices, it's your agency they call.
That's why Probecast monitors the whole chain, not just the homepage: the site, the store, the public providers underneath it and the internal APIs only your team knows exist. Each dependency is mapped to the clients that rely on it — so when one link slows down, you see a list of affected clients, not a mystery.
Websites & stores
Every site, checked from outside.
Uptime and latency for each client site, measured from multiple regions every 5 minutes. Shopify & WooCommerce connect read-only — and we test the key, refusing anything that could write.
Public providers
A catalog of 1,000+ APIs, already monitored.
Payments, shipping, email, hosting, AI. Pick the providers each client depends on; Probecast is already watching them around the clock.
Your own APIs
Internal endpoints, same treatment.
The client's backend, an internal service, a staging API nobody else sees. Add any endpoint as a custom monitor and it joins that client's dependency map like any public provider.
Heartbeats
The jobs that fail in silence.
The cron, the backup, the stock sync. The day the ping doesn't come, you know.
Synthetic flows
A real browser, walking the checkout.
Scripted flows run in a real browser — login, add to cart, pay. When the flow breaks, you get the step and the screenshot.
Stack Pulse
The providers, from the inside.
Read-only connections to the services your clients run on — real errors, usage and spend, not just a ping at the front door.
The report is fed by the tools you already use — read-only, always.
Your clients will ask. You'll have the answers.
EU data, a DPA you can pass on.
Data processed in the EU and a public DPA covering EU and UK GDPR, with every sub-processor named.
Read-only, checked — not promised.
Payments, stores, helpdesks: read-only access everywhere it matters, tested when you connect. From support tickets, counts only — no content, no customer names.
Analytics your clients' lawyers won't mind.
The Probecast pixel is cookieless and first-party, on your client's own domain. If Google Analytics has become a conversation you'd rather not have in Germany or France, this one is easy.
For twenty years, I was the one who explained the month to clients.
Before Probecast, I managed projects and service delivery in enterprise consulting and telecom — Accenture, Ericsson, Celfocus — across different markets, clients and technologies. More times than I can count, I sat in the monthly review in front of SLAs and executives who wanted the number, not the story. And when something broke, the call often found me. I learned that a review goes well when the numbers come from somewhere both sides trust.
Probecast is the tool I wanted on those mornings: every client on one screen, the cause before the call and a monthly record both sides can trust — drafted before anyone has to ask for it. I built it running my own products first. Now it's built for teams who answer for other people's sites.
“If something doesn't fit the way your agency works, tell me. I read every message.”
In their words.
Public posts, nothing commissioned. Every quote links to the original.
“When a service degrades, putting the spotlight on the actual business impacts is where the real value lies.”
“It brings APIs, sites and other services together in a single dashboard, so you spot any instability quickly — before it reaches your users.”
Be one of the first ten agencies.
I'm onboarding the first agencies one to one. Try Probecast free for 30 days with up to three of your clients. If it earns its place, you get a founding price agreed with you and locked for as long as you stay.
What you get
- 30 days free with up to three clients
- Onboarding with me, one to one
- Every client on one screen, with cross-client impact
- Independent monthly reports under your brand
- SLA & error budget per client
- A founding price, locked while you stay
No credit card. No commitment until the pilot ends.
Honest feedback.
Fifteen minutes at the start and fifteen at the end of the pilot: what worked, what didn't, what your clients said. And, only if it works for you, your logo on this page.
Questions agencies ask.
How does the founding pilot work?
We talk for 15 minutes, set up up to three of your clients together and run it for 30 days, free. At the end we look at it together. If it's worth paying for, we agree a founding price that stays locked while you stay. If not, you walk away — no card, no contract.
Will my clients see the Probecast name?
Only where it works for you. The report, the private link and the email carry your agency’s name and logo. A small "Independently measured by Probecast" line tells your client the numbers come from a third party — keep it on or switch it off.
Can anyone on my team change the numbers in a report?
No. Your team chooses the template, the sections and the language and writes the notes. The numbers come from the measurement record and a finalised report is frozen.
Do I have to review every report?
No. Every report is drafted on the 1st. Send it as it is or adjust it first — your call, client by client.
Which helpdesks do you connect to?
HelpScout, Zendesk, Gorgias and Freshdesk, all read-only. Each client is mapped by mailbox or by tag, so one helpdesk can serve all your clients.
What if a client doesn't use Stripe or Shopify?
The report shows what's connected and says plainly what isn't — never a zero. A brochure site can use the Minimal template: uptime, incidents and your notes.
Can freelancers get access without seeing everything?
Yes. Scope each person to specific clients, keep revenue as a separate permission and make anyone read-only.
Can Probecast change anything in my clients' accounts?
No. Every integration is read-only; for Shopify and WooCommerce we test the key and refuse one that could write.
Do you read my clients' support tickets?
No. We store counts and timings only — never a subject, a message or a customer's name.
Where is the data stored?
In the EU. Our DPA covers EU and UK GDPR and names every sub-processor.
Not running client sites?
Let your clients hear it from you first.
Your team gets the alert — and its week back. Each client gets a record it can trust.