The questions I would ask a product design firm before signing anything.

A design firm’s pitch is a designed object. It is rehearsed, beautiful, and built to make you feel like the decision is already made. I know because I have given those pitches, through my own studio, and I have sat through them as the client, and I have competed against them as the one-person alternative.

So this essay is the cheat sheet I wish every founder had in that meeting: seven questions plus one phone call, what a good answer sounds like versus a rehearsed one for each, and a copyable checklist at the end so you can take the whole thing with you.

Who exactly will do the work?

This is the question that matters most, and the one pitches are built to blur. The senior partner who wins your business is often not the designer who shows up in your files three weeks later. The gap between those two people is where most firm disappointments live.

The partner who wins the pitch is often not the designer who shows up on your project.

So ask to meet the actual team, by name, before you sign. Ask how senior they are, what they shipped last, and how much of the partner’s time you actually get. A good firm answers instantly, because they already know who is staffed. A firm that says the team will be assigned after kickoff is telling you something. Believe them.

There is a softer version of this trick worth knowing too. Some firms staff a strong lead for the first two weeks, long enough for the kickoff to feel senior, then rotate them to the next pitch while the project settles onto junior shoulders. So do not just ask who starts. Ask who is in the files in week six, and whether the people you meet today are contractually the people on the work. It is a normal thing to put in writing, and firms who staff honestly will not blink at it.

What did your last three projects change?

Not what they looked like. What they changed. Screens are cheap to make and easy to dress up in a portfolio, and every firm’s work looks good in a case study they wrote themselves. The question that cuts through is: what happened to the client’s numbers after you shipped?

A firm that works toward outcomes will get specific without flinching: sign-ups went up, checkout stopped leaking, the launch hit its date, the client came back with a second project. A firm that talks in process, our discovery phase, our design sprints, our methodology, is usually describing activity, not results. I wrote more about telling those apart in how to measure design ROI.

How small can the first engagement be?

Big firms like big contracts, and the pitch is built to sell you the whole roadmap at once. Resist that. The single best de-risking move you have is a small first scope: one flow, one surface, one problem, done in weeks. You judge the work instead of the promise, and the firm earns the roadmap instead of pre-selling it.

Good firms say yes to this readily, because they know the first project sells the second one. If a firm will not scope anything under a quarter of work, they are optimizing for their pipeline, not your risk.

What happens when you are wrong?

Every real project has a moment where the first idea does not survive contact with users. Ask how they handle it. Who catches it, how fast, and what it costs you. You are listening for evidence they test their own work against reality, research, analytics, a beta, anything, and that revisions inside a scope are normal rather than a change order ambush.

The rehearsed answer is that their process prevents mistakes. Nobody’s process prevents mistakes. The honest answer describes how they find them early, say so plainly, and fix them without drama.

Who owns everything when we are done?

Files, research, the design system, the accounts everything lives in. The answer must be you, fully, without an ongoing dependency on the firm to make changes. Some firms create quiet lock-in: source files held back, a system only they can operate, a retainer you did not plan for just to keep the lights on.

Ask directly: when this ends, can my team open the files and keep going without you? A confident firm says yes, because they would rather win your next project on merit than hold your last one hostage.

Make the checklist concrete before kickoff, not at handoff: design source files in your accounts, research recordings and notes in your drive, the design system documented well enough that a designer who never met the firm can use it, and any tooling licensed to you rather than to them. None of this is exotic. It is just easier to agree to on day one than to negotiate on the last day, when the leverage has quietly changed hands.

How do you use AI?

In 2026 this question earns its place on the list. A firm that quietly refuses AI is billing you for hours the rest of the market no longer needs. A firm that leans on it without senior judgment ships polished slop at speed. Both failure modes are common, and both are expensive.

What you want to hear is specifics: where AI accelerates their work, where a senior human still decides, and how the savings show up in your scope or your bill. Vague enthusiasm is as much a red flag as denial. This is the lens I bring as an AI design consultant, and it transfers directly to evaluating firms.

What will you need from us?

The quietest cause of failed firm engagements is not the firm. It is the client who assumed hiring one meant the problem was handled. Every good project needs things from your side: decisions on a schedule, access to users and data, someone empowered to say yes. Ask the firm to name what they will need and how much of your team’s time it costs.

A firm that has done this before hands you a clear, short list. A firm that says do not worry, we handle everything, has either never shipped anything complicated or is planning to design in a vacuum. Both end the same way.

While you are on the subject, ask who your single point of contact is and how decisions travel. If every question routes through an account manager to a designer you have never met, you are playing telephone with your own product. The best engagements I have been part of, on either side, put the client and the designer in the same room, with the structure supporting that conversation instead of replacing it.

The reference call worth making

Do not ask for references. Every firm has three delighted clients on speed dial, and those calls all sound the same. Ask a sharper version: which client has hired you more than once, and can I talk to them? Repeat business is the one signal a firm cannot stage, because it means the first project’s results were worth paying for twice.

When you get that client on the phone, skip the satisfaction questions and ask what went wrong. Something always goes wrong. What you are buying with the call is a preview of how the firm behaves mid-project when the plan bends: whether they surfaced the problem or sat on it, whether the fix cost drama, whether the client felt like a partner or an account. Ten minutes on that beats an hour of curated praise.

Take this into the meeting

Here is the whole essay compressed into something you can copy with one tap. Ask these in order; the early ones are the hardest to answer with rehearsal. Every checklist and calculator on this site lives in the toolkit if you want the full set.

The questions you can skip

Just as useful as the right questions: the ones that waste your meeting. What is your process? Every firm’s answer is a variation of the same diagram, and none of them run projects the way the diagram says. Can we see more of your portfolio? You will see more polished outcomes with the failures edited out; the outcomes question above gets you further. What tools do you use? Unless the answer affects who owns your files, it does not matter, and the AI question covers the part of tooling that does.

These questions feel diligent, which is exactly the problem. They let a mediocre firm perform competence for an hour while the questions that discriminate go unasked. Pitch meetings are short. Spend the minutes where the answers actually differ between a great firm and a rehearsed one.

What a good conversation feels like

Notice that none of these questions are hostile. Good firms enjoy them, because they are the questions their best clients asked. If the conversation gets defensive, or every answer routes back to the methodology slide, you have learned what you came to learn for the price of a meeting.

And if the honest answer to the bigger question, do you need a firm at all, is unclear, that is a different conversation, and often a cheaper one. The full comparison lives in my guide to choosing a product design firm. Sometimes what you need is one senior person to find the real problem first; that is the work I do, and I will tell you plainly if a firm is the better call. Tell me what you are building.