On time, or a full refund.How the guarantee works

Hire Webflow developers for your agency

A Webflow developer in your Workspace, for the months you need one.

When agencies hire Webflow developers from us, it’s month by month: 40 or 80 hours from a team, or a senior developer of their own, full time. The work happens in your agency’s Webflow Workspace, in whatever class system the site already uses, and every change reaches the staging domain before the live one. Tell us which month you want to start and we’ll check capacity for it.

  • In your own Workspace
  • Staging domain first
  • The site’s own class system
  • A seat you add and remove

What a Webflow developer spends a normal month on.

After launch, most Webflow work is adding to a site that already has a structure. The trick is to add to it without leaving a second set of classes behind.

  • New pages from your Figma

    Built from the components and classes the site already has.

    • Landing and campaign pages, at every breakpoint
    • New sections added to the component library
    • Client-First kept where the site uses it, otherwise the site’s own system
    • New classes added to the class list in the handover doc
  • CMS collections and templates

    Fields named so an editor knows what each one does.

    • A new collection with its template and list pages
    • Reference fields between collections, so content is entered once
    • Content imported from a CSV and checked on the page
    • Item and collection counts checked against the site plan’s limits
  • Interactions and animation

    Each one with a reduced-motion version.

    • Load and scroll interactions built on shared classes
    • Custom-coded animation where the design needs more
    • Tested on real phones as well as in the Designer’s preview
    • Nothing that hides content while it animates
  • Forms, embeds and tracking

    Connected to the tools your client already pays for.

    • Forms sent to the CRM or email platform, and tested
    • Booking, chat and video embeds placed so they don’t slow the page
    • Analytics and ad tags, with the consent tool your client uses
    • Custom code kept in one place and listed in the handover doc
  • SEO settings and redirects

    The settings. Where pages rank is up to Google.

    • Titles and descriptions per page and per CMS template
    • A 301 for every URL that changes
    • Sitemap, canonical URLs and structured data
    • Alt text and heading order on new pages
  • Clean-up on a site someone else built

    Done in small steps, each one reviewed on staging.

    • Duplicate and unused classes merged or removed
    • Layouts that break at one breakpoint repaired
    • Slow pages: images, fonts and scripts cut back
    • Common WCAG 2.2 AA failures fixed: contrast, focus, labels

From your board to the live domain: one Webflow change.

Nothing reaches the custom domain until it has been on staging. That’s where we check a change first, and then you do.

  1. A task, with its Figma frame

    Your team writes it on your board and links the frame. Your Project Manager checks it has what the developer needs: copy, images, and which CMS items it affects.

  2. A backup is saved

    Before a larger change we save a backup of the site in Webflow, so there is a version to go back to.

  3. The change is made in the Designer

    Using the site’s existing classes, variables and components. A new class is added only when none of the existing ones fits.

  4. It’s published to staging only

    The site is published to its webflow.io staging domain and not to the custom domain. You get that link.

  5. Staging is checked, then you look

    The page is opened at 6 breakpoints, its forms are sent and its interactions are run on a phone. Flex 40 and Studio 80 put a second person on that. With a Dedicated Developer it’s the developer, with the Project Manager overseeing. Then the link is yours.

  6. It’s published to the live domain

    In a quiet hour for the site. Pages, forms and redirects are checked on live straight after.

One change, from staging to the live domain

Example Webflow update.

If one site only needs content edits, form checks and uptime monitoring, that’s a care plan, and it costs less than hours.

How a Webflow build runs, start to launch

The access a Webflow developer needs.

Everything sits in your Workspace or your client’s. We never build in a Workspace of ours and move the site over later.

Your Workspace, your client’s bill
Your Workspace
A member on your domain with the Designer role, which in Webflow needs a full seat. The seat is yours: you add it, and you remove it when the plan ends. Webflow includes one full seat for the Workspace owner and charges for more.
A client’s own Workspace
If the site lives in your client’s Workspace, Webflow lets them add an agency as a guest without using one of their seats. Your agency is the guest, and our developer works through your agency’s Workspace. Whether your agency can join as a guest depends on its Webflow Workspace plan.
The site plan
Billed to you or to your client, as now. Before adding a collection we check the plan’s limits on CMS items and collections, and tell you if the site needs a bigger one.
Connected tools
A login or a seat in whatever the site sends data to: the CRM, the email platform, analytics, the consent tool.
No repository
Webflow sites aren’t kept in Git. Custom code lives in the site’s settings and embeds, and we list it in the handover doc.
The Figma file
The file the pages are built from. We read it for missing states and breakpoints before any building starts, and ask you about the gaps.
Once the plan is over
You take the seat back. Nothing has to be exported, because the site was built where it lives.

