Questions to Ask a Design Agency Before You Sign Anything
Protect your project with the right Questions to Ask a Design Agency Before You Sign Anything. Ensure clarity and alignment for success!
📆

Asking the right questions before signing with a design agency is the single most effective way to protect your budget, your brand, and your timeline. Founders who skip this step routinely discover misaligned deliverables, surprise invoices, and contracts that leave them without ownership of their own files. This guide covers the essential design agency inquiries you need to make before any contract is signed, organized by category so you can move through discovery calls with structure and confidence.
What to ask about agency process and project management
The questions to ask a design agency before you sign anything start with process. A polished portfolio tells you what an agency has produced. Their process tells you whether working with them will be organized or chaotic.
Start by asking how they structure their discovery phase. A credible agency will have a defined onboarding sequence, not a vague "we'll get to know your brand" answer. Ask who specifically will be on your project team, what their roles are, and how many years of experience each person brings. Team assignments should be specified in writing in the statement of work. Paying senior rates while juniors do the actual work is a common and expensive mismatch.
Communication structure is equally important. Ask which tools the agency uses for project management, whether that's Linear, Notion, Basecamp, or something else. Clarify who your single point of contact will be, how often you'll receive status updates, and what the escalation path looks like if something goes wrong. Agencies that can't answer these questions clearly are signaling that their internal operations are equally unclear.
Also ask directly about revision policies. How many rounds are included? What triggers a change order? What happens if the project runs over schedule? These aren't awkward questions. They're the baseline of professional engagement.
How is the discovery phase structured, and what do you need from us to begin?
Who will be on our project team, and what are their individual roles?
What tools do you use for communication and project tracking?
How many revision rounds are included, and what counts as a revision?
How do you handle timeline delays or scope changes mid-project?
Pro Tip: Score each agency on a consistent rubric during discovery calls, which should run 20 to 30 minutes. Assign points for clarity of process, communication structure, and team transparency. This removes the bias toward whoever has the most impressive visual portfolio.
Who owns what? Questions on IP, files, and contracts
Ownership is where founders get burned most often. As AIGA's guidance on design services contracts makes clear, contracts need to explicitly state the transfer of all design files and code repositories, not just access to a finished product. Access to a finished website is not the same as owning it. If the agency holds your Figma files, Adobe CC assets, or Git repositories, you're dependent on them for every future change.
Ask the agency directly: who owns the source files, the code, and all final deliverables upon project completion? The answer should be unambiguous. You should also ask about third-party assets, including stock photography, icon libraries, and licensed fonts. If those assets carry usage restrictions, you need to know before you publish.
Domain registration and CMS access are two more areas where vendor lock-in hides. Some agencies register domains in their own accounts and retain admin access to WordPress, Webflow, or Shopify installations. Ask who controls these accounts and what the transfer process looks like at the end of the engagement.
Undefined scope change policies cause a large share of project disputes. A meaningful portion of clients report unexpected add-on costs once a project is underway, and that pattern reflects what happens when billing and scope are left ambiguous in the original contract. Ask for documented processes around kill fees, scope additions, and offboarding.
Do we receive full ownership of all source files, code, and design assets at project completion?
Are any third-party assets licensed in ways that restrict our use?
Who registers and controls the domain and CMS admin accounts?
What is your kill fee policy if we need to end the project early?
How are scope changes documented and priced?
Pro Tip: Before signing, ask your attorney or a trusted technical advisor to review the IP and ownership clauses. A single paragraph in a contract can determine whether you own your brand assets or are renting them.
Does the agency build for performance, SEO, and long-term stability?
A website that looks good but loads slowly or loses search rankings after launch is a liability. These technical questions are among the best questions for design firms because they reveal whether the agency thinks beyond aesthetics.
Ask specifically about their SEO migration strategy. Failing to map URLs and set up proper 301 redirects during a redesign is one of the most common causes of a post-launch traffic drop, and recovery can take months when it's handled poorly. A competent agency will have a documented process for redirects, canonical tags, and metadata preservation. If they look confused by the question, that's your answer.
Mobile performance is non-negotiable. Deloitte and Google's joint research on page speed found that a 0.1-second improvement in mobile load time increased retail conversion rates by 8.4% and average order value by 9.2%, a real revenue impact from a change most users would never consciously notice. Ask whether they build mobile-first, what their target load time is, and how they test against Google's Core Web Vitals. These are measurable benchmarks, not opinions.
Post-launch support is where many agencies go quiet. Ask what happens after the site goes live. Is there a warranty period for bugs? What are the SLA terms for critical issues? Clear escalation paths and defined SLAs protect site stability and give you recourse when something breaks at 2 a.m. on a Monday.
How do you handle URL mapping and redirects during a redesign to protect SEO?
What is your target page load time, and how do you test Core Web Vitals?
Who manages hosting, security, and backups during and after the project?
What post-launch support is included, and what are your SLA terms?
How do you track and report on performance after launch?
How to evaluate agency fit beyond the portfolio
A portfolio shows finished work. It doesn't show how the agency handled a client who changed direction three times, a developer who went silent mid-sprint, or a launch that had to be delayed. Design agency evaluation questions that probe for real-world behavior are far more revealing than any case study.
Ask for recent case studies with measurable outcomes, not just visual results. Conversion rate improvements, organic traffic growth, and reduced bounce rates are the metrics that connect design to business performance. If an agency can only show you how something looks, they aren't thinking about how it works.
When checking references, go beyond "were you satisfied?" Probe references on how the agency communicated during difficult moments, how they handled scope disputes, and whether they'd hire them again for a more complex project. These questions surface the agency's character, not just their capability.
The best agencies operate as strategic consultants, questioning assumptions and pushing back on briefs to solve actual business problems rather than executing requests blindly. If an agency agrees with everything you say in a discovery call, that's a warning sign. You want a partner who will tell you when your idea won't work.
Pro Tip: Ask the agency directly: "Have you ever turned down a project, and why?" Agencies that have declined work because of misalignment are agencies that know their own strengths. That kind of self-awareness protects you.
Indicator | What it signals |
|---|---|
Measurable case study results | Agency connects design decisions to business outcomes |
Pushback on your brief | Consultative mindset, not order-taking |
Named team in the proposal | Accountability and transparency |
Documented scope change process | Operational maturity |
References who describe hard moments | Real partnership experience |
Key takeaways
Choosing a design agency without asking these questions first is how founders lose ownership of their assets, absorb hidden costs, and end up with a site that underperforms.
Point | Details |
|---|---|
Process transparency matters | Ask about discovery structure, team roles, and communication tools before anything else. |
Ownership must be explicit | Contracts should transfer all source files, code, and CMS access to you at project end. |
SEO and performance are non-negotiable | Confirm URL mapping, Core Web Vitals targets, and post-launch SLA terms in writing. |
Portfolio is not enough | Request measurable case studies and probe references on how the agency handles problems. |
Strategic fit beats aesthetic appeal | Agencies that push back on your brief are more valuable than those who simply agree. |
The questions founders avoid but can't afford to skip
The most revealing question you can ask a design agency is: "What would cause this project to fail?" Most founders never ask it. They worry it sounds pessimistic or signals distrust. It does neither. It signals that you're serious.
Agencies that answer this question honestly will tell you about client-side delays, unclear feedback, and late content delivery. That answer reveals two things at once. It shows you how the agency thinks about risk, and it tells you what your own responsibilities are in making the project succeed. An agency that blames only external factors or gives a vague non-answer hasn't thought carefully about partnership.
I've seen founders walk into contracts with agencies that had beautiful portfolios and zero process documentation. Six months later, they owned a finished website but had no access to the Figma files, no documentation, and a support contract that renewed automatically at a rate they hadn't noticed in the fine print. The portfolio was irrelevant. The contract was the problem.
The uncomfortable questions are the ones that matter most. Ask what happens if the lead designer leaves mid-project. Ask how the agency has handled a client who was unhappy with the final result. Ask whether they've ever missed a launch deadline and what caused it. These questions don't make you a difficult client. They make you a prepared one.
- Arnob
Find the right agency before you sign a thing
Find Design Agency is a hand-curated directory built specifically for founders and teams who need more than a Google search to find a trustworthy design partner. Every studio listed has been reviewed for process transparency, portfolio quality, and client feedback. You can filter by location, specialty, and project type to narrow your shortlist before you ever get on a discovery call. Whether you're looking for vetted studios in New York or browsing top-rated agencies in London, Find Design Agency gives you the curated starting point that turns a stressful search into a confident decision. Start with the right list, ask the right questions, and sign with clarity.
FAQ
What are the most important questions to ask a design agency?
Ask about ownership of source files, team composition, revision policies, SEO migration strategy, and post-launch SLA terms. These cover the areas where most projects go wrong, and most contracts leave founders exposed.
How do I know if a design agency actually owns my files?
The contract must explicitly state that all source files, code repositories, Figma files, and CMS admin access transfer to you at project completion. Access to a live website is not the same as ownership of the underlying assets.
What should I look for in a design agency's case studies?
Look for measurable outcomes like conversion rate improvements, traffic growth, or reduced bounce rates. Visual results alone don't confirm that the agency connects design decisions to business performance.
How can I avoid hidden fees from a design agency?
Request a fully itemized proposal rather than a single lump-sum number, and ask specifically whether contact forms, SSL certificates, stock imagery, and plugin licenses are included in the quoted price. Unexpected add-on costs are common enough that asking upfront is worth the awkwardness.
What does it mean when an agency pushes back on my brief?
It means they're operating as strategic consultants rather than order-takers. Designers who question assumptions and push back on briefs consistently produce better outcomes because they're solving the actual problem, not just executing a request.
Recommended
More articles you might find useful
Load More
Load More



