July 18, 2026
6 min read
4 views
Hiring the wrong development partner twice is expensive: once when you pay for the work, and again when you pay someone else to fix it. The tricky part is that most software consulting companies sound equally impressive in a sales call. Everyone has a slick deck, a "proven process," and a wall of logos. Your job as a buyer is to get past the polish and find out how the firm actually operates when the contract is signed and the demo pressure is off.
The best way to do that is to ask specific, uncomfortable questions and listen carefully to how people answer — not just what they say. Below are ten questions worth asking every firm on your shortlist, along with what a strong answer sounds like and the red flags that should make you pause.
A polished pitch tells you the company is good at selling. It tells you nothing about who writes your code, how they'll handle the inevitable curveball, or whether you'll own what you paid for. Good answers are specific, confident, and occasionally admit limitations. Bad answers are vague, defensive, or suspiciously perfect. Treat every question below as a two-part test: the content of the answer, and the willingness to answer it plainly.
Good answer: They name the specific engineers who'll be on your project, their seniority, and how much of the work is done in-house versus subcontracted. You can meet them before signing.
Red flag: "We have a team for that" with no names, or a bait-and-switch where senior people pitch and juniors deliver. Undisclosed offshore subcontracting is a common surprise.
Good answer: Real URLs, apps in the app store, or a walkthrough of a system currently serving users — ideally in a domain close to yours.
Red flag: Only mockups, prototypes, or "we can't show that due to NDAs" for everything. Some NDA work is normal; a portfolio with zero verifiable shipped product is not.
Good answer: They explain their method — breaking work into milestones, ranges rather than false precision, and assumptions that could change the number. They ask you clarifying questions before quoting.
Red flag: A firm, exact quote before understanding your requirements, or an estimate so vague it's meaningless. Both signal you'll fight about money later.
Good answer: Clear options for maintenance, bug fixes, monitoring, and support, with response expectations spelled out. They treat launch as the middle of the story, not the end.
Red flag: No plan, or an assumption that you'll handle everything yourself the day after go-live. Software that isn't maintained rots quickly.
Good answer: You do — full source code, repositories, cloud accounts, domains, and third-party services registered in your name. They hand over credentials and documentation as a matter of course.
Red flag: They host everything under their own accounts, keep the repo private to their org, or get cagey about a full handoff. This is how vendors hold clients hostage.
Good answer: A defined change process — they flag the cost and timeline impact before doing the work, and you approve it. Small changes get absorbed reasonably; big ones get re-scoped honestly.
Red flag: Either "everything is a change order" (nickel-and-diming) or "sure, no problem" to every request (a recipe for blown budgets and finger-pointing).
Good answer: A recommendation tied to your needs, team, and long-term maintainability — not just what they happen to know. They can explain trade-offs and hiring implications.
Red flag: The same stack for every client regardless of fit, trendy tech with no justification, or an inability to explain why. You'll live with these decisions for years.
Good answer: A predictable rhythm — regular demos of working software, a shared board or repo you can see anytime, and a named point of contact. Transparency by default.
Red flag: "We'll update you when there's something to show," monthly status emails with no working software, or a communication style that requires you to chase them.
Good answer: They have opinions. A mature firm will decline work outside their expertise, push back on features that hurt your product, and tell you when a cheaper off-the-shelf tool would do the job.
Red flag: They'll build literally anything you ask. A yes-to-everything vendor is optimizing for your budget, not your outcome.
Good answer: Two or three past clients willing to talk, including at least one longer engagement. Bonus points if they'll share a project that hit rough patches and how they handled it.
Red flag: No references available, only carefully curated written testimonials, or reluctance to let you speak with anyone directly.
Comparison shopping often defaults to agencies, but an experienced independent consultant is a legitimate — sometimes superior — alternative. The biggest advantage is direct access: the person you talk to is the person writing the code. There's no account-manager telephone game, no risk of your senior pitch team quietly handing off to juniors, and no layers of overhead baked into the rate.
The trade-offs are real too. A solo consultant has finite capacity, limited coverage if they're sick or on vacation, and a narrower range of specialties than a full shop. For a focused build, an MVP, or deep expertise in one area, a strong solo consultant can outperform a mid-sized firm. For a large, multi-discipline program that needs designers, DevOps, and several engineers at once, a team may be the better fit. Ask a solo consultant the same ten questions — the answers about ownership, communication, and what they won't build are just as revealing.
You don't need to grill every firm on all ten questions in one call. Use them to structure your evaluation and to compare answers side by side across your shortlist. A few takeaways to keep in mind:
The firms worth hiring will welcome these questions. The ones that get defensive just answered the most important question of all.
How do AI receptionists work? An engineer's plain-language teardown of the call pipeline — from routing to booking — for small business owners wary of AI.
Tired of searching "date night ideas near me" and still not deciding? See how DateVibes helps couples plan a date by vibe, budget, weather, and time.
Real 2026 custom software cost ranges by project type, plus the hidden costs, cost drivers, and when off-the-shelf beats building your own.