What "cheap" actually means

A cheap small business website can be fine. It can also be a waste of money. The difference has less to do with the price than with what the price covers.

A low quote might cover a simple scope. A high one might include research, writing, custom features, integrations, migration, compliance work, or ongoing support. Different jobs. The number tells you about the proposal and the shop's business model, and almost nothing about whether the site will be any good.

Better questions: does the site do what your business needs? Who owns the domain, hosting, and accounts? Who maintains it? How will you know it's working?

The non-negotiables at any price

Whatever you pay, a quote that skips any of these isn't cheap. It's incomplete.

  • It works on a phone. Test on real phones and tablets.
  • It loads fast: properly sized images, no code the site doesn't use.
  • The contact form reaches the right person. Send yourself a test.
  • Name, phone, hours, and service area are correct everywhere.
  • HTTPS is on, you own the accounts, and someone has a plan for updates and backups.

Test the finished site, not the promise: No single load-time number predicts every visitor. Check Core Web Vitals, real-user data when you have it, and an ordinary phone.

Getting these right removes the avoidable problems. It doesn't bring in leads by itself. Demand, visibility, your offer, reviews, prices, and follow-up matter at least as much.

What you can skip on a budget

Plenty of things that make a proposal look expensive do nothing for a customer who wants a quote. Question these first:

  • Animations and scroll effects
  • Video backgrounds, or a YouTube embed in the header
  • Interactive galleries and portfolio builders
  • Live chat widgets
  • Custom illustrations
  • Multiple typefaces and an elaborate design system

A plain site is usually easier to maintain and easier to get around than one full of effects. We hold that opinion firmly. Measure speed and usability on the finished thing, not the mockup.

Where a low quote usually cuts the wrong thing

A low quote saves money somewhere, usually on work you can't see in a screenshot. Check whether it includes:

  • Performance work: image sizing, caching, removing unneeded code
  • Search foundations: descriptive titles, pages Google can crawl, redirects from old URLs, structured data that matches the page
  • Testing on real devices, including keyboard use
  • A written handoff naming who controls the domain, hosting, platform, analytics, and content
  • Support after launch for bugs, updates, backups, and forms that stop sending

A simple-looking site can be built properly. An expensive one can have holes. The only way to know is to check the work.

The right question to ask

"How much?" is the wrong first question. Ask these instead, at any price:

  • How will you test mobile performance, accessibility, forms, and browsers?
  • Who controls the domain, hosting, platform, analytics, and content afterward?
  • Which search foundations, redirects, and migration tasks are in this quote?
  • Can I see similar work, and what exactly did you do on it?
  • What do maintenance, support, and recurring fees cost after launch?

Compare equivalent scopes: A low quote and a high quote often cover different work. Ask each provider to split out strategy, content, design, development, integrations, hosting, maintenance, and support, then compare line by line.

The right site meets the requirements you've verified, leaves you in control of your accounts, and costs what you can keep paying. For what goes into the number, see what a small business website costs. If you're a contractor, this is how we build them: scope on a discovery call, and a free homepage preview before anything is billed.