logoalt Hacker News

harrantoday at 1:07 AM3 repliesview on HN

I've been building implementation guides for solo founders and small businesses trying to use AI practically, so I read the PwC CEO Survey closely when it dropped.

The headline number (12% of CEOs generating measurable returns) gets cited a lot, but I think the more revealing finding is the 56% with zero financial impact.

These are companies with enterprise AI budgets, dedicated teams, and access to every tool on the market and the majority are getting nothing back.

PwC calls it "Pilot Purgatory." The pattern: AI gets deployed in isolated, tactical projects that don't connect to revenue. internal tooling, content drafts, meeting summaries while the 12% they call the "Vanguard" are using AI in the product and customer experience itself (44% of Vanguard vs 17% of everyone else).

What I found interesting from a solo founder angle: the structural barriers causing large companies to fail at this “bureaucracy, legacy systems, misaligned incentives, multi-department approval processes” don't exist at the one-person scale.

The bottleneck for small operators is different: it's not knowing which workflows are worth building, in what order, and what "system-level" vs "task-level" use actually means in practice.

Curious if others have a take on why the enterprise failure rate is this high despite the investment, and whether the Vanguard pattern (AI into the product, not just the back office) matches what people are seeing in practice.


Replies

al_borlandtoday at 1:33 AM

I work in a large enterprise. On one hand, we’re being told we should think of ways to use AI more. On the other hand, to even start (beyond just using Copilot to develop what I’m already working on), I need to have an idea and sell it to some AI board to get their blessing. At that point, I will have a microscope on me, tracking everything, to watch if this wild experiment is a success or failure. No thanks.

If they really want me to try something new, they will give me the space to try things where I am free to fail quietly and privately, pivot, and continue trying things. Asking for ship dates on day one is no way to operate projects with so many unknown unknowns. No one wants to learn and fail with an audience.

show 2 replies
treetalkertoday at 2:34 AM

The following is my take on what's happening — outside the software-development domain, which is special vis-à-vis LLMs for obvious reasons.

Given worker access to generative LLMs, plus training and motivation to use them, LLMs are effective for certain workflows. Those workflows tend to be personal, one-offs, or summarization in nature: write a bash script for this headache I have every day; tell me what colleague X is trying to say in his 1200-word email, since his writing is garbage and he can't get to the point; "what's the Excel formula syntax for this other thing that I keep forgetting?"; etc.

So the time and mental-energy savings inures to the workers, mostly from coordination tasks that don't directly create core value. And then those savings aren't "reinvested" into value-producing activities whose benefits would inure to the firm because the workers have no incentive to do so; don't know how to create core value; don't have the skills to create core value; or aren't permitted to do those activities by higher-ups.

Bottom line: LLMs are eating busywork coordination activities — hence no impact on most firms' bottom lines.

show 1 reply
andsoitistoday at 1:30 AM

> The bottleneck for small operators is different: it's not knowing which workflows are worth building, in what order, and what "system-level" vs "task-level" use actually means in practice.

Are you saying that from what you see, small operators also fail to get ROI, but for different reasons?

show 1 reply