SaaStr bought 30+ APIs this year. Only one asked how it went.

Jason Lemkin, SaaStr founder and former EchoSign CEO, tested 30+ APIs for production use. Exactly one vendor followed up to ask if the product worked. The gap between API sales motions and what technical buyers actually need is wider than most vendors think.

SaaStr bought 30+ APIs this year. Only one asked how it went.

The setup

Jason Lemkin runs 21+ AI agents in production at SaaStr and signed up for 30+ APIs this year: search, enrichment, structured data, email infrastructure, inference, storage. He is not a tire kicker. He is the founder who built EchoSign to $100 million+ ARR before Adobe bought it, runs the largest B2B/SaaS founder community, and manages a $90 million early-stage fund.

Exactly one vendor checked in after he used their product. Not one vendor who did it better than the others. One, total.

What everyone else did

Most vendors ran a standard sequence: day 0, day 1, day 3, day 7. Same emails whether he used the product or abandoned it in four minutes. A Coresignal rep did reach out after Lemkin upgraded his tier, clearly had done homework, but the trigger was the credit card, not usage. That is an upsell motion, not a check-in. The difference matters.

The rest: crickets.

What Exa did

Four days after Lemkin ran his first real batch, a PM named Alina sent four sentences:

"I'm on the product team here at Exa. I noticed you signed up and tested Exa. If you have a one-liner on how we did (or what could have been done better), that would be greatly appreciated (& I'm happy to drop $50 of credits in your account)"

Lemkin wrote back 33 minutes later with 400 words of production feedback, benchmark numbers, feature requests, throughput constraints, and pricing needs. She replied in under three hours with specific endpoint configurations and an honest "we don't support that yet" on one request.

That exchange beat every onboarding and customer success motion the other 30 companies ran.

Why it worked

Small ask, big answer. "A one-liner" is a 15-second commitment. "Do you have 30 minutes for a call?" is a calendar negotiation that gets ignored by the exact users you want to hear from, because those users are shipping.

Named human from product. Not "The Exa Team." Not an SDR working a 7-touch sequence. Someone who works on the product, using their own name, who can actually do something with the answer. Automated outreach is infinite now. Human attention from someone with roadmap influence is scarce.

Usage trigger, not signup trigger. The email fired after a real batch of API calls, not account creation. Most vendors send identical sequences whether you are in production or abandoned the product in four minutes. They are not looking.

Instant, small, product-denominated incentive. $50 of credits dropped in the account. Marginal cost to Exa is close to nothing, runs at volume, and pays developers in more usage of the thing you want them using more. The incentive and the activation goal are the same object.

Reply from someone who knew the product cold. Specific configurations by endpoint and parameter, a second path Lemkin did not know about, direct "we don't have that yet" on one request, and an offer to run test examples together. Most feedback loops die when you get "Thanks, I've passed this to our product team!" That response teaches customers never to bother again.

What this means for sales

API and infrastructure vendors are leaving pipeline on the table. They are optimising signup-to-meeting conversions and running sequences that ignore whether the product works for the use case. The gap is not in top-of-funnel tooling. The gap is in asking one question after someone uses your product: how did it go?

Lemkin is not a random trial user. He is the exact buyer API vendors pitch to investors: technical founder, high-volume use case, budget, public platform. If he is getting zero follow-up from 29 out of 30 vendors, your ICP is getting the same treatment.

The fix is not complicated. It is four sentences, sent by someone who can answer product questions, triggered on usage, asking for one line of feedback. Most vendors will not do it because it does not scale the way a seven-touch drip scales. That is the opportunity.