Techaisle Analyst Insights

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

Key Takeaways

• The advantage is not the AI PC itself. It is the breadth of device categories Lenovo can integrate and manage through a common software and services layer, which is what lets a single agent work across an entire fleet. A vendor focused primarily on PCs has fewer categories to work across.
• The FIFA World Cup 2026 proved the model at scale. More than 26,000 Lenovo and Motorola devices across three countries, deployed and managed as one fleet, with FIFA highlighting Lenovo’s rapid deployment and managed lifecycle approach as helping accelerate operational readiness in weeks rather than months.
• The constraint is go-to-market, not portfolio. MSPs influence 61% of SMB PC decisions, yet only 34% of SMBs say their MSP explains the business value of an AI PC. Closing that gap is the highest-return move available to Lenovo today.

For the past two years, almost every conversation I have had about the AI PC has been a conversation about a single device. How many TOPS. Which NPU. How the battery holds up running a model locally. Vendors brief on it, partners repeat it, and buyers listen politely before asking the only question they actually care about: what any of this does for their business on Monday morning.

I have come to think the industry has been measuring the wrong thing, and that the mistake is more basic than any argument about silicon. We keep asking a single device to deliver value that is not created on a single device. Almost nobody does their job on one screen anymore.

Watch how a piece of work moves through a company today. A proposal gets drafted on a laptop, discussed in a message thread on a phone, approved on a tablet in the back of a taxi, and then picked apart the following week on a workstation by someone in finance who was never in the original meeting. No single device holds that story. The work lives across all of them, and so does the context that explains it.

That distinction matters enormously once you put an AI agent into the picture, because an agent is only as useful as the context it can actually reach. An agent that lives on the laptop and nowhere else is reasoning about a fraction of what happened. It will summarize the document but miss the decision, because the decision was made on the phone. Techaisle research consistently shows buyers reporting the same frustration in different words, and it is the reason so many AI PC deployments have been underwhelming in practice even when the hardware was perfectly capable.

"We keep asking a single device to deliver value that is not created on a single device," Anurag Agrawal .

Techaisle’s 2026 Global Channel Partner Survey ran across 5,450 partner firms in 24 countries, and buried in the revenue-band cuts is a number that belongs on the first slide of every channel planning session next quarter. Partners under $10M project 8.4% revenue growth for 2026. Partners above $500M project 16.8%.

Some of that gap is simply the shape of the market. Smaller firms carry less capital, chase smaller deals, and cannot hire their way into a new practice on a quarter’s notice, and no program will change any of that. But the survey makes something more useful visible when it cuts the data by revenue band. The market disadvantages are not acting alone. Sitting on top of them is a second layer of disadvantage that vendors build and control directly, and that layer is currently compounding the first rather than offsetting it. Separating the two is where the opportunity is, because one of them can be fixed.

The Market Tilts the Field Before Any Vendor Acts

Deal economics tilt it first. Customer acquisition cost consumes 31% of first-year value on deals below $25K and 9% on deals above $2M, and 67% of sub-$10M partners operate in the $25K to $100K band. A small partner therefore spends 3.4x proportionally to win the only deals its size permits it to chase. No vendor set that ratio. It falls out of the arithmetic of selling.

Practice economics tilt it again. Security revenue averages 18% at the largest partners and 10% at the smallest, not because small firms want to offer security practices less but because a practice does not become commercially viable below a certain team size. AI is tracking the same curve, with 37% of $500M+ partners reporting an AI-security pipeline above a quarter of their total against 13% of sub-$10M partners. 60% of the channel names talent as the primary constraint on scaling AI, and hiring is the one lever a 40-person firm cannot pull on demand.

None of that is any vendor’s fault. All of it is the condition a partner program encounters on arrival, and the only question that matters is what the program then does about it.

Worldwide IT spending by firms with 1 to 4,999 employees will reach US$1.667 trillion in 2026, excluding communication services, and the majority of it will go to IT services rather than to technology products. A market of that size, spread across every economy and every industry, sets the direction for commercial IT rather than following it. These firms are now spending more on the implementation, integration, management, and security of technology than on the technology itself, and the margin between the two is wide and widening.

That composition is the product of two forces working against each other. AI is pulling money up and forward, into software, infrastructure, and services that were not in the budget a year ago. Cost is pulling the other way, as component inflation, tighter budgets, and a higher cost of capital are pushing firms to defer what they can and to rent what they cannot. That second force is the quieter one, and it explains the tilt toward services better than any capability argument does. Buying an outcome instead of an asset moves cost from the balance sheet to the income statement, and it moves operational risk from the firm to the provider. In a year of expensive capital and unforgiving threats, that trade is worth paying for, which is why the money is moving toward services even where the technology itself is cheap.

Within services, the mix has shifted. Maintenance, support, and break-fix, the labor of keeping systems alive, once defined the SMB services market. The money is now concentrating in consulting, integration, and putting AI into production. Transformation work has overtaken recurring management, and it is not close.