“I just need a simple website.”
Okay.
Define simple.
Five pages? No login? No ecommerce? One contact form?
Great.
Now who is writing the copy?
Who is choosing the photos? Who is resizing them? Who is deciding which services deserve their own page? Who is setting up analytics? Who is checking the mobile layout? Who is connecting the form? Who is handling revisions? Who is fixing the thing when Outlook decides the form email belongs in spam?
Suddenly “simple” has a payroll.
This is why one developer can quote $500 and another can quote $5,000 without one of them automatically being insane.
They may not be pricing the same project.
Page count is useful. It also lies a little.
“Five-page website” sounds specific.
It is not.
Five pages for a neighborhood barber could be straightforward: Home, Services, Gallery, About, Contact.
Five pages for a medical courier company could include compliance language, service-area logic, intake requirements, documentation, trust signals, specialized forms, and content that has to be reviewed very carefully.
Same number of pages.
Not remotely the same amount of thinking.
A page count tells me how many rooms are in the house. It does not tell me whether we are furnishing an apartment or installing an operating room.
Who is writing this thing?
This is the part that mysteriously disappears from cheap website conversations.
“Client provides content.”
That sentence can save a lot of money.
It can also create a folder called:
FINAL WEBSITE COPY USE THIS ONE 3.docx
If the business already has strong copy, organized service descriptions, approved testimonials, real photos, and a clear call to action, fantastic.
The project just got easier.
If the developer has to interview the owner, organize the services, write the pages, research terminology, clean up testimonials, find image direction, and rewrite the About page because it currently says “we strive for excellence” six times, that is not “putting text on a website.”
That is content work.
A template and a custom design are not the same starting line.
I sell templates.
So let me say the quiet part clearly: templates can save real time and real money.
If a strong template already solves the navigation, responsive structure, common page layouts, forms, typography, and basic visual system, there is no medal for deleting all of that and rebuilding it because suffering feels premium.
But a template is still a starting point.
Maybe the business fits it beautifully.
Maybe the template needs heavy restructuring.
Maybe the brand requires a completely custom interface.
Those are different scopes.
“Uses a template” does not automatically mean cheap. “Custom” does not automatically mean good.
The question is whether the approach fits the project and whether the finished site actually does the job.
Every “small feature” has friends.
This is where estimates reproduce.
“Can we add online booking?”
Sure.
Which booking system? Does it already exist? Does it need payment? Calendar sync? Confirmation emails? Cancellation rules? Different appointment types? Staff availability?
“Can customers upload a file?”
Sure.
What kind? How large? Where is it stored? Who can access it? How long should it remain there?
“Just add a customer portal.”
Absolutely.
And while we are here, I would like to “just add” a second floor to my garage.
Name, email, message, delivery to the business.
Conditional fields, uploads, service choice, routing.
Availability, calendars, reminders, rescheduling.
Accounts, permissions, data, security, workflows.
A lot of website work is invisible when it goes right.
Responsive behavior.
Keyboard navigation.
Form validation.
Image optimization.
Search metadata.
Redirects.
Error states.
Browser testing.
Performance cleanup.
Accessibility details.
None of that photographs particularly well for Instagram.
It still takes time.
Google publishes technical guidance around crawlability, page experience, structured data, mobile behavior, and performance. W3C publishes accessibility standards and guidance for making web content usable by more people.
Whether a project includes serious attention to those details changes the amount of work.
And yes, the $500 website can be completely fine.
I know this is where website people sometimes start sweating.
Not every business needs a $5,000 site.
A new solo operator with a tiny budget may need a clean template, five good pages, one form, clear contact information, and a site that does not embarrass anybody.
That can be a smart decision.
The problem is not cheap.
The problem is pretending cheap includes things it does not.
If the $500 quote clearly says: template-based, client provides content, one revision round, basic SEO setup, no integrations, no ongoing support, then everybody knows what they are buying.
Beautiful.
Trouble starts when “simple website” means “everything I saw on three competitors' websites, plus booking, plus a portal, plus can you write the copy?”
Compare the scope, not just the number at the bottom.
When two website quotes are far apart, line them up.
Once you compare those, the mystery usually gets smaller.
Sometimes one quote is overpriced.
Sometimes one is suspiciously cheap.
And sometimes both are reasonable because one person quoted a website and the other quoted the project you actually described.
Sources behind the invisible-work part
- Google Search Central: Search Essentials
- Google Search Central: Link best practices
- web.dev: Core Web Vitals
- W3C WAI: Web Content Accessibility Guidelines
Ask what is included before asking which quote is crazy.
The number matters.
The scope tells you what the number means.
The comment section has entered the chat
Join the discussion
0 approved commentsWhat should a small business actually expect to pay for a website, and which parts of the scope change the price the most?
No approved comments yet. You could be first, which is either exciting or suspiciously responsible.
Add your two cents
Keep it useful, keep it human, and disagree without flipping the table. Comments are reviewed before they appear.