A Webflow agency that builds sites your marketing team can edit without a developer
Your site is built in your own Webflow Workspace, with a CMS and page layouts your team can change, and the limits of your plan written down before we start.
Three parts of a Webflow site, and which one sets your limits
A Webflow agency works on three parts: the design that is built on the canvas, the CMS that holds the content, and the plan that hosts it. Webflow publishes the limits of each plan, so we read yours before we design anything. The choice between Webflow and another platform is covered under website development.
The design
Pages are built visually on the Webflow canvas, from reusable styles and components. We build a class system and a set of components from your Figma file, so a new page is assembled from parts that already match the brand.
The CMS
Blog posts, case studies, team profiles and job openings live in Collections with their own fields. We design the Collections before the pages, because the fields decide what your editors can change and what a template can show.
The plan
Webflow limits pages, CMS items and bandwidth by plan, and some features only come with a higher one. Localization, for one, is an add-on to a paid plan. We name the plan the site needs and what it costs Webflow-side, so nothing surprises you in year two.
How the site is delivered
Built in your Workspace, or built elsewhere and transferred
Two ways to deliver a Webflow site. Both end with a site you own. What differs is where it lives while it is being built and how the handover works.
Built in the builder’s WorkspaceTransferred at the end
Built in your WorkspaceYou hold it from day one
Where it is built
In the builder’s Workspace, then moved to yours
In a Workspace you create, with us added as a guest
Billing
The builder’s account carries the plan until the transfer
Your card pays Webflow for the site plan from the start
Seats
Your editors are added when the site moves
Your editors take seats you control; our guest access uses none
Review
You review a staging link, and edit once it is yours
You open the working site and edit in it as it is built
Handover
A transfer, which Webflow supports without downtime
Remove our guest access and nothing else changes
Why we build in your Workspace
It removes the handover as a risk. The site, the plan, the domain and the editing seats are yours while the work is going on, so there is no day when ownership changes hands.
The platform rules
Six things Webflow publishes that shape how we build
Five rules from Webflow’s pricing page, and one limit from web.dev. Plans changed in 2025 and 2026, so each was read on the date shown.
01
PlansWebflow
The Basic site plan has no CMS.
Webflow lists Basic at $15 a month billed yearly, with 300 static pages, 10 GB of bandwidth and no CMS. The Premium plan, from $25 a month billed yearly, adds the CMS and bandwidth tiers up to 2.5 TB a month. A site with a blog needs Premium or above, and we say so in the first estimate.
02
CMS limitsWebflow
Premium holds 20,000 CMS items in 40 Collections.
Webflow’s plan table gives Premium 20,000 CMS items and 40 Collections, and Team 20,000 items and 100 Collections. A Starter site holds 50 items and 20 Collections. A large library or a product catalog can reach those numbers, so we count items before choosing the plan.
03
LanguagesWebflow
Localization is an add-on, and Team includes two locales.
Webflow lists Localize as available with a paid site plan, translating a full site or single elements with machine learning, and more locales cost extra. The Team plan includes two locales, and starts at $2,500 a month on an annual contract. A bilingual site is priced with that add-on in view.
04
ExportWebflow
Code export leaves your CMS content behind.
Webflow’s Workspace table lists code export, clean HTML and CSS files, from the Core Workspace plan up, with a note that dynamic content such as CMS items and pages can’t be exported. Its pricing FAQ adds that forms stop working on an exported site. Leaving Webflow later means moving the content through the CMS API or a CSV and rebuilding the forms, and we keep both routes documented.
05
AccessWebflow
Agency guests don’t take up one of your seats.
Webflow’s Workspace plans let a Workspace add agency and freelancer guests without using seats; the Starter Workspace allows two teams of five guests. Seats are for your editors and designers. This is how we work in your Workspace without adding to your seat count.
06
Speedweb.dev
A good page loads its main content in 2.5 seconds or less.
Google’s web.dev sets the Core Web Vitals limits at 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint and 0.1 for Cumulative Layout Shift, measured at the 75th percentile of real visits. A Webflow site can meet them, and we test the pages on a phone to see whether yours does.
The scope
What each part of the Webflow build produces
Layout, CMS, editing, interactions, speed and search, and the forms and tracking, each with what you take away.
Design build
Your approved Figma pages built on the canvas with a consistent class naming scheme, reusable components and responsive layouts checked at each Webflow breakpoint. A section is built once and reused, so the home page and a campaign page share the same parts. You receive: the built pages in your Workspace and a short style guide naming the classes and components.
FigmaClass systemComponents
CMS structure
Collections for posts, customer stories, team profiles, locations or whatever your site holds, with the fields editors fill in and the references that link them, such as a story tagged to an industry. Each template reads from those fields. We count the items against the plan limit before building. You receive: a map of the Collections, their fields and the item count against the limit.
CollectionsReference fieldsTemplates
Editing setup
Roles that let your marketers change text, images and CMS items without touching the design, a staging step for changes you want reviewed, and a walkthrough with the people who will use it. Where a change would break the design, we build a field so the change is made in the CMS instead. You receive: an editing guide with screenshots of your own site, and the walkthrough.
Editor roleStagingPublishing
Interactions and custom code
Scroll and hover effects built with Webflow’s interactions, and custom code only where the canvas can’t do the job, such as a calculator, a map or a tracking snippet. Each piece of code sits in one named location with a description. Code adds weight, so we weigh it against the page’s speed. You receive: the list of scripts and embeds, where each lives and what it does.
GSAP interactionsCustom codeEmbeds
Speed and search setup
Image sizes and formats, font loading and script weight set so key pages meet the Core Web Vitals limits on a phone, plus title and description fields on every template, a sitemap, canonical tags and 301 redirects from your old URLs. Redirects keep old links working; no one controls rankings. You receive: the speed report before and after, and the redirect map.
Core Web VitalsRedirectsSitemap
Forms, tracking and handover
Forms that deliver to your inbox or CRM, tested with a real submission, and analytics events for form sends and key clicks. The site, plan, domain and every account stay in your name, and our guest access is yours to remove. You receive: the test submission record, the event list and a handover sheet of what is where.
HubSpotGA4Tag Manager
How it runs
Plan the Collections, build the pages, move the old site, hand it over
Each stage is signed off in your Workspace and leaves a document behind.
collection-map.csv
Collection map
Sample · Sample Northgate Software
Collection
Items
Key fields
Blog posts
84
Title, author, topic, body, cover image
Customer stories
14
Company, industry, result, quote
Integrations
36
Name, logo, category, setup steps
Team profiles
12
Name, role, photo, short bio
Help articles
48
Title, product area, body, related articles
Job openings
6
Title, team, location, apply link
200 items in 6 Collections, plus 22 static pages, so 222 pages in all. The Premium plan allows 20,000 items and 40 Collections, so the site has room to grow.
Build checklist
Sample · Sample Northgate Software
Item
Status
Checked on
Class system and style guide
Done
Naming scheme applied to all 22 pages
Components
14 built
Header, footer, hero, logo row, form, cards
CMS templates
6 of 6
One per Collection, filled from the fields
Responsive layouts
Done
Each Webflow breakpoint
Editor role trial
Done
Two marketers edited a post and a story
Interactions and custom code
3 items
Scroll reveal, pricing calculator, tag script
Custom code is limited to the calculator and the tag script, each placed in one named location and described in the handover sheet.
Redirect map
Sample · Sample Northgate Software
Group
Old URLs
Goes to
Blog posts
84
Same slug under /blog, 301
Customer stories
14
Same slug under /customers, 301
Integrations and help articles
84
Matching new page, 301
Static pages kept
22
Matching new page, 301
Team and jobs
18
Matching new page, 301
Old tag and archive pages
16
Merged into the nearest category page
238 old URLs in all: 222 redirected one to one and 16 merged into category pages. Redirects keep old links working, but no one can promise search traffic holds exactly, so we compare before and after.
Launch report
Sample · Sample Northgate Software
Measure
Old site
New site
Lighthouse performance, phone
52
91
Largest Contentful Paint, phone
4.4 seconds
2.2 seconds
Cumulative Layout Shift
0.21
0.02
Content edits that need a developer
Most, on the old site
None in the six Collections
Test form submission
Not recorded
Arrived in the CRM
Guest access for Webzenia
None
Active until you remove it
Median of 5 runs on the home page, using the same method each time. These are lab runs. Google’s limits are 2.5 seconds and 0.1, measured on real visits at the 75th percentile.
Our stack
What the Webflow build is made and tested with
What the Webflow work is designed, built and measured with. Pick one for the detail.
Webflow
Why Webflow
Webflow is an independent visual site builder with a built-in CMS and hosting, one platform choice among several.
How we use it
We build in a Workspace you own, as a guest, so the site, the plan and the editing seats are yours from the first day.
Design controlEditor controlCode
WebflowClean
WixBloated
TemplatesGeneric
Questions
Webflow development, answered
A Webflow site starts at $8,000, and larger sites start at $15,000. The price is fixed and written down after we plan the site map and Collections. What moves a quote is the number of unique page designs, how many CMS Collections and items must be built or migrated, how many languages the site needs and whether custom code is involved. Webflow’s own plan fee is separate and is paid to Webflow from your account.
FAQ · 01
Webflow sets those fees. On October 9, 2026 its pricing page listed Basic at $15 a month and Premium at $25 a month, both billed yearly, with Premium adding the CMS and bandwidth tiers. The Team plan starts at $2,500 a month on an annual contract. Workspace plans are priced separately. We name the plan your site needs in the first estimate.
FAQ · 02
It depends on who edits the site. Webflow suits a marketing team that wants to change pages visually and doesn’t want to manage plugins, updates and hosting. WordPress is software you host and update yourself, with plugins for niche features. We pick from your team and your content, and the scope names the platform and the reason. If WordPress fits better, we say so.
FAQ · 03
Yes, for text, images, CMS items and the page content the design allows. Webflow has a content editing role that changes page content but not the design, and we build the Collections so that most changes are fields rather than layout edits. A change to the design itself, such as a new section type, still needs someone who knows the canvas.
FAQ · 04
It depends on the plan. On October 9, 2026 Basic allowed 300 static pages and no CMS, Premium allowed 20,000 CMS items in 40 Collections, and Team allowed 20,000 items in 100 Collections with 500 static pages. We count your content before choosing a plan, and tell you how much room is left.
FAQ · 05
You own the Workspace, the site, the domain and the plan, because we build in your account. Leaving is possible but takes work. Webflow’s code export gives clean HTML and CSS from the Core Workspace plan up, but dynamic content such as CMS items can’t be exported that way, and Webflow’s pricing FAQ says forms stop working on an exported site. We document how the CMS content can be pulled out through the API or a CSV, and which forms would need rebuilding.
FAQ · 06
We can move the content and map the old URLs to their new pages with a 301 redirect, then test the redirects before the switch. That keeps old links and bookmarks working. It does not promise rankings, which depend on far more than a move. We compare Search Console data before and after and report what changed.
FAQ · 07
Yes, through Webflow Localize, which translates a full site or single elements and is an add-on to a paid site plan. The Team plan includes two locales. Machine translation is a first draft, so a person who reads the language should review pages that matter, and we plan time for it. Extra locales cost extra, so we price languages early.
FAQ · 08
It can be both, and it can be neither if the build is careless. Page weight, large images, fonts and added scripts decide speed, and we test on a phone against Google’s limits. Accessibility depends on structure, contrast, labels and keyboard use, which we build to WCAG 2.2 AA. Webflow gives the tools; the build decides the result.
FAQ · 09
The site is yours, so your team or any Webflow developer can carry on. We can stay on as a guest in your Workspace for fixes and new pages, scoped and priced before the work starts. Ongoing care is covered under website maintenance, and your editors handle everyday changes themselves.
FAQ · 10
Both. Webflow takes custom code and embeds, and we use them for things like calculators, maps and third-party widgets. Each adds weight and a point of failure, so we use the canvas first and keep the list of scripts. A feature that needs accounts, payments or a database is better as a web application beside the site, and we say so when it is.
FAQ · 11
No. Leads, rankings and traffic are not things we promise. A Webflow site can be fast, tidy and easy to edit, and the visits still come from search, ads and referrals that no builder controls. We agree on what to measure before launch, such as form submissions and page speed on a phone, and report against it.
Share your current site address, or a Figma link if the site isn’t built yet. We’ll count the pages and content, check the count against Webflow’s plan limits and send back a plan with a fixed price.