Private, Useful AI for Every Employee, at Emerging-Market Prices
**
What would it take to give every employee in an emerging-market company the AI tools that a few people in a rich company take for granted?
AI has an access problem hidden inside a pricing problem. The tools that make office work faster are priced in dollars, per seat and increasingly per task, for buyers in the richest economies. The leading office-suite AI add-on lists at $21 to $30 per user per month, on top of the base licence. A company in Mumbai, Jakarta or Lagos often pays much the same dollar price for employees whose salaries are a fraction of their counterparts’ in New York or London. So it buys a few seats for senior people, and everyone else goes without, or uses whatever free tool they can find.
This essay completes a series of three. The Compute Strait asked how much inference a job needs. The Compute You Already Own asked where the inference that remains should run. This one asks who gets it, and at what price. The goal is not cheaper AI for a few. It is useful, private AI for every employee, at a price an emerging-market employer can sustain.
My answer is not a set of cheaper substitutes for famous AI products. It is a shared utility inside the enterprise: a few everyday AI jobs, joined by one layer that remembers the work, running first on compute the company already owns, under rules the company sets. The rest of the essay explains why that combination could cost a tenth of today’s prices, what competes with it, what it would take to make the economics work for the supplier as well as the buyer, and how it could fail.
Figure 1. Three essays, three questions

1 AI is priced for the few
Run the arithmetic for a company of 500 people. At $20 per employee per month, below today’s list prices for the leading business add-ons, covering everyone costs $120,000 a year. For a services firm in India, that is the salary of several employees, spent on software for all of them. Few companies make that trade. They ration instead: seats for managers and a handful of enthusiasts, and nothing for the support agent, the operations clerk or the sales coordinator who would gain the most from help with routine writing and reading.
Figure 2. Covering every employee in a 500-person company (prices assumed)

When AI is priced per seat in dollars, an emerging-market company does not decide how to use it. It decides who may use it. Metered pricing makes this worse. A finance team that cannot predict the bill caps the usage, and the cap falls hardest on the people with the least authority to ask for an exception.
The market is not standing still, and an honest argument has to start there. The largest office-software vendors are folding AI into what companies already buy. One has bundled its AI assistant into its business plans, funded by a base-price increase of $2 to $4 per user a month rather than a separate add-on; the other has offered promotional prices on its business AI add-on. At the same time, employees without a company seat do not wait. Many paste work into free consumer tools, with no governance over what leaves the company or what comes back. The competitor is not only the $30 seat. It is AI bundled into software a company already pays for, and free tools its employees use without asking.
So the opportunity is not to introduce AI where none exists. It is to offer a coherent, governed and affordable alternative to fragmented tools and uncontrolled use. A bundled assistant serves the company that runs its whole office on one vendor’s suite. Many emerging-market firms do not: email may sit with one vendor, documents with another, accounts in a local system, customers on a messaging app. What they lack is AI that works across that mixed environment, keeps the company’s memory under its own control and costs a predictable amount. That is the gap this essay is about.
2 Four jobs, one suite
Most everyday AI use in a company reduces to four verbs. Ask: a private assistant that answers questions from approved company knowledge. Act: a mail and work agent that drafts replies and follow-ups, with nothing sent without a person’s yes. Listen: meetings transcribed and written up, ideally on the machine that recorded them. Watch: company records checked against rules, with each exception sent to its owner, with evidence.
None of these is new on its own. Self-hosted chat over company documents is already available as open-source software, and cheap tools exist for each of the other three. Four inexpensive applications would not be much of a business. What changes the picture is the work that passes between them.
Take a single meeting. On Tuesday morning, a team agrees three actions. The Listen job writes up the meeting and records who promised what, by when. The Act job drafts the three follow-ups, and each goes out only when its owner approves. On Friday, the Watch job checks the records: two actions are done, one has slipped, and its owner is told, with the evidence. The following week, a manager asks where Tuesday’s actions stand, and the Ask job answers from the same records, showing only what that manager is allowed to see. Nobody copied anything from one application to another.
Figure 3. One meeting, four jobs, one shared record

