Every development agency's website says the same things: senior team, proven process, on-time delivery. The words are free, so they filter nothing. What separates the agency that ships from the one that burns six months of your runway is a short list of specific questions and how comfortably they answer them. Vetting an agency well takes an afternoon, and it is the cheapest insurance you will buy on the whole engagement.
Key Takeaways
- Ask who actually writes your code, and insist on meeting them, not only the sales team.
- Get IP ownership, a clear process, and communication cadence in writing before you sign.
- References from real clients matter more than a slick portfolio.
- The way they behave during the sale previews how they behave during the project.
Ask Who Actually Builds It
The most common agency trap is the bait-and-switch: a polished senior team wins the pitch, and juniors build the work. So ask directly who will be on your project, and insist on meeting and talking to those specific people before you sign. Ask how the team is staffed, whether it is dedicated to you or shared across clients, and what happens if a key person leaves mid-project. An agency confident in its people introduces them happily. One that keeps you talking only to account managers is hiding something about who does the work.
Get the Terms That Actually Protect You
The contract, not the pitch, decides whether you own your product and can leave cleanly. Read for a few things specifically, and get vague answers clarified before signing rather than after.
| Check | Good answer | Red flag |
|---|---|---|
| Who writes the code | Named engineers you meet | "Our team" and nothing more |
| IP ownership | Yours, in plain contract language | Vague or carved out |
| Process + cadence | Defined sprints, regular demos | "We'll keep you posted" |
| References | Recent clients you can call | Only logos, no contacts |
| Exit terms | Clean handover, you own the code | Punitive or lock-in |
A Concrete Version
A founder almost signed with an agency that gave a flawless pitch: senior architects, a beautiful portfolio, a confident timeline. On a reference call he made himself do, a past client mentioned in passing that the senior architects were on the sales call and never on the project, which was built by rotating juniors, and that the codebase came back undocumented and hard to hand off. That one call, twenty minutes he almost skipped, saved him a six-figure mistake. He asked the agency who specifically would build his product and to see the code from a past project. The answers got vague fast, and he walked.
The Honest Counterpoint
A weak answer to one question is not proof of a bad agency. A newer agency might have a thin reference list and still be excellent, and a great one can fumble a single question. Do not treat the checklist as pass-fail on any one item. Treat it as a pattern. One vague answer is noise; vague answers about who builds it, who owns the IP, and how you exit, together, are the agency telling you how the engagement will go. And even a perfect-scoring agency is the wrong fit if it cannot start when you need it, so weigh availability alongside the answers.
Frequently Asked Questions
What is the single most important thing to check?
Who actually writes your code. Insist on meeting the specific engineers who will build your product, not only the sales or account team. The bait-and-switch of a senior pitch and junior delivery is the most common way agencies disappoint.
Are references really worth the effort?
Yes. A twenty-minute call with a recent client tells you more than any portfolio, because past clients mention the things a case study leaves out: who really did the work, how communication went, and what the handover was like.
How is an agency different from staff augmentation?
An agency typically delivers a project its own way; staff augmentation embeds engineers who work under your direction inside your team. If you want control and continuity, that difference matters. See staff augmentation vs a software agency.
The Bottom Line
Ignore the homepage adjectives and vet an agency on specifics: who writes the code, whether you own it, how they communicate, and what real references say. The answers, and how comfortably they come, tell you most of what you need before you risk a dollar. For a related screen, see how to evaluate a staff augmentation provider and freelancer vs agency to build your app. See available engineers.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
