Joachim Fauerskov
Web developer & Digital Designer
joachim@aarland.dk
+45 20 70 46 81
Thomas Bendorff
Founder & Digital Designer
thomas@aarland.dk
+45 31 43 43 94

Let's create something
exclusive together.

Thank you for your message. We will get back to you within one business day.

The message could not be sent. Please write to kontakt@aarland.dk instead.

By clicking “Accept” you consent to the storage of cookies on your device to improve website navigation, analyse website usage and assist with our marketing efforts.
Website design

How to Tell a Webflow Agency from a Template Reseller

November 2, 2026
Skrevet af
Joachim Fauerskov
Template reseller versus Webflow agency: identical template blocks against a tailored structure
Two website proposals can look alike and still not be comparable. Here are four criteria you can check yourself, and where to find them in the written proposal before you sign.
Kapitler

Two website proposals can look alike on price and still be completely different in content. That is exactly the situation this guide helps you see through. Many buyers end up with several proposals, one from a specialised Webflow agency and another from a cheap template reseller. The difference is rarely visible in the price itself. It hides in the details: architecture, components and what happens after launch.

Instead of a ranking of agency names, you get four criteria you can verify yourself in any proposal: certification, CMS architecture, custom components, and handover and support. You will learn where to find the evidence for each one and exactly what to ask. Along the way you get a checklist to take to your next proposal meeting, so you can decide on the four factors that actually drive the price, not on the number of pages.

Why two proposals can look the same and still not be comparable

Almost every web proposal uses the same words: responsive design, CMS, SEO-ready and scalable. The words are not wrong, but they do not tell you who makes the decisions behind them. Two proposals with identical wording and almost the same page count can cover very different solutions and very different risks for you as the buyer.

Price follows four factors, not the number of pages or templates, because the page count says nothing about who architects the CMS, how much is built for your specific job, or what comes with it after launch.

After reading this, you should be able to ask four questions and point to four specific places in the written proposal where the answers should be. Claims that a decision rests on should be documented, not just repeated.

Webflow's partner tiers: what a badge documents, and what it does not

Webflow describes two documented partner levels: Foundations and Certified. Some sources also mention a Premium level, but Webflow's own help pages do not describe it clearly, so ask the agency directly which level they mean. You will still come across older descriptions of the former Experts Program, which causes confusion when two proposals use different names for the same kind of partnership.

Foundations is the entry level and is open to Starter, Freelancer and Agency plans. Certified requires a pre-qualification assessment, three client sites built from scratch and a portfolio assessed against a rubric.

The claim is easy to check: Certified partners are listed in Webflow's partner directory with their tier and any distinction badges. That is where you look, not in a proposal. The badge documents platform skills and programme requirements that have been met. It says nothing about experience in your industry, about CMS architecture or about support terms after launch.

Criterion 1: Certification. Where it should appear, and what to ask

Certification is the first thing you can check, and the easiest to check wrongly. In buyer's terms, it means the work is done by someone qualified on the platform by Webflow's own standards, and that the level can be looked up in the partner directory rather than appearing as a line in an email. If you are unsure whether Webflow is the right platform for you at all, read our comparison of Webflow and WordPress.

The proposal should state three things: the agency's full name, its tier and a direct link to its partner profile. Then the claim can be checked tomorrow and a year from now.

Ask three questions that give useful answers: Who on the team is certified? Who actually does the work? And who is responsible after launch? The answer often reveals that the certified person is not the one actually building the solution.

Checkpoint: ask for the partner profile URL as a separate line in the proposal. If it cannot be provided, treat the certification claim as a sales statement, not a fact.

Criterion 2: CMS architecture. Who designs the content structure?

Certification says something about the platform. It says nothing about how your content will be structured. That is decided by the CMS architecture: how content is modelled in collections and fields, how items relate to each other through reference fields, and how editors can update text without breaking the layout. A simple sketch might look like this: a "Case studies" collection with the fields Title (text), Summary (text with a character limit), Client (reference to "Clients"), Services (multi-reference) and Image. It is an illustrative example, not a standard.

