This series started with the questions to ask before hiring an engineering partner, then how to tell in the first 30 days whether it's working, then how to calculate the real cost of cutting corners, then how to build a roadmap worth executing. This final piece closes the loop: the warning signs that show up before you've even signed anything - if you know where to look.
Red Flag #1: They Say Yes to Everything, Immediately
An unqualified, instant "yes" to every requirement, timeline, and budget constraint in a sales call sounds like great service. It's usually the opposite - a sign the firm hasn't engaged critically with what you're asking for, or doesn't plan to push back later when it matters.
A firm that agrees with everything in the sales process will agree with everything in production, too - including the decisions that will hurt you.
Red Flag #2: The Sales Team and the Delivery Team Are Different People - and You Never Meet the Latter
If the people closing the deal aren't the people who will build your product, ask to meet the actual engineers before signing. A firm that's reluctant to let you talk to delivery before the contract is signed is often hiding team quality, seniority, or availability concerns.
Red Flag #3: Vague Answers About Code Ownership
"You'll have access to everything you need" is not the same as "you own 100% of the code, outright, from day one." Any hesitation or qualification on this point - especially around proprietary frameworks or internal tooling - is a sign the firm is building lock-in into the relationship by design.
Red Flag #4: No Real Examples of Pushback
Ask any firm to describe a time they told a client their idea was wrong. A confident, specific answer is a good sign. A vague answer, a pivot to "we always try to understand the client's vision," or visible discomfort with the question tells you they see their job as execution, not partnership.
Red Flag #5: Pricing That's Suspiciously Lower Than Everyone Else
If one quote is 40–50% below every other comparable quote you've received, something is being cut to hit that number - usually seniority, testing, documentation, or all three. Cheap isn't automatically bad, but a dramatic outlier deserves direct questions about what's different in how the work will actually get done.
Red Flag #6: No Questions About Why, Only About What
A discovery call that's entirely about features, timelines, and tech stack - with zero questions about your business model, your users, or what success actually looks like - signals a firm that builds specs, not products. The best partners ask uncomfortable, clarifying "why" questions before they ever quote a price.
The Signs Worth Trusting
- They ask hard questions about your business before talking price
- They've told you "no" or "not yet" about something - even in the sales process
- Code ownership is unambiguous, in writing, with no qualifiers
- You can talk to the actual engineers before signing anything
- Their pricing is in a reasonable range, not a dramatic outlier
The Bottom Line
None of these red flags are disqualifying in isolation - context matters, and every firm has an off day on a sales call. But when two or three of them show up together, they're telling you something real about how this relationship will go once the contract is signed. The best time to notice is before you sign, not six months in.