Use the actual business context
Start with the public website URL. Preserve recognizable branding and useful content. Do not imply access to private customer or sales data.
Give a prospective client a concrete reason to talk. Create a website redesign preview around one useful improvement, then explain the idea without a generic audit or an exaggerated sales promise.
Look for a business whose website and customer journey you understand. Pick an observable issue: an important service is difficult to find, the next step is unclear, or the mobile experience makes a routine task awkward.
Do not invent lost revenue, traffic problems or security issues from a glance at the website. Your preview should explain a useful possibility, not manufacture a problem to sell a solution.
Start with the public website URL. Preserve recognizable branding and useful content. Do not imply access to private customer or sales data.
For example, bring the main services together, clarify the service area and make requesting a quote easier. Refine the preview before sharing it.
Agency plans support branded client-facing previews. Share a link that fits your agency presentation, then use the same project for delivery if the prospect chooses to work with you.
Replace the placeholders with a real observation. Ask whether they want to see the idea rather than treating an unsolicited redesign as an agreed project.
Subject: An idea for [business]’s [service] page Hi [name], I noticed [specific, accurate observation] while looking at your website. I put together a design direction that makes [customer task] easier to find. Would you like me to send the preview? Happy to explain the thinking behind it. [Your name and agency]
If they ask for the preview, send it with one or two points to review. Explain what is a proposed design and what still needs their input. Invite a response about their priorities.
Follow applicable outreach rules, use an appropriate business contact method and respect requests not to be contacted. A preview is not permission to publish work on behalf of another business.
Hi [name], here is the preview we discussed: [link]. The main change is [specific improvement]. Does this reflect the direction you want for [business], or is there another priority you would put first?
Agree the pages, content, customer journeys, connected tools and launch responsibilities with the client. Keep the approved preview and continue building the website in that project.
Add bookings, payments, customer areas or other business functions as needed. Share changes for review, publish on the client’s domain and keep supporting the website afterward. Your agency manages its own relationship and billing with the client.
Explore agency plans for branded previews, client projects and the websites you keep managing after launch.
Explore agency plansNo. Use the business’s actual context and an improvement relevant to its customers. A generic preview is unlikely to explain why your agency is the right fit.
Yes. Share the preview link so they can review it in their browser. Agency plans provide branded client-facing presentation.
No. It is a separate project. Do not connect their domain or publish on their behalf without their authorization.
Yes. Continue in the same project, add the agreed pages and business functions, share changes for review, then publish and maintain the website.
Shape what comes next in Revamp.
Create an outreach preview