hq0
Blog

What to ask a web agency before you hire one

Ask the main questions first, then use a practical checklist for scope, ownership, pricing, QA, and post-launch support.

By hq0. Updated 2026-11-22.

What to ask a web agency before you hire one

If you are hiring a web agency, ask about scope, ownership, pricing, QA, and post-launch support before you compare creative work or sales talk. If those terms are not in writing, stop there.

A good first call should tell you what is included, what you own, what you pay for, and what happens after launch. If any of that is vague, the project is not ready to buy.

Start with scope, not design

Scope comes first because it sets the price, the timeline, and the handoff. The University of Illinois groups vendor questions into onboarding, payment structure, QA, and post-launch support, which is the right order for the conversation. Illinois vendor questions

Ask the agency to define the work in writing before you review mockups.

Use these questions:

If the agency cannot separate included work from extra work, every change becomes a dispute later.

Example: “Build me a site” is too vague. “Home page, about page, contact form, mobile QA, launch support” gives the agency something real to price.

Copyable scope checklist

Ask how pricing works

Price is not just the total. It is the structure behind the total. Duke lists a one-time start-up cost and a recurring maintenance fee for its Sites@Duke Pro service, while Princeton publishes an hourly model for full website projects. Duke pricing and Princeton website projects

Ask whether the price is fixed or hourly, what triggers overages, what is billed monthly, and what is due before work starts. hq0 does not publish prices, and the client sees the full price in the proposal before any work starts.

Confirm these terms:

A fair pricing model is one you can explain back to the agency in one sentence. If you cannot, keep asking.

Ask who owns the site and the files

Ownership is more than the domain name. Ask who owns the website, source files, design files, and custom code after payment and acceptance. INTA warns that work-for-hire is limited in the U.S., so contracts should use assignment language rather than assume work-for-hire alone solves ownership. INTA checklist

Also ask whether you can move the site to another professional later. A web standards interview guide says you should not be tied to the agency and should be able to take the site elsewhere or edit source files yourself. Web standards interview guide

Ask for:

If you do not get this in writing, you may pay for a site and still not fully control it.

Ask how QA and acceptance work

Testing should happen before launch, not after complaints arrive. Illinois recommends browser checks and mobile checks, and the U.S. Department of Justice procurement guide says deliverables should be inspected before acceptance and accepted only after contract terms are met. Illinois vendor questions and DOJ procurement guide

Ask:

A common mistake is accepting a site because it looks fine on one laptop. Fix it by requiring a launch checklist and a written list of open issues.

Ask what support continues after launch

Support is not optional cleanup. Virginia procurement guidance says the contract should spell out maintenance and support, who to contact, severity levels, response time, and billing structure. It also says the contract should describe user manuals, technical support manuals, application documentation, training materials, and other training needs. Virginia procurement manual

Duke’s recurring fee is a useful example of what ongoing support can cover: web hosting, security updates, materials, support, bug fixes, 24/7 monitoring, backups, and service operations support. Duke pricing

Ask these questions:

If the agency treats documentation or training as optional, you may end up with a live site and no clear way to run it.

If you are already deciding whether you need ongoing help after launch, ongoing website support is the sister product for that task.

Common mistakes and fixes

MistakeFix
Vague scopeList deliverables and exclusions before pricing
No handoff clauseAsk for written ownership and source files
No maintenance termsDefine support, response times, and billing
No launch acceptanceRequire a checklist and sign-off

A short buyer checklist for the call

If you are comparing agency-style delivery with template work or doing it yourself, hq0 versus traditional agency compares approaches, not results.

When a template or DIY route may be enough

A full agency engagement is not always necessary. If you only need a simple landing page, a template, or a quick internal site, you may not need the scope, support, or handoff process of a larger build. The trade-off is that you also take on more setup, maintenance, and ownership work yourself.

That is the point where a buyer should decide whether to buy speed, flexibility, or control. You usually do not get all three at once.

FAQ

What should I ask a web agency before hiring them?

Ask about scope, pricing, ownership of files, QA, training, and post-launch support. The University of Illinois groups those topics as the main vendor questions to cover.

Who owns the website after launch?

Check the contract. In the U.S., work-for-hire alone is limited, so ownership should be assigned in writing and the handoff should include the files you need. For your case, check with a lawyer.

Should post-launch support be included?

Yes. Virginia procurement guidance says the contract should define support contact paths, severity levels, response times, billing, and training materials.

How should agency pricing be structured?

Ask whether pricing is fixed, hourly, or split between build and ongoing support. University examples show both one-time and recurring models, so the key is whether the terms are clear before work starts.

Sources

  1. ITPF Spring 2025 / Questions to Ask (checked 2026-11-22)
  2. sitespro.duke.edu (checked 2026-11-22)
  3. www.ojp.gov (checked 2026-11-22)
  4. www.inta.org (checked 2026-11-22)
  5. Interview Guide Question 10: After the website is finished, will we own copies of the source code and asset files? (checked 2026-11-22)
Book a discovery call