A small business website can mean roughly $200–$600 a year in DIY software, a $1,000–$5,000 simple freelancer build, or an $8,000–$25,000 small custom agency build, according to the commercial guides cited below. Those figures cover different things: software access is not professional implementation, and a simple site is not a custom agency project.
To set a useful budget, define what the website must do, price the work needed to launch it, then add 12 months of operating expenses. I would compare that total—and the responsibilities behind it—before comparing proposal headlines.
How much does a small business website cost?
These published estimates provide a starting point, not a representative US market average or a guaranteed quote.
| Delivery model | Published estimate, USD | Scope and limitations |
|---|---|---|
| DIY website builder | Roughly $200–$600/year | GruffyGoat’s guide estimates software spending including hosting. Staff time and unspecified extras are excluded. |
| Simple freelancer build | $1,000–$5,000 | Thervo’s guide describes a limited-feature site, generally fewer than 10 pages. Confirm content, recurring costs, and extras separately. |
| Small custom agency build | $8,000–$25,000 | Thervo’s estimate covers custom agency work, not the same scope as its simple freelance example. Unspecified content, recurring expenses, and extras need separate confirmation. |
A provisional budget should therefore have two parts: an implementation budget tied to a written scope, and an operating budget tied to actual subscriptions and support arrangements. Neither should depend on a provider’s label alone.
Compare DIY, freelancer, and agency delivery—not identical packages
The delivery model determines how you organize the work. It does not reliably tell you everything included in the price.
DIY fits manageable requirements and available staff time. Someone inside the business still needs to plan the pages, write the content, configure the site, test it, and keep it current. A low software bill can be sensible when that person has the skills and capacity. Include their workload in the decision, even if it is not an additional cash expense.
A freelancer can fit a defined project. Establish whether that person handles planning, copy, design, development, and testing—or whether you must supply some of those skills. Ask about availability after launch rather than assuming support ends at delivery.
An agency can coordinate several disciplines. That can help when content, design, development, search setup, and integrations need to move together. Still, verify who actually does the work, what coordination is included, and who owns decisions. “Agency” does not automatically mean strategy, copywriting, or ongoing maintenance is included.
For each option, ask: Who plans, writes, builds, tests, approves, and maintains the website? Any unanswered role becomes work the buyer must assign.
Define the scope before requesting a price
Start with the customer action: request an estimate, book an appointment, buy a product, or contact the right department. Then describe the pages and functionality needed to support it.
Separate page count from design and content work
Ten pages using one reusable layout are different from ten individually designed pages. Your scope should identify:
- Pages and unique layouts: list both, including service, location, product, and landing pages where relevant.
- Content: who writes, edits, supplies images, and approves factual details.
- Content entry: who places approved material into the site, and how much is included.
- Design approach: an adapted template, custom layouts, or another explicitly described approach.
- Revisions: the included rounds, what each round covers, and who consolidates feedback.
“Content supplied by client” needs a deadline and a format. Otherwise, the build price may be clear while the launch schedule remains uncertain.
Describe working processes, not feature labels
A “booking feature” might be a link to an existing scheduling service. It might instead involve appointment types, staff availability, confirmations, and cancellation handling. Those are different scopes.
The same distinction applies elsewhere:
- A catalog displays products; checkout and shipping introduce additional purchasing workflows.
- A contact form notification sends a message; CRM synchronization needs agreed field mapping, routing, and handling when a transfer fails.
- An integration may require implementation work, a separate subscription, testing, and someone responsible for future changes.
For each workflow, document the trigger, the information collected, where it goes, and who responds. Ask providers to separate setup fees from subscription charges and ongoing responsibility.
Also distinguish SEO setup from ongoing acquisition work. Specify launch deliverables—such as agreed page titles, redirects, or indexing checks—rather than accepting “SEO included” as a complete scope. Continuing content and search work need their own plan. If that is part of the budget, consider whether ongoing SEO spending makes sense separately from the build.
Calculate the first year—not just launch day
For comparison, define year one as implementation plus 12 operating months. Use the same period for every proposal, even when development takes several months.
Separate expenses into these categories:
| Category | What to record |
|---|---|
| One-time work | Planning, design, development, content, content entry, integration setup, migration, and launch work |
| Recurring expenses | Domain, hosting or platform plan, licenses, business email, integration subscriptions, and agreed support |
| Variable charges | Usage-based services and transaction-related fees, where applicable |
| Budget adjustments | Applicable taxes and an allowance for approved changes |
Check bundles before adding costs. If a platform plan includes hosting, do not add another hosting charge. Apply the same check to licenses and support. If business email is already paid for elsewhere, show it as an existing expense rather than a new purchase.
A hypothetical first-year budget
The following amounts are illustrative USD figures, not a quote, a recommended budget, or Kohl Digital pricing.
| Item | Illustrative cost |
|---|---|
| Build | $4,000 |
| Content | $800 |
| Hosting: 12 months | $360 |
| Domain: one year | $20 |
| Licenses: one year | $120 |
| Support: 12 months | $1,200 |
| Subtotal | $6,500 |
| Change allowance | $500 |
| Planning total | $7,000 |
This example assumes no additional email, integration, usage, or tax charges. Those lines still need an explicit answer in a real budget; omission does not establish that they cost nothing. The allowance is reserved money, not necessarily money you will spend.
Keep annual cash cost separate from owner and staff time. Both matter, but combining them without explanation makes proposals harder to compare.
Agree on acceptance, ownership, and post-launch responsibility
A proposal should explain how you will decide that the work is complete. I would ask for observable acceptance checks rather than “website delivered.” Depending on scope, those checks could include:
- Agreed mobile layouts display correctly on the specified test devices or browsers.
- Form submissions reach the intended staff, with the expected information.
- Included booking or payment workflows pass agreed tests; a test payment is distinguished from a completed customer purchase.
- Authorized staff can sign in and edit the agreed content.
- Specified analytics and SEO deliverables are implemented and demonstrated.
These are suggested contract checks, not universal platform requirements. Agree on the test scope and who approves completion before work begins.
Put control and handover in writing
Record who controls the domain registration, hosting, platform accounts, and connected services. Specify content rights, code and design rights where applicable, third-party license terms, and export limitations. Paying for a website does not automatically transfer ownership of proprietary platform software or every third-party asset.
The handover should identify credentials or access invitations, any agreed training, and who manages backups and restoration. Ask what you can take with you if you change providers and what would require rebuilding.
Separate post-launch responsibilities explicitly:
- Defect correction: what counts as a defect, how it is reported, and the applicable terms.
- Maintenance: the updates, monitoring, or backup work included in the agreement.
- New work: how content additions, new features, and other changes are approved and charged.
- Renewals and cancellation: who pays, who receives notices, and what happens when a subscription or service agreement ends.
For the operational side, a practical website maintenance check can help identify tasks that need an assigned owner.
Use this worksheet to compare website quotes
Copy this worksheet into a spreadsheet. Replace the prompts with quantities and specific requirements. In the cost columns, record A and B separately; label each recurring amount with its billing term.
| Requirement / quantity | Buyer supplies | Acceptance check | Proposal A / B inclusion | One-time USD: A / B | Recurring USD and term: A / B | Responsible party | Exclusions |
|---|---|---|---|---|---|---|---|
| Pages, layouts, design approach | Page list, brand assets | Agreed pages and layouts approved | — | — | — | — | — |
| Copy, images, content entry | Drafts or approved assets | Agreed content published | — | — | — | — | — |
| Forms and integrations | Access, workflow rules | Agreed end-to-end tests pass | — | — | — | — | — |
| Revision rounds | Consolidated feedback | Included rounds completed | — | — | — | — | — |
| Launch, analytics, SEO setup | Account access, approvals | Listed launch checks pass | — | — | — | — | — |
| Handover and rights | Authorized account holders | Access, rights, training documented | — | — | — | — | — |
| Support and defect correction | Named contact | Scope and reporting terms agreed | — | — | — | — | — |
| Hosting, licenses, renewals | Existing subscriptions | Billing and renewal owners named | — | — | — | — | — |
| Changes and cancellation | Approval authority | Charges and exit terms documented | — | — | — | — | — |
Replace every dash with an answer. Mark unknowns “not specified,” not $0. Where proposals differ, ask each provider to price the same requirement or clearly exclude it. Then request revised implementation and first-year totals without double-counting bundled items.
If you want help building around customer needs, clear content, useful functionality, and inquiry paths, Kohl Digital’s website development service is an option.
Your next step is to send the same completed scope to each provider and resolve every “not specified” item before accepting a proposal. That gives you a budget you can explain—and a clear account of what the business is buying.