What to Ask an Engineering Agency in the First Call

Most founders evaluate engineering agencies on portfolio and day rate. Those things don't predict whether the engagement will go well. What predicts it is how they answer questions about process, ownership, and failure. What happens when the lead developer goes on holiday? Who owns the codebase? Have they ever had a client take them to court? These questions make bad agencies uncomfortable for a reason.

Five categories of questions that cut through the pitch. IP ownership from day one — not on project completion, on day one. Who is actually doing your work day to day — not the senior account lead you're talking to. Client references who are willing to share what went wrong — not just what went right. Their post-handoff support policy in writing. And what went wrong on their last project. Every good agency has an honest answer to that last one.

Here's how red-flag answer patterns actually sound on a call. The questions are ordinary. The deflection is what reveals everything. Vague ownership language means lawyers drafted it that way intentionally. "Our whole team works on every project" means no one person is accountable. When references are all current retainer clients, you're not getting an honest picture. Contrast these with the answers a confident, well-run agency gives — specific, fast, no hedging.