The proposal should include this as a separate section on information architecture or CMS structure, ideally with a sketch like the one above. A single line saying "the solution will be built in Webflow CMS" is not a specification.

Ask four questions: Who decides the field structure? How is content reused across pages? How is a new content type added, and by whom? Is the structure delivered with documentation?

Red flag: proposals where page count and templates are the only specification of the deliverable, and the CMS structure is only mentioned as something to be agreed along the way.

The consequence is long-term. The architecture determines your editorial freedom for years after launch, and therefore what every change costs, whatever the build cost.

Criterion 3: Custom components or borrowed templates

Once the CMS structure is in place, the components decide how much of the solution is built for your job. Custom components are designed and developed for your content types and editorial flow. Borrowed templates and component libraries are brought in and adjusted at the edges. That makes a real difference to maintenance and further development.

Component libraries are often marketed as a speed advantage. Treat that as a supplier claim, not a quality guarantee. The speed may be real, but it says nothing about how well the components fit your needs.

The proposal should list which components will be built, which will be reused, and how cards, tables and forms are handled consistently across the site. Ask: Who owns the components? Where do they live in the design and in the CMS? How are they updated? What does a new component cost later?

Checkpoint: ask for the names of any libraries or components used, and whether they are part of the delivery or a third-party dependency the agency does not control. That decides whether the solution can be developed further without the same supplier.

Criterion 4: Handover, training and what happens after launch

Once the components are delivered, the next question is who can use them. Handover should consist of named parts: full CMS access, roles and permissions set up, documentation of the structure and components, and a fixed contact person. Ask for the timing, format and recipient of each part, not just a sentence saying "it will be handed over".

Training often hides an empty promise. Ask for the number of sessions, whether they are live or recorded, who attends, what is covered, and whether written material is left behind that can be opened again in six months.

After launch, the proposal should answer what the agreed period includes, what is billed separately, how errors and change requests are reported, and how long the commitment lasts. Treat these as requirements for the specific proposal rather than an industry standard.

The hard questions: Who actually answers when you get in touch? What happens if the responsible person changes jobs? And how is the setup handed over if the partnership ends?

Checkpoint: ask for handover and support as a separate section in the proposal, so it can be compared point by point with another proposal rather than folded into a general sentence about good service.

The price logic: price follows the four factors, not the page count

Page count is easy to compare and therefore misleading. As the criteria above show, the real price hides in these four layers, not in the number of pages.

Two imagined proposals with 12 pages each illustrate the point. One includes a template-based CMS and two hours of training. The other includes its own architecture, purpose-built components and a defined training programme. The difference is in the content, not the page count.

Checkpoint: ask for the scope of delivery broken down by criterion, so proposals can be held up against each other point by point instead of being decided on a single total at the bottom of the table.

The checklist to bring to your next proposal meeting

  1. Certification: What tier does the agency hold, and what is the partner profile URL?

  2. CMS architecture: How are collections, fields and relations structured?

  3. Components: Which are built for the job, and which are reused?

  4. Handover: What do training, documentation and post-launch support include?

The order matters. Look up the certification in the partner directory before the meeting, even when the recommendation comes from a colleague or an AI. Ask the CMS and component questions in the meeting. Read the support section last, once the other answers are known.

Complete answers can be compared directly. Incomplete answers need a written follow-up. If all four are missing, pause the process rather than choosing faster.

Conclusion: four things you can check before you sign

Once you have been through the checklist, you are left with one question: can the proposal document its own claims? The difference between a specialised Webflow agency and a cheap alternative lies in four checkable factors, not in the number of pages or the size of the total.

The four checkpoints, the partner profile URL, the CMS structure in writing, the component list and the handover section, should be in the proposal, not just in the presentation. If a proposal cannot answer them, the price is not comparable, however low it looks. Aarland is a certified Webflow partner in Aarhus, and our proposals answer all four.