A website is a revenue instrument, not a brochure

A well-scoped informational site runs four to six weeks from kickoff. E-commerce platforms and web applications typically take three to six months, longer where there are complex integrations or a large content migration. The variable that moves the date most is not development — it is how quickly content and approvals arrive from your side, so we plan for that explicitly.

It depends on integrations, custom functionality and content volume far more than on page count, which is why a single published figure would be wrong for most projects. We break the work into priced stages, so you approve spend against a visible plan rather than one number quoted before anyone has seen your requirements — and you get a real figure in the first conversation, not after a discovery invoice.

Headless earns its keep when you publish to several surfaces, have a large editorial team, or need the front end to evolve independently of the content store. It adds cost and moving parts, which is a poor trade for a fifteen-page marketing site with two editors. We ask how many people publish, how often, and to how many destinations — and if the answers are small, we recommend a well-configured traditional CMS and spend the difference on performance and content.

They are a ranking signal, but the stronger argument is behavioural: interaction delay on a checkout or enquiry step measurably costs completions. Interaction to Next Paint in particular exposes sites that look fast on load and then stall when a user taps something. We treat these as revenue metrics with an engineering owner, not as an SEO report line.

Every site we build is responsive by default and built against WCAG 2.2 AA. That means keyboard operability, sensible focus management, colour contrast, proper form labelling and error messaging, and testing with a screen reader — not just an automated scan. If you are selling into the public sector or a large enterprise, this is increasingly a pass/fail item in procurement, so we document conformance as part of handover.

It is already happening, and it changes what a page needs to do. Pages need clean semantic structure, accurate structured data, and the substantive facts stated plainly on the page rather than implied by imagery or hidden behind interactions. We build that way as standard. It also means your site should answer questions rather than only assert positioning — the pages that get cited are the ones that contain something specific.

Yes. Maintenance covers dependency and CMS patching, uptime and performance monitoring, backups with tested restores, and an agreed response window. Hosting can sit in your accounts or ours; we prefer yours, because it keeps the exit simple if you ever want to move.