← Back to concept explainers

Concept Fable

Software as a Service

Conclusion first:SaaS (Software as a Service) continuously delivers software capabilities online, usually charged by subscription, seat or usage, with the vendor responsible for operation, maintenance, upgrades and availability. Its commercial focus shifts from one-time software license sales to continuous retention, ARR, NRR, gross margin, productized delivery and multi-tenant efficiency. For AI / Agent companies, SaaS remains an important foundation, but as products begin to directly complete work, pricing and delivery may further move from "software access rights" toward "tasks, work orders or results."

SaaS, Software as a Service · Business model / product

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

After the cloth merchant stopped selling looms, the town's tailors became even more dependent on him

The cloth merchant on Willow Street used to sell looms. A tailor paid once and took the machine away, then found someone to repair it if it broke. The cloth merchant made money each year from new shops opening, and old customers rarely came back unless the machine broke.

Later the looms became more complex, and tailors who bought them could not use them well. Some did not know how to change the shuttle, some forgot to adjust the tension, and some let the machine sit idle for three months before discovering the parts had rusted. The more cloth the merchant sold, the more complaints he received.

He first sent craftsmen to train each household, then sold thick maintenance manuals. The effect was limited: what the tailors wanted was cloth produced every day, not to become loom experts. However thick the manual, it would not hand the cloth to their customers for them.

Once a heavy snow blocked the roads, the cloth merchant kept several of his best looms in his own workshop and let tailors pay monthly fees to use them. He handled thread, oil, maintenance, and upgrades, while the tailors brought only patterns and orders.

This small matter changed the ledger. The cloth merchant no longer focused only on a single transaction, but cared about how many tailors kept using it each month, how much cloth each loom produced, who would add nighttime slots, and who had not come for two weeks.

To let more people share it, he standardized the loom, saved patterns as templates, stored different tailors' cloth rolls in separate compartments, and arranged a unified maintenance window. Every client felt it was their own machine, but underneath it was one shared workshop.

Revenue changed too. In the past, selling a machine brought the greatest joy that day, and afterward there was only maintenance cost; now there is rent every month, but the cloth merchant must continuously guarantee availability, speed, and new features. If the customer is dissatisfied, they will leave next month.

Many years later, some people in the town still bought their own looms. But more tailors chose to use one by the month, because what they really wanted to buy was the ability to produce cloth reliably, not to haul a complex machine home. The cloth merchant also discovered that the difficulty of this business had shifted onto him. If a machine broke, he could not push it onto the tailor; if there was congestion, he had to expand the workshop; if there were new patterns, he had to add them in time. The upside was that as long as he kept making cloth production stable, customers would stay month after month. What the cloth merchant feared most also changed. In the past he feared the machines would not sell; now he feared the customer's weaving would go poorly this month. Revenue became continuous, and responsibility became continuous too. Later, during the retrospective, the group wrote this lesson into their daily rules: first look at where on the ground the result actually changed, then decide what to keep, what to repair and what to restrict.

Reveal

This story is about: Software as a Service

SaaS (Software as a Service) continuously delivers software capabilities online, usually charged by subscription, seat or usage, with the vendor responsible for operation, maintenance, upgrades and availability. Its commercial focus shifts from one-time software license sales to continuous retention, ARR, NRR, gross margin, productized delivery and multi-tenant efficiency. For AI / Agent companies, SaaS remains an important foundation, but as products begin to directly complete work, pricing and delivery may further move from "software access rights" toward "tasks, work orders or results."

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Selling the loom: one-time software license or on-premises deployment
  • Using the workshop's loom by the month: subscription-based online software services
  • The cloth merchant is responsible for maintenance and upgrades: the SaaS vendor bears operational responsibility
  • Shared looms, compartmentalized storage: multi-tenancy and tenant isolation
  • Monthly Rent: Recurring Revenue ARR/MRR
  • The tailor who has not come for two weeks: churn risk and usage health
  • Stable cloth output: the ongoing business capability customers actually buy
  • From owning machines to using capabilities: the core shift in the SaaS business model

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

Subscriptionmulti-tenancyself-serveARRgross marginproduct-led growth

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号