Inside a Webflow plan, and outside it.

The hours go on the Designer and the CMS. Some Webflow jobs need a scope and a quote first, and those are listed here.

Inside the hours

  • Pages, components and CMS work in the Designer, from your Figma or ours
  • Interactions, forms, embeds, tracking and redirects
  • Page design in Figma, on Flex 40 and Studio 80
  • A staging link for every change, checked at 6 breakpoints
  • The class list and CMS notes kept up to date as the site grows

Outside them

A new store, memberships and multi-language sites, without a scope
These depend on what the site plan and the design allow. A small new store is the fixed-price Webflow Ecommerce package. The rest we scope on a call and quote a fixed price before any of it starts.
Work Webflow is the wrong tool for
Very large or heavily related content, complex user accounts, or a large catalogue or store logic beyond Webflow Ecommerce. We tell you, and suggest WordPress, Shopify, WooCommerce or a headless build.
Webflow seats and site plans
We don’t resell them. Seats are in your Workspace and on your bill.
Figma design, with a Dedicated Developer
A Dedicated Developer builds. The designs are yours to supply, or they come out of Flex 40 or Studio 80 time.
Fonts and paid embeds
Bought on your client’s account or yours. We list what a design needs before it is built.
Writing the content
CMS items are filled from what you send or import. Blog posts are a separate content writing service. Other copy, such as case studies, is not part of a plan. We can write it for an extra fee, quoted before we start.
Guaranteed search positions
We set titles, redirects and structured data correctly. Nobody controls where Google ranks a page, so we don’t promise it.

Your assigned Project Manager, and the developer in the Designer.

Webflow tasks are often small. Part of the Project Manager’s job is to group them, so the site isn’t published for each one.

  • Batching and publishing

    Your assigned Project Manager groups small tasks, so that what goes to the staging domain together is ready to go live together.

  • Keeping the class list current

    When a task adds a class or a CMS field, the Project Manager sees that it lands in the site’s documentation the same week.

  • When the developer is yours full time

    Your designers hand Figma files straight to the developer. The Project Manager looks over what is built, and your order says how often everyone meets.

A Webflow plan, from day one to the end.

Day 1
You add a seat in your Workspace for an address on your domain.
Each week
A written note from name@youragency.com, with the staging link.
Tasks arrive
On your board, with the Figma frame linked.
Changes appear on
The site’s webflow.io staging domain.
Published live
In batches, after your approval.
At the end
The site never left your Workspace. You remove the seat.

What a Webflow site is usually wired to.

Tools your client’s site already sends data to or loads. We connect them through embeds, native integrations or custom code, and list each one in the handover doc.

From design to structure

  • Figma
  • Relume
  • Finsweet Attributes

Forms and CRM

  • HubSpot
  • Typeform
  • Calendly

Motion and measurement

  • GSAP
  • Lottie
  • Google Tag Manager

Monthly hours, or one Webflow developer full time?

For most Webflow work, our pick is hours. A full-time developer makes sense once you have a queue of builds. Each card shows what its plan costs and commits you to.

Hours for pages and CMS changes

Flex 40

In the Designer

A Webflow developer, with a designer for pages that have no Figma yet and a tester for the staging check.

A Webflow queue it fits

A campaign page or two, CMS changes and small fixes across the sites you look after.

Not enough for

A new site of several templates. Order that per template.

Seats needed

One full seat in your Workspace.

What Flex 40 includes

Hours for design and build together

Studio 80

In the Designer

The same roles with twice the time, so pages can be designed in Figma and built in the same month.

A Webflow queue it fits

New pages that are designed as well as built, every month, for clients whose marketing teams keep asking.

Not enough for

A migration from another platform, which is quoted with its redirect map.

Seats needed

One full seat in your Workspace.

