Why Enterprise Customers Say Yes Slowly

Enterprise customers buy deep tech slowly because the risk of a wrong decision lands on named people, and the people who will use the technology often fear it. Expect 12 to 24 months for a first large contract. Build for the whole buying committee, the certification paperwork and the internal business case before you need them.

Christian Hertel

Christian Hertel

Thought leadership

·

·

11 min read

Illustration: a deal passes each member of a wide buying committee before the final yes

Key takeaways

Plan for 12 to 24 months for a first large contract, and size your runway to match.

Sell to the whole buying committee. A contract signed at the top and ignored in the field does not renew.

Fear of replacement and disappointment with earlier technology slow deals more than price. Proof on the customer’s own assets answers both.

Give your champion a business case written for finance, and start certification and supplier onboarding before a deal depends on them.

We planned six months. It is one of the most common mistakes in deep tech sales, and I made it too.

Six months looked reasonable on a spreadsheet. The technology worked. The economics were clear. The executives we spoke to were interested. What the plan left out was everyone else: the people who would have to use the product, the people who would have to approve the vendor, and the people who had been promised something similar before and never got it.

Across the sales calls I’ve worked through, the pattern repeats with very little variation. Here is what I would tell any founder heading into their first enterprise deal.

Why does a six month sales cycle fail in deep tech?

Six months assumes the customer already understands the use case. In deep tech they usually don’t. You are asking them to change a process that works well enough, using a method they have never seen, and to defend that choice internally.

That takes education, and education takes time. It also takes trust, and in industrial markets trust still gets built in person. The large deals I’ve seen close took between 12 and 24 months and a lot of time on site.

One customer described the pace of his market plainly: decisions take anywhere from one to eight months, and once a company commits, it keeps ordering for years. Slow at the front is the price of loyalty at the back. Plan for both.

Why selling only to the C-suite creates an adoption problem

Executive sponsorship feels like progress, and you need it. On its own, it is dangerous.

When a deal is signed at the top and never reaches the field, you win the contract and lose the deployment. The technicians and operators who were never asked will find every reason the new system doesn’t fit their work. The product sits unused, the renewal conversation gets hard, and the reference you were counting on disappears.

Buying committees in industrial companies are wide. In our calls they regularly included country leaders across several markets, members of the C-suite, operations managers and field staff. Each group asks a different question. The executive asks whether it pays. The country lead asks whether it fits local practice. The field team asks whether it makes their day harder or their job disappear.

Some of the most important members never appear on an org chart. At one operator, the evaluation ran through a senior technical expert who also helps shape the industry standard for the very measurement we wanted to change. The standard was written around a different method, and the question was simple: how does your result translate into ours? Until that had an answer, nobody else’s enthusiasm mattered.

Insurers play a similar role. A method accepted by insurers in one country is not automatically accepted in the next, and a buyer operating in five countries needs all five.

Answer only the first question and you have exactly one supporter.

The fears nobody writes into the tender

Two fears came up again and again, and almost never in the formal requirements.

The first is fear of being replaced. When you sell automation into a workforce of skilled specialists, some of them hear that their expertise is about to become optional. They rarely say it in the meeting. They show it through delay, extra testing and objections that keep changing shape.

The most convincing answer I heard came from a customer. Their head of inspection told us he had been the skeptic. Two years later his company worked almost entirely with the new system. What changed his mind was evidence, plus something he hadn’t expected: experienced colleagues who could no longer do the physically demanding fieldwork could stay in the company and keep using their judgement. The technology kept the expertise in the business. That story did more for adoption than any feature.

The second fear is the second wave. Many enterprises already bought the first generation of a technology and were disappointed. One buyer summed up the AI claims in his market in one line: if the AI needs three days, it isn’t AI, it’s people somewhere else. Anyone who has been burned once judges the next vendor through that experience. Your claims start at a discount, and only proof on their own assets closes the gap.

Fear of replacement also exists at company level. A service company with a long inspection record asked one question almost before the demo was over: would their data train our AI, and could they exclude it? They were building their own model, and their own customer portal was what set them apart from competitors. If their data improved a shared model their competitors could use, they would be paying for their own replacement. Questions about data ownership, AI training and what happens if the vendor is acquired come early in enterprise deals, and they need answers that hold up in a contract.

One customer tested us exactly that way. They sent us to assets they already knew were faulty and didn’t tell us. We found the faults. That test was worth more than our entire sales deck.

When the champion can’t sell it internally

Most stalled deals I’ve seen died in a room the seller never entered. The champion wanted to buy and couldn’t make the case to the person who signs.

Often the reason is pricing and ROI framed for the wrong reader. In one negotiation our model had three parts: hardware, a subscription and a fee per use. The operations lead liked the product. Then he explained his problem. Two of those elements were fine; three would be hard to sell to his finance department. His business also used the equipment four or five months a year, while the subscription ran for twelve. The person who would decide was a COO with a finance background, and he wasn’t on the call.

We had built a price that made sense to us and asked our champion to defend it in a meeting we would never attend.

The same thing happens in technical deals. An engineer at a North American operator had seen exactly the failure our method detects: a cable that passed the standard resistance test and turned out to be partially melted. He was convinced. He also had no commercial authority, didn’t know the fully loaded cost of his current inspection campaigns, and told us he would have to talk to his commercial colleagues. Our next meeting had one goal: get introduced to them.

