I've spent 15 years on the vendor side of this conversation. I know what makes clients pick us, what makes them stay for a decade, and what makes them fire the last shop and come looking for someone new. So here's the framework I'd use if I were the one buying.
You're not buying code
This is the part nobody talks about in the first call. You think you're buying code. You're not. You're buying a relationship with a group of engineers who will live inside your product for years. The code is what comes out of that relationship. If the relationship is bad, the code will be bad — no matter how impressive the portfolio looked.
A code vendor gets you the cheapest rate and the fastest delivery. You'll replace them in 6 months. An engineering partner gets you team fit, strong communication, and genuine interest in your domain. You'll work with them for 3, 5, 10 years. Figure out which one you need before you start comparing hourly rates.
Five things I'd actually check
Engagement length. Ask every vendor how long their average client sticks around. If it's under a year, something is broken — churn, retention issues, or they optimize for starting projects rather than finishing them. Ours is 3+ years. Our longest is 10 (MyFlyRight, a LegalTech platform). Long engagement length is the single strongest quality signal because it means the vendor delivers enough value that people don't leave.
Can you talk to the engineers? You should interview the actual developers who'll write your code. Not a sales rep. Not a delivery manager who vanishes after week one. If a vendor says "we'll assign the best team" but won't let you choose — that's a red flag. At EltexSoft, engineers join your Slack and attend your standups from day one. You talk to them directly, always.
Retention rate. Ask what percentage of their engineers have been there 2+ years. Turnover is the silent killer. When a developer leaves mid-project, you lose months of domain knowledge. The replacement ramps up on your codebase, your business logic, your team culture. You pay for that learning curve twice.
Technical honesty. The best vendors say things you don't want to hear. "Your architecture won't scale past 10K users." "This feature is 3 months, not 3 weeks." "Don't build this — there's a third-party tool that does it better." If a vendor agrees with everything during sales, they'll agree with your bad technical decisions during the project too. That costs months.
Process clarity. Ask them to walk you through a typical sprint. Not buzzwords. Not "we're agile." How do standups work? How do code reviews happen? How are bugs triaged? If they can't describe their process before you sign, they won't execute it after.
How I'd actually evaluate
Shortlist 3-5 vendors from Clutch, LinkedIn, or referrals. Do a 30-minute call — engagement length, team size, stack. Filter fast. Then do a 60-minute technical interview with 2-3 engineers who'd work on your project. Ask about recent work, how they handle disagreements, what they'd do differently on a past project.
Call 2-3 references. Ask "what went wrong?" Every engagement has problems. What matters is how they handled them.
Then — and this is the step most people skip — do a trial engagement. 4-8 weeks. Small, well-defined scope. Evaluate communication, code quality, velocity. It's the only way to know if the relationship actually works before you commit.
What to negotiate
Monthly retainer, not fixed-price. Fixed-price creates adversarial incentives — vendor minimizes scope, you maximize it. Retainer aligns interests.
30-day exit clause. If a vendor needs 6-month commitments upfront, they're not confident they can keep you through quality.
IP ownership — all code is yours, full assignment, work-for-hire. Standard. If anyone pushes back on this, walk.
Knowledge documentation. The vendor should maintain docs that let you onboard a new team if the relationship ends. That's your insurance against lock-in.
How we work
We're a retained engineering studio. Same team, month 1 and month 36. No juniors on client projects — every engineer has 5-15 years of experience. We don't do fixed-price. We don't do body shopping. We build long-term partnerships where our engineers become part of your team.
Last updated May 9, 2026