What dev shop founders misdiagnose when discovery calls don't close
Most dev shop founders blame lead quality when discovery calls fill with tire-kickers. Three structural failure modes look identical from the outside, and each one needs a completely different fix.
By Stacey Tallitsch | May 18, 2026
You're a software development firm founder. You pulled the last 30 days of inbound discovery calls into a spreadsheet on Sunday night because something has been bothering you. The number is worse than you thought.
Of 18 calls, 14 went exactly the same way. Polite founder on the other end. Vague description of what they want to build. Questions about hourly rate and timeline. A promise to "circle back" after they "talk to a few other shops." Two never replied to your follow-up. None of them booked a paid scoping engagement. Your sales lead calls them tire-kickers. Your agency says you need more leads. Your spouse asks why you took those calls in the first place if they were never going to close.
Here is the problem with the tire-kicker label. It is true at the surface and useless at the layer where you can actually do something about it. Calling a buyer a tire-kicker describes an outcome — they didn't buy — and then dresses up the description as a diagnosis. It is not a diagnosis. It is the same noun, painted.
The real question is upstream. Why is your inbound producing this kind of buyer in this volume?
Three structural failure modes that look identical from the outside
Tire-kicker pipelines in dev shops come from three different structural problems. They all look the same on the call. They need completely different fixes. If you apply the wrong fix, you spend the next quarter making the wrong number bigger.
Failure mode one — generic positioning produces comparison shoppers
Open your homepage. Read the first 40 words above the fold. Now open the homepages of three competitors you respect in roughly your size range. Read theirs. If a stranger could not tell the four pages apart with company logos removed, you have a positioning problem, and your discovery calls are running on the rails of that problem.
Buyers in a generic category default to procurement behavior. They are not being difficult. They are being rational. When all the options look the same from the outside, the comparison reduces to price and timeline. Your discovery call is functioning as a price-discovery instrument because your marketing told the buyer it would be. The fix is upstream of the call.
Failure mode two — pricing-shaped pipeline produces estimate hunters
This one is structural. It is also a specific case of a pattern I've written about more broadly — most "marketing problems" founders bring me are pricing problems wearing a marketing costume. For dev shops specifically, the pattern shows up like this. Your hourly rate is published or easily reverse-engineered from the proposals you've sent into a buyer network that talks. Your packages are denominated in hours, not outcomes. Your discovery questions revolve around scope — how many screens, how many integrations, how many API calls. The pipeline you've built is doing exactly what you trained it to do. It hunts for an estimate.
If your marketing implies you are a billable-hours vendor, you will attract buyers who are running a billable-hours procurement process. That buyer's job, on the discovery call, is to extract enough information to compare your number against three other numbers. The fact that they don't close with you is not a failure of qualification. It is a successful execution of the procurement process you invited them into.
Failure mode three — an over-broad target buyer produces wrong-fit applicants
The third failure mode is the one founders resist most, because the fix sounds like it shrinks the business. Look at your inbound. If your website says you build "custom software for ambitious companies" — or any phrase that broad — you are running an open-tryout audition for any founder with a software project. You will get exactly what you cast for. Anyone with a project. The vast majority of "anyone with a project" is at a stage of buying readiness, budget, or technical sophistication that does not match what you sell well.
This is the same upstream pattern that produces wrong-shaped pipelines in adjacent tech-services verticals. I wrote a few weeks ago about why MSP marketing keeps producing break-fix leads instead of managed services contracts, and the mechanism is identical. The marketing brief, downstream of the positioning, is calling for the wrong audience. The agency is responsibly executing that brief. The leads are correctly shaped for the brief and wrong-shaped for the business.
The diagnostic that tells you which one
You cannot fix three problems at once. You will pick the wrong one, do the wrong work for 90 days, and the call pattern will not change. Run this 20-minute audit instead.
Pull 10 recent discovery-call recordings or call notes. For each call, write down the prospect's answer to two questions: "Why did you reach out to us specifically?" and "What does success look like to you in 90 days?"
If the answer to the first question is some variant of "we're getting bids" or "you came up when I searched" or a referral name with no other context, you are looking at failure mode one. The buyer cannot articulate what made you the right call because nothing in your marketing told them. Generic positioning. Comparison shoppers.
If the answer to the second question is denominated in hours, screens, features, or deliverables — and not in business outcomes the buyer's CFO would recognize — you are looking at failure mode two. Pricing-shaped pipeline. Estimate hunters. The fix is to repackage how you sell before you touch how you market.
If the answers across 10 calls describe 10 completely different kinds of business, problem, and stage of company, you are looking at failure mode three. Over-broad target buyer. The fix is to pick a sharper version of who you serve and accept that you are walking away from inbound that was never going to close anyway. Those calls were taking your time and giving nothing back.
In practice, most dev shops have some of all three. The audit tells you which one is dominant — the one that, fixed, would move the most pipeline.
What to do this week
This is not a positioning workshop pitch. It is not a "niche down or die" sermon. Those framings get the cause and effect backwards. You are not failing to close because you don't have a niche. You are getting the wrong inbound because what you've published does not give a competent buyer a reason to call you specifically. The fix is the same shape as any structural fix. Identify which load-bearing element is wrong. Replace it. Test for 60 days. Move to the next one.
If you're not yet sure whether the problem is with your marketing agency or with the brief you handed them, start there first. The audit in this post assumes you've already ruled that out.
Per U.S. Census Bureau data on NAICS 541511 (Custom Computer Programming Services), there are roughly 62,000 establishments and 944,000 employees in this category. The market is not short of dev shops. It is short of dev shops that have given the buyer a reason to pick them specifically before the price discussion starts. That is the entire game. Everything else is downstream.
So before you ask your agency for "better leads" or your sales team for "tighter qualification," do the audit. 20 minutes. 10 discovery calls. Two questions per call. The honest answer to which failure mode is dominant changes the work for the next 90 days. The lazy answer — that you have a tire-kicker problem — changes nothing, because the call pattern keeps coming.
The discovery calls are not the failure. They are the report. Read it as a report.
— Stacey Tallitsch, Stronghold CMO
About the Author
Stacey Tallitsch is the President of Stronghold CMO, a Fractional AI CMO service operating under Talisman Capital, Inc. He is a 30-year tech veteran and the author of 21 books on systems thinking, operator-grade decision-making, and personal sovereignty, with more than 30,000 students across his Udemy course catalog.