CMS websites
Webflow website development services
Webflow development is offered by freelance designers, specialist studios and general web agencies. Because the platform makes building look easy, the differences between providers show mostly in what you cannot see on launch day: how tidy the class system is, how well the CMS is structured, whether the site sits in your account, and whether your team can update it confidently. Comparing providers on these points, and on a written scope with acceptance criteria, gives you a clearer picture than comparing portfolios alone.
This page covers the stages to expect, responsibilities, what you should receive, questions to ask and warning signs. LetGetGrow builds, redesigns and maintains WordPress and Webflow websites, with the scope, cost and timeline of each project set out in a custom quotation.
Illustrative diagram
- Discovery
- Design
- Build
- Testing
- Handover
Stages to expect
Discovery
Goals, content types, plan choice.
Output: Scope and content model
Design
Key pages and components.
Output: Approved designs
Build
Style system, templates, collections.
Output: Site for review
Content and testing
Content in; devices and forms tested.
Output: Test results
Launch and handover
Domain, redirects, training.
Output: Editor guide and access
Design and build together or separately
Some providers design directly in Webflow, others design in a separate tool first and then build. Both can work. Designing in a separate tool can make review easier for complex projects; designing directly can be quicker for smaller sites. Ask how designs will be reviewed and approved before build time is spent.
Who does what
| Task | Usually |
|---|---|
| Choosing and paying for the plan | Client |
| Content and images | Client, or a copywriter |
| Style system and build | Provider |
| Collection structure | Provider, client approves |
| Domain and DNS | Client owns, provider configures |
Warning signs
Site kept in the provider's account
Moving it later may be awkward.
No mention of class conventions
Styles may become hard to maintain.
Collections built before content is planned
Restructuring later costs time.
No editor handover
Your team may avoid updating the site.
Acceptance criteria
Agree what finished means: pages match approved designs at agreed screen sizes, forms deliver to the right inboxes, collection templates display all fields correctly, redirects are in place, page titles and descriptions are set and editors can complete listed tasks. A checklist makes sign-off straightforward.
Example: choosing a provider for a start-up's Webflow site
Illustrative example — not a client case study
Situation: A start-up shortlists two Webflow providers with similar portfolios.
- Both are asked how they name classes and where the site will be hosted.
- One builds in the client's workspace and shares its class conventions; the other keeps sites in its own account.
- The start-up chooses the first and agrees acceptance criteria in the contract.
What this shows: Asking about the unseen parts made the choice clearer. This example is illustrative.
What you should receive
Ownership
- Site in your workspace
- Domain configured in your name
Documentation
- Class and component notes
- Collection field descriptions
Training
- Editor walk-through
- Guide for common tasks
Questions worth asking
How do you name classes and reuse components? How will collections be structured? Which plan do you recommend and why? How will editors be trained? What happens if we want to move off Webflow later? Clear, specific answers suggest a provider thinking beyond launch.
Support after launch
Hosted platforms remove server maintenance, but sites still need content updates, new pages and occasional fixes. Ask about a warranty period for defects and what ongoing support costs and includes.
Reading a portfolio
Look at live sites on a phone, check how quickly they load and whether animations help or distract. If possible, ask past clients how easy their site is to update.
What the contract should cover
Scope, stages and review rounds; acceptance criteria; payment milestones; ownership of designs and content; account arrangements; confidentiality; and support after launch.
Advice on the plan
A provider should recommend a Webflow plan based on your content, traffic and features, explain why, and point you to Webflow's current pricing so you can check it yourself. Be wary of a recommendation that does not account for how much CMS content you will add over the next year or two, since moving plans later is possible but may change the recurring cost.
Accessibility and performance
Ask how the provider checks accessibility, such as heading structure, alt text, keyboard navigation and contrast, and how it keeps pages fast, such as image sizing and restrained interactions. These are easier to build in than to fix after launch, and they affect everyone who visits.
Replacing an existing site
If the Webflow site replaces an older one, the provider should map old URLs to new ones and set permanent redirects, as Google recommends for site moves. Ask to review the redirect list before launch.
Questions about Webflow website development services
Who offers Webflow development?
Freelancers, specialist studios and general web agencies.
Should design happen in Webflow or separately?
Either can work; agree how designs are approved first.
Who should pay for the Webflow plan?
Usually the client, in its own account.
What should a Webflow handover contain?
Ownership, class notes, field descriptions and editor training.
How do we define when the Webflow build is finished?
A checklist of what must be true for the site to be finished.
Can we move off Webflow later?
Ask the provider and check Webflow's current export options.
Sources referenced
Platform features, guidance and rules change. We check the current versions before committing to an approach. This page is general information, not legal advice.
- Google Search Central: Move a site with URL changes (opens in a new tab) — reviewed 2026-10-30
Request a Custom Quote
Ask about Webflow website development services
Thank you — your enquiry has been sent.
We have received your message and will reply by email. If you need to add anything, email info@letgetgrow.com.