AI pricing is not broken. We have the answers for how to do it
This is a response piece actually, because a roundup of four practitioner talks went around last week under the headline that "AI pricing is broken". It opens like this: three out of four SaaS companies have added generative AI features, and only 15% are successfully charging for them.(I've redacted the details because I don't want to call them out specifically)Sure, fine. But that 15% is doing SO MUCH heavy lifting in this.
- ▪This is a response piece actually, because a roundup of four practitioner talks went around last week under the headline that "AI pricing is broken".
- ▪It opens like this: three out of four SaaS companies have added generative AI features, and only 15% are successfully charging for them.(I've redacted the details because I don't want to call them out specifically)Sure, fine.
- ▪But that 15% is doing SO MUCH heavy lifting in this.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,609 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Solvimon |
| Canonical URL | https://www.solvimon.com/blog/ai-pricing-is-not-broken |
| Publication time | Tue, 04 Aug 2026 13:13:24 +0000 |
| Retrieval time | 2026-08-04T13:15:43.518Z |
| Last seen | 2026-08-04T13:15:43.518Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 4ha356nth1Kg · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
This is a response piece actually, because a roundup of four practitioner talks went around last week under the headline that "AI pricing is broken". It opens like this: three out of four SaaS companies have added generative AI features, and only 15% are successfully charging for them.(I've redacted the details because I don't want to call them out specifically)Sure, fine. But that 15% is doing SO MUCH heavy lifting in this. Everything the experts argue immdiatley after it (mainly that product should own pricing, PLG metrics don't fit agents, your heaviest user is your most expensive one, start from revenue architecture) just glosses over how the AI pricing is stuck or "broken".It's a very Claude-heavy attempt to grab your attention (Claude LOVES saying things are "quietly broken")So I…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Solvimon.
Discussion
0 commentsMore from Solvimon
