21 Questions to Ask Before Hiring a Design Agency

On this page30 sections

• Questions About Process
• 1. Walk me through your typical engagement from kickoff to first deliverable.
• 2. How do you handle scope changes and revision requests?
• 3. What does your feedback and review process look like?
• 4. How do you handle disagreements about design direction?
• Questions About Team
• 5. Who specifically will work on my account?
• 6. What is the designer's experience with B2B SaaS specifically?
• 7. What happens if my assigned designer leaves or is unavailable?
• Questions About Pricing
• 8. What's included in the monthly retainer (or project fee)?
• 9. What gets billed outside of the agreed fee?
• 10. What is the minimum commitment and what happens if we need to stop?
• Questions About IP
• 11. Who owns the work when the project ends?
• 12. Do you maintain the right to show this work in your portfolio?
• Questions About Results
• 13. How do you define and measure success on a project?
• 14. Can you share a case study where design work led to a measurable outcome, positive or negative?
• Questions About Communication
• 15. What does a normal working week look like with you?
• Questions About Collaboration Process and Deliverable Timelines
• 16. Walk me through the collaboration process from kickoff to first deliverable.
• 17. What is the timeline for each type of deliverable, and what makes it slip?
• 18. How many revision rounds are included, and how long does a round take?
• 19. Who reviews and approves on your side, and what happens if our feedback is late?
• 20. What do you need from us, and by when?
• 21. How do finished deliverables reach engineering?
• How to Use These Questions
• The Alternative to Asking All of This

Hiring a design agency without asking the right questions is how founders end up locked into a six-month retainer with a junior designer doing the work while a senior designer was in the sales presentation. The agency model has real advantages, but it also has real structural risks that aren't visible until you're already committed. The investment is significant, so the due diligence needs to match: companies that excel in design grow revenue 32% faster than industry peers (McKinsey Design Index, 2018), but that return only materialises when the agency relationship is structured correctly.

These 21 questions are designed to reveal the actual working relationship before you sign. Some of the answers will be obvious. Others will make an agency visibly uncomfortable, and that discomfort is often the most useful signal.

---

Questions About Process

1. Walk me through your typical engagement from kickoff to first deliverable.

This is the most important question you can ask. The answer reveals the real timeline, not the timeline in the proposal.

A typical agency engagement involves: a kickoff call, a discovery phase (1–2 weeks), wireframes or low-fidelity concepts (1–2 weeks), review cycle, high-fidelity design (2–3 weeks), another review cycle, and then delivery. You're looking at 6–10 weeks before you have something you can hand to engineering.

That's not necessarily bad, if you have time, if the scope is large, if the discovery is valuable. But if you're expecting to see design work in two weeks, this is the wrong model for you.

Red flag: vague, unspecific answers. "We have an agile process that adapts to client needs" doesn't tell you anything. Push for a specific week-by-week breakdown.

2. How do you handle scope changes and revision requests?

Scope creep is the primary source of friction in agency relationships. Get specific: what counts as a revision (included) vs. a scope change (billed extra)? How many revision rounds are included? What happens if you want to change direction mid-project?

Agencies that have vague revision policies tend to be agencies that bill for everything or agencies that let scope creep drag the project on indefinitely. Neither is good.

3. What does your feedback and review process look like?

How do you share feedback? Is it async (Figma comments, Loom videos) or sync (weekly calls)? What format should your feedback take? How much time do you have between receiving work and the deadline to respond?

This matters because your ability to give good feedback directly determines the quality of the output. If the agency's process doesn't accommodate how your team works, if you're remote and async and they want scheduled review calls, you'll have friction every week.

4. How do you handle disagreements about design direction?

Good agencies push back. They'll tell you when they think a direction is wrong, but they should be able to do it with reasons, not just preference.

What you're listening for: does the agency have a process for resolving creative disagreements, or do they just defer to the client? Deference sounds nice but produces mediocre work. An agency with a point of view produces better results.

---

Questions About Team

5. Who specifically will work on my account?