What Studio 80 includes

One Webflow developer, all month

Dedicated Developer

In the Designer

One senior Webflow developer, building only for your agency.

A Webflow queue it fits

Your designers produce Figma files faster than your team can build them, and there is a full site in the queue most months.

Not enough for

Design. Every page needs a finished Figma frame from your side.

Seats needed

One full seat, for the same person every month.

What the plan includes

One new site from a finished Figma file? Order it per template at a fixed price.Carrying hours over, notice and the minimum term Hours by region Hire WordPress developers Hire Shopify developers

Webflow sites our team has built.

Three sites our team built on Webflow, each at a fixed price. None of them was plan work; we can’t show any site from a plan here.

  • The NTRO homepage, headed Driving Excellence in Infrastructure Measurement.

    Web design & development

    NTROBuilt on Webflow

    A national transport research organisation. One site for its services across road, rail, ports and airports, its software products, a training catalogue and a large library of news and research.

    About this project: NTRO
  • The Rare Gem homepage, headed The Most Trusted Source for Rare Gemstones Online, over a photo of cut blue gemstones.

    Webflow development

    The Rare GemBuilt on Webflow

    A dealer in rare gemstones. An online shop for certified alexandrites and padparadscha sapphires, with buying guides, a find-your-stone form and a wholesale application.

    About this project: The Rare Gem
  • The Guardian Financial homepage, headed Where stability meets investment excellence.

    Web design & development

    Guardian FinancialBuilt on Webflow

    A private mortgage investment firm. A calm, dark site that explains the fund, shows its returns as a chart and gives investors and borrowers one clear way to get in touch.

    About this project: Guardian Financial
See all work

Shown with written consent. Your own clients’ work only ever appears here if you say so.

What a monthly plan promises, in writing.

Our on-time refund is for fixed-price projects, because they have a delivery date. A plan has these four instead.

  • Never in front of your client

    We never contact, pitch or quote your client, during the plan or after it. If they contact us, we decline and tell you within 1 business day.

    Read the zero-poach terms
  • Inside your agency

    We work from accounts you create on your domain, in your tools. You own them, and you can switch any of them off at any time.

    How it works
  • On your hours

    Your assigned Project Manager works during your business day, within the working hours written in your order.

    See hours by region
  • Service targets, with a way out

    Working hours and updates are service targets, and the on-time refund doesn’t cover them. If we materially miss the same one two months running and don’t fix it within 10 business days of your written notice, you can end the plan at once and get back prepaid fees for the unused period.

    Read the Partner Agreement

What it costs to hire a Webflow developer by the month.

Our plan prices don’t change by platform. Webflow’s own seat and site plan charges are separate and go to Webflow.

Flex 40

A steady queue of mixed work, for one or several clients.

$1,200per month

Team hours · monthly · Start date agreed after a capacity check

  • 40 hours across design, dev, QA and PM
  • Assigned Project Manager
  • Weekly written update
  • Up to 20% of unused hours roll over
  • No minimum term, 30 days’ notice

Studio 80

Twice the hours, and a Project Manager on your account.

$2,200per month

Team hours · monthly · Start date agreed after a capacity check

  • 80 hours across design, dev, QA and PM
  • Dedicated Project Manager
  • Twice-weekly check-in and a shared Slack channel
  • Up to 20% of unused hours roll over
  • No minimum term, 30 days’ notice

Dedicated Developer

One senior developer on your work and nobody else’s.

$3,200per month

One person, full time · 3-month minimum · Start date agreed after a capacity check

  • One senior developer, full time
  • One developer’s hours (design and QA not included)
  • Project Manager oversight
  • Meeting rhythm agreed in your order
  • 3-month minimum, then monthly
  • Works only on your projects
  • Weekly written update

Not sure which plan?

Tell us what a normal month looks like in a 20-minute call. You get a written scope and a fixed monthly price within 2 business days of the call.

Outside a plan

For the odd job that doesn’t justify a monthly plan.

  • Ad hoc hours

    Billed in 30-minute blocks, and always quoted before we start.

    $40 per hourQuoted before we start

Freelancer, employee, per-template order or plan: which fits?

Four ways to get Webflow work done under your agency’s name, and each one is right for somebody.