Separate subscriptions can be connected, of course, through integrations. But integration across four vendors is usually partial, expensive to maintain and fragile when any one of them changes. A shared architecture makes the connection the default rather than a project. The value is not four inexpensive AI applications. It is one inexpensive system that remembers what happened across them and helps finish the work.
What runs underneath matters less than buyers assume. The leading frontier models are proprietary; their weights cannot be installed on an office server. Open-weight models can be, and they are closer than most buyers think. Epoch AI finds that the best open-weight models lag the closed frontier by about four months on its capability index, and that open models able to run on a single top-end consumer graphics card typically match the frontier of six to twelve months earlier. Last year’s frontier now fits on a well-equipped desk. Not on every desk: that finding is about a high-end graphics card, not an ordinary office laptop. But narrower models doing narrower jobs reach far more modest hardware, and for summarising a meeting, drafting a reply or answering from a policy manual, that is often enough. It has to be proved task by task rather than assumed. The company is buying completed work, not a model name.
3 The office already owns much of the infrastructure
Every office already owns an AI computing infrastructure. Most of it has never been organised to work together. It sits on desks: well-specified laptops and desktops, some with enough memory to hold a capable open model, idle for much of the day while their owners are in meetings, at lunch or at home.
The architecture that uses it has three parts, and the order of importance matters.
- An always-on office server provides the service guarantee. It routes every question, holds the models and their updates, and runs anything sensitive. If every employee laptop were switched off, the service would still work.
- Idle employee machines contribute optional capacity. They take eligible, independent tasks while their owners are away and the machines are plugged in, each running a whole model so that nothing is split across machines.
- The router uses an idle machine only when it helps. It sends work there only when the gain is measurable and the owner is unaffected; otherwise the server does the work.
In The Compute You Already Own I set out why such an office pool is plausible where a public pool of strangers’ devices is not, and the questions that decide whether it pays. The most important is timing. What matters is not total idle computing power. It is dependable compute available in the hours employees need AI. An office might have twenty idle machines at lunchtime and three at eleven in the morning, precisely when questions peak. If one dedicated server handles the load more cheaply, use the dedicated server. The business does not depend on proving that distributed office compute always wins.
It is tempting to call this an “Airbnb for compute”. As an image, it works: an underused asset put to productive use. As an operating model, it misleads. Airbnb rents strangers’ property to strangers. This is a private pool inside one company, among colleagues, managed by IT.
The economics need stating carefully too. On hardware the company already owns, the marginal compute cost of an answer is mostly electricity. The service around that compute is not free. Models have to be kept ready in memory, machines’ availability detected, work moved when a machine disappears, employee endpoints secured and failures diagnosed. Those costs belong in any honest comparison, and they are the reason the dedicated server comes first.
4 The meta-model decides what runs where
If every question goes to a large model, the system is expensive. If every question goes to a tiny one, it fails on the hard cases. The answer is a meta-model in the practical sense: a routing layer that chooses the cheapest way to complete each task correctly. It follows the ladder from The Compute Strait. Code handles dates, sums and rules. Validated memory answers what is already settled. A small local model extracts, classifies and drafts. The office server’s larger model handles harder shared work. A premium external model is called only for the cases that need it, and only where policy allows that data to leave the approved environment.
The router must itself be cheap: rules, capability checks and past evaluations first, never an expensive model asked whether an expensive model is needed. And it should record what it learns: completion, errors, corrections, response time and cost per completed task, by type of work. Over time the company comes to own an evidence-based map of what its own work requires.
Figure 4. One suite, one shared layer, compute the office owns before compute it rents