This is the single most common source of agency disappointment. The senior designer you met in the pitch is often not the designer who does the work. The work goes to a junior designer, sometimes offshore, who gets occasional review from the senior.

Ask: "Can I meet the designer(s) who will actually execute my project?" If they hedge or pivot to talking about "the team" generically, that's a red flag.

For a smaller studio or subscription, this is simpler; you're working directly with the designer. For a larger agency with 30+ staff, get explicit clarity on who your day-to-day designer is.

6. What is the designer's experience with B2B SaaS specifically?

Consumer design, B2B SaaS, and brand design are different skills. A designer who is excellent at consumer apps or brand work may struggle with the complexity of SaaS dashboards, role-based interfaces, and multi-step workflows.

Ask the agency to show you specific B2B SaaS work done by the designer who will be assigned to you, not just the agency's portfolio overall.

7. What happens if my assigned designer leaves or is unavailable?

Agencies have turnover, sick days, and competing priorities. What's the continuity plan if your designer goes on leave mid-project? Who picks up, and how do they get up to speed?

An agency with no clear answer to this question has no real continuity plan, which means you're exposed if something changes.

---

Questions About Pricing

8. What's included in the monthly retainer (or project fee)?

Get a specific list. "Design work" is not an answer. What kinds of tasks are in scope? How many rounds of revisions? Are kickoff calls, presentations, and strategy sessions included or billed additionally? What about design system work, documentation, or handoff assets for engineering?

The scope definition is the contract. Vague scope definitions are how disputes happen.

9. What gets billed outside of the agreed fee?

Ask directly. Common extras: additional revision rounds beyond the agreed number, rush fees for tight turnaround, expenses (user testing tools, stock imagery), additional stakeholder presentations, scope changes.

You want to know this upfront because the extras can add a meaningful amount to the quoted price. If the agency says "everything is included," push for specifics; that's an unusual answer from a traditional agency.

10. What is the minimum commitment and what happens if we need to stop?

Agency contracts often have 3-month or 6-month minimums. Understand exactly what you're committed to before signing.

Ask: what happens if the business situation changes and you need to pause or end early? Is there a kill fee? Will you own all work-in-progress up to that point?

A design subscription with no minimum commitment is a fundamentally different model, the ability to pause or cancel anytime changes the risk profile significantly. See Designpixil's pricing for how that works in practice.

---

Questions About IP

11. Who owns the work when the project ends?

This should be obvious but isn't always. In a properly structured engagement, you own all deliverables once paid for. Source files (Figma files, not just exports) should transfer to you.

Red flag: "you own the designs but we retain the source files" or any variation where the agency holds files you need to make changes. This creates lock-in and is a reason to walk away.

Ask specifically: do we get the Figma source files? All of them?

12. Do you maintain the right to show this work in your portfolio?

