How to sell websites to local businesses: opportunora

Learning how to sell websites to local businesses is mostly learning how to reduce uncertainty. The owner has to believe the site solves a real problem, see what you intend to deliver, understand the price, and know what happens after saying yes.

You do not need a complicated funnel. You need a qualified business, one clear observation, a useful preview, a written offer, and a delivery process you can repeat.

Quick answer

To sell websites to local businesses, choose one category and town, find active businesses with a weak or missing website, and verify the problem before making contact. Show the owner a private preview built from accurate public facts, explain the customer action it improves, and offer a fixed package with clear scope, revisions, ownership, hosting, and payment terms.

The basic sequence is:

Find an active business with a verifiable website problem.
Identify the customer action the current setup makes difficult.
Build a private, accurate preview rather than sending a generic portfolio.
Contact the business with one specific observation.
Agree the package, scope, approval process, and price in writing.
Publish only after the client approves the site.
Invoice from the accepted offer and provide a clear care option.

The website is the deliverable. Reduced risk is what closes the sale.

Sell a business outcome, not a page count

A local business owner rarely wants a website for its own sake. They want customers to call, book, request a quote, find the premises, read a menu, or understand a service before making contact.

Start by naming that action. A useful offer sounds like this:

A fast mobile site that lets homeowners understand your emergency electrical services and call you in one tap.

A weak offer sounds like this:

A modern five-page responsive website built with the latest technology.

The first describes what changes for the customer. The second describes your production process. The production process matters later, when you define scope and quality, but it is not the reason the owner buys.

Pick categories where a website supports a visible customer action. Trades, clinics, salons, instructors, repair services, restaurants, and local professional services can fit. Do not assume every business needs the same site. A subcontractor working through established relationships may gain little from search traffic, while an emergency plumber can lose a call when a phone number is hard to find.

Choose one category and one town

Selling becomes easier when prospects have similar customers and similar website requirements. Ten electricians in one region are easier to compare than ten unrelated businesses across a country.

A narrow starting market gives you:

A repeatable search query
Comparable websites and offers
Reusable quality checks
Familiar objections
A clearer package
Local context for the first message

Write down the category, location, practical radius, and the package you can deliver before collecting names. If the search is broad enough to fill a spreadsheet with hundreds of businesses, it is probably too broad to produce a good first conversation.

Qualify the business before you pitch it

“No website” is a useful signal, but it is not enough. A missing URL can mean the business has another domain, relies on a booking platform, recently closed, or simply forgot to connect its website to a map profile.

Before you spend time on a preview, confirm four things.

The business is active

Look for current opening hours, recent public reviews or posts, a working phone number, and consistent address information. Save the source and the date you checked it. Old directory entries should not be treated as proof that a business is trading today.

The website problem is real

Search the exact business name and town. Check its map listing, social profiles, directory pages, and any domain you find. Classify the current setup as missing, social-only, parked, broken, outdated, difficult on mobile, or already fit for purpose.

A business with a usable site is not a prospect merely because you dislike the design. Move on.

The problem affects a customer action

Open the current page on a phone and try to complete the action a customer came for. Can you call, book, request a quote, find the address, understand the service area, or check today's opening hours?

The strongest sales observation connects a visible website issue to one of those actions. “Your design looks old” is subjective. “The phone number is an image and cannot be tapped on mobile” is specific and testable.

There is a legitimate contact route

Use a public business contact method intended for enquiries. Do not infer a private email address, collect unnecessary personal data, or bypass a platform's access rules. Record where the contact detail came from so the research remains auditable.

Audit before you build

A short audit keeps the preview focused. Check the parts that matter to a local customer:

Business name, service, and location are clear in the first screen
Phone number and primary action work on mobile
Opening hours and address agree with public listings
Service area is understandable
Images are real, relevant, and properly sized
Forms ask only for information the business will use
Pages load securely without obvious errors
The owner can see what happens after an enquiry

Google documents the business information it expects to be represented consistently in its Business Profile guidelines. For technical quality, web.dev's Core Web Vitals provide named measures for loading, responsiveness, and visual stability. You do not need to turn the first conversation into a technical report. Use these checks to decide what the new site must improve.

Write the opportunity in one sentence before building:

The business is active and well reviewed, but its current page hides the quote request on mobile and does not explain the service area.

If you cannot write a factual sentence, you do not yet have enough evidence to build or pitch.

Build a private preview, not a fake live website

A preview removes the owner's hardest task: imagining what you mean. It should use the business's real name, public services, logo, photos, location, and contact details only when you can verify them.

Keep the preview private and clearly treat it as a proposal. Do not publish it on the business's domain, present it as the official site, manufacture reviews, or invent prices, staff, qualifications, years in business, guarantees, or service areas. Missing facts should remain missing until the owner supplies or confirms them.

A useful first preview needs less than most designers expect:

A clear headline naming the service and location
One primary customer action
A short service summary
Accurate contact and location information
Real visual material where permission and source allow it
A mobile layout that works without explanation
A note listing the facts that still require client approval

The preview is evidence of your proposed solution, not permission to act on the business's behalf.

Price the work as a package

Fixed packages are easier to understand than an open-ended hourly estimate. They also force you to define the boundary of the work.

A simple structure is:

Starter: one focused page, supplied content and images, contact action, domain connection, and launch
Professional: several service pages, stronger content structure, forms, local information, and a larger revision allowance
Care plan: hosting, monitoring, backups where relevant, and an explicit allowance for future content changes

Every package should state:

