The Bulletin Design

No. 001

Why a designer should ask for your own photos

Stock photos make every small business site look the same. Your own images, even imperfect ones, do more work than a polished stranger.

A good web designer's first request is almost always the same: send your own photos, not a link to a stock library. Here's why that request matters, and what's actually worth sending.

Stock photography is a shortcut with a cost

Stock photos are easy, and visitors can tell. The same handshake and the same laptop-on-a-desk image appear on thousands of sites. When a visitor is deciding whether to call you, an image that could belong to anyone doesn't help.

Real images do three jobs

What homeowners actually say about photos and proposals

This isn't just a design preference. A 2026 survey of 292 US homeowners who had hired a roofer, run by Roofr, found that professional proposals ranked in the top three trust factors for 66% of respondents, and that 74% wouldn't hire a roofer without an inspection first. Photos of real, specific work are part of what makes a proposal or a page feel like it came from someone who actually did the job, instead of a template filled in with someone else's pictures.

What stock photography actually costs you

Beyond looking generic, a page built on stock photos misses the two things research says matter most before someone calls: proof and specificity. The Roofr survey mentioned above found 74% of homeowners wouldn't hire a roofer without an inspection first, which is really a proxy for wanting to see real evidence before committing. A page with your own truck, your own crew and a real finished job answers that instinct before a visitor even has to ask for it. A stock photo of a stranger's smiling face answers nothing.

A simple system for gathering photos on the job

Most businesses don't have a photographer on staff, and they don't need one. What works is a habit:

  1. Take a "before" photo the moment you arrive, before anything changes.
  2. Take an "after" photo from roughly the same spot, once the job is done.
  3. Take one photo of the crew or the truck at some point during the job, even a quick one.
  4. Send them the same day, while it's easy to remember what job they were from.

Building this into how a job wraps up, rather than trying to gather photos retroactively months later, is what actually produces a usable library over time.

Organize what you send, don't just send everything

A folder of 200 unsorted photos is harder to use than 12 chosen ones. Group what you send by project type (a roof replacement, a kitchen remodel, a panel upgrade) rather than handing over a phone's entire camera roll. Before-and-after pairs of the same angle are the single most useful format, because they show the actual change instead of describing it.

What to send

  1. Your work: finished projects, before and after shots, anything you're proud of.
  2. Your people: the owner and the team, even from a phone.
  3. Your place: the shop, the office, the vehicle.
  4. Your logo, in the best quality you have.

Questions

What if my photos aren't good enough?

Phone photos are usually fine. Good light and a steady hand matter more than the camera, and a designer can crop, correct and place them properly.

What if I have almost no photos?

Send what you have, and work with your designer on a short list of the few shots that would matter most going forward. A handful of real images beats a page of stock.

Do before-and-after photos need to match exactly?

As close as you can manage: same angle, same distance, similar light. A rough match still works far better than two unrelated photos, but a careful match is what makes the comparison obvious at a glance.

Sources

Want a site that launches with answers already written?

Start a project