Website costs in 2026 span from a few hundred dollars for basic DIY platforms to mid-five and six figures for custom enterprise builds. The final number hinges on technical complexity, content scope, integrations, and who builds it—but understanding the cost drivers lets you allocate budget to features that genuinely move the needle.
Choosing between WordPress, Shopify, Webflow, or a custom-coded solution determines your cost floor and ceiling. Managed platforms like Squarespace or Wix charge monthly subscription fees and constrain customization; you trade cost predictability for flexibility. WordPress offers a middle path—open-source core, paid premium themes, and plugin licenses—but requires hosting, maintenance, and security hardening. Headless CMS architectures (Contentful, Sanity) paired with frontend frameworks (Next.js, Gatsby) unlock performance and omnichannel publishing but demand developer expertise and higher hourly rates. Each architecture also dictates recurring expenses: Shopify's transaction fees, WordPress plugin renewals, or API usage tiers for headless setups. The platform decision ripples through every line item, so align it with your technical team's capabilities and growth trajectory before signing contracts.
A pre-built theme costs a one-time fee, typically under two hundred dollars, but customizing it to match brand guidelines still requires designer hours for color schemes, typography, and component tweaks. Fully bespoke design—wireframes, high-fidelity mockups in Figma, interactive prototypes—can consume dozens of billable hours before a single line of code is written. The iteration loop matters: three rounds of feedback built into the contract versus unlimited revisions changes the budget substantially. Accessibility compliance, responsive breakpoints for mobile and tablet, and micro-interactions (hover states, scroll animations) all add design time. Agencies often package design as a fixed milestone, while freelancers may bill hourly, making scope definition critical. If brand assets—logos, photography, iconography—don't exist yet, factor in those production costs separately. Design is where subjective preferences collide with budgets; clear stakeholder approval workflows prevent endless revisions.
Writing service pages, blog posts, product descriptions, and legal copy takes time whether you handle it internally or hire a copywriter. Professional web copy typically runs per word or per page; technical content and bilingual work (French for Quebec markets, for example) command premium rates. Photography and videography add another layer: stock images are inexpensive but generic, while custom shoots require budgeting for a photographer, location, and post-production. If the site requires structured data markup, meta descriptions, header-tag hierarchy, and keyword optimization from day one, that SEO layer increases content costs. Large e-commerce catalogs or membership sites with hundreds of pages amplify these expenses. Many budgets underestimate content because stakeholders assume existing brochures can be pasted in, but web content demands brevity, scannability, and semantic structure that print materials lack. Plan for content as a discrete workstream with its own timeline and budget allocation.
Connecting a CRM like HubSpot or Salesforce, payment gateways (Stripe, PayPal, Moneris in Canada), email marketing platforms (Mailchimp, ActiveCampaign), or booking systems introduces integration complexity. Some platforms offer native plugins; others require custom API development, webhooks, and error-handling logic. Each integration carries setup time, testing cycles, and often recurring API fees or transaction percentages. Multi-currency support for cross-border transactions, tax calculation engines compliant with CRA requirements, or inventory sync between online and brick-and-mortar systems all demand developer hours. The more systems that need to talk to each other in real time, the higher the build cost and the more critical ongoing monitoring becomes. Free plugins exist for common integrations, but they may lack the customization, security, or support that a paid solution or custom build provides. Budget integrations as separate line items rather than assuming they are included in a base package.
Offshore freelancers on platforms like Upwork advertise low hourly rates but often require detailed specifications, tight project management, and acceptance of timezone and communication friction. Domestic freelancers offer proximity and language alignment at mid-tier rates; their capacity is limited, and a single contractor falling ill can stall the project. Mid-sized agencies bring process, account management, and multi-disciplinary teams—designers, developers, strategists—but layer overhead into their pricing. Senior-led agencies or boutique studios charge premium rates in exchange for strategic guidance, fewer revisions due to experience, and accountability. In-house builds shift salary and benefits onto your books; they make sense for ongoing platform development but carry high fixed costs for a one-time launch. Each model also affects intellectual property ownership, post-launch support availability, and the speed at which changes can be deployed. The cheapest option rarely delivers the lowest total cost of ownership when rework, delays, and missed strategic opportunities are factored in.
A website is not a one-time purchase; it is an asset that requires continuous investment. Hosting costs range from shared plans at a few dollars monthly to dedicated or cloud infrastructure running hundreds per month for high-traffic or compliance-sensitive sites. SSL certificates, domain renewals, CDN usage, and backup storage add recurring line items. Security patches, plugin updates, and CMS version upgrades prevent vulnerabilities; neglecting them invites breaches and downtime. Content updates—adding blog posts, rotating banners, publishing case studies—demand either staff time or a retainer with your agency. Conversion-rate optimization, A/B testing, and performance monitoring generate ongoing analytics and tool subscriptions. Many organizations underestimate these costs and find their site stale or insecure within a year. Budget at least fifteen to twenty-five percent of the initial build cost annually for maintenance and iteration, more if the site is a revenue driver or operates in a regulated industry.
Fixed-price contracts offer budget certainty but require exhaustive upfront scope definition; any deviation triggers change orders and delays. They work well for straightforward projects with clear deliverables—brochure sites, template-based builds—but penalize discovery and iteration. Time-and-materials agreements bill actual hours against a roadmap; they accommodate evolving requirements and strategic pivots but demand trust and active oversight to prevent runaway costs. Hybrid models cap total spend while allowing flexibility within phases. The contract structure also governs how risk is shared: fixed-bid shifts risk to the vendor, who may pad estimates or cut corners to preserve margin, while time-and-materials places risk on the client, who must manage scope and prioritize features. Whichever model you choose, ensure the contract specifies ownership of code and content, post-launch support terms, and the process for handling out-of-scope requests. Misaligned expectations on these points cause more disputes than the billing model itself.
Estimates reflect different assumptions about scope, platform, design originality, content volume, integrations, and the provider's overhead and expertise. A freelancer quoting a basic WordPress site with a purchased theme will come in far below an agency proposing custom design, original copywriting, CRM integration, and strategic consulting. Without a shared requirements document, you are comparing different products under the same label.
Content creation, third-party service subscriptions, SSL and security tools, CDN usage, ongoing maintenance retainers, training for internal staff, and contingency for scope changes are frequently underestimated. Many clients also forget to budget for pre-launch user testing, accessibility audits, and post-launch marketing to drive traffic. These costs can equal or exceed the build itself over the first year.
In-house development shifts costs to salaries, benefits, and opportunity cost—your team is not working on other priorities. Agencies bundle expertise, tooling, and process but charge for overhead and profit. For one-off projects, agencies typically deliver faster and with broader skill sets. For ongoing platform work or proprietary systems, in-house makes sense. The crossover point depends on your project pipeline and internal technical maturity.
Plan for fifteen to twenty-five percent of the initial build cost each year, covering hosting, security patches, plugin updates, content revisions, and minor feature enhancements. High-traffic e-commerce sites, membership platforms, or regulated industries may require more. Neglecting maintenance leads to security vulnerabilities, broken functionality, and declining search visibility, which cost far more to remediate than proactive upkeep.
Template platforms work well for straightforward marketing sites, portfolios, or small e-commerce catalogs where speed and cost matter more than differentiation. Custom builds are warranted when you need unique user flows, complex integrations, proprietary features, or scalability beyond what SaaS platforms support. Evaluate your competitive landscape, technical requirements, and growth roadmap rather than defaulting to either extreme.
A basic informational site with a template, modest customization, and stock content typically runs a few thousand dollars. A fully custom small-business site with original design, professional copy, lead-capture forms, and foundational SEO sits in the mid-four to low-five figures. Adding e-commerce, membership areas, or advanced integrations pushes costs higher. The defining variables are design originality, content volume, platform complexity, and the expertise level of who builds it.