Market data · Dec 2024 to Oct 2026 · aggregated, no names
Why companies said no to custom apps
Selling for Futured, a Brno studio that builds mobile and web apps, I counted every company I reached as a deal: how far it got, and if it said no, why. 2,209 companies in 22 months, from my outboxes, my phone calls, the CRM and our lead notes.
From first message to signed project
- 2,209companies reached
- 351replied, 16% of delivered
- 95interested or asking
- 47meetings booked
- 12proposals (SQL)
- 2won
A person replied at one in 6 of the companies my messages reached. About 27% of the replies turned into interest, and 49% of those into a meeting. Of the 12 proposals, 2 were won, 7 lost and 3 are open or postponed. Price decided 4 of the lost ones.
This page counts outreach only. 3 more qualified deals came from outside this outreach, which makes 15 in total.
Why they said no
270 companies replied with a no or a not-now. Each answer is counted once, under the main reason the company gave.
Shares are of the 270 no's. Not counted as a no: 35 replies that sent me to a colleague and 10 without a position. 36 companies showed interest or bought. The real number of no's is higher: many refusals on LinkedIn never made it into the CRM.
“We'll build it ourselves” is growing
Share of no's that named in-house development, by half-year of the reply.
- 14%H1 202510 of 74
- 29%H2 202516 of 56
- 24%H1 202616 of 66
- 34%H2 202625 of 74
In H1 2025, 14% of the no's said they build it themselves. In H2 2026 so far, it was 34%. It is the most common reason overall: 67 of 270, about one in 4.
Price rarely ends the conversation (4% of no's), even though it decided 4 of the lost proposals. Ready-made, white-label or SaaS came up only 9 times. Supplier or agency answers are back in the latest half-year: 13 of 74.
The channel mix changed over time, LinkedIn in 2025 and email in 2026, so read this as a direction, not a precise rate. Without the replies to our AI automation offer, the shares move by 4 points at most.
What I expected, and what the data says
I expected big companies to build their own teams and small ones to buy white-label. The data says otherwise.
| Company size (people) | No's | In-house | Supplier, ready-made or “we have one” |
|---|---|---|---|
| Small, under 50 | 35 | 13 37% | 3 9% |
| Mid-size, 50 to 249 | 56 | 11 20% | 10 18% |
| Large, 250 and more | 64 | 11 17% | 13 20% |
Small companies name their own developers most often. Large ones more often already have a supplier or an app.
Only the 155 no's with a known headcount. Small samples, so this is a correction of my assumption, not a market estimate.
Where the replies came from
Sequences bring reach. The personal channels bring replies: only 4 of the 47 meetings started with an automated sequence.
| First contact | Companies | Replied | Meetings | Proposals |
|---|---|---|---|---|
| Automated email sequence | 1,089 | 48 4% | 4 | 1 |
| Personal cold email | 500 | 74 15% | 9 | 2 |
| LinkedIn message, by hand | 359 | 139 39% | 23 | 7 |
| Follow-up after a website visit | 151 | 49 32% | 7 | 2 |
Companies whose first message was delivered. LinkedIn replies count only where I logged them in the CRM, and the channels ran in different periods and segments, so this is not a fair head-to-head. Calls and events are left out of the table: mostly answered calls got logged.
How this was built
- Unit and period. One company is one deal, deduplicated by domain, at the furthest stage it reached. First contact from 1 December 2024 to 13 October 2026.
- Sources. Three outboxes (1,988 companies), the CRM with emails, logged LinkedIn conversations, call notes and deals (693), our lead notes (173) and campaign lead lists (819). A company can appear in several.
- Left out. Inbound requests, referrals, existing clients, partners, suppliers and conference sponsorship sales (34 companies).
- Weak spots. LinkedIn replies exist only where I logged them, until December 2025. Many no's are one sentence, so “we don't need it” says the least. Company size is known for 38% of the companies (65% of those who replied).