When Lead Generation Works But Product-Market Fit Doesn't
B2B SaaS · Two Products · 55 Demos Generated · Instructive Case
This case study documents two engagements with the same founder across two different products. In both cases, the lead generation system performed. In both cases, the products failed to convert. Both products were eventually discontinued.
The value of this case is diagnostic: it demonstrates what happens when functional lead generation infrastructure meets insufficient product-market fit and inadequate founder engagement.
A methodology that only reports wins is incomplete. This case shows the system working exactly as designed: generating opportunities, measuring conversion, and diagnosing when the problem is not lead flow but product viability.
Keyura Cloud was a logistics SaaS product—a mapping integration that connected to CargoWise, the dominant transportation management system in the freight industry.
The product originated from a single client engagement. A custom integration was built for one company that needed a lower-cost alternative to CargoWise’s native mapping solution. Based on that client’s positive response, the founder concluded the product could sell broadly across the logistics industry.
This assumption—that solving one client’s problem indicates market-wide demand—would prove unfounded.
A complete outbound prospecting system was constructed:
Targeted prospect lists of CargoWise users in the logistics industry
Email sequences and outreach cadences
Sales assets and demo infrastructure
CRM integration and lead tracking
Customer research to understand the actual value proposition
The lead generation system delivered:
| Metric | Result |
|---|---|
| Demos Generated | 25+ in 90 days |
| Demos Attended by Founder | Fewer than 5 |
| Customers Closed | 1 |
| Revenue | $5,000 |
Twenty-five qualified prospects agreed to see a product demonstration. The system delivered exactly what it was designed to deliver: opportunities for the product to prove its value.
The founder attended fewer than 20% of the demos the lead generation investment had produced.
Assessment: Insufficient product-market fit to justify continued investment.
The product’s primary value proposition was price—cheaper than the incumbent solution. This is commodity positioning that invites price pressure and provides no defensibility. The logistics industry showed no broad demand for a cheaper mapping tool; the original client’s interest was an anomaly, not a market signal.
Recommendation: Engagement terminated. Generating leads for a product without market fit wastes resources.
Product status five years later: Discontinued.
Following Keyura Cloud, the founder pivoted to a second product: Collude, a private social network for HR and workplace communication.
The pattern repeated: a product built on assumption rather than validated demand, brought to market with the belief that lead generation would solve underlying product-market fit questions.
Based on the first engagement—specifically the founder’s failure to attend demos—the structure was adjusted:
Lead generation system built and operated
Founder’s team responsible for all sales conversations
Clear accountability: scheduled demos required attendance
| Metric | Result |
|---|---|
| Leads Generated | 30 in 30 days |
| Demos Scheduled | 10 |
| Revenue Closed | $0 |
The system produced a qualified lead per day for 30 consecutive days. Ten of those leads agreed to product demonstrations.
From 30 leads and 10 demos, zero customers were acquired. The product could not convert interested prospects into paying customers.
Product status five years later: Discontinued.
Across both products, identical dynamics emerged:
Product built on assumption: One client’s interest was extrapolated into market demand without validation.
Lead generation performed: 55 total demos were generated across both products. The system worked.
Founder engagement insufficient: A fraction of available demos were attended. Feedback was not incorporated.
Products could not convert: 1 customer from 55 demos represents a 1.8% conversion rate—catastrophically below viable thresholds.
Diagnosis validated: Both products were eventually discontinued, confirming the original assessment.
55 demos is not a lead generation failure. It is proof that the system works. When 55 qualified prospects see a product and only 1 purchases, the product is the variable—not the leads. No amount of additional lead generation can compensate for a product that prospects evaluate and decline.
When a founder invests in lead generation but does not attend resulting demos, no system can succeed. The leads existed. The demos were scheduled. Attendance was insufficient. This is not a marketing problem. This is a leadership problem that no external partner can solve.
Keyura Cloud was built because one client needed a cheaper CargoWise integration. That single data point was treated as market validation. It was not. Product-market fit requires repeatable demand from multiple independent buyers. Building a product for one client, then assuming broad market interest, is a common and expensive founder mistake.
The assessment that both products lacked viable product-market fit was not accepted at the time. Five years later, both products are discontinued. A system that correctly identifies unwinnable situations—even when that diagnosis is unwelcome—provides genuine value by preventing further capital deployment into failure.
The Keyura engagements demonstrate the system’s diagnostic function:
55 demos generated across two products
1 customer acquired for $5,000
1.8% demo-to-customer conversion rate
Lead generation performed—system worked as designed
Products could not convert—market fit absent
Both products discontinued within five years
The lead generation system performed exactly as designed. The products did not. The diagnosis—insufficient product-market fit, inadequate founder engagement—was accurate.
This is what methodology produces: not magic, but clarity. The ability to distinguish between lead flow problems and product problems. The ability to identify when conditions for success do not exist. The ability to prevent future capital from deployment into situations where the outcome is already determined.
Products: Keyura Cloud (Logistics SaaS), Collude (HR Technology)
Keyura Cloud Duration: 90 days initial + 6 months extended
Collude Duration: 30 days
Total Demos Generated: 55
Total Revenue Closed: $5,000 (1 customer)
Outcome: Engagement terminated; insufficient product-market fit
Product Status (5 years later): Both discontinued
Classification: Instructive Case