5 A tenth of the price, if the economics hold
The commercial target should be bold: roughly a tenth of developed-market per-seat prices, about $2 to $3 per employee per month for everyday workplace AI. Four things make it plausible. Open-weight models carry no per-token licence. Much of the compute is already owned. One shared layer serves four jobs instead of four vendors each building their own. And frugal routing keeps premium spending to the cases that need it.
A low price has to work for the supplier as well as the buyer, and that is where the argument is most exposed. At $2.50 per seat, a 500-person company brings in $1,250 a month and a 50-person company $125. Against that sit installation, updates, security patching, monitoring, compatibility testing and support. Those costs do not shrink in proportion to headcount. Supporting a 50-person office does not cost a tenth of supporting a 500-person one.
Figure 5. Supplier economics per office at $2.50 a seat (all costs assumed)
| Office size | Monthly revenue | Cost to serve | Monthly margin |
| 50 seats | $125 | $425 | –$300 |
| 200 seats | $500 | $500 | $0 |
| 500 seats | $1,250 | $650 | +$600 |
| 2,000 seats | $5,000 | $1,400 | +$3,600 |
Assumes $400 a month fixed per office (updates, monitoring, security, support) plus $0.50 per seat. Illustrative, not measured.
Three design choices follow. A tenth-price seat needs a minimum commitment, either a seat floor or a fixed office fee, so that small offices cover the cost of serving them. It needs standardised installation and predominantly self-service operation, because a support visit can wipe out a year of margin. And it probably needs local partners who install and support it, paid from the hardware and services they sell rather than from the subscription.
The buyer’s comparison must be complete too. For the 500-person company, the full cost includes the subscription, the office server, IT time and approved premium use.
Figure 6. The buyer’s full annual cost, 500 employees (all inputs assumed)
| Item | Assumption | Annual cost |
| Subscription | $2.50 per employee per month | $15,000 |
| Office server | $4,000, written off over three years | $1,333 |
| IT time | Two hours a week at $15 an hour | $1,560 |
| Premium AI | Administrator cap | $3,000 |
| Total | about $20,900 |
Against $120,000 for developed-market seats, that is about a sixth, not a tenth, once everything is counted. Against AI bundled into an existing suite, the money may be similar, which is why price cannot be the whole case. The case is coverage across a mixed environment, memory the company keeps and control over where data goes. The $2 to $3 seat is a design constraint to be proved in pilots, not a price the architecture has already earned. The test is cost per completed task, including hardware, IT effort and human rework, not the licence fee alone.
A flat price also cannot mean infinite work for infinite users. It means a predictable price per employee, with fair-use and concurrency limits set by the office’s own capacity: when the office is busy, answers queue or slow down; they do not generate a bill. Premium external inference is different. It should be approved by the administrator, priced separately and visible before it is spent. A flat price is a promise about the bill, not about unlimited compute.
6 Sovereignty is an operating promise
For a bank, a manufacturer, an insurer or a services firm, the attraction is not only cost. It is control. Questions, documents and answers can be processed on machines the company owns, under permissions the company sets.
The promise needs precise wording. “No data leaves the building” is too narrow: companies have remote employees, several offices, existing cloud software and, sometimes, a good reason to use a premium external model. The real promise is this: no enterprise data leaves the approved processing environment without explicit policy authorisation. That environment may span offices and a private cloud the company controls. Telemetry, software updates, connectors to other systems and premium escalation can all carry data out unless they are configured not to, which is why the promise is a policy to enforce and audit, not a slogan inherited from where the server sits. Sensitive classes of work, such as legal, HR and finance, should run only on machines IT controls, by default rather than by request.
The record-keeping needs the same precision. Storing every raw prompt indiscriminately would defeat the purpose. But a ledger that records nothing but usage is too thin for work that needs evidence. Audit records may need source references, decisions, approvals, model versions and access logs, kept under retention rules the company sets. The objective is that the enterprise keeps control of sensitive information and can prove where it went, who saw it and what was done with it.
Regulation is a reason for some buyers, not all. In India, the data-protection law does not impose blanket localisation: its cross-border framework allows transfers except to countries the government restricts, while sectoral regulators such as the RBI can impose stricter rules. Local processing can simplify governance and satisfy contractual or sectoral requirements. For most firms, it is a choice about control rather than a statutory necessity, and the essay should not claim otherwise.
Open source helps, but it is not a guarantee. Code that can be inspected makes a backdoor findable, not impossible. The stronger promise is verifiability: published code, signed releases, builds that independent parties can reproduce, documented components and external audits, practices of the kind NIST’s Secure Software Development Framework sets out. Trust comes from what can be checked, not from what is promised.
7 The layer that lasts
Underneath the four jobs sits the asset that matters most: the shared operating layer. It records what each application knows, what each employee is authorised to see and do, where each task should run and whether completed work met the agreed standard. Applications are replaceable. A company might change its meeting writer, its chat assistant or its local model next year. It should not have to replace its memory, its policies or its operating history when it does.
This is the argument of From Rented to Owned, carried into the office: own what compounds, rent the rest. Here, what compounds is the record of the company’s work and the rules around it. The models underneath can be swapped as better ones appear, and the routing adjusts to use them.
It also clarifies what kind of business this is. A suite of cheaper substitutes competes on price. A trusted, portable operating layer that helps several applications work together competes on continuity, convenience and control. The first can be undercut by any incumbent willing to cut a price. The second becomes more valuable the longer a company uses it.
8 The business model
The opportunity grows in three levels. At the first, a company saves on AI bills by running routine work on hardware it owns. At the second, it gains private AI infrastructure: local routing, permissions, memory and controlled escalation, valued for control as much as cost. At the third, several applications share one operating layer for office intelligence. The lasting advantage sits at the third level, and it comes from making many applications cheap and dependable to run, not from idle processors alone. It would be a mistake to claim all three before proving the first.
Figure 7. How the business earns, and what it refuses
| Revenue line | How it works | Why it fits |
| Base subscription | A flat price per employee, about a tenth of developed-market seats, with a seat minimum or office fee | Predictable for the buyer; covers everyone; covers the cost to serve |
| Premium escalation | A disclosed commission on approved external inference, capped by the administrator | Pays for hard cases without hidden metering |
| Hardware and partners | The always-on office server, sold or leased, installed and supported by local partners | One machine turns idle capacity into a dependable service |
| Advertising | Not offered | A product sold on keeping data inside cannot be paid for by anyone who wants to know what is in it |
Two cautions belong in the model itself. If the escalation commission becomes the main source of margin, the incentive tilts towards sending work outside; disclosure and caps exist to prevent exactly that. And the natural first market is emerging-market enterprises, where the price gap is widest, software environments are most mixed, local languages matter and data rules are tightening. Those buyers do not need a lesser version of AI. They need a different economic architecture for delivering it.
9 How the thesis could fail
Three bets should be tested separately. Product fit: does one integrated suite complete everyday work better than separate tools or the AI bundled into existing software? Economics: does a seat at around a tenth of developed-market prices, with a minimum commitment, cover models, support, updates and margin? Trust: will security and compliance teams approve a shared local service, and will employees use it without feeling their machines or their data have been commandeered?
Figure 8. Eight ways the thesis fails
| Failure | What would show it |
| Bundled AI is good enough | Companies on one vendor’s suite see no gain worth switching for |
| Open models fall short on real office work | The share of tasks escalated to premium models stays high, or human rework rises |
| The shared record adds little | Users rarely move work between the four jobs; the suite behaves like four separate tools |
| The idle pool adds nothing | One office server matches the pool at equal cost; then sell the server and drop the pool |
| The price cannot fund the service | Cost to serve exceeds revenue even above the seat minimum |
| Buyers trust global brands more than local control | Pilots convert slowly even where the product performs |
| Escalation becomes the real business | Commission revenue outgrows subscriptions |
| Global vendors cut prices for emerging markets | Developed-market tools arrive at local prices, removing most of the gap |
A ninety-day pilot in one office of 20 to 50 consenting users would answer much of this. Run the four jobs on real work against current practice, including whatever bundled or free AI tools employees already use. Serve them three ways: one dedicated office server, the server plus an idle-machine pool, and a hosted small model. Measure completion, errors, response time, availability at peak hours, human rework, energy, the share escalated outside, the share of work that crosses between jobs, the supplier’s cost to serve and cost per completed task. Set the stop rules before starting.
If the suite needs constant human rescue, the shared record adds nothing, or incumbents close the gap on price and control, this particular route is wrong. The need it addresses does not go away.
**
The first wave of AI sold extraordinary intelligence to those who could afford the invoice. The next should make dependable intelligence ordinary, private and affordable across whole organisations, in the countries where most of the world’s office workers live. The answer is not merely to make intelligence cheaper. It is to make it a shared utility inside the enterprise: available to every employee, across applications, with the company keeping control of its data, its memory and its costs.
Affordable for one person is a subscription. Affordable for everyone is infrastructure.