Write proposals for the finance reader first and put the operational detail in the appendix. Give your champion a business case they can present without you: their volumes, their seasonality, their cost per unit, compared honestly against the alternative they already know.

The paperwork wall: ISO, SOC 2 and vendor portals

Then there is everything that has nothing to do with your product. ISO certifications, SOC 2, security questionnaires, insurance requirements, financial statements, and supplier onboarding in large procurement portals that can take months on its own.

For a small company these requirements arrive as a surprise and a cost at the same time. Some are genuine barriers. Some are a polite way of saying not yet. Either way, they are predictable. If enterprises are your target customers, the certification roadmap belongs in your plan from day one, right next to the product roadmap.

Sometimes the wall is the customer’s own system. The procurement lead of a global manufacturer told us nearly all of their inspection volume goes to subcontractors, and the biggest barrier those suppliers face is the company’s internal reporting platform: an API connection, testing and a lot of work before the first report can be delivered. Their annual volumes are tendered in a fixed window each summer. Miss the window and you wait a year.

Every new country starts the paperwork again. One market entry we assessed in Asia needed a separately certified radio module, local drone registration and an entry budget estimated at around half a million euros.

Bigger customers, more pain, and when to walk away

The bigger the customer, the more painful the process. More stakeholders, more countries, more procedures, more people who can say no and fewer who can say yes.

Sometimes the right move is to walk away. Some organizations aren’t ready for what you’re selling, and some small companies aren’t ready for a customer that size. A deal that needs eighteen months of your best people’s attention while the customer’s own teams resist it can cost more than it will ever return. Knowing when to step back is part of selling to enterprise.

Large customers also ask the reverse question, usually without saying it out loud: will you still be around? They worry about what happens to years of their data if your pricing changes or you get acquired. For a small company that is a fair question. Answer it with data portability and clear contract terms before they have to raise it.

What to build before your first big contract

  1. A realistic timeline. Plan for 12 to 24 months, align with the customer’s annual tender window, and size your runway to match.

  2. A map of the whole buying committee. Executives, country leads, operations and field staff, plus the people no org chart shows: standards experts, insurers and procurement.

  3. An answer to the fear of replacement. For the people, show how the technology changes their work, told by customers who have lived it. For the company, put data ownership, AI training and data export in the contract.

  4. Proof on the customer’s own assets. A test they design themselves beats any case study.

  5. A business case built for finance. At most two price components, the customer’s own numbers, written for the person who signs.

  6. A way out. Free repeat measurements, a hardware buyback or a short first term lower the risk of saying yes.

  7. Certification, security and integration readiness. ISO, SOC 2, security questionnaires, supplier onboarding, export into the customer’s own platform and the registrations each country needs, started before the first large deal depends on them.

  8. Support where the customer operates. A field team stuck on a remote site waiting for another time zone is a risk the customer will price in.

  9. One team on the account. Sales, marketing and customer success working each large account together, the way account based marketing is meant to work.

  10. Your CEO or owner in the room. Large accounts expect to deal with the people who run the company. Bring them in early and keep them close.

Let the customer be the hero

The last lesson took me longest to learn. In big accounts it is tempting for the seller to become the hero of the story: the one who found the deal, ran the pilot and pushed it through.

The customer needs to be the hero. The operations lead who took the risk. The skeptic who changed his mind. The team that now gets more done with the people it has. One service company told us they didn’t want anyone else’s logo on the reports they hand to their clients. That instinct is right. Your product should make someone inside the customer look good, because that person carries your deal through every meeting you will never attend.

Spend more time with customers than feels efficient. Treat sales, marketing and customer success as one team. Work the big accounts with your CEO. And let the customer be the one who wins.

Frequently asked questions

How long does it take to sell deep tech to an enterprise?

In industrial markets, a first large contract typically takes 12 to 24 months. The length depends on how new the use case is, how many countries and stakeholders are involved and how much certification the customer requires. Pilots and in person meetings belong in that plan.

Why do enterprise deep tech deals stall?

Most stall inside the customer. Field teams fear being replaced, an earlier technology disappointed them, the champion can’t justify the pricing to finance, or vendor onboarding and certification take longer than the evaluation itself.

Should you sell deep tech to the C-suite or to the people who use it?

Both. Executive sponsorship gets the contract approved. Adoption by the people doing the work decides whether it renews. Map the whole committee and answer each group’s own question.

What do enterprise customers expect from a small technology vendor?

Commonly ISO certifications, SOC 2 or a comparable security attestation, completed security questionnaires, proof of insurance, financial statements and registration in the customer’s supplier portal. Start before the first large deal depends on it.

Why do enterprise customers ask about data and AI training so early?

For many enterprises, especially service companies, operational data is a competitive asset. They want to know who owns it, whether it trains a vendor’s shared AI model, whether they can opt out and whether they can export everything if they leave. Clear contractual answers remove one of the most common late stage blockers.

Christian Hertel

Christian Hertel

Chief Growth Officer for tech companies

I help tech companies turn great products into strong market positions. Before that I led marketing, and for a time sales, at METER Group, AROYA and Addium.

Technical precision is your competitive edge. Market silence wastes innovation.

I help tech companies transform great products into strong market positions.

Explore my work with AI

© 2026 Christian Hertel