The short answer
Put every quote on the same grid, line by line, and look for what is missing as much as what is there. Then ask each team the same short list of questions and check their live work on your own phone. Price is one row on the grid, not the whole decision.
A cheaper quote that leaves out redirects, CMS setup or support is not cheaper. It is a smaller project, and you pay for the gap later.
Put quotes on one grid
Copy this grid into a spreadsheet, one column per quote. Fill a cell only with what the quote says in writing. If it does not say, write "not stated" and ask.
| Line | Quote A | Quote B | Quote C |
|---|---|---|---|
| Unique layouts counted | |||
| CMS collections and templates | |||
| Design included, and review rounds | |||
| Copy written by | |||
| Integrations, listed by tool | |||
| Content moved, and redirects | |||
| SEO basics: titles, descriptions, schema, sitemap | |||
| Analytics and form tracking | |||
| Testing: screen sizes, forms, speed | |||
| Training for your editors | |||
| Support after launch, and what it covers | |||
| Timeline and what it depends on | |||
| Price, payment terms, what is extra |
When the grid is full, the price differences usually make sense. One team counted twelve layouts and another counted six. One includes copy and another expects it from you. Now you can compare like with like, or ask a team to re-quote on the same scope.
What included should mean
"Included" is the most important word in a quote and the least defined. For each line, a good quote answers three things: what exactly, how much of it, and how you know it is done.
| Vague line | What to ask for instead |
|---|---|
| SEO included | Which pages get titles, descriptions and structured data, and who writes them |
| Responsive design | Which screen sizes are designed, and which are only adjusted in the build |
| CMS setup | Which collections, which fields, and whether existing content is loaded |
| Revisions | How many rounds, at which stages, and what counts as a new request |
| Support | How long, what kind of changes, and how fast replies come |
| Migration | How many pages and posts, and who checks redirects after launch |
None of this needs to be long. A line like "Blog collection with 8 fields; 40 existing posts imported; editors trained in a recorded call" is short and clear.
Red flags
None of these alone means a team is bad. Two or three together should make you slow down.
- A firm price before anyone asks about your editors, content or tools
- Promises of rankings, traffic or AI citations. Nobody controls those
- No live sites you can open, only images or mockups
- The site would sit in the agency's account, with no plan to move it to yours
- Support after launch is not mentioned, or is "whatever you need" with no limits
- A yes to everything, with no questions back
- The person who sells is not the person who does the work, and you cannot meet the second one
- Redirects are not mentioned on a redesign of a site that already ranks
A team that says "we do not do that, but here is who does" is often a better sign than one that says yes to every line.
Questions to ask every team
Ask everyone the same questions, in writing if you can, so you can compare answers side by side. We cover a longer list for Webflow in how to choose a Webflow agency.
- Who will do the work, and can we speak to them before we sign?
- Which platform would you use for this brief, and why that one?
- How many unique layouts and CMS collections did you count?
- How will our team edit the site, and how will you train them?
- What happens to our current URLs, and who builds the redirect map?
- Whose accounts will the site, hosting and analytics live in?
- What is not included that we might expect to be?
- How do you handle a request that is outside the scope?
- What support do we get after launch, for how long, and what does it cover?
- Can we see two live sites you built that are close to ours?
Then check those live sites yourself. Open them on your phone, click through the menus and forms, and run a page through a speed test. You will learn more in ten minutes than from any portfolio deck.
Freelancer, agency or in-house
The kind of team matters as much as the team itself. This is how we see the trade-offs. We are an agency, so weigh our view with that in mind.
| Freelancer | Agency | In-house hire | |
|---|---|---|---|
| Suits | Small, clear jobs with a finished design | Several skills at once, a firm date, ongoing help | A steady flow of work for years |
| Main strength | Direct contact, often lower cost | Cover for holidays and sickness, a range of skills | Knows your business deeply, always there |
| Main risk | One person: availability and cover | Being handed to junior staff | Hiring time, and one person's skill set |
| Ask about | Backup if they are away | Who exactly works on your site | Who reviews their work |
For the long version, see Webflow agency vs freelancer, Kookies vs a freelancer and in-house hire or agency.
Making the call
When the grid is full and the answers are in, rank the teams on three things, in this order:
- Fit to the brief. Did they understand the goal and who edits? Did they question anything?
- Completeness of the quote. How many "not stated" cells are left after you asked?
- Price for that scope. Only now compare prices, on the same scope.
Decision rule If two teams are close, pick the one whose written answers were clearer. How a team writes a quote is how it will write your scope, your updates and your handover notes.
If you want to see how we run a project from first call to launch before you decide, our process page lays out each step and what you get from it.


