Why founders get this wrong
Most founders hire design agencies the same way they buy art. They scroll the portfolio, feel something, and sign. That instinct makes sense - design is visual, and taste is real. But it's also how you end up with a $40K invoice and work that looks nothing like the case studies that sold you.
The portfolio tells you what the agency has done. It tells you almost nothing about who will do your work, how they'll approach it, or what happens when the first direction misses.
Here's what most founders actually evaluate when picking an agency:
Does the portfolio look polished?
Have they worked with companies at a similar stage?
Does the founder seem confident on the call?
Here's what they should be evaluating:
Who specifically made the work in the portfolio?
Is the portfolio showing range or a repeating house aesthetic?
What does the process look like after the contract is signed?
What happens if the first phase goes sideways?
The risk isn't bad taste. It's signing with a team whose process, staffing, and incentives don't match startup reality. 82% of leaders report stable or rising design needs in 2026, which means more agencies pitching, more polished sales calls, and more ways to get it wrong. The questions below are the ones worth asking before any money changes hands.
Red flags on the first call
Before you even get to the questions, the sales call itself is data. Agencies reveal a lot by how they run it.
They lead with packages. "We have Package A, B, and C" before they've understood your product or stage. This means their priority is closing you, not diagnosing your problem. A studio that genuinely cares about fit asks questions first.
They push retainer before the core scope is clear. Monthly support, ongoing partnerships, maintenance plans - all reasonable things. But if they're brought up before the core project is defined, that's a commercial signal, not a strategic one.
The discovery feels scripted. Generic questions about timelines and budgets with no real curiosity about what you're building, who your users are, or what's actually broken. If the call could have been copy-pasted from their last five clients, it probably was.
They can't explain their process without buzzwords. "We take a holistic, human-centered approach" means nothing. If they can't describe what week one looks like in plain language, that vagueness doesn't disappear after you sign.
If the sales experience is off, the service will almost always be worse. The call is the agency at their most motivated. It only gets harder to communicate once the contract is signed.
The 10 questions to ask before you sign
These aren't meant to be read off a list on the call. Use them to frame your thinking before you meet, and work the relevant ones into the conversation naturally. Each one is designed to surface something the agency probably won't volunteer.
1. Are the people who made the portfolio work the same people who will work on my project?
Good answer: Specific names, specific roles. "Marta leads identity work, she'll be your primary designer."
Bad answer: "Our team." Vague references to "our senior designers" with no names attached.
This is the most important question on the list. The bait-and-switch - where the senior team closes the deal and juniors do the work - is the most common agency failure mode. If they can't answer with names, assume the answer is no.
2. What is the size of your core team?
Good answer: 5-10 people. Small enough to be predictable, large enough to have some redundancy if someone is sick or unavailable.
Bad answer: 20-30 people, or "we scale the team based on project needs." Larger teams almost always mean account layers, junior execution, and diluted senior attention.
The sweet spot for startup work is a small, senior-heavy team where the people you meet are the people who ship.
3. Walk me through your process from kickoff to first deliverable - what's fixed and what adapts?
Good answer: Clear non-negotiable steps (discovery, direction, refinement) with honest flexibility about where the process bends to fit the product.
Bad answer: "We adapt to everything" (no structure, no reliability) or a rigid package with no room to move (optimized for the agency, not the project).
A studio worth hiring has a backbone. They know what they won't skip. But they can also tell you exactly where they flex and why.
4. What's the realistic timeline - not the ideal one?
Ask for both. The ideal timeline tells you what they're pitching. The realistic one tells you what they've actually experienced. Studios that only give you the ideal are setting you up for disappointment. Typical time from kickoff to first shippable deliverable runs 4-6 weeks for most startup-focused engagements - if an agency is promising less without a clear reason, ask why.
5. What happens if the work isn't going in the right direction after the first phase?
Normal answer: The first payment stays with the agency. Risk is shared. Both sides have skin in the game and a clear process for course correction.
Red flag: Either extreme - "we'll redo everything until you're happy" (no boundaries, no process) or "deliverables are defined in the contract, changes are billed separately" with no flexibility built in.
This question reveals how the agency thinks about conflict before you're in one.
6. Who specifically will be on my project - by name and role?
Similar to question one, but pushed further. You want a named roster, not a category. "A senior designer and a strategist" is not an answer. Ask who, ask what their background is, and ask if they'll be on other projects simultaneously.
7. How do you approach projects where the client already has reference examples - do you use them as direction or as inspiration?
Good answer: Inspiration. References help us understand your taste and what resonates with you. We build from your product's logic, not from what you've pointed at.
Bad answer: Direction. Any studio that treats your references as a brief will produce work that looks like someone else's work with your logo on it.
This is the question that separates studios with genuine creative range from studios with a repeating house aesthetic. A portfolio where every project looks vaguely similar is a signal - what technical founders often miss when evaluating design partners is that a recognizable house style can mean 80% agency aesthetic and 20% your product, not the other way around.
8. What do you do when a client wants something that looks like everyone else in their category?
Honest studios say this upfront: if you want a clone, we'll tell you early so we don't waste each other's time. Studios that say "we always deliver what the client wants" are telling you they'll execute whatever you ask without pushing back. That's not a design partner. That's a production shop.
9. Who owns the source files and Figma files after the project ends?
Standard answer: The client owns everything, no exceptions. Source files, Figma files, all assets.
Red flag: Anything that involves licensing, ongoing fees for file access, or vague language about "proprietary tools." A clear scope of work is essential to avoid disputes over deliverables and ownership - and file ownership should be spelled out explicitly before you sign, not assumed.
10. What does your first call look like - what are you trying to understand about us?
Good answer: Creative fit, founder mindset, appetite for originality. Whether the founder is ready to experiment or wants something safe. Whether references are being shared to show thinking or because they want it copied.
Bad answer: Budget, timeline, and scope. If those are the first three things an agency wants to know, they're qualifying a deal, not a relationship.
The best studios use the first call to decide if the fit is real. They're not trying to close you - they're trying to figure out if working together will produce something worth making.
What heartbeat looks for on the first call
We ask a version of question 10 ourselves. The first call at heartbeat isn't about budget or scope - it's about whether the creative fit is real.
Specifically, we're trying to understand three things:
Are you ready to experiment, or do you want something safe? Both are legitimate. But they require different studios. We push toward differentiation. If a founder wants category conformity, we'll say so early.
Why are you sharing references? References that show thinking ("I love how this brand communicates trust without being corporate") are useful. References that are directions ("make it look like this") usually mean the founder has already decided and needs execution, not partnership.
Is there genuine openness to being challenged? Some founders want a studio to validate what they already believe. Others want a team that will tell them when a direction is wrong. We're built for the second type.
The first call is the cheapest moment to find out you're not a fit. Both sides should be using it that way.
If a founder wants something that looks like everyone else in their category, we say so before anyone has spent a dollar. That's not a rejection - it's the most useful thing we can tell them.
Who this article won't help
If you already have a visual language you love and want to stay inside it, these questions are still useful - but the right hire is probably a freelancer or a 1-2 person studio. They'll execute within a defined aesthetic efficiently, without the overhead of a strategic process you don't need.
A studio built around pushing toward differentiation will create friction if what you want is category conformity. That friction is intentional - it's part of how original work gets made. But if you don't want that, it's just friction.
Not every startup needs the same level of design partnership. Pretending otherwise wastes everyone's time. The 10 questions above are most useful if you're looking for a team that will challenge your assumptions, not just execute them. If you want a Figma vendor, find a good one - there are plenty.
If you're not sure which type of partner you need, this breakdown of what technical founders look for in a design partner is a useful starting point.
A soft fit check before you reach out
Use the 10 questions first - on any studio, including us. If a studio can't answer them clearly, that's your answer.
If you're evaluating heartbeat specifically, here's the honest self-check:
You're at seed or approaching Series A, and the design doesn't match the moment
You want senior people on your project, not an account manager relaying feedback
You're open to being pushed somewhere you didn't expect to go
You'd rather have a system that holds up without us than work that only looks good in the handoff deck
If that sounds right, you can see how we work and what we've built before reaching out. And if it doesn't sound right, the questions above will still help you find whoever does fit.
The best agency relationship starts before the contract. It starts with both sides being honest about what they're actually trying to build - and whether working together gets them there.
