There's a moment in every cold outreach campaign that most guides skip over. A local business owner replies to your email with something like "Sure, what did you find?" or "Send me more details." They're curious, but they aren't ready for a sales call, and they definitely aren't ready for a proposal. What you send next decides whether this turns into a project or quietly fades out of their inbox.
For web designers and small agencies, the strongest thing to send at that moment is a short website audit: a one-page, plain-English summary of what's wrong with their site and what it's likely costing them. This guide covers what to put in it, what to leave out, whether to charge for it, how to walk a prospect through it on a quick call, and how to turn the findings into a proposal they'll actually sign.
Why an Audit Beats a Portfolio
The instinct when a prospect shows interest is to send your portfolio. The problem is that a portfolio is about you. It shows work you did for other businesses, and the owner has to do the mental work of imagining what that would mean for them. Most won't bother.
An audit is about them. It shows their own website, their own problems, and their own lost leads. It also proves something a portfolio can't: that you actually looked. Local business owners get a steady stream of generic pitches, and the fastest way to stand apart from all of them is to hand over something that could only have been written about their business.
An audit also moves the conversation from "do I need a new website?" to "which of these problems should we fix first?" That's a much easier question to say yes to.
What to Include (and What to Leave Out)
The most common mistake with prospect audits is giving them too much. A 40-item technical report full of terms like "canonical tags" and "HSTS headers" feels thorough to the person who wrote it, but to a busy restaurant owner or roofer it reads like homework. They skim it, feel overwhelmed, and set it aside for later, which usually means never.
A good prospect audit has three to five findings, chosen because they're the most expensive problems on the site, and each one is explained in terms of what it does to the business. Most of the findings worth including fall into four groups:
Trust and security
No HTTPS, mixed secure and insecure content, or an outdated copyright year. These are the problems a visitor notices before they read a word, and browser security warnings scare people off instantly.
Mobile experience
A site that isn't mobile-ready or loads slowly on a phone. For local service businesses, most first visits happen on a phone, often while the person is ready to call someone.
Getting found
A missing page title or meta description, no local business schema, or a site that's accidentally blocked from Google. These decide whether the business shows up in local search at all.
Turning visitors into calls
No contact form, a phone number buried at the bottom, or no clear next step on the homepage. This is where interested visitors quietly leave for a competitor.
The technical finding is only half the job. The other half is translating it into something the owner cares about. Here's what that translation looks like for the findings that come up most often:
| Technical Finding | How to Say It to the Owner |
|---|---|
| No HTTPS / SSL | Chrome shows visitors a "Not secure" warning before they see your homepage. |
| Not mobile-ready | On a phone, your site shows up as a tiny desktop page that people have to pinch and zoom to read. |
| No contact form | Anyone browsing after hours has no way to reach you except to remember to call tomorrow. |
| Slow load time | Your homepage takes several seconds to appear, and a lot of mobile visitors give up before it does. |
| Blocked from Google | Your site is set up in a way that tells Google not to list it in search results. |
| No local business schema | Google has to guess your hours, address, and service area instead of reading them directly from your site. |
Leave out anything the owner can't see or feel. Security headers, alt text counts, and duplicate H1 tags are real issues worth fixing during the project, but they don't belong in the audit that's meant to start the conversation. Save them for the scope of work.
A One-Page Audit Format That Gets Read
The format matters as much as the findings. One page, readable in two minutes, with a clear next step at the bottom. Here's a structure that works for almost any local business:
1. Header: the business and a single score
The business name, their website, the date, and one overall score or grade. A single number gives the owner an instant sense of how serious things are and something to compare against after the fix.
2. The top three fixes, in priority order
Each one gets a short heading ("Your site isn't mobile-friendly"), one or two sentences in plain English, and ideally a screenshot. Lead with the problem that's costing the most leads, not the one that's easiest to explain.
3. What it's likely costing them
Tie the findings back to the business: missed calls, lost after-hours inquiries, visitors bouncing to a competitor. Keep it honest and directional. You don't know their exact numbers, and inventing a dollar figure undermines everything else on the page.
4. One clear next step
Offer a 15-minute call to walk through the fixes, with your name, phone, and email right there. Not a menu of packages, not a price list. Just the one next step.
Notice what's missing: a list of your services, your agency's history, and pricing. All of that comes later. The audit has one job, which is to get them on a short call.
Free vs. Paid Audits
Whether to charge for an audit depends on what kind of audit it is. The short, outside-in version described above should almost always be free. It's a sales tool, and it takes minutes to put together once you have a repeatable process. A deeper audit that involves logging into their analytics, reviewing every page, and building a full roadmap is real consulting work, and charging for it is reasonable.
| Audit Type | What It Covers | Typical Price | When to Use It |
|---|---|---|---|
| Mini-audit | 3–5 outside-in findings, one page | Free | Cold outreach replies and warm leads |
| Full audit | Every page, analytics, competitors, roadmap | $100 – $500 | Prospects who want a plan before committing |
| Credited audit | Full audit, fee applied to the project | Credited | Bigger projects where trust needs to be built first |
The credited version is often the best of both worlds. The prospect pays a small amount for the full audit, which filters out people who were never going to buy, and the fee comes off the project price if they hire you. Either way, they walk away with something useful, and you get paid for your time.
How to Send It
Send the audit as a PDF attached to a short email, or as a link. Don't make the email itself long. The audit does the talking, and the email's only job is to get it opened and point toward the call.
Hi [First Name],
As promised, here's a quick one-page review of [Business Name]'s website. I kept it to the three things I think are costing you the most leads right now, starting with [top finding].
None of these are complicated fixes. If it's helpful, I'm happy to walk through them on a 15-minute call this week. No pitch, just the findings and what I'd do about each one.
[Your name]
If they don't reply within five to seven days, send one short follow-up that references the top finding by name. If you're not sure how to handle the replies that do come back, How to Handle the 5 Objections Every Web Design Cold Pitch Gets covers the most common ones.
The 15-Minute Walkthrough Call
The walkthrough call is where the audit turns into a project. Keep it short, keep their website on screen, and let them do a lot of the talking. A simple structure:
Minutes 0–2Confirm What Matters to Them
Before showing anything, ask one question: "Where do most of your new customers come from right now?" If the answer is phone calls from Google, the mobile and search findings will land. If it's referrals, the trust findings matter more, since referred customers still check the website before calling. Their answer tells you which finding to lead with.
Minutes 2–10Walk Through the Top Three Findings
Show each problem live, on their own site, ideally on a phone view. Seeing their own contact form fail, or their own homepage take six seconds to load, is far more convincing than reading about it. After each one, ask a question instead of making a point: "Had you noticed that before?" or "How many calls do you think come in from the website in a normal week?"
Minutes 10–15Offer a Next Step, Not a Hard Close
End by offering to put together a proposal: "Would it be helpful if I sent over what it would take to fix these, with a price, so you can think it over?" Almost everyone says yes to that, because it costs them nothing and keeps them in control. It's also the natural point to mention anything else you noticed that's outside the audit's scope.
Turning Findings Into a Proposal
The best part of starting with an audit is that the proposal mostly writes itself. Every line item in your scope traces back to a finding the prospect has already seen and agreed is a problem. Instead of "website redesign: $4,000," the proposal reads like a list of fixes: rebuild the mobile layout, add a working contact form, move the site to HTTPS, set up local business schema, plus the smaller technical items you held back from the audit.
Size the project from how many findings there are and how serious they are, not from a gut feeling. A site with one or two problems is a tune-up. A site with problems in every one of the four groups above is a rebuild. For price ranges at each level and how to present them, see How Much to Charge for a Website Redesign in 2026.
Offer two options at most: the full fix and a smaller starting version that tackles the top finding only. A smaller starting point gives a cautious owner an easy yes, and the rest of the audit is still sitting there as the obvious next project.
Common Audit Mistakes
- Sending a giant report. Forty findings feel thorough to you and overwhelming to them. Three to five, in priority order, is enough.
- Using jargon. "Missing viewport meta tag" means nothing to a dentist. "Your site doesn't fit on a phone screen" does.
- Auditing every lead. Save audits for businesses that are clearly active, with steady reviews, real customers, and maybe some ad spend. A perfect audit for a business with no budget is wasted work.
- Writing a how-to guide. Explain what's wrong and why it matters, not step-by-step instructions to fix it. The audit should make them want help, not replace it.
- Making it scary. A wall of red warnings and alarming language feels like a sales tactic. Calm and factual is more persuasive.
- No next step. An audit without a clear call to action is a free consulting report. Always end with the 15-minute call offer.
Building Audits Faster
The biggest obstacle to using audits consistently is time. Checking a site by hand for HTTPS, mobile layout, load speed, a contact form, and the basic search signals takes a careful person several minutes per site. That's fine for a handful of prospects but hard to keep up week after week. For a full breakdown of what to check and where to find the businesses worth auditing, see How to Find Local Businesses With Outdated Websites.
However you build it, the audit only works if it reflects real findings. The specifics are what make it credible. For more on writing the first email that leads to the "sure, what did you find?" reply, see Cold Outreach for Web Agencies.
Frequently Asked Questions
Turn Any Local Website Into an Audit in a Minute
Sponge analyzes local business websites, scores them for opportunity, and gives you a report card you can save as a PDF, so your next audit starts with real findings.
Try Sponge Demo