Ten client apps. One honest answer.
You delivered these sites months ago. You are still the person the client calls when something goes wrong with one of them - so you need to know before they do, across all of them, without opening ten dashboards.
Sound familiar?
A site you handed over in March breaks in September and the client assumes it is yours to fix, urgently, for free.
A client’s new enterprise customer sends a sixty-question security form about a site you built in three weeks.
“It is secure” is not a deliverable. Anything you say at handover should come with something the client can read.
The advisory that lands next month affects four of your builds, and nobody is subscribed to anything that would tell you.
A portfolio view, and a report per client.
Every site has its own health, its own history and its own report. The portfolio screen ranks them so the worst one is the one you look at first, and every report exports as a PDF you can send without editing.
- Per-site everything
Health, severity spread, fix-first list, scan history and changes since the last report - kept separate for each client.
- Reports you can hand over
CSV, JSON or PDF. The PDF reads like something you wrote, because it says what was checked and what was found, not just numbers.
- Roles for the people who need them
Owner, admin, member and viewer. A client contact can be given a viewer seat instead of your password.
- An audit trail when asked
Every dismissal, invite, role change and export is written down, exportable, and streamable to a SIEM if a client insists.
- Criticalnorthwind-shop.comNeeds work · 6 open issues
- Lowrankflow.worksHealthy · 1 open issue
- Highclinic-booking.appWatch · 3 open issues
- Lowstudio-portfolio.devHealthy · 0 open issues
- Mediumevents-platform.ioWatch · 2 open issues
How it fits an agency month
- 01Add the sites you still support
Start with the URL of each one. The runtime half needs nothing from the client and gives you a ranking immediately.
- 02Connect the repositories you own
Where you still hold the code, the source, dependency and infrastructure rules turn on and pushes get watched.
- 03Hand the PDF over at the end of the month
Each client gets a report showing what was checked, what was found, and what changed since the last one.
- 04Turn an advisory into an invoice
When something lands that affects four builds, you already know which four - and you contacted them first.
Ten sites, ten people, six thousand credits a window and five scans running at once - sized for a studio that maintains what it builds.
- Ten sites with separate health, history and reports
- Ten team members with real roles
- Five scans at the same time
- Audit log of every sensitive action
Start on Free, which does not expire. Upgrade when it pays for itself.
Start with the client you worry about most.
One free scan, no account. If it comes back clean, that is one fewer thing on your mind this quarter.