The standard vetting ritual — portfolio review, reference calls, a polished proposal — tells you how good an agency is at sales. Portfolios are curated, references are hand-picked, and proposals are written by whoever writes best, not whoever will build your product. What you actually need to predict is different: how will these people behave in week nine, when something is late, a requirement was misunderstood, and the easy options are silence or spin?
You can't ask that directly and get an honest answer. But you can ask questions whose answers are hard to fake.
Questions that reveal the build
- "Who, by name, will do the work — and can we talk to them before signing?" The great sales-to-delivery handoff is where agency projects go to die. If the people in the pitch won't be in the repository, you're buying a brand, not a team.
- "How often will we see working software?" The only acceptable answers are measured in days or a couple of weeks. "We'll demo at the end of each phase" means you'll discover misunderstandings after they're expensive.
- "What's the smallest first project you'd take with us?" Good agencies love small first engagements — an audit, one feature, a prototype — because they're confident you'll come back. Pressure toward a big commitment up front tells you where the confidence isn't.
- "Walk me through a project that went wrong." Every experienced team has them. You're not judging the failure — you're judging whether they name their own mistakes or only their clients'. The way they talk about past clients is the way they'll talk about you.
- "What do we own, and when?" The right answer: code, accounts, infrastructure, and documentation are yours from day one, and you could walk away mid-project with everything. Hesitation here is a lock-in strategy announcing itself.
Red flags that override a good pitch
- A big detailed quote from a short conversation. Precision without understanding is theater. (A range with named unknowns is the honest version.)
- Everything is possible, nothing is a trade-off. Teams that never push back in the sales process won't push back when you're about to make an expensive mistake.
- The spec must be complete before anything starts. Waterfall dressed as diligence — it front-loads your risk and their revenue.
- You can't name your point of contact. Layers between you and the builders are where context — and your budget — evaporate.
- Vague answers about post-launch. If maintenance, hosting costs, and handoff aren't discussed before signing, they become surprises priced accordingly after.
Green flags worth trusting
- They talk you out of scope in the first conversation — smaller first versions, cheaper alternatives, "you don't need this yet."
- They ask about your business model before your feature list.
- They show you something real early — a repository, a staging link, a working slice — without being asked.
- Their bad news arrives early and with options.
The meta-test
Notice the thread: every reliable signal is about transparency under mild pressure. A vendor who is open about ownership, mistakes, uncertainty, and trade-offs while trying to win your business will be at least that open once they have it. A vendor who is evasive in the honeymoon phase has shown you the ceiling, not the floor.
And genuinely — ask us these questions. We wrote this list because we're happy to answer every one of them, and because the clients who ask them are the clients who make projects go well.