How Much Should a Small Business Spend on a Website?

DIY: spend your time before spending on a team

A website builder can be a sensible choice when the offer is simple, the budget is tight, and someone has time to handle writing, layout, and updates. Templates provide a starting point. They do not decide what belongs on a page or test the customer journey for you.

Before choosing a tool, try building the actual page you need. Check the mobile layout, form notifications, domain connection, and export options. Compare the plan that includes your required features, not just the advertised entry price. Include your own time in the decision even if it does not appear on an invoice.

Freelancers and small studios: direct access, defined capacity

A freelancer or owner-led studio can connect strategy, design, and implementation with fewer handoffs. This suits businesses that want help making decisions without coordinating a larger team. The tradeoff is capacity: clarify availability, support, and who handles work outside the person’s specialty.

Forerunner’s published $500, $1,500, and $3,000+ packages give concrete examples of scopes, not a universal pricing rule. Monthly hosting adds $50, $100, or $200 respectively, with update allowances on Growth and Custom. Review the pricing page for limits. A budget is only useful when you know who provides content, which integrations are supported, and what happens after launch.

Agencies: pay for the team you actually need

A broader team may be appropriate when the project combines research, brand strategy, copywriting, photography, development, and stakeholder coordination. A larger organization can also need procurement, documentation, or service coverage a solo studio cannot reasonably provide.

Ask who will do the work and how responsibilities are divided. A higher fee is not automatically waste, and a lower fee is not automatically value. Choose based on the capabilities the project needs and whether you will use them.

Custom development: budget for behavior as well as pages

Custom development makes sense when the site must do something an existing tool cannot adequately support. Account systems, complex quoting, inventory, or operational workflows add requirements beyond a marketing website. They also add testing, security, maintenance, and support obligations.

Start by checking whether a reputable existing service solves the problem. A supported booking integration may be easier to maintain than a bespoke scheduler. Ask for the ongoing maintenance implications alongside the initial build estimate.

Use a break-even scenario, not a revenue promise

For illustration only, if a website costs $1,500 and an additional completed job contributes $300 after direct fulfillment costs, five genuinely incremental jobs would cover the build cost before ongoing expenses and tax. That arithmetic does not predict that the website will produce those jobs.

Use your own contribution per job, not total sales revenue. Include hosting and support, consider how long you can wait, and ask how new customers will reach the site. If those inputs are unclear, keep the initial scope modest and measure before adding features.

• □What customer task will improve?
• □Where will relevant visitors come from?
• □What can the business afford without relying on hypothetical leads?
• □Who maintains the site?
• □Which features can wait for evidence?

Bring a practical brief to the first conversation

Write down your services, ideal customer, service area, primary action, content readiness, and comfortable budget range. Include the current website if there is one. A useful designer can then recommend a scope or explain why a simpler option is enough.

The aim is a site you can launch, operate, and learn from. Spending more before the offer is clear rarely solves that uncertainty.