A freelance Webflow developer, an employed one, a per-template order and a monthly plan, compared
Freelance Webflow developerWebflow developer you employPer-template order with usMonthly plan with us
Right whenYou have a freelancer who knows your class system, and the work comes in bursts you can plan aroundYou sell Webflow builds all year and want the developer beside your designersOne site from a finished Figma file, priced per templatePages, CMS changes and fixes arrive most weeks, across several client sites
Seat in your WorkspaceA full seat, or guest access from their own WorkspaceA full seat, all yearA full seat until handoverA full seat for as long as the plan runs
Class systemTheirs, unless you hold them to yoursYours, if someone has documented itClient-First if the site uses it, otherwise ours, documented in the handoverWhatever the site already has, with new classes added to its list
When a page has no designThey may design in the Designer as they goYour designers supply itWe design it in Figma on a Starter or Business SiteWe design it on Flex 40 and Studio 80; you do on the Dedicated Developer plan
BillingPer hour or per projectPayrollPer template, fixedPer month, fixed
DrawbackUnavailable in the week you need themA salary to cover when builds are thinSmall edits don’t justify an order eachHours you don’t use are mostly lost

Whichever you choose, ask who documents the classes. An undocumented Webflow site is slow for the next person to change, whoever that is.

Questions about hiring a Webflow developer.

Seats, Workspaces and class systems are below. What every plan promises is on the dedicated developers page.

Questions about the plans themselves

Flex 40 is $1,200 a month and buys 40 hours from a team. Studio 80 is $2,200 and buys 80. A Dedicated Developer, one senior person on your sites full time, is $3,200 a month for at least 3 months. Webflow’s charges for the seat and the site plan are separate.

Unless you have a spare one, yes. To design in your Workspace the developer needs a full seat. Webflow includes one full seat for the Workspace owner and charges for each one you add. You add the seat for an address on your domain and remove it when the plan ends. We don’t resell Webflow seats or plans.

Yes, through your agency. If the site sits in your client’s own Workspace, Webflow lets them add an agency as a guest without using one of their seats, and the agency joins on behalf of its whole Workspace. Your client adds your agency, and our developer works as a member of your Workspace on your domain, so your client sees only your name. Check that your agency’s Workspace plan includes guest access to client Workspaces.

The one the site already has. If it was built on Client-First, we keep to Client-First. If it has its own system, we follow it and add to its class list. If a site has no clear system, we tell you before we add to it and agree with you how far to tidy it.

Usually hours. Webflow work after launch tends to be small tasks, and many of them need a designer as well as a developer. Flex 40 and Studio 80 include design, and the Dedicated Developer doesn’t. Take the Dedicated Developer when builds from your own designers fill one person’s month. For a single site, a per-template order at $250 a template is simpler.

Webflow Ecommerce, yes, for a small catalogue: a new store is a fixed-price package at $3,500. For memberships and localised sites, ask us first. They depend on the site plan and on what the design needs, so we scope them on a call and quote a fixed price before starting, and we say if another platform would suit the job better.

On the site’s webflow.io staging domain. Webflow lets a site be published to that domain alone, without touching the custom domain, so you review the change at a real address. Before a larger change we also save a backup in Webflow that the site can be restored from.

Yes. Webflow imports Collection items from a CSV file, and each column is mapped to a field or left out. We prepare the file, run the import, then check the items on their template pages. First we count the items against the site plan’s CMS limit.

The Figma frame at desktop and mobile, the copy and the images. For CMS work, send the list of items or a CSV. If the file is missing a state or a breakpoint, we ask you before building anything.

Not from us. The Workspace member the developer logs in as is on your domain. Our name isn’t in the footer or the custom code, and nothing of ours shows up in your Workspace or its billing. Asked directly, the developer says they’re on your web team and doesn’t claim to be your employee.

In writing, 30 days ahead, on Flex 40 or Studio 80. A Dedicated Developer stays for a minimum of 3 months and needs the same 30 days after that. You then take back the seat. The site, its class list and its CMS notes were in your Workspace all along.

Show us your Webflow queue for a normal month. We’ll build it in your agency’s Workspace.

Next, you send a short brief and we reply with a fixed price and a delivery date in writing. You pay nothing until you sign the order.

See plansTalk through a plan