Techaisle Analyst Insights

A customer stranded at a rental counter after a late flight calls for help and reaches a phone tree built to keep her away from a person for as long as it can. Press one. Press two. That system is not broken. It is working exactly as designed, because for 30 years the design goal of customer service was to reduce how often anyone reached a human, and the human was the expensive part. The same constraint shaped three other functions. Supply chain teams worked only the deviations they had hands for. Recruiters read only the resumes they had time for. Care teams followed up with only the patients they could reach. In each case the limit was the cost of a person, and in each case the work that did not get done was invisible to the company failing to do it.

The contact center is the only function in a company that measures itself on how often it avoids its own work. Deflection rate counts how often customers are kept out of a live conversation. Containment rate counts how often they are held inside a self-service loop. Both metrics were rational under the old cost structure. Amazon Connect Customer treats them as the wrong measures and replaces them with a single question: whether the customer’s problem was solved.

I was not in Berlin for Lenovo Innovation World at IFA 2026. My doctor made it clear that long-distance travel is off the table for now, and I followed the instruction. Keeping up with the announcements was a different matter, and on that point I was not willing to be told no. I went through every release, every spec table, and every footnote, which is often where the actual product strategy sits.

Earlier this year I argued that Lenovo's real position in the agentic era is not any single device but the whole endpoint fleet, across commercial PCs, workstations, tablets, phones through Motorola, and wearables, paired with the largest commercial channel and a services business capable of operating all of it. That argument had a known weakness, and I said so at the time. Breadth of portfolio is copyable. What is not copyable is control at the system layer across every device type in the fleet, and until this event, that layer was a roadmap item.

Berlin is where it stopped being a roadmap item.

What matters, in order

1. Motorola Qira is extending to the wearable and will take over from moto ai and AI Now, carrying the operating layer across four device types in software rather than only in hardware.
2. The Workato collaboration lets Qira finish tasks rather than only answer questions, and it asks for approval before acting.
3. Extending Lenovo Qira to eligible 16GB configurations determines whether any of this reaches fleet scale, and the download requirement determines whether it gets switched on.
4. Lenovo announced everything from a mainstream consumer laptop to a cluster-ready AI desktop in the same room on the same day, which is the estate argument stated as a range.
5. Local inference silicon moved onto the desk and into the notebook, and the channel has no motion for selling it, at least not yet.

Most AI pilots do not stall because the technology failed. They stall because the buyer and the partner are standing at different points on the same path. Drawing on studies of SMB, midmarket, and channel partner populations, I built the AI continuum to show where those points are, what gets bought at each one, and how customers pay for it.

Three years ago I published a slide mapping how small and midmarket firms moved along the cloud continuum. It traveled further than almost anything else I have produced, mostly because people put it into their own decks and argued with it. I have now rebuilt it for AI and agentic adoption, because the questions vendors and distributors are asking me this year are the same questions they asked about cloud, and the honest answer is again that the market is not one market moving at one speed.

Here is the argument in a sentence. Demand exists at every stage of AI adoption. Partner supply does not. And the gap between the two widens the further right you go.

Continuum diagrams are usually somebody's hypothesis drawn neatly. This one rests on Techaisle's 2026 survey programs across small business, midmarket, and channel partner populations, running to thousands of respondents globally, and on the qualitative work around them: structured interviews, vendor and distributor briefing sessions, and a large number of unstructured conversations with buyers and partners. The surveys established the stages and the volumes. The conversations established the sequence, and sequence is the part a questionnaire cannot reach.

Why a continuum instead of a maturity model

Maturity models rank companies. They tell a vendor which customers are ahead and which are behind, which is a comfortable thing to know and a useless thing to sell against. Every maturity model ends up recommending that the laggards catch up.

A continuum does something different. It maps what a customer actually buys at each stage, who they buy it from, and how they pay for it. That turns the picture into a route. A partner can look at a continuum and see the specific line item they are missing. A vendor can look at it and see which stage their program is funding and which stage their marketing is describing, and those are frequently not the same stage.

The version I have built runs on the same spine as the original: partner entry point across the top, partner revenue flywheel through the middle, end-point on the right, current state to future ready along the bottom. Four stage columns, with five layers of data underneath each one.

Depending on geography, between 7% and 12% of SMB and midmarket buyers use a cloud marketplace to discover software. The rest arrive at AWS Marketplace, or at any of its competitors, already decided. A partner or an ISV brings them, and they transact there for contract consolidation, committed-spend drawdown, and procurement governance rather than for anything resembling search.

Call it the Discovery Deficit. Cloud marketplaces have functioned as procurement rails, not demand engines. They close deals that were originated somewhere else, by someone else, usually a partner.

That gap is why the AWS Marketplace agentic procurement announcements matter, and it is also why most coverage is aimed at the wrong question. Whether AI improves marketplace search is not interesting. Whether a marketplace that has never originated demand in the smaller segments can begin to do so, once the buyer stops being a person typing keywords, is a different question entirely, with different consequences for everyone downstream.

Three changes, and what each one is actually buying

AWS Marketplace has made three structural changes that are easy to read as feature releases. Read against the Discovery Deficit, each is doing something more specific.

The first is the replacement of lexical search with conversational discovery. Agent Mode, launched at re:Invent 2025, lets a buyer describe a requirement in natural language, upload an RFP or a requirements document, and receive ranked recommendations with side-by-side comparisons. Conversational search converts better than keyword search, which is unsurprising. The more important change is in what the interface is for. A keyword catalog fulfills a decision the buyer already made, and works only for someone who knows what to type. A conversational one helps make the decision, and deciding is the step SMB and midmarket buyers have always outsourced, because they have no procurement function to run comparative analysis internally. That is also why so few of them discover software in a marketplace: a catalog that cannot help you decide is little use to someone who cannot decide alone.

The second is building for machines to read rather than people. Most web pages assemble themselves in the browser, so a crawler or an agent that arrives sees almost nothing. AWS builds Marketplace pages to arrive complete, which means an agent reading one gets the whole listing. It has also opened the catalog to direct queries through an MCP server, so a buyer's own AI assistant can ask it questions without visiting a page at all. Most platforms building AI discovery are building a destination and trying to keep the buyer inside it. AWS is doing close to the opposite, and that choice says more about the strategy than anything else in the set. Making the catalog legible to agents AWS does not own is a distribution choice rather than an experience choice, and it concedes that the buyer's first conversation about software will happen somewhere else. The competitive unit shifts accordingly, from whose marketplace interface is best to whose catalog is most readable by someone else's agent.

The third is the automation of the transaction, which arrives from two directions at once. Express Private Offers let a seller define rate cards, discount tiers, volume breaks, and qualification criteria in advance, so an offer can be generated and accepted without a human negotiating it, which lowers the cost of serving a small software deal. All of this aims at deals neither AWS nor its partners could previously work economically, which are the same deals where the Discovery Deficit lives.

Individually these read as product announcements; together they describe a platform trying to convert itself from a procurement rail into a demand engine, which is a considerably harder thing to be.

The Composed Shelf