Build a websiterevenue channel.

Six to ten weeks from kickoff to live for most builds. A platform with custom integrations runs longer; a focused campaign site is quicker. We scope the timeline before anything starts, and it holds unless the brief changes.

If the structure and the stack are sound, fixing is cheaper and faster. If your team cannot edit it, it does not rank and it loads slowly, patching costs more over a year than replacing it. We will tell you which on the call, including when the answer is to leave it alone.

It is scoped on the call, because the number moves with the count of templates, the integrations involved, and whether content needs writing as well as building. We will give you a range on that call rather than after a proposal cycle.

You do, from day one. The repository, the CMS accounts, the hosting and the analytics are all in your name — we are a collaborator on them, not the owner. If you stop working with us, nothing needs to be handed back because nothing was ever held.

Yes. Content lives in a headless CMS, and handover includes training your marketing team rather than just sending logins. Most teams stop needing us for content changes within a fortnight.

If it is serving you, yes. We build on Next.js because it is faster and cheaper to run at scale, but we have left clients on WordPress where a migration would not have paid for itself. The stack is a decision, not a religion.

Technical SEO is part of the build — site structure, page speed, structured data, sitemaps and analytics all ship with it. Ongoing content production and link work is a separate engagement, and we will say plainly whether you need one.

Yes — booking systems, client portals, dashboards and internal tools, along with the product roadmap and the go-to-market that follows a launch. If the thing you need is software rather than a website, that is a conversation we have often.