Skip to content

Insights ·

How to Choose a Design Studio: Quote and Delivery Checks

When choosing a design studio for a company website, do not start by chasing the lowest number. Check whether the quote and the delivery terms are clear. A quote should spell out scope, revision rounds, exclusions, milestones and post-launch service. Delivery should cover source files, CMS and account ownership, training notes and a defect-fix window. Signing before scope is clear often leads to rework. Before kickoff, also align on the materials the client should prepare for a redesign.

When a company asks a design studio to build a website, the first question is often "about how much." Price matters, but a steadier approach is to see whether the quote and the delivery terms are written clearly. If the scope does not match, a low price turns into rework. If delivery is incomplete, updating content or renewing the domain later gets stuck.

This article is a checklist for what to read in the quote and in delivery. For template versus custom, see Brand website: template or custom, how to decide. For materials the client should hand over before a redesign starts, see Website redesign: what materials the client should give the studio. Here we only cover how to read quote and delivery when choosing a studio.

1. Quote: align scope before the number

A single total is not enough. Check at least these five points:

  1. Is the scope explicit? Design only, or also interaction, front-end development, a content CMS, multilingual pages, a mini program? Is each item listed. If scope is one vague sentence, extra pages, languages or a CMS later tend to become "extra fees."
  2. How are revision rounds counted? How many rounds for key pages; do structure changes or a full restyle count as the same round. How overages are priced should be in the quote, not only oral.
  3. What is excluded? Copywriting, photography, domain and hosting, filing help, third-party licenses, and post-launch content ops are often outside the base quote. Clear exclusions prevent later disputes.
  4. Timeline and milestones. Dates for confirmed structure, confirmed design and launch acceptance; what happens if either side slips. "About two months" with no milestones is hard to track together.
  5. What is included after launch? How long defects are fixed; whether content updates are trained for your team or sold as separate maintenance. Ongoing work after launch is covered in What to keep doing after a website launches.

FIM's public pricing note is: after discussing needs, each project is quoted on its own, with design, development and follow-on service listed in the scope. Use the same standard when asking other studios—not who names the lowest figure orally, but who writes the scope clearly.

2. Delivery: more than a site that opens

Delivery is not only "the URL works." Check these six items:

  1. Design source files. Who owns editable logo, layout and component files, and where they live; whether a later studio or your own team can continue from them.
  2. Front end and CMS. Admin accounts, roles and an update guide; whether marketing can edit news and products without calling development every time.
  3. Domain, hosting, filing and analytics. Whether registration is under the brand; which mailbox gets expiry notices; whether analytics and webmaster accounts are in your name.
  4. Account list. Domain, host, email, code repo, design files and third-party services, each with owner and handover path. Missing one item can block you months later.
  5. Training and notes. Written or recorded steps for updating an article, swapping an image or adding a section; whether key actions were walked through once.
  6. Defect-fix window. How long in-scope defects are fixed free after launch; what counts as a defect versus a new request.

With these six in place, the brand has truly taken over the site, not only received an address that opens.

3. How to compare: ask three studios the same sheet

Turn the five quote points and six delivery points into one sheet and ask two or three studios the same questions. Compare three things:

  • Who writes scope and exclusions more specifically;
  • Who puts account ownership and source-file handover into the contract or an attachment;
  • Who can describe practices close to your industry, not only show portfolio covers.

Price still matters, but only after scope matches. A low price with a much smaller scope usually does not save money.

4. FAQ

Quotes differ a lot—pick the cheapest?Align scope first. Some quotes exclude development or a CMS; others include multilingual and maintenance. Different scope means the numbers are not comparable. Align, then compare price.

Design only, development elsewhere?Yes. The quote should then spell out design deliverables (source files, specs, assets or component notes) and how handoff to development works, so neither side can say the other was unclear.

What is most often missing in the contract?Asset and account ownership, and the post-launch defect boundary. After page acceptance, these two gaps cause the most friction when updating content or fixing issues.

Can we get a total before the sitemap is set?You can get a range, but before signing, recalculate against the confirmed sitemap and page list. Big structure changes usually change the quote.

Summary

When choosing a design studio, check the quote for scope, revision rounds, exclusions, milestones and post-launch service; check delivery for source files, CMS, domain and hosting ownership, account list, training notes and a defect-fix window. Ask with one shared sheet before you talk price, and rework drops.

FIM's digital experience service covers strategy, design and development for websites, mini programs, apps and H5; each project is quoted after discussing needs.

← All articles