Pages and features included
Who supplies and approves facts, images, and legal text
Number and meaning of revision rounds
Domain, hosting, and account ownership
Accessibility, browser, and mobile checks
Target schedule and what can delay it
Price, tax treatment, deposit, and payment timing
What support exists after publication
What is specifically excluded

Do not hide a weak scope behind a low price. If the owner needs a lower number, remove a page, feature, revision round, or service. Changing the scope keeps the price credible.

Write a first message about one observed problem

The first message should earn a conversation, not close the entire project. Keep it short enough that the owner can understand it on a phone.

A practical shape is:

Identify yourself accurately.
Say where you found the business.
Mention one website issue you personally verified.
Explain the customer action it affects.
Offer to send the private preview.
Give the recipient an easy way to decline.

For example:

Hi, I was looking for local repair services in Bath and noticed your current page makes the call button difficult to use on a phone. I prepared a private homepage preview showing a simpler mobile route to call or request a quote. Would you like me to send the link? If not, no problem and I will not follow up.

Adapt the wording to the facts. Do not say you found lost revenue, poor search rankings, security problems, or legal violations unless you have competent evidence for that exact claim.

Commercial communication rules depend on where you and the recipient are. In the United States, the Federal Trade Commission publishes a CAN-SPAM compliance guide. For the United Kingdom, the Information Commissioner's Office explains direct marketing and electronic communications. Check the rules for the relevant jurisdiction and channel; a public contact detail is not a universal permission for automated outreach.

Use the first call to confirm facts and fit

The discovery call is not a design presentation. Its job is to learn whether the problem matters, whether the preview is directionally right, and whether there is a workable decision process.

Ask questions you can use:

Which enquiries do you most want the website to produce?
Which services should be prominent, and which should not appear?
Which towns or areas do you actually serve?
Who answers calls and form submissions?
Which facts on the current listings are wrong or outdated?
Who owns the domain, logo, photos, and existing accounts?
Who approves the final site?
Is there a date the site needs to be ready?

Do not fill silence with promises. If the client wants bookings, payments, multilingual content, integrations, regulated claims, or account access you did not include, write those down and revise the scope before accepting the work.

Turn the conversation into a written offer

The offer should mirror the package discussed on the call. A client should be able to compare the preview, scope, price, and approval steps without decoding a sales document.

Include:

The current problem, stated without exaggeration
The agreed customer action
Deliverables and exclusions
Information the client must supply
Review and approval stages
Price and payment schedule
Offer expiry date
Ownership and hosting arrangements
Cancellation and post-launch support terms

Keep proposal facts and invoice facts connected. Re-entering the scope, price, and client information in separate systems creates avoidable disagreement.

Control revisions and approval

Revisions become expensive when “one round” means an unlimited stream of messages. Define a round as one consolidated list of changes returned by one named approver.

Keep versions. After each revision, record what changed and which version the client is reviewing. When the site is ready, ask for approval in a durable form such as email or the project's approval system.

Do not publish merely because the preview looks complete. The client must confirm names, services, locations, prices, images, contact details, legal text, and any regulated or professional claims that appear on the site.

Publish, invoice, and make the next step explicit

Before launch, check the production domain, HTTPS, mobile layout, forms, phone links, metadata, crawlability, analytics consent where used, and legal pages appropriate to the site. Test the actual deployed URL, not only the preview.

Then tell the client:

What went live
Which account or domain they own
Where enquiries arrive
How to request corrections
What the invoice covers and when it is due
What happens if they do or do not choose ongoing care

A care plan should not be a vague promise to “maintain the website.” Name the hosting, monitoring, response time, update allowance, backups, reporting, and items billed separately. The client can then decide without wondering whether the launch price contains a permanent support obligation.

A repeatable website sales workflow

Use this checklist for each prospect:

Choose one category, location, and package.
Find candidates from public local sources.
Verify the business is active.
Classify the current website or substitute.
Identify one affected customer action.
Save the source and a factual opportunity reason.
Build a private preview from verified information.
Send one relevant, compliant first message.
Confirm needs, facts, ownership, and the approver.
Issue a fixed written offer.
Apply consolidated revisions and keep versions.
Obtain explicit approval before publication.
Test the live domain and enquiry path.
Invoice from the accepted scope.
Offer a clearly bounded care plan.

Opportunora keeps most of that sequence in one workspace: it finds source-backed opportunities, generates a reviewable site, records edits as versions, publishes only when the operator clicks Publish, and creates the invoice from a won deal. The software shortens the hand-offs, but the operator still controls the claims, communication, approval, and client relationship.

Frequently asked questions

Should I build a website before contacting the business?

A small private preview can make the offer concrete, provided it uses accurate information and is not presented as the business's official live site. Do not invest in a complete production build before confirming the business is active, the problem is real, and the owner is willing to review it.

Is a business with no website always a good prospect?

No. It may be inactive, rely on referrals, use a booking marketplace, or have a website that is not linked from the listing. Activity, customer need, reachability, and evidence quality matter alongside website status.

Should I charge once or monthly?

Use a one-time project price for a defined build and a separate monthly fee for ongoing services with recurring work or cost. State exactly what the monthly plan includes. Do not disguise financing as maintenance or promise unlimited changes without pricing that risk.

How many packages should I offer?

Three is usually enough to make the trade-offs visible: a focused starter site, a broader professional site, and an ongoing care option. Fewer can be suitable when the niche has one standard need. More often creates unnecessary decisions.

When should the client pay?

Set the schedule in the offer before work begins. The right deposit and final payment structure depends on project size, jurisdiction, trust, and your business model. Whatever you choose, connect each payment to a clearly defined stage and issue an invoice that matches the accepted scope.

How to sell websites to local businesses