How to choose a software development partner: 12 red flags

Choosing the wrong software development partner is one of the most expensive mistakes a startup can make. We’ve talked to 100+ founders about their agency experiences. Here’s what we learned.

The 12 red flags

1. “We’ll figure it out as we go”

What they say: “Don’t worry about the details, we’re experts.” What it means: They don’t have a process. Scope will balloon. You’ll pay for their learning curve.

What to look for instead: A clear process — discovery, design, build, iterate — with milestones and deliverables at each stage.

2. They won’t give you a fixed price

What they say: “It depends on what you need” (forever). What it means: They’re going to bill you hourly and surprise you with overages.

What to look for instead: Fixed-price quotes after a paid discovery sprint. Variable scope is OK; variable budget is not.

3. “We don’t do NDAs, but trust us”

What they say: “We’re professionals, we don’t need paperwork.” What it means: They’ve probably worked on 50 things and have no process for protecting client IP.

What to look for instead: Standard NDA signed before any conversation. IP assignment in the contract. They’ll bring this up, you shouldn’t have to ask.

4. They show you mockups, not working software

What they say: “Here’s what it’ll look like” (shows Figma screenshots). What it means: They can’t actually build what they’re showing.

What to look for instead: Live demos every week, in production-ish environments, with real data.

5. They want 50% upfront

What they say: “Standard industry practice.” What it means: They’re going to disappear with your money.

What to look for instead: Milestone-based payments. You pay for completed work, not promises. 10-20% deposit is reasonable, 50% is a red flag.

6. They can’t explain the tech stack in plain English

What they say: “We use the best tools for the job” (without saying what those are). What it means: They don’t know what they’re using, or they’re using whatever they learned last week.

What to look for instead: A clear, boring, proven stack. React, Next.js, Node, Python, PostgreSQL, AWS. If they can’t justify the choices, run.

7. Their “senior team” is actually one senior + five juniors

What they say: “We have a team of experienced engineers.” What it means: You’re paying senior rates for junior work.

What to look for instead: Ask who specifically will work on your project. Names, LinkedIn profiles, years of experience. Then ask to talk to them.

8. They have 50 active clients

What they say: “We’re in high demand.” What it means: You’ll get 10% of their attention. Your project will sit in a queue.

What to look for instead: Teams that cap active engagements. Ask: “How many projects does each engineer work on at once?” Good answer: 1-2.

9. They say yes to everything

What they say: “We can definitely do that” (to every feature request). What it means: They don’t push back. You’ll over-build. Your timeline will slip.

What to look for instead: Partners who say “that’s a bad idea” or “let’s ship the simpler version first”. The best partners are the ones willing to disappoint you now to make you happy later.

10. They ghost you between meetings

What they say: “We’ve been heads-down on your project.” What it means: They’ve been working on someone else’s project. You’re not a priority.

What to look for instead: Slack/Linear access. Daily async updates. Weekly demos. If they can’t maintain 5 minutes of communication a day, find someone else.

11. They have no case studies

What they say: “We have many happy clients” (won’t name them). What it means: Either they don’t have happy clients, or they can’t ask for testimonials.

What to look for instead: Named case studies, ideally in your industry, with verifiable metrics. If they can’t show you a 6-month-old project, they probably haven’t shipped one.

12. The contract is “standard” and can’t be customized

What they say: “Everyone signs the same contract.” What it means: They use boilerplate that protects them, not you.

What to look for instead: Willingness to negotiate IP terms, payment milestones, scope change processes. Standard contracts are fine, but “we can’t change anything” is a sign they’re optimizing for themselves.

What actually matters

After 12 red flags, here’s what really separates good partners from bad ones:

1. They can say no

The best partners will push back on bad ideas, scope creep, and unrealistic timelines. If every conversation is “yes, absolutely”, they’re not thinking about your business.

2. They show their work in progress

Not polished demos. Raw, in-progress work with bugs. You should see what they’re building as they build it.

3. They have a clear onboarding process

A good partner will have a defined way to start: kickoff call, environment setup, communication channels, first sprint planning. No “we’ll figure it out” energy.

4. They name names

You’ll work with specific people, not “the team”. Ask who they are. Talk to them. If the senior engineer disappears mid-project and gets replaced by a junior, that’s a problem you want to know about.

5. They have a single point of contact

One person owns your project. They triage questions, make decisions, escalate when needed. If you have to chase three people for every update, run.

6. They measure outcomes, not outputs

Outputs: features shipped, story points completed, lines of code. Outcomes: users signed up, revenue, retention, time saved.

Good partners care about outcomes. They’ll ask about your business metrics, not just your feature list.

7. They talk about post-launch

If a partner’s proposal ends at “we ship the MVP” without discussing what happens after, they’re going to disappear. The best partners want long-term relationships.

A simple vetting process

1. Check their recent work — last 3 projects, ideally in your industry
2. Talk to their references — ask about scope creep, communication, post-launch support
3. Pay for a discovery sprint — 2 weeks, fixed price, with a clear deliverable
4. Evaluate the discovery output — is the scope clear? Is the quote justified? Do you trust their analysis?
5. Start small — first milestone should be 2-3 weeks of work, not 6 months

What we look like

To be transparent, here’s what you get with us:

• Senior team (5+ years average experience)
• US timezone, English-first
• Fixed-price projects with weekly demos
• Source code is 100% yours at delivery
• Post-launch support available (or handoff to your team)
• Direct Slack channel with the engineers
• Case studies in your industry (fintech, healthtech, logistics, SaaS)

Book a free intro call if you want to talk.

The bottom line

The cheapest partner will cost you the most. The most expensive partner isn’t always the best. Look for: process, communication, and proof of work — in that order.