Choosing a software development partner is one of the highest-leverage decisions a founder or product team makes — and one of the most consistently done badly. Most teams pick by deck quality, hourly rate, and the warmth of the sales call. None of those predict whether the software will ship on time, run reliably, or be maintainable in two years.
We've been on both sides of this — running Taqnihuband consulting for clients who hired the wrong studio first. Here's the short list of signals that actually matter.
The signals that mislead
A polished pitch deck tells you the studio knows how to sell. A long client list tells you they've closed deals. A low hourly rate tells you almost nothing — total project cost is a function of velocity, not hourly billing. A 200-person headcount tells you they have overhead.
None of that tells you whether the engineers who'll touch your code are good at their job, or whether the studio will still answer the phone on month nine.
Signals that actually predict outcomes
- They write publicly about their work. A studio with an engineering blog or open-source repo has put their reasoning on the record. You can read it before you commit a budget.
- They scope before they quote. A fixed price quoted in 48 hours from a one-paragraph brief is a guess. Real scoping requires real conversations.
- Senior engineers are on the call.Not just at the pitch — every week. If the people building your product never speak to you, the people speaking to you don't know what's being built.
- They'll show you a real codebase. Under NDA if needed. Decks are theatre; code is evidence.
- They push back. A studio that says yes to every request is selling hours, not outcomes.
Questions to ask before signing
That last one matters most. Anyone can produce a happy reference from last quarter. References from completed projects, a year on, tell you whether the software is still running and whether the relationship held up.
Red flags to walk away from
- Vague ownership.If the contract doesn't say you own the code, the deploy keys, and the cloud accounts, you don't.
- Bait-and-switch staffing. Senior engineers in the pitch, juniors on the project. Insist on names in the statement of work.
- No mention of testing or CI.If they don't bring it up, they don't do it.
- Reluctance to commit to a fixed milestone. Time and materials with no shape is how a 12-week project becomes 12 months.
The studio you want is the one that's a little annoying to hire — asks pointed questions, pushes back on your timeline, and makes you sign things. That friction is the same friction that ships software.
If you'd like to compare what a real engagement looks like, our services page has the shape of how we engage. Or just tell us about your project.
End of article · Thanks for reading