Most small business website projects go wrong in the same two places: the scope was described in adjectives rather than deliverables, and nobody agreed who owns what when the project ends. Neither problem is technical, which is why comparing developers on their portfolios alone is a poor filter. A portfolio tells you what a developer can make look good. It does not tell you whether the site will be fast on a phone, whether you can edit it without going back to them, whether it can be found in search, or whether you will still control the domain and the code after a disagreement. This page covers what to specify, what to insist on owning, and the search and accessibility basics worth writing into the contract rather than hoping for.
Specify deliverables, not adjectives
A brief that asks for a modern, professional site invites five quotes that cannot be compared. A brief that lists the page count, the specific templates needed, who writes the copy, who supplies photography, which forms exist and where their submissions go, which integrations are required, and what the launch date is will produce quotes you can put side by side. Write down the things you assume are included, because those are the items that reappear as change requests: content migration from the old site, redirects for old URLs, an email setup, training, and a warranty period for bugs after launch. If a developer refuses to quote against a specific scope, that tells you something useful before you have spent anything.
Ownership terms that protect you later
Four things should be in your name from day one. The domain, registered to your business rather than to the developer's registrar account. The hosting account, or at minimum an account you can take over without a migration. The content and images, with a written licence for anything stock or a transfer of copyright for anything commissioned. And the analytics and Search Console properties, created by you and shared with the developer. Ask explicitly what happens to the site if you stop paying: some proprietary builder arrangements mean the site is rented rather than owned, which can be perfectly reasonable value if you know it, and a nasty surprise if you do not.
The search basics to require in the build
You are not asking a developer to run a search campaign, you are asking them not to ship a site that fights one. Google's SEO starter guide sets out the foundations plainly: pages must be crawlable and indexable, each page needs a unique descriptive title, images need meaningful alt text, and the URL structure should be readable. Add three items from experience: redirects mapping every old URL to its new equivalent, a single canonical version of the site so http, https, www and non www all resolve one way, and real HTML text rather than words baked into images. Getting these wrong at launch is the most common cause of a site that was working losing its traffic overnight, and it is much cheaper to specify than to repair. The remedial work afterwards is exactly what most small businesses end up paying an SEO provider to unpick.
How to compare quotes that look different
Three quotes for a small business site will often differ by a factor of five, and the gap is usually explained by four variables rather than by quality. Custom design versus a configured template. Custom code versus a content management system with plugins. Who writes the copy, which is the single biggest hidden cost and the most common reason projects stall. And ongoing support, which some quotes bundle for a year and others bill hourly from launch. Normalise for those four before you judge, ask each developer for their hourly rate for post launch changes, and ask how long a typical small change takes. That number matters more than the build price over the site's life.
Questions people ask about website developers for small business
Should a small business use a website builder or hire a developer?
A builder is often the right answer for a simple brochure site if someone internal will maintain it. Hire a developer when you need custom functionality, integrations, a migration, or when nobody in the business has time to learn a tool. Cost includes your own hours, not just the invoice.
How do I stop a redesign from losing my search traffic?
Map every existing URL to its replacement and set redirects at launch, keep the page titles and content of pages that already perform, and verify the new site is crawlable and indexable. Google's starter guide covers the foundations, and skipping them is the usual cause of a post launch drop.
Who should own the domain name?
Your business, in an account you control. A domain registered under a developer's account is the single most disruptive thing to recover in a dispute. If yours is already there, ask for a transfer now rather than when you need it.
What should I budget for maintenance?
Plan for hosting, software updates, backups, security patching and a small allowance for changes. Ask the developer for their hourly rate and their typical response time for small edits, then decide whether a support retainer or pay as you go fits your rate of change.