Websites engineered to rank, convert, and outlast the next replatform

A typical marketing site runs 8 to 14 weeks depending on page count, integrations, and how ready your content is. Discovery and design take the first 3 to 5 weeks, build and CMS wiring the next 4 to 6, then QA, redirects, and a staged cutover. If you have a migration with hundreds of legacy URLs or complex integrations, we scope that separately. We share a live build tracker in Aphra so you always know where we are, not a Gantt chart that goes stale in week two.

Marketing site rebuilds typically land in a mid-five to low-six-figure range, and the range is driven by scope — not by us moving numbers around. The real drivers are page template count, CMS complexity, integrations (CRM, marketing automation, personalisation), migration size, and how much net-new content and design work is required. We scope in phases so you can see exactly what each phase buys you. If a fixed budget is the constraint, we will tell you honestly what fits inside it and what does not.

WordPress and Webflow are fine tools — plenty of good sites run on them. We reach for Astro or Next.js when performance, editorial workflow, and long-term maintainability actually matter to the business, because static and hybrid rendering give us headroom on Core Web Vitals that theme-and-plugin stacks struggle to hold. It also means no plugin rot, no mystery updates breaking the site, and a codebase your next engineer can read. If your use case is genuinely better served by Webflow or WordPress, we will say so.

Default is Sanity for most B2B and marketing sites — the Studio is fast, the schema is code-first, and pricing scales sanely. Storyblok wins when non-technical editors need a strong visual editor and block-based composition. Contentful is a fit for larger enterprises with existing licensing or strict governance requirements. We pick based on your editor workflow, not what we happen to like this quarter.

This is the number one thing that goes wrong on agency rebuilds, so we treat it as engineering work, not an afterthought. Before cutover we run a full URL inventory against Search Console and analytics, build a 1:1 redirect map for every ranking or traffic-earning URL, and do a parity audit on titles, metadata, schema, and internal links. Post-launch we monitor indexation, crawl errors, and rankings daily in Aphra for the first 30 days. It ties directly into our SEO service if you want ongoing coverage.

Yes — that is the whole point of the CMS setup. We build a component library your editors can compose into pages, with preview mode, draft workflow, and role-based permissions. Landing page tests, campaign pages, and content updates ship without a developer ticket. If you need something genuinely new — a new template or integration — that is a dev task, and we scope it honestly rather than pretending everything is drag-and-drop.

Yes, through a lightweight care plan — hosting on Vercel or Netlify, dependency updates, security patching, uptime monitoring, and a monthly performance and CWV review in Aphra. You own the code and the CMS content, always. If you prefer to run hosting and maintenance in-house, we hand it over cleanly with documentation and runbooks.

We enforce LCP, INP, and CLS budgets in CI — every pull request runs Lighthouse and fails the build if it regresses. Images are optimized and served responsively, third-party scripts are audited and deferred, and fonts are self-hosted. Post-launch we track CrUX field data (real user metrics, not lab scores) in Aphra so we catch drift before it hits rankings. When marketing loads the site with a new tag or embed, we get the alert first.

Yes, and often it is the smarter play. A phased rebuild — new design system and a handful of high-value templates first, then progressive migration of the long tail — lowers risk, keeps SEO equity intact, and gets business impact live faster. Big-bang launches look decisive on a slide but tend to slip and hide problems until cutover. We will recommend the approach that fits your team, traffic, and calendar.

Yes — HubSpot, Salesforce, Marketo, Pardot, Segment, GA4, GTM, server-side tracking, and the usual suspects. Form submissions, CTA clicks, and lifecycle events get wired through cleanly, and we prefer server-side event tracking for accuracy and privacy. Everything surfaces in Aphra alongside your CWV and SEO data so you can see the full funnel in one place, not four dashboards.