Showing the Work Without Showing Anyone's Data
The most convincing proof of a website's value is often the admin behind it: the requests, orders and schedules a business runs on. Those are also the screens most full of other people's information.
October 16, 2026
Real screens, not real people
A screenshot of a working admin shows what a site actually does far better than a description can. But a live admin contains customer names, phone numbers, messages and job applications. None of that belongs in a portfolio.
Use a copy with sample data
The safe approach is to run a private copy of the site with its own throwaway database filled with sample data, then capture screenshots from that. The screens are real, built from the same code the business uses. The people in them are not.
Script the captures
Writing down exactly which screens to capture, at which sizes, makes the process repeatable. When the site changes, the screenshots can be retaken the same way instead of rebuilt by hand, and nobody is tempted to grab a quick shot from the live system.
Check what's still visible
Sample data handles the obvious information, but screens can show other details: a business address, a staff email, a real street on a map. Each screenshot should be reviewed before it is published, and the business owner should approve what appears.
Ask before showing anything
Even with sample data, a case study is about someone else's business. Clients should agree to what is shown and said, and should be able to say no.
Proof without exposure
Done this way, a case study can show the real work in detail while every customer who ever used the site stays exactly as private as they expected to be.