A founder asks: We got certified, worked through testing, and still lost the deal after five months. What did we do wrong?

The founder of an AI agent startup wrote on Hacker News that an enterprise buyer had approached his company and asked for ISO 27001 certification. After the company got certified, the two sides spent about a month testing the product and revising it. Then the buyer stopped replying. He heard from someone he knew inside the company that it had chosen another vendor. By his account, he'd put five to six months into the deal.

What's hard to let go of is the collaboration that came before. If they ended up choosing someone else, why did they take the time to lay out their requirements carefully and work through changes with you?

Have you been through something similar?

We don't think losing the deal means all the earlier work was wasted. Once the requested certification was in place, the two sides did move on to testing. That step had value. But getting certified doesn't mean the buyer now has a reason to choose you.

What's easier to miss is that a buyer may keep testing carefully precisely because they still need to understand how the vendors differ.

Wynter surveyed 100 B2B SaaS marketing leaders who had recently evaluated competing vendors. In response to the question “When the vendors on your shortlist feel interchangeable, what do you typically do?”, 41% selected “Push for a deeper trial or demo.”

That doesn't represent all enterprise AI purchasing, but it does make one possible motive clear: a buyer needs the trial to develop a basis for choosing that they don't yet have.

The buyer's requirements can be real, and the people involved in testing can be taking it seriously. Fixing problems uncovered during testing helps the buyer see how the product performs in actual use. But once those problems are solved, the differences between you and the other vendors may still not be enough to affect their choice. A deeper trial might even show them that a particular feature difference isn't all that important to them.

An evaluation can make progress and end with a decision not to choose you. Serious collaboration doesn't mean you'll win the deal.

Testing can end in a pass, a failure, or no clear conclusion. Even if a product passes technical testing, the buyer may not yet have secured budget approval, completed internal approvals, or signed a contract. During procurement, the problem they want to solve and what they intend to buy may also change.

We can't use any of those possibilities to draw a conclusion about this founder's case. He didn't report the test outcome or say whether the buyer had made a commitment to purchase. The specific reasons for the lost deal and the silence are also unclear. If a deal already includes a clear commitment to buy once certain conditions are met, we need to look at what that commitment was, whether the conditions were met, and what happened afterward.

When a buyer assigns engineers, discusses problems seriously, and works through repeated rounds of testing, it's understandable that the seller feels more hopeful. For example, suppose a company wants to use AI to answer customer support questions and worries that it will mix up old and current return policies. The buyer gives two vendors past customer questions that could easily lead to mistakes, asking each to answer using the current policy and show what the answers are based on.

If both meet the agreed requirements, that round of testing serves a real purpose: the buyer has seen how the products handle those questions, and the errors they were worried about haven't appeared in testing. But the buyer may also discover that both products are good enough for this particular use. The test has resolved one concern without giving them a reason to choose you.

If the buyer then asks, “Could you adjust the tone of the replies a little?”, we'd look at how much that change matters to their choice. If they think both products' answers are suitable for their support team to use with only a small adjustment in tone, further refinement can make the product easier to use without changing their judgment that both are good enough.

In this example, we recognize the value of the first round of testing. But we wouldn't raise our expectations of winning the deal just because the buyer has made another request. If the next round of work is intended to help win this order, we wouldn't support investing more in tone adjustments at this point: there's no basis yet for saying that this improvement would change the buyer's choice.

The work already done doesn't have to be written off as wasted. The work that comes next still needs its own justification.