Technical Due Diligence on a Dev Agency

Most founders treat agency selection like a pitch contest. They compare decks, ask about timelines, and pick whoever seemed most confident. This is how you end up six months in with a codebase nobody else can maintain. Technical due diligence takes two hours and saves you months.

What You Are Actually Evaluating

The goal is not to find the agency with the nicest portfolio. It is to find the agency whose delivery process, code standards, and team structure match what your project actually needs. A polished case study tells you they can design a slide deck. It does not tell you how they handle a critical bug at 2am on a Friday before your launch.

You are evaluating four things: code quality signals, team composition and stability, delivery track record, and contract transparency. If an agency is evasive on any of these, that is your answer.

Code Quality Signals

Ask the agency for a public GitHub profile or a sanitized repository they are proud of. Look for commit frequency, message quality, branch naming conventions, and whether they write tests. An agency that does not write tests is not an agency — it is a bill-generator.

Check dependency freshness. A repo full of packages three major versions behind is a maintenance debt you inherit. Our Code Quality Analyzer grades any public repo in under 60 seconds across test coverage, commit hygiene, and dependency health.

Team Composition and Stability

Ask directly: who will be on your project, what is their seniority level, and what is the agency's subcontracting policy? Many agencies sell you on a senior team and deliver with juniors and freelancers they recruited last week.

Ask for the LinkedIn profiles of the engineers who will do the work — not the account manager and the CEO. If they cannot provide this before signing, they are hiding something. Also ask about turnover: if the agency loses a key engineer mid-project, what is their continuity plan?

Delivery Track Record

References are not optional. Ask for two or three client contacts from projects of similar size and complexity. Call them — do not email. Ask how close the final cost was to the original estimate, how the agency handled scope changes, and whether they would hire them again. The pause before that last answer tells you more than the words.

Ask the agency directly about a project that went wrong. Every agency has one. How they describe it — ownership vs blame-shifting, what they changed afterward — is one of the strongest signals you can get.

Contract Transparency

Before you sign, read the IP assignment clause, the acceptance criteria definition, the change order process, and the exit rights. A contract that does not specify what "done" means is a contract that will be used against you. Run the draft through our Contract Scanner to surface the clauses that cost founders post-signature.

The Five Questions Most Founders Forget

Beyond the standard interview, these five questions consistently reveal what a deck cannot hide: (1) Walk me through your QA process — not conceptually, but for the last project you shipped. (2) What does your handoff package include when a client takes the code in-house? (3) What happens to my project if a key engineer leaves mid-engagement? (4) Can you show me the commit history on a real project — not a portfolio piece? (5) What is the one thing your past clients wished they had clarified before signing?

The answers matter less than how they answer. Specificity, honesty about past failures, and clarity of process are the signals you are looking for.