Send the finished thing first
Make a private sample page with honest content.
Start this Play →A private one-page prototype outline and owner review checklist.
A builder testing whether a small website concept helps a local business.
- Estimated effort
- 45–90 min sample exercise
- Cost / access
- Free sample / hosting costs vary
- First move
- Use the fictional business facts to write one headline and one booking action.
Prerequisites, inputs & cost details
Before you begin
- A clear one-page purpose
- Permission before using a real business’s assets
Inputs you need
- Approved services, hours, and contact route
- Real supplied claims or explicitly marked placeholders
A local text or HTML sample can be free. Real design tools, hosting, domain names, and third-party features vary.
Make it your next small win.
My saved workWrite a brief, practice the workflow, and keep your notes. This workspace saves your planning; it does not run tools or send anything.
See the fictional sample
A fictional repair business with no real booking destination.
business: Northline Bike Bench (fictional) services: Tune-ups; puncture repair; brake adjustment hours: Sample hours, owner to confirm contact: Placeholder only; no form destination reviews: None supplied prices: None supplied
Outline a private one-page prototype for fictional Northline Bike Bench. Include a clear purpose, three supplied services, a booking placeholder, and questions for the owner. Do not invent prices, reviews, awards, hours, or results. No publication or live form is part of this exercise.
- Separate facts and gapsList supplied facts and every placeholder that needs approval.
- Draft one pageWrite headline, services, and one clear next action using the fixture.
- Review the experienceCheck mobile reading, labels, and whether the visitor understands the offer.
- Prepare owner reviewWrite a short private preview note and list the approvals needed before publishing.
Review before a real build.
- Use fictional assets or material you have permission to use. Keep the prototype private.
- Owner approval is required for claims, real contact destinations, external messages, and publication.
Measures to consider
- Ask sample reviewers what the business offers and what action they would take.
- Record mobile usability issues found and resolved; measure real inquiries only after a separately approved launch.
Editorial scenario · Source review 2026-11-01. A learning hypothesis, not an independently validated result or proof of customer demand. The sample is fictional; linked tools require their own access and cost checks.
Understand the approach.
A real page they can click beats a pitch. Build it first, then say hello.
01The outcome
+
- The tool is a website prototype. The house is a business that shows up well online and turns visitors into booked work.
- The prototype is the first conversation. It proves you understand their business.
- Be honest about who you are and why you are writing.
02Who this is for
+
- Local businesses with a weak or missing website and a good reputation in person.
- Owners who prefer a face-to-face conversation, so the plan mixes automation with a visit or call.
03Signals to investigate
+
- No website, an outdated one, no clear call to action or bad on mobile.
- Good reviews but few of them.
- Social pages with no link to book.
04Data sources and access
+
- OpenStreetMap via Overpass Turbo: free map data on businesses by type and area
- Overpass API guide: how to query it; the public server limits heavy use
- County Business Patterns: how many firms of each type exist in an area
05Conversation starters
+
- 'I built a small sample page for your business. Can I send you the link?'
- Subject: the business name and 'sample page.' Body: what you noticed, the link, one question.
- A new business opening, a new owner or a rebrand.
06Validate before building
+
- Build five prototypes by hand for five local businesses. Send them with an honest note.
- Count how many replied. Ask each one what made them reply.
- Ask what they would pay attention to if you sent the next one.
07Build the smallest useful version
+
- Pull a small list of businesses from public map data and grade each on how strong its online presence is.
- Generate a one-page prototype for each, with their name, services and a booking form.
- A person reviews each page and each note before anything is sent.
- Track who replied and why.
08Deliver and operate
+
- AI builds the first draft. A person checks every fact and every link.
- Reuse the same template across businesses, changing only what is true for each one.
- When they say yes, move the sample to their own domain.
09Limits and things to check
+
- Never invent reviews, prices or claims. Use only what is true.
- Say who you are in the first line. A sample page is not a trick.
- Respect the terms of any data source. Do not scrape sites that forbid it.
- Check email rules before you send: a real sender, a clear opt-out.
Tools and supporting resources
Source recommendations; check current access, costs, API availability, and setup in the linked documentation. No integration is installed by opening this guide.
Plan your version.
Read the planning prompt
You are a web designer building a one-page sample site for a local business. Business: [name], [type], in [city]. Services: [list]. Tone: [warm / professional / bold]. Build a single page with: a clear headline, the three main services, honest reviews I give you, a map and hours, and one button to book or call. Use only information I give you. Do not invent reviews, awards or prices. Then write a short note to the owner that says who I am, that I built this as a sample, and asks if they want to see more. Treat this scenario as a hypothesis, not a proven business result. Check source coverage, permissions, costs, and integration support for my location and accounts. Work with sample or authorized data. Keep outreach and external changes in draft until I approve. Report unverified assumptions.
