Web & Design
Webflow developers: how to recognise genuine expertise
Portfolio, CMS experience, custom code and maintenance: six criteria and the key red flags to help you properly assess a Webflow developer or agency.
Short answer
You can recognise genuine Webflow expertise through verifiable live references, real CMS experience, documented custom code and a clear plan for ongoing operation after launch. A freelancer is enough for one-page sites and small websites. Once CMS structures, migration, multiple languages or ongoing development come into play, an agency is more cost-effective because capacity and maintenance are covered. Typical red flags include template customisation with no underlying plan, no maintenance service and access credentials retained by the provider.
Why your choice of Webflow developer determines the project's success
Webflow lowers the barrier to entry. Anyone can buy a template, change the colours and call themselves a “Webflow developer”. The difference between a site that serves you well for two years and one that the editorial team can no longer maintain after three months rarely comes down to design. It lies in the underlying structure: clearly defined classes, a well-planned CMS, well-built interactions and a plan for ongoing operation.
This article shows you how to recognise genuine Webflow expertise, which questions to ask in your first meeting and when a freelancer is enough – and when they are not.
Freelancer or agency: an honest comparison
Both can work. The question is how large and complex your project is, and how long it needs to last. As with choosing between an SEO freelancer or agency, it is less about ability than capacity and continuity.
| Criterion | Freelancer | Agency |
|---|---|---|
| Project size | One-page sites to small company websites | CMS projects, migrations, multilingual sites |
| Disciplines | usually one core skill (design or build) | Strategy, design, build, SEO, content in one team |
| Response time | depends on workload and holidays | team cover available, fixed SLA possible |
| Costs | lower day rate | higher day rate, less coordination overhead |
| Continuity risk | high (single point of failure) | low |
| Ongoing operation | often not included in the proposal | maintenance and ongoing development can be planned |
Kernaussage
For a one-page site or a site with five static subpages, a good freelancer is the more cost-effective choice. Once CMS structures, migration of existing content, multiple languages or ongoing development come into play, a team becomes worth the investment.
Criterion 1: a portfolio of real Webflow projects
Ask to see live links, not screenshots. Webflow sites are identifiable: the source code contains
webflow.js, and the class structure from the Designer appears in the page source. Check three things:- Are the projects still online and actively maintained?
- Are the sites distinct, or do they look like the same template in three colours?
- Is there at least one project of a similar scale to yours?
Criterion 2: CMS experience, not just design
The Webflow CMS is where beginners and professionals part ways. Ask specific questions:
- How are Collections modelled when content is reused (e.g. author, category, location)?
- How are the CMS limits accounted for – Webflow allows a limited number of Collections and fields per site?
- What does the editorial interface look like? Can someone create a post without knowing how to use the Designer?
Anyone whose only answer is “we'll do that in the Editor” has not yet been responsible for a CMS project.
Criterion 3: custom code and Finsweet
Much of what a business needs falls outside Webflow's standard features: filtering CMS lists, displaying more than 100 items in a list, tables, search and form logic. Finsweet Attributes and custom JavaScript code can handle these requirements. The question is: can your developer use both, and do they know when not to?
- Knowledge of Finsweet Attributes (CMS Load, CMS Filter, CMS Nest)
- custom JavaScript in the page or site custom code, version-controlled and documented
- understanding of the performance implications: every script adds to loading time
The best answer to a question about custom code is not “of course, anything is possible”. It is: “We'll use native features for that, because someone will still need to maintain it in two years.” Anyone who immediately suggests a script has often not looked for the simpler solution.
Criterion 4: interactions in moderation
Webflow interactions are powerful, which is precisely why they carry risks. Good developers build animations that help users find their way: loading states, brief scroll reveals and hover feedback. Poor developers build effects that stutter on smartphones and delay the first visible content. Ask about the mobile performance of a reference project and check it yourself with PageSpeed Insights.
Criterion 5: verifiable references
A reference only counts if you can call the client. Ask for two contacts from completed projects and ask three questions: Was the schedule met? What went wrong, and how was it resolved? Would you work together again?
Criterion 6: ongoing operation after launch
A website is not a project with an end date, but a system that remains in operation. Clarify the following before signing a contract:
- Who owns the Webflow Workspace, and who pays for the hosting plan?
- How are change requests handled – an allocation of hours, a flat fee or ad hoc requests?
- Who regularly checks forms, redirects and loading times?
You can find details of ongoing costs in our Webflow pricing breakdown.
Red flags: how to spot a lack of expertise
| Red flag | Why it is a problem |
|---|---|
| Template customisation with no underlying plan | Structure and content do not fit your business, and disorganised classes remain |
| No questions about goals or target audience | Design becomes a matter of taste rather than informed decisions |
| No maintenance included in the proposal | You are on your own after launch, and every small change becomes a separate job |
| The provider retains access credentials | You cannot access your own site |
| No explanation of SEO fundamentals | Redirects, metadata and structure get overlooked during the relaunch |
| Fixed price without a defined scope | Additional charges and disputes are inevitable |
Kernaussage
The most reliable question to ask in your first meeting: “What happens to the site in the twelve months after launch?” Anyone without a concrete answer is selling a template, not a system.
Practical example: Chaerry GmbH
For Chaerry GmbH, we built a website where animation and structure had to work together: animated visuals above the fold, backed by a clear site architecture that the agency can maintain itself. This is exactly where expertise shows – the animation is the visible part; the maintainable class and content structure is the valuable part.
When an agency is the better choice
Once several disciplines overlap – strategy, design, CMS setup, migration, SEO and editorial work – coordination becomes a service in its own right. An individual developer can build excellent sites, but cannot simultaneously structure content, plan redirects and train the editorial team. That is exactly what teams are for.
If you want to know how a project like this works in practice, what it costs and who works on it, our Webflow agency page covers the scope of services, price ranges and references. For an introduction to the platform itself, start with What is Webflow? and the Webflow vs. WordPress comparison.
Send us your existing site or your brief. We will give you an honest assessment of whether Webflow is a good fit and the likely scale of your project.
Gespräch vereinbarenFrequently asked questions
What does a Webflow developer do?+
A Webflow developer builds websites in Webflow's visual editor: layouts, responsive behaviour, CMS structures, interactions and custom code where needed. Good developers also take responsibility for structure, performance and the handover to the editorial team.
How do I recognise a good Webflow developer?+
Look for verifiable live references, real CMS experience, a clear class structure, documented custom code and a clear plan for ongoing operation after launch. A portfolio of recoloured templates is not proof of expertise.
Freelancer or agency for Webflow?+
A freelancer is enough for one-page sites and small websites without ongoing editorial needs. Once CMS, migration, multiple languages or continuous development come into play, a team is more cost-effective and offers better continuity.
How much does a Webflow developer cost?+
Freelancers typically charge between 60 and 110 Euro per hour, while agencies price by project. You can find a detailed breakdown by project size in our article on Webflow pricing.
What are Finsweet Attributes, and why do they matter?+
Finsweet Attributes are script extensions for Webflow that enable features such as CMS filters, loading more than 100 items or nested Collections. Familiarity with them shows that a developer understands Webflow's limitations.
Which red flags should I look out for when choosing a Webflow provider?+
Template customisation with no underlying plan, no questions about goals and target audiences, no maintenance service, access credentials retained by the provider and fixed prices without a defined scope.
Do I still need a Webflow developer after launch?+
Not for editorial content: that is what the CMS is for. For new page types, interactions, technical updates and performance checks, you should budget for a regular maintenance plan or an allocation of hours.
Who owns the Webflow project once it is built?+
You should clarify this in the contract. Ideally, the Workspace should be in your name, with the provider invited to it. This lets you retain access and control over hosting even if you change providers.
#Webflow#Agency Selection#Web & Digital
Author
Josef KujawskiManaging Director & Creative Director at Maluure
Josef leads the strategic and creative development of brands at Maluure. For over a decade, he has guided medium-sized businesses from brand positioning to digital delivery.
Managing Director of Maluure GmbH, Cologne. Specialising in corporate design, brand strategy and digital brand experiences.
Weiterlesen
Web & Design
Website Maintenance: Costs, Services and Why It Pays Off
Updates, backups, security: what website maintenance costs, what should be included, and when you can handle it yourself.
2 min read
Web & Design
WordPress Agency Cologne: When WordPress Fits and When It Doesn't
We support WordPress websites in Cologne, but we don't always recommend WordPress. Here's an honest look at when it fits and when other systems are better.
2 min read
Branding
Packaging Design Agency: What to Look for When Choosing One
From die-cut to print approval: how to recognize a good packaging design agency and what you should budget for in terms of price.
2 min read
Explore more blog topics
Web & Design
Getting an Online Shop Built: Costs, Systems, and Process
From Shopify to Webflow: which systems exist, what a professional online shop costs, and how to get from concept to first sale.
2 min read
Branding
3D Animation for Businesses: Uses, Process, and Costs
3D animation shows what cameras can't: internal workings, processes, prototypes. What it costs, when it pays off, and how production works.
6 min read
Web & Design
Getting a Landing Page Built: Costs, Structure, and What Matters
One page, one goal: what makes a good landing page, what it costs, and how it works together with Google Ads and SEO.
3 min read