Small business clients expect a website to show what they do, where they are, how to reach them, and proof that other people trust them — and they expect it without having to ask. Missing even one of these baseline features is one of the fastest ways to trigger an awkward "wait, where's my—" conversation after launch, which quietly erodes confidence in everything else you delivered.
Freelancers who focus purely on visual design sometimes ship genuinely beautiful sites that skip functional basics a business owner assumed were automatic. The client doesn't experience that as "a design choice" — they experience it as something being forgotten, and it's hard to fully recover the trust that erodes from that moment, even after you fix it.
The Baseline Feature Set (Applies to Almost Every Local Business)
| Feature | Why it's non-negotiable | |---|---| | Click-to-call phone number | For local businesses, phone often converts better than any form | | Address with an embedded map | Customers deciding "is this close to me" bail without it | | Hours of operation | One of the most-searched pieces of info for local businesses | | Contact form or booking link | A backup channel for people who won't call | | Clear "what we do" statement above the fold | Visitors decide in seconds whether they're in the right place | | Mobile-optimized layout | 60%+ of traffic is mobile — this isn't optional, it's primary | | Social proof (reviews, testimonials, or ratings) | Local purchase decisions lean heavily on trust signals from other customers | | A way to see the actual product/service (photos, menu, portfolio, service list) | Abstract descriptions convert worse than concrete visuals |
None of these are technically difficult. They're easy to forget precisely because they're so basic that neither the client nor the freelancer thinks to double-check them explicitly during scoping.
Industry-Specific Features Clients Assume Are Included
Beyond the baseline, different business types have unstated expectations specific to their industry — missing these reads as "the designer didn't understand my business," which is a harder problem to recover from than a missing baseline feature.
- Restaurants/cafés: an actual menu (not a PDF buried in a link — a real page), online ordering or reservation link if applicable, current hours including holiday exceptions.
- Medical/dental/professional services: booking or appointment request flow, staff bios, insurance/payment info, before/after or case examples where relevant.
- Home services (plumbers, electricians, contractors): service area explicitly stated, emergency contact prominence, licensing/insurance mentioned, before/after project photos.
- Retail: product categories or a simple catalog, store hours, in-store vs. online availability if both exist.
- Salons/spas/fitness: booking flow front and center, service menu with pricing ranges, staff/instructor profiles.
Building a Feature Checklist Into Every Scope
The fix for missed features isn't more design talent — it's a scoping habit. Before starting a build, run a short intake specific to the business type:
- [ ] What's the #1 action you want a visitor to take? (call, book, visit, order)
- [ ] Where does that action need to be visible? (above the fold, sticky nav, every page)
- [ ] Do you have real photos, or do we need to plan for stock/placeholder?
- [ ] What information do customers most often ask you for that isn't obvious? (parking, accessibility, walk-ins vs. appointment-only)
- [ ] Do you have existing reviews or testimonials we should feature?
This turns feature completeness into a scoping deliverable you can point back to, rather than a subjective judgment call the client discovers is missing after launch.
Why This Directly Affects Whether You Get Paid Well
A site with every expected feature reads as "this person understood my business," which is exactly the impression that makes a client comfortable recommending you and paying full rate on the next project without negotiating. A site that's visually strong but missing an obvious feature undercuts that impression regardless of how good the design is — the client remembers what was missing more clearly than they remember what looked good.
This is also directly relevant when you're writing the proposal — naming specific features for their specific business type in the proposal itself (rather than a generic feature list) is a strong signal of competence before you've built anything, and it sets a documented scope that protects both of you if something gets missed later.
Where This Fits in the Framework
Feature completeness is the functional counterpart to the visual polish covered in what makes a website look professional vs. amateur — a site needs both to actually convert. Next: how to present website work to a non-technical client, covering how to walk a client through what you built without losing them in jargon. For the full delivery framework, see how to build websites that win and keep clients.
Runvax: Understanding What Prospects Are Missing Before You Pitch
Knowing the expected feature set by industry is also useful before you ever land the client — it lets you name a specific gap in an outreach message ("I noticed your listing has no online menu or booking link") instead of a generic pitch. Runvax finds local businesses with no website (or an outdated one clearly missing these basics) in any city and category, and drafts that first, specific outreach message for you.