The four common paths
Once the sitemap from Chapter 1 exists, the next decision is what to build it on. Almost every business site is built one of four ways, and each comes with a genuinely different set of tradeoffs — there is no universally "best" option, only the best fit for a specific budget, timeline and team.
WordPress (self-hosted). An open-source content management system that now powers a large share of the web. It is flexible, has a plugin for nearly anything, and can be as simple or as complex as the site needs. The tradeoff is that flexibility comes with responsibility — someone has to keep the core, theme and plugins updated, or the site becomes a security risk (Chapter 7 covers this in detail).
Shopify (and similar hosted e-commerce platforms). A fully hosted store builder purpose-built for selling products online. Hosting, security patching and PCI-compliant checkout are handled for you, which removes a huge amount of maintenance burden. The tradeoff is a recurring subscription fee, transaction fees on some plans, and less flexibility outside what the platform and its app ecosystem allow.
No-code builders (Webflow, Wix, Squarespace and similar). Visual, drag-and-drop tools that let you design and publish a site without writing code. They are fast to launch and easy for a non-technical owner to update afterward. The tradeoff is a ceiling on customisation — at some point a specific feature or integration simply is not possible on the platform, and migrating off it later can mean rebuilding from scratch.
Fully custom-coded. A site built from raw HTML/CSS/JavaScript or a code framework, with no page-builder layer in between. This gives complete control over performance, structure and functionality. The tradeoff is cost and time up front, and every future change needs someone who can write code — there is no visual editor to hand to a non-technical team member.
Comparing cost, flexibility and maintenance burden
These three factors trade against each other in a fairly predictable pattern. Hosted platforms (Shopify, no-code builders) trade some flexibility and an ongoing subscription for low maintenance burden — you are paying, in effect, for someone else to worry about security patches, uptime and infrastructure. WordPress sits in the middle: lower recurring cost than a hosted platform in many cases, high flexibility through its plugin ecosystem, but real maintenance responsibility that either the owner or a developer has to own. Fully custom code sits at the far end: the highest upfront cost and the most flexibility, with maintenance being whatever the codebase demands, which can range from minimal to substantial depending on how it was built.
None of these is more "professional" than the others by default — plenty of large, successful businesses run on each of the four paths. The right question is never "which platform is best," it is "which set of tradeoffs matches this project's budget, timeline, team and how often the site will need to change after launch."
When custom code is actually worth it — and when it is overkill
Custom code earns its cost when the site needs something a platform genuinely cannot do: a non-standard product configurator, a real-time booking system with unusual logic, tight integration with an internal system, or performance requirements that off-the-shelf themes cannot meet at scale. It also makes sense when a business already has, or plans to hire, the in-house or agency capacity to maintain code long-term.
It is overkill for the far more common case: a business that needs a clean five-to-fifteen page site, a straightforward product catalogue, or a booking form that any established plugin already handles well. In that case, custom code adds cost and fragility without adding anything the visitor can actually perceive. A useful rule of thumb: if you cannot name the specific feature that a mainstream platform cannot deliver, you probably do not need custom code yet.
- Does this site need a feature that no plugin, app or builder block already provides?
- Who will make routine content changes after launch — a non-technical staff member, or a developer?
- Is there a realistic budget and plan for ongoing maintenance, not just the initial build?
- How fast does this need to launch, and does that timeline rule any of the four paths out?
- Does the business expect to scale significantly in the next one to two years, and does the platform scale with it?
If you are choosing between WordPress and Shopify for a store, the deciding question is usually simpler than it looks: is this primarily a content-and-blog site that also sells a few things, or primarily a store? WordPress with WooCommerce leans toward the former, Shopify toward the latter.
Matching the platform to the business
A local service business collecting quote requests rarely needs more than WordPress or a no-code builder — the content is mostly static, updates are infrequent, and a plugin or built-in form handles lead capture fine. A retailer selling a genuine product catalogue online is usually better served starting on Shopify or WooCommerce than trying to bolt e-commerce onto a page builder never designed for it. A fast-growing SaaS or a business with an unusual, differentiated process is where the custom-code conversation becomes worth having seriously, ideally with a developer who can scope the actual cost against the actual benefit.
Whatever gets chosen, revisit the sitemap from Chapter 1 against it honestly. If the platform cannot cleanly produce every page on that list, that is worth knowing before any money is spent — not after.