We’d like to see how people use our site with Google Analytics and PostHog, including recordings of clicks and scrolls. Anything you type is hidden. Nothing runs unless you accept.OK to use Google Analytics and PostHog?Cookie Policy
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.
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.
01
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.
02
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.
03
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.
04
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.
05
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.
06
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
Update · yourclient.comPricing section on the Services page0 of 7 done
Backup of liveRestore point saved first, where the platform allows
Change made in the DesignerPricing section added, from components
Published to stagingAt yourclient.webflow.io
Internal QA on staging6 breakpoints, forms and links
Your review on stagingApproved by Your agency
Published to the live domainAt 06:30, a quiet hour for the site
Live checkedPages, forms and redirects · restore point ready
Staging yourclient.webflow.io
Push to live
Live yourclient.com
Updated 3 SepRestore point 06:12
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.