The 5 Essential Questions to Vet a Development Company

Most founders vet development companies the wrong way. They look at star ratings, scan the portfolio, maybe hop on a 15-minute call, and make a gut decision.

That process optimizes for comfort, not competence. The companies that look polished in sales calls are often the same ones that deliver messy code six months later.

We've been on both sides — hiring dev teams and being hired as one. Here are the five questions that actually predict whether an engagement will succeed or fail.

Why These Five?

These questions test the things that matter after the honeymoon phase: process discipline, redundancy, technical ownership, and accountability. A team that scores well on these five dimensions will deliver. A team that doesn't will eventually burn you.

Question Breakdown

1. Do they have a documented development process?

This separates professionals from hobbyists. A real development team has sprint cadences, version control workflows, and deployment procedures that exist in writing — not just in someone's head.

2. Can they show previous work with verifiable references?

Portfolios are marketing. References are evidence. Ask for a client you can actually contact, and ask that client one question: "Would you hire them again?"

3. How do they handle scope changes?

Every project changes scope. The question isn't whether it will happen — it's whether the team has a mature process for handling it without blowing up the timeline.

4. What happens if a key team member leaves?

This is the redundancy test. Solo freelancers fail this by definition. Even agencies can fail it if their knowledge is concentrated in one person.

5. Do they own the CI/CD pipeline?

If you're setting up your own infrastructure, you're not hiring engineers — you're hiring typists. A competent team owns the full delivery pipeline from commit to production.

The best time to ask hard questions is before you sign the contract. The worst time is after your launch date has slipped.