Two companies in the same industry bought comparable AI tooling. A year later the first had trimmed a few percent off operating costs; the second had a revenue line that had not existed twelve months earlier. The difference was not the technology. It was the question each asked itself. The first asked how to do the same work more cheaply. The second asked what it could now sell that had been impossible the day before.
AI's deeper effect is not on productivity but on the logic of revenue. When the marginal cost of producing an analysis, a report or a personalised interaction collapses, more changes than the gross margin: the value proposition, the unit of pricing, and the line between product and service all move.
Three fundamental shifts
- From selling time to selling outcomes: Once much of the work is automated, hourly pricing stops making sense and the customer pays for output rather than person-hours.
- From dormant data to a revenue asset: Data collected for years purely for internal reporting may be worth something as an analytics service to customers in the same industry.
- From uniform service to personalisation at scale: What was economical only for large accounts becomes deliverable across the whole portfolio.
The cost structure changes shape too
A point discussed less often: part of a fixed headcount cost migrates into variable consumption cost. That is good news at the start, because it shrinks the upfront investment. But if your pricing is fixed while delivery cost scales with usage, growth in sales can eat the margin. Every AI-based revenue model needs a known unit cost of delivery; otherwise commercial success turns into a finance problem.
Why it matters for Iranian SMEs
Many Iranian companies hold something they do not count as an asset: years of operational data from a specific industry, plus an understanding of the local market that no general-purpose model possesses. That combination is a sound foundation for a new service, provided it starts from a small hypothesis.
A concrete picture
Consider a technical services firm that has logged its customers' equipment repairs and failures for years and used that record only to raise invoices. The same data can tell a customer which asset is likely to fail next quarter — a service they will pay for, because a production stoppage costs far more than any maintenance contract. Test that hypothesis with two or three existing customers rather than building a finished product for a market whose answer you do not yet know.
A 90-day starting path
- Days 1–30: List the data you hold that generates no revenue today, and identify which of it means something to your existing customers.
- Days 30–60: Test one revenue hypothesis with two or three real customers. The measure is whether they will pay, not whether they find it interesting.
- Days 60–90: If you see willingness to pay, write down the pricing and the unit cost of delivery, then launch at small scale; if not, change the hypothesis.
Recurring mistakes
- Reducing AI to cost reduction. Savings have a ceiling; new revenue does not.
- Building a complete product before finding the first customer willing to pay.
- Ignoring data ownership and confidentiality when the data you intend to sell came from customers. Settle it in the contract before the sale.
- Fixed pricing on a service whose delivery cost rises with consumption.
Three moves for this quarter
- Start with one unused data asset and be specific about who it is valuable to.
- Test one small revenue hypothesis with a real customer.
- Track progress as the share of new revenue in total revenue, not the count of features shipped.
Frequently asked questions
- Our current business model works. Why now?
Because redefining a value proposition is cheap from a position of strength and expensive under competitive pressure. The time to decide is before the pressure arrives. - Where do we start?
With your own data and your own customers. The first new service almost always comes from an existing asset rather than a novel idea. - What is the principal risk?
Building something nobody pays for. Sell before you build: test the hypothesis with a price on the table.
Takeaway
Business-model transformation through AI does not mean abandoning what pays the bills today. It means asking what has newly become sellable now that producing analysis and interaction costs a fraction of what it did. Companies that ask early do not hold better technology; they simply reached the answer before the market forced it on them.
Glossary
- Business model: How an organisation creates value, delivers it, and gets paid for it.
- Value proposition: The clear reason a customer should choose you over the alternatives.
- Outcome-based pricing: Charging for the result delivered rather than the time spent.
- Unit cost of delivery: The cost of serving one unit of service to one customer, which varies with usage.
- Data asset: Data an organisation holds that can underpin a new product or service.