A strong portfolio shows what an agency has produced, but it does not show how your project will be handled. 5 direct questions fit within one meeting: who actually works the project, how revisions run, what discovery includes, how disagreements get handled, and what follows launch. Answers separate matching partners from polished pitches faster than portfolio reviews ever manage, because portfolios show outcomes while questions expose the machinery producing them.
Asking identical questions across every startup creative agency candidate matters most throughout the process, since patterns appear only through direct comparison. Vague answers from one partner stand out sharply beside specific answers from another, and founders keeping short notes per meeting watch the ranking write itself before any decision gets forced.
Who joins our project?
Team questions come first because pitch teams and delivery teams often differ; senior partners visible during sales sometimes vanish entirely once contracts are signed, and juniors inherit everything.
- Which named people touch our files weekly, and how many other projects does each person carry right now?
- Who attends our standing calls, and does that person hold real decision authority?
- What happens when a named person leaves mid-project, and who absorbs their work?
Every conversation should produce specific names matched against specific roles without hesitation. Delay around naming signals staffing decided after signing rather than before it, while two or three names carrying a clear ownership signal a genuine delivery plan already formed.
How do revisions run?
Revision questions expose process honesty directly, since every project hits rework somewhere, and improvised answers show themselves immediately under mild pressure.
- How many revision rounds sit inside standard scope, and who decides when a screen counts as finished?
- What happens when user testing contradicts our stated preferences about a direction we like?
- How fast does submitted feedback become updated screens sitting in front of us?
Strong answers carry numbers and named steps throughout, two rounds per screen, feedback returned within three days, decisions logged against test evidence rather than opinion. Reassurance without mechanics, unlimited revisions, whatever you need, sounds generous during sales and predicts chaos during delivery almost every single time.
What does handover include?
Handover questions reveal whether the relationship ends at delivery or survives past it, because products need adjustment for months after shipping and partner behaviour during that stretch varies enormously between candidates who otherwise look identical. Founders should ask what the final package contains, how questions get answered during the first build cycles, and what support costs are once the files are transferred.
Partners describing documented handovers, response windows, and structured transitions have finished real projects before and planned for what follows them. Silence or improvisation around these questions means launch day quietly becomes goodbye. One closing question confirms everything else heard across the meeting: may we speak with a founder from a finished project, and their willingness there validates every previous answer.
Fit reveals itself through answers holding names, numbers, and working mechanisms rather than warmth. Founders asking these five questions across candidates watch the difference appear inside a single afternoon, and the partner answering plainly during evaluation almost always works plainly during delivery too, which makes the questions themselves the cheapest screening any startup ever runs.
