How I fix it · 01 / 04

Plan the CMS before the pixels.

Collections, fields and page types mapped first, so blog posts, case studies and landing pages scale without a developer.

Turn Figma into components.

Every section becomes a reusable Webflow component with clean class names. No one-off styles, no copy-paste pages.

Build clean and fast.

Optimised images, minimal custom code, no heavy interactions on mobile. Tracking and schema wired in from the start.

Launch and hand it over.

Staging link first, then launch with redirects in place. Your team gets an Editor walkthrough and a short style guide.

Planning the Webflow build0 to buildPlanning
Step 1 · plan0 / 5 live
  • HomepagePlanning…
  • Service pagesPlanning…
  • CMS collectionsPlanning…
  • Landing pagesPlanning…
  • BlogPlanning…
  1. 01 / 04

    Plan the CMS before the pixels.

    Collections, fields and page types mapped first, so blog posts, case studies and landing pages scale without a developer.

  2. 02 / 04

    Turn Figma into components.

    Every section becomes a reusable Webflow component with clean class names. No one-off styles, no copy-paste pages.

  3. 03 / 04

    Build clean and fast.

    Optimised images, minimal custom code, no heavy interactions on mobile. Tracking and schema wired in from the start.

  4. 04 / 04

    Launch and hand it over.

    Staging link first, then launch with redirects in place. Your team gets an Editor walkthrough and a short style guide.

  5. Launch day0 to buildLive
    Step 4 · launch5 / 5 live
    • Homepage✓ Live in Webflow
    • Service pages✓ Live in Webflow
    • CMS collections✓ Live in Webflow
    • Landing pages✓ Live in Webflow
    • Blog✓ Live in Webflow
    Launched: Lighthouse 95+ on mobile, CMS ready for your team.
Planning: 0
What’s included

Six things every build ships with.

Standard on every Webflow site, not add-ons.

AreaWhat’s built inWhat you get
ComponentsReusable sections with clean class namesNew pages without a developer
CMSCollections and fields planned for growthBlog, cases and landing pages that scale
PerformanceImages, fonts and interactions kept lightLighthouse 95+ on mobile
SEOMeta, schema, sitemaps and redirectsReady to rank at launch
TrackingGA4, GTM and Consent Mode v2Every lead counted from day one
HandoverEditor walkthrough and style guideYour team runs it, not me
Pricing

Fixed scope. Fixed price.

Before you sign, we agree the pages and a Lighthouse target. You see it measured at handover.

Starter$2,500Up to 8 pages · 3 weeks
  • Components from your Figma
  • CMS collections set up
Get a fixed quote
Webflow + growthComplete$7,000Full site · 6–8 weeks · fast, found, counted
  • Everything in Fullcomponents, CMS, tracking, content
  • Technical SEO auditstructure, internal links, redirects
  • Schema and AI readabilityOrganization, Service and FAQ markup
  • Offline conversionsclosed deals sent back to Google Ads
  • Leak watch for 3 monthsweekly checks after launch
Get a fixed quote
Prices exclude VAT · Webflow plan billed by Webflow, design not included

When Webflow is the right choice

Webflow fits marketing sites that change often and are run by a small team: service pages, landing pages, a blog and case studies. Hosting, security and updates are handled for you.

It’s a weaker fit when you need complex logic, a big plugin ecosystem or deep integration with an app. Then WordPress or Next.js usually wins.

A CMS structure that scales

Most Webflow sites get messy because the CMS was an afterthought. Pages get duplicated instead of driven by collections.

I plan collections and fields first: services, cases, posts, authors, FAQs. New content becomes a form to fill in, not a page to rebuild.

Fast Webflow sites

Webflow can be very fast, or very slow. Heavy interactions, huge background videos and unoptimised images are the usual causes.

I keep animations purposeful, compress media, and test on a real phone so the site passes Core Web Vitals, not just the desktop preview.

SEO and tracking in Webflow

Webflow handles the basics well, but meta fields, schema, redirects and canonical rules still need to be set up on purpose.

Tracking is often left to “add later”. GA4, Tag Manager and Consent Mode v2 go in before launch, so every lead is counted from the first day.

Handing over to your team

Your team edits content in the Webflow Editor, without touching the design. A short recorded walkthrough and a style guide show what goes where.

For bigger changes, I stay available, but the site doesn’t depend on me.

Not sure where your site stands?The free scan checks your speed, meta and schema on your real pages, in a few minutes.Run the free scan
Webflow FAQ

Webflow, answered.

Design, CMS, plans and who runs the site.

Something else?Write a line about your site. You’ll get a reply from me within one business day.

I build from your designer’s Figma. If you don’t have one, I can recommend studios I work with.

Usually CMS or Business. I check your page count and traffic before recommending one.

Content, yes, in the Editor. Layout changes stay in the Designer so the site can’t break by accident.

Yes, when meta, schema, redirects and speed are set up properly. That’s included in every build.

Yes. Forms go to HubSpot with source data, and tracking is wired through Tag Manager.

Only if your team wants simpler editing and doesn’t need plugins. There’s a separate service for that move.

Often done together