Most companies own more than their business model can charge for.
Whether the company is two years old or a hundred, the pattern is the same. The assets are already on the balance sheet. The data is already being collected. What's missing is either the model that turns them into revenue, or the redesign that changes what the existing operation earns. Both are design problems, not technology problems.
All three start from the same place — what already exists — and all three end in a drawn model. What differs is whether the revenue line is new, existing, or somebody else's in a market they cannot reach.
An asset, dataset or capability the organisation already holds becomes a product someone else will pay for. The existing business is untouched; a revenue line is added beside it.
The operation stays the same on the outside and earns differently on the inside. Throughput, cost per unit and utilisation are redesigned as one system rather than three departmental targets.
A model that works in one market is usually invisible in three others — not because the product is wrong, but because the buyer, the price point and the procurement path are different. We redesign the commercial model for the new territory and carry it there.
A sketch is a picture of an idea. A design is a specification something gets built from — priced, sequenced and owned. Four parts, delivered together; a model missing any one of them is a document, not a design.
| Item | Part | Description | Delivered as |
|---|---|---|---|
| BM-01 | Revenue model | Who pays, for what, on what basis, and why they keep paying. Priced, with the unit economics worked through rather than asserted. | Model + workings |
| BM-02 | Operating architecture | The data, systems and decisions the model depends on — drawn as one diagram a board can read in a minute. | Drawing set |
| BM-03 | Capital story | The version an investor, a grant committee or a ministry can act on. Same model, framed for whoever is writing the cheque. | Narrative + figures |
| BM-04 | Execution sequence | What gets built first, what it costs, who owns it, and the point at which the model starts paying for itself. | Sequence + owners |
In capital-heavy industries the asset is rarely the constraint — the decision layer over it is. Dispatch, allocation, schedule. Every model is drawn before it is written, and priced before it is drawn — if it cannot be priced, it is not a design yet.
Households across the Gulf and Europe are installing batteries, solar and EV chargers. Each is bought to do one job: cut a bill. Once installed it sits idle most of the day.
The hardware was already paid for. What did not exist was a model letting one asset earn three times, from three different buyers.
Vara is the dispatch layer that decides, second by second, whether stored energy is worth more to the household, the grid operator, or the wholesale market.
Canvas is the instrument that sits behind every engagement. It holds the organisation's current position across the dimensions that matter — AI readiness, resource visibility, governance, capital exposure — and the target it has decided to reach. As new data arrives the position moves, so progress is something you can see rather than something you assert at the end of a programme.
The first live deployment is currently being built for a private hospital group in the Gulf. The gap between current and target state is the engagement.
State-scale agricultural productivity. Land, water and grower networks that already exist, with an allocation and verification layer that turns yield improvement into something a development financier can underwrite.
Processing capacity co-located with generation, so the energy input becomes controllable and the cost position is defensible against imports rather than dependent on subsidy.
A clinical operating model where throughput, cost per episode and capacity utilisation are designed as one measured system instead of three departmental targets.
A proposition for technology owners, not buyers. If the product works and the geography doesn't, the barrier is almost never the product.
Founders who have built something that works in one market rarely have a route into another one eight thousand kilometres away — and the instinct is to treat that as a sales problem and appoint a reseller.
It is a design problem. In a new territory the buyer sits in a different seat, the price point is different, procurement runs on a different clock, and the capital story has to be told to a different kind of committee. The product is finished. The commercial model for that market does not exist yet.
That is the same work as everything else on this page, applied to a market rather than a business — and it is why we take territory rather than referral fees. A market has to be built, not introduced.
We work under exclusive territory for India and the GCC, with a defined term and a performance floor, so the incentive to build the market properly sits on our side of the table. Introductions are free; markets are not.
The sequence is fixed because the failure modes are predictable. Pricing comes third, not last, for exactly that reason.
An architect does not pour the concrete, and the drawing is still what gets built from. The studio designs; it does not implement. Build is assembled from specialist partners under your contract or ours — data engineering, platform, integration — so capacity scales with the project instead of with a payroll you would be funding between projects.
The models are not invented case by case. They come from a single thesis about where unclaimed value sits — that what an organisation's resources return and what they cost are one question, not two. Every drawing on this site is an instance of it.
A business model has to be coherent, and coherence is hard to get from a committee. The design is done by one person so the logic holds end to end — and everything downstream of it is assembled from people who do that one thing well.
That structure is why a studio this size can credibly take a model to a board, a ministry or an investment committee. You are buying a design, not a team you have to keep busy.
The work sits where AI and resource economics meet — because that is where most of the unclaimed value currently is, not because either is interesting on its own.
That is enough for a first conversation. If there is a model in it you will know inside an hour — and if there is not, you will know that too.
Tell me what you think is underused. No deck required.