The post says software is moving away from the old SaaS playbook where you build once, serve many users, and keep most of the revenue because incremental delivery is cheap. In the AI version, useful features require inference, inference costs money every time, and gross margins get squeezed unless pricing changes with usage. The author frames this as a structural shift in software economics, not just a temporary cost spike.
Most of the useful pushback was not "AI is fake". It was that the old world was never as costless as the post implies, and the new world may settle into something more familiar than it sounds. Enterprise software has always carried per-customer costs through support, security, compliance, integrations, and custom work. What changes with AI is that the variable compute bill becomes large enough to show up directly in product design and packaging. People pointed out that users are already trained to accept quotas and metered plans, so AI pricing is not alien if the value is clear.
The more interesting line of argument was that inference cost is only half the story. Several commenters argued the bigger shock is that LLMs lower the cost of building bespoke software, which raises the floor for weak SaaS products. If a customer or employee can generate a good-enough internal tool, script, or workflow automaton in hours, a lot of thin wrapper software loses pricing power even if inference gets cheaper. That did not translate into "all products disappear" though. Collaboration, reliability, support, compliance, and shared workflows still make packaged software valuable. Good-enough one-off generation can kill some table-stakes work, but it does not replace products that coordinate teams or sit inside real business processes.
A recurring theme was that falling model costs will not automatically fix margins. Even if inference gets dramatically cheaper, products tend to spend the savings on more calls, deeper integration, longer context, and autonomous behavior rather than pocketing the difference. That leaves founders with a familiar but harsher problem: build products whose value comes from workflow ownership, proprietary data, network effects, or integration depth, because code alone is getting easier to reproduce while model usage remains an expense someone has to pay.
If you run software with meaningful AI usage, stop assuming classic seat-based SaaS margins will return on their own. Price for variable usage, build around workflow, data, and collaboration, and treat falling model costs as something customers will quickly consume rather than leave in your margin.
Skeptical but engaged. People largely accepted that AI introduces visible variable costs, but many rejected the idea that this alone creates a wholly new economic regime. The strongest mood was that weak SaaS gets commoditized faster, while durable products will survive on workflow, trust, collaboration, and pricing discipline rather than on code or hoped-for inference cost collapse.
Key insights
01
Feature creation got cheaper than defensibility
Lower development cost changes the market faster than serving cost does. Frontier models let a competent person prototype niche tools in hours, which makes small software products easier to copy and harder to defend. The surviving advantage shifts toward brand, support, data, integration depth, and other things a weekend rebuild does not capture.
Audit your roadmap for features that are valuable only because they used to be expensive to build. Put more effort into data loops, distribution, and embedded workflow where fast cloning does not erase pricing power.
For many table-stakes tasks, users do not need a polished category leader. They need something that works well enough right now. The important point is not that people will trust raw model output forever. It is that models are already good at writing deterministic programs and one-off automations, which cuts out a lot of software that existed mainly to package routine work for broad audiences.
If your product mainly repackages a narrow repeatable task, expect customers to test custom scripts and agent-built automations against you. Move up the stack into shared process, approvals, auditability, and team coordination.
Even people who expect model costs to keep falling did not treat that as a margin story. As intelligence gets cheaper, products expand usage through more reasoning, more background agents, longer context windows, and more ambitious features. The unit price drops, but total consumption rises with it, so founders should not assume cost declines will quietly restore old SaaS economics.
Model your business with usage expansion built in. A lower cost per call is not enough. You need guardrails on where inference is used and pricing that scales when customers lean into heavier workflows.
Running open models on your own GPUs does not make inference free in any business sense. The hard part is not just electricity. It is utilization, ops overhead, hardware failures, provisioning, monitoring, finance, and capacity planning. Even full utilization often fails to beat cloud AI pricing once all of that is counted, so self-hosting makes more sense for privacy, control, or compliance than for easy margin improvement.
Do not greenlight self-hosting from a spreadsheet that counts hardware and ignores operations. If you are considering it, justify it with control or compliance first, then prove the economics under realistic utilization.
The post's baseline is too clean for real enterprise software. High-value software has always come with expensive per-customer work, from support and security to compliance and custom integrations. That means the jump to usage-aware pricing is less radical than it sounds, especially because buyers already accept storage caps, seats, and tier limits when the purchase solves an expensive problem.
If you sell into enterprises, frame AI charges as another measurable capacity tier, not as a philosophical break from SaaS. Buyers can absorb metering when it maps cleanly to business value and budgeting.
A blunt minority view was that the article mistakes AI novelty for broad demand. Core business systems for accounting, reservations, inventory, and sales still make most software money, and many of those workflows gain little from probabilistic generation. From that angle, inference-heavy software is a side market, not the new default shape of software.
Do not retrofit AI into operational systems just because it changes the margin model. Check whether the workflow actually benefits from generation or reasoning before you accept a permanent variable cost.
One proposed escape hatch is to make users authenticate with their own Anthropic, OpenAI, or Gemini accounts or provide their own API keys, so the product orchestrates work while the model provider bills the customer directly. That would spare startups from runaway inference costs, but it would also hand more power to model vendors and make them the real platform owners.
If you consider bring-your-own-model pricing, treat it as a platform dependency decision, not just a billing tweak. It can help margin, but it may also weaken your control over customer relationships and product packaging.
Some commenters argued the current cost pain is temporary inefficiency, not a durable economic break. In that view, inference will look more like ordinary app hosting as models and infrastructure improve. Others pushed back that memory requirements for state-of-the-art models are so large that app-hosting price levels are still far off. The useful contrarian point is that the whole thesis depends on how fast model serving gets cheaper in practice, not just in benchmark headlines.
Keep a rolling view of model cost curves by capability tier instead of locking strategy to today's API prices. The right packaging for a product can change quickly if useful performance moves down to much cheaper models.