Screenshots
Collect current website screens, app screens, booking flows, menus, product pages, forms, dashboards, or page sections that can be shown publicly.
Proof inventory
A practical inventory for turning real proof into stronger website pages.
Before a case study or service page gets more visual, collect what can actually be shown. This keeps the site credible and gives each page specific material instead of generic claims.
Send proof assetsProject notes
Write what was built, why it mattered, what changed, what constraints existed, and what parts should stay private.
Reviews and quotes
Save the exact review text, source, date, name display preference, and whether the quote is approved for public use.
Photos and brand files
Gather real location photos, team photos, product images, logos, color notes, typography notes, and image-use permissions.
Service evidence
Map each proof asset to the service page it supports so web design, SEO, landing pages, refreshes, and bilingual pages each have relevant proof.
Public-use limits
Mark what can be public, anonymous, blurred, summarized, or kept internal. Do not publish anything that is not approved.
FAQ
Questions worth answering before the build.
Why make an inventory before redesigning?
The UI can change later, but real proof determines what the page can honestly show.
Can we use anonymous examples?
Yes. Anonymous proof can work when screenshots, process notes, or examples are approved and do not expose private client details.
What should be collected first?
Start with screenshots, service examples, real photos, approved reviews, and short notes about what the work solved.
What should never be added?
Do not add fake clients, fake metrics, unapproved testimonials, private screenshots, or claims that cannot be backed up.
Related resources
Contact
Want to turn this into a site plan?
Send the business type, current site if there is one, and deadline. We will reply with a clear direction.