Most agencies will want to add your work to their portfolio, which is reasonable. What you want to control is timing (you may not want the work public before launch) and the level of detail (some founders don't want case studies that reveal business strategy).

Get the portfolio use clause explicit in the contract. Most agencies will agree to embargo the work until post-launch if asked.

---

Questions About Results

13. How do you define and measure success on a project?

This is a good question to ask early because the answer tells you whether the agency thinks about outcomes or just deliverables. An agency that answers purely in deliverable terms ("we'll deliver X screens in Y weeks") is in the output business. An agency that asks about your goals upfront and talks about how design will affect activation, conversion, or retention is in the outcomes business.

For B2B SaaS, the outcomes that matter are usually: activation rate, feature adoption, support ticket volume, sales demo conversion, or time-to-value for new users. A design agency that's never heard these terms being used about their work has never been held accountable for them.

14. Can you share a case study where design work led to a measurable outcome, positive or negative?

"Positive or negative" is important. A case study that's all success and no failure is marketing, not evidence. Agencies that have done real product work have stories about things that didn't go as planned, a redesign that hurt a metric, a feature that users ignored, a direction that had to be scrapped.

Honest case studies signal experience. Pristine case studies signal a marketing department.

---

Questions About Communication

15. What does a normal working week look like with you?

Get the cadence: how often will you communicate, through what channel, and what's the expected response time? Who is your primary contact, the account manager or the designer?

The worst agency experiences come from communication gaps: you're waiting to hear back on a revision, your agency contact doesn't respond quickly, and you're blocked. Get specific commitments on response times and the communication channel you'll both use.

Also ask: "If I have an urgent change, something that needs to be done in 24 hours, how does that work?" The answer reveals whether the agency has any flexibility or whether everything runs on a fixed weekly cadence.

---

Questions About Collaboration Process and Deliverable Timelines

Process and timeline questions are where proposals quietly differ, because every agency says "collaborative" and "fast" and almost none define either. Six questions that force specifics:

16. Walk me through the collaboration process from kickoff to first deliverable.

You want a sequence with names and dates attached, not a methodology diagram. Who runs kickoff, what happens in week one, when do you see the first real screen rather than a mood board, and how is feedback collected. A partner who has done this often answers in minutes because the process is real. Ours, for comparison: onboarding call, shared Figma workspace and a request queue, first deliverable inside 24 hours, then 3 to 4 deliverables a week with review in Figma comments.

17. What is the timeline for each type of deliverable, and what makes it slip?

Ask for the normal turnaround on the specific things you need: a landing page, a dashboard screen, a full onboarding flow, a design system. Then ask what causes delay. Honest answers name dependencies on your side (content, product decisions, access to users) rather than blaming scope. If every estimate is the same number regardless of deliverable, the estimate is marketing.

18. How many revision rounds are included, and how long does a round take?

Two rounds with a two-day turnaround is a different engagement from unlimited rounds that each take a week. Ask what counts as a round, what counts as new scope, and what a round costs once the included ones are used.

19. Who reviews and approves on your side, and what happens if our feedback is late?

Design work stalls on approvals more often than on production. Find out whether late feedback pauses the clock, rolls into the next cycle, or quietly costs you a week. Ask how they keep working while waiting.

20. What do you need from us, and by when?

Every timeline assumes inputs: brand assets, product decisions, technical constraints, access to real data or users. A partner who cannot list their dependencies has not planned the work, and you will discover the list in week three as an excuse.

21. How do finished deliverables reach engineering?

Ask specifically: component structure, naming, tokens, documentation, and whether your engineers or your AI coding tools can implement from the file without a translation meeting. A beautiful file that engineering cannot build is not a deliverable, it is a proposal.

---

How to Use These Questions

You don't need to ask all 21 in one meeting. Split them:

Before the proposal: Ask questions 1, 5, 6, 8, 10, these help you evaluate whether to even request a proposal.

When reviewing the proposal: Ask questions 2, 3, 9, 11, 12, these help you understand what you're actually agreeing to.

Before signing: Ask questions 4, 7, 13, 14, 15, these are the accountability and communication questions that determine day-to-day experience.

Before signing, if the engagement has fixed deliverables: Ask questions 16 to 21, the collaboration and timeline questions. They matter most when you are paying per project rather than per month.

If an agency is reluctant to answer any of these directly, that reluctance is the answer. Good design partners are transparent about how they work because they've built their process to serve clients well and they're not afraid of scrutiny.

---

The Alternative to Asking All of This

One reason the design subscription model has grown among B2B SaaS founders is that it eliminates most of the ambiguity in these questions.

With a subscription: pricing is flat and fixed, IP transfers on delivery, you own all files, you can cancel anytime, and you work directly with the senior designer doing the work. The questions about "who will actually work on this" and "what happens if we need to stop" have simple, clear answers.

This doesn't mean subscriptions are right for every situation, for large, defined-scope projects, an agency with a full team may be the better fit. But for ongoing product design work at a startup, the subscription model removes the friction points that these 21 questions are trying to uncover.

If you're comparing models, the design agency vs. freelancer vs. subscription breakdown lays out the honest tradeoffs.

---

Frequently Asked Questions