A website build is usually a one-off project cost. Website ownership has recurring costs that continue after launch. These may include the platform, hosting, domains, software, maintenance, support, content and integrations. Ecommerce adds another layer.
This question comes up often in our website discovery sessions. Buyers want to know if the quoted build price is the full cost, or if more fees will follow. The honest answer is that both matter. A sound quote should separate them clearly.
One-off build costs
The build fee pays for the work needed to plan, create and launch the site. Depending on the scope, this can cover strategy, user research, site structure, copy, design, development, testing, search setup, analytics, accessibility checks, content entry, training and launch.
It may also cover a fixed set of features, such as forms, site search, a blog, gated downloads or a store. Work outside that set may be priced as an option or saved for a later phase. This can be sensible. You do not need to build every idea on day one.
See our full range of digital capabilities and examples of our website work to understand what can sit inside a build.
Platform and hosting
Your platform is the system used to run and edit the site. Hosting is the service that keeps it online. Some platforms bundle both. Others need a separate host.
That difference affects cost and workload. With a managed platform such as Webflow, hosting, security updates and much of the core platform care sit together. A WordPress site may need separate hosting plus regular updates to WordPress, its theme and its plugins. Plugin conflicts can also create support work.
This does not make one platform right for every project. It means quotes should name the platform, hosting plan and limits. Check traffic limits, content limits, form limits, storage, user seats, backups and what happens if you outgrow the plan. Our approach to Webflow websites focuses on reliable hosting and a visual editor that trained teams can use themselves.
Domains and related services
Domain names are usually renewed each year. You may need more than one. An old domain might stay active so it can send visitors to the new one. That small detail is easy to miss during a rebuild.
Email is separate from website hosting in many setups. DNS management, privacy services and an SSL certificate may also appear as separate items, though many modern hosts include SSL. Ask who owns each account, who receives renewal notices and whose card pays the bill. Your organisation should control its domain.
Third party tools
Websites often connect to other paid services. Common examples include email marketing, forms, booking tools, search, cookie consent, donation tools, digital publications, member areas and analytics products.
Each tool may have its own monthly or annual fee. Costs can rise with contacts, submissions, users or data. A feature described as included in the build may still rely on a paid service after launch. Ask for the product name, plan level, billing cycle and likely reason for an upgrade.
Maintenance and support are different
Maintenance keeps the technical base healthy. It can include software updates, backups, security checks, performance work, image checks and testing after platform changes.
Support is help from people. It may cover fixing a form, adding a page, adjusting a layout, publishing a campaign or answering a question. A platform can need little technical maintenance while your team still needs regular support.
We often see teams want both control and a safety net. They want to publish routine content themselves, then call an expert for larger changes. Your support plan should match that working style. Ask if help is billed by the hour, sold as a monthly allowance or included as a defined service. Check response times, unused hours, cancellation terms and what counts as urgent.
Content is a running cost too
A website does not stay useful by itself. Someone must write news, update staff pages, replace old documents, add campaign pages and keep facts correct. The cost may be staff time rather than an agency invoice, but it is still a cost.
In discovery, we also see small teams managing the same content in two systems. That duplication turns a simple update into a chore. A better build can reduce the work by giving content one clear home and training the team well.
Before launch, decide who owns each content type and how often it changes. If nobody has time, include content support in the running budget.
Integrations need care
An integration moves data between the website and another system, such as a CRM, email platform, enrolment tool or payment service. The build fee may cover the first setup. Ongoing costs can include the connector, API usage, monitoring and repairs when another service changes.
Do not pay for an integration simply because it sounds efficient. If a form gets only a few useful entries each year, a manual process may be fine. If staff copy hundreds of records every month, automation may save real time. Price the integration against the work it removes.
Ecommerce has extra moving parts
An online store may involve a commerce platform, payment fees, product data, stock, shipping rules, tax settings, discount codes and customer emails. Apps can add more subscriptions. Product photography, descriptions and catalogue updates also take time.
For a rebuild, confirm whether the quote covers a new store, a connection to an existing store or only links to one. Ask who will migrate products and orders, test payments, set redirects and support the store after launch. Payment processing fees are usually separate from website support.
How to compare website quotes
Put each quote into two columns: launch cost and yearly ownership cost. Then compare the same period, ideally the first three years.
- List every platform, hosting, domain and software fee.
- Mark each fee as monthly, annual, usage based or optional.
- Check what maintenance is required and who does it.
- Compare support scope, response time and exit terms.
- Add expected content and internal staff time.
- Record limits, likely upgrades and ecommerce fees.
- Confirm account ownership and how you can move providers.
A low build price can become expensive if the site is hard to edit or each small task needs a developer. A higher quote may include training, stronger components and a simpler platform that cuts future work. Ask vendors to state their assumptions so you can compare like with like.
Set a budget you can keep
Choose a site your organisation can afford to run, not just launch. Start with the platform and essential care. Add support based on your team's skill and available time. Review the plan after a few months and change it if the real workload is higher or lower.
If you want a clear view of build and ownership costs for your next website, talk to IGNITE. We can help you define the scope, choose the right platform and see the costs that continue after launch.