Choosing the wrong development partner is one of the most expensive mistakes a business can make. Not because the code is bad — though it might be — but because months of momentum are lost, budgets are burned, and trust is eroded to the point where the next partner starts at a disadvantage.

This guide is designed to help you avoid that. It’s not a pitch for Vindico — though obviously we’d like to think we pass these tests. It’s a genuine framework for evaluating any development partner, based on the patterns we’ve seen after a decade in this industry.

Start With Their Process, Not Their Portfolio

Portfolios are curated. Every agency shows their best work. What matters more is how they work — because that’s what determines whether your project will be their next success story or their next lesson learned.

Ask: “Walk me through how a typical project runs from start to finish.”

You want to hear specifics. Not “we follow agile methodology” — that tells you nothing. You want: “We start with a paid discovery phase that takes 2–3 weeks. Here’s what we deliver. Then we build in two-week sprints. Here’s what each sprint produces. Here’s how we communicate. Here’s what happens after launch.”

If they can’t describe their process in concrete terms, they don’t have one. They’re making it up as they go — and they’ll be making it up on your project.

Understand Their Pricing Model

How an agency prices tells you how they think.

Hourly / time-and-materials: The agency gets paid for time spent, regardless of output. This works when scope is genuinely undefined, but it transfers all risk to you. If the project takes twice as long as estimated, you pay twice as much.

Fixed-price project: The total price is agreed upfront. The risk sits with the agency. This sounds ideal, but it incentivises the agency to cut scope if things get difficult. It also requires extremely detailed specifications upfront, which are rarely possible for complex software.

Fixed-price sprints: Each iteration has a defined scope and fixed price, but the overall project is flexible. This balances predictability with adaptability — you know what each sprint costs, but you can adjust priorities between sprints.

None of these is universally right or wrong. But you should understand which model your partner uses and what incentives it creates. If their model rewards slow delivery, expect slow delivery.

Check Their Team Structure

Ask: “Who will actually be working on my project?”

Many agencies sell with senior people and deliver with junior ones. The impressive architect in the pitch meeting vanishes after the contract is signed, replaced by a team of mid-level developers you’ve never met.

You want to know: how many people will work on your project? What are their roles? Will you have direct access to them? How does the agency handle knowledge transfer if someone leaves?

The best partners have small, stable teams where the people building your software are the same people who scoped it. Fewer people means fewer handoffs, less miscommunication, and better outcomes.

Demand Transparency

Ask: “Can I see the code during the build, or only at the end?”

If the answer is “at the end,” walk away. You should have access to your codebase from day one — ideally through a shared GitHub repository that you own. This isn’t about trust. It’s about risk management. If the relationship goes wrong, you need to be able to walk away with your code and your progress.

Also ask: “What does your day-to-day communication look like?”

You should expect regular async updates (daily is ideal), a shared project board you can check at any time, and recorded video walkthroughs that show progress in a way that written updates can’t convey. If their communication plan is “we’ll schedule a weekly call,” that’s not enough. A lot can go wrong in a week.

Evaluate Their Discovery Process

The first phase of any project is the most revealing.

Good partners insist on a proper discovery phase — and charge for it. This is where they learn your business, map your requirements, design the architecture, and produce a plan. It should result in a tangible deliverable: a technical blueprint, a prototype, or at the very least a detailed specification.

Bad partners skip discovery or do it for free. Free discovery sounds generous, but it means one of two things: either they’re cutting corners to win the deal, or they’re building the cost into the development phase where you can’t see it.

The best test: does their discovery include a break clause? Can you take the deliverable to another developer if you’re not satisfied? If yes, they’re confident in their work. If no, ask why not.

Ask About Post-Launch Support

Most agencies are eager to talk about building your product. Fewer want to talk about what happens after.

Ask: “What does ongoing support look like? What’s included? What costs extra? What’s your response time for production issues?”

The answers reveal how the agency thinks about long-term relationships. A partner who offers structured, tiered support with clear SLAs is planning to stick around. An agency that’s vague about post-launch support is planning to move on to the next project.

Also ask: “What happens if we want to bring development in-house eventually?” A confident partner will help you plan the transition. A partner who relies on vendor lock-in will resist the conversation.

Check Their References — Properly

Don’t just ask for references — ask for specific kinds of references.

Ask for a client where things went wrong and how the agency handled it. Every agency has had difficult projects. What matters is how they responded. Did they own the problem? Did they fix it at their own cost? Or did they blame the client and send a change order?

Ask for a client in a similar sector or with a similar project size. An agency that’s built ten e-commerce sites may struggle with your healthcare compliance platform. Relevant experience matters more than general capability.

Ask if you can speak to the reference without the agency present. Honest feedback flows more freely in private.

Trust Your Gut — But Verify

After all the due diligence, there’s a human element that matters. Do you like these people? Do they listen? Do they push back when you say something that doesn’t make sense? Do they ask questions that surprise you?

The best development partners feel like an extension of your team — people who care about the outcome, not just the invoice. That’s hard to evaluate from a proposal, but it becomes obvious in a discovery call.

One final test: after your first conversation, do you feel smarter about your own project? A good partner should leave you with new insights, not just a quote.

The Checklist

Before you sign with any development partner, verify:

  • Can they describe their process in concrete, specific terms?
  • Is their pricing model transparent and aligned with your interests?
  • Will you have direct access to the people building your product?
  • Can you access your codebase from day one?
  • Do they insist on a proper, paid discovery phase?
  • Is there a break clause after discovery?
  • Do they offer structured post-launch support?
  • Can they provide relevant, verifiable references?
  • Do they make you feel smarter about your own project?

If the answer to all nine is yes, you’ve probably found a good partner. If not, keep looking.