AI-native companies,
built block by block.

Most companies are bolting AI onto a business built for a world without it. That’s why the spend never shows up in the results.

somai is a studio — we build the foundations underneath, so the company runs ai-native. Block by block: one piece of the operating model at a time, built, handed over. The business keeps trading the whole way.

The layers between people and what the business knows — those go. People do more of the right things — and the returns follow.

company context (about us)
§ 01 Thesis

Thesis

The companies built before AI will not survive the era it defines.

Not because AI will replace them. That framing is wrong, and it cost the market three years of misdirected effort. They will not survive because they were built for a world where intelligence was scarce, expensive and human. That world is ending. Almost none of the incumbents are built for the one taking its place.

The consensus response has been to add AI on top: pilots, copilots, chatbots, automation layers, productivity gains. That is the wrong unit of work. Bolting AI onto a business built for scarce intelligence does not produce an AI-native company, any more than fitting an engine to a horse-drawn carriage produced a car. The ceiling most firms are pressed against is not the model. It is process, structure and how decisions get made. The firms doing it loudest will be the most exposed.

AI-native is what happens when the company is built on the other side of that ceiling. The model becomes a participant in the work rather than a tool applied to it. Knowledge is structured so the model can read it. Decisions get made with the model in the loop. Operations run on foundations the model can act on. In regulated environments, the integrity layer is engineering work, not posture. The evidence has to hold up to an auditor.

Most firms cannot do this work. Consultancies write the strategy deck and leave before anything is built. AI vendors sell the tools and assume the integration is someone else’s problem. System integrators deliver the implementation but not the architecture. The missing work is the build itself. A senior team doing the architectural thinking, the engineering work and the cultural change together, in the same room, for the duration.

That is the work somai does. We embed senior teams inside companies to build the foundations underneath them, block by block: cognition, perception, reaction, regulation, execution. Typically in eight-week blocks, with value-anchored pricing. If a foundation does not deliver the value agreed at brief, the outcome bonus is not earned. At the end of the block, the client team owns and operates it.

The next decade will be defined by companies that were built for it. We exist to build them.


§ 02 The work

Five foundations that we believe make a company AI-native. We work with you to build them one at a time, from pilot to production.

Brain COGNITION Receptors PERCEPTION Muscles EXECUTION Immune System REGULATION Nervous System REACTION

Signal architecture, four flow types.

RECEPTORS | EXTERNAL SIGNAL CAPTURE COGNITION | REACTION | REGULATION MUSCLES | EXECUTION LAYER Market RECEPTOR Regulatory RECEPTOR Operational RECEPTOR Nervous System REACTION Brain COGNITION Immune System REGULATION Process MUSCLE Delivery MUSCLE Compliance MUSCLE token feed — receptors to cognition / reaction / regulation strategic command — brain to muscles · nervous system to process feedback — nervous system & muscles return episodic learning regulation — immune system polices process & compliance

Memory architecture, at a glance.

§ memory architecture — subsystem × memory type
SemanticEpisodicProceduralWorkingProspectiveShared
Brain COGNITION
Receptors PERCEPTION
Nervous System REACTION
Immune System REGULATION
Muscles EXECUTION
full minimal none cognition-anchored

§ 03 How we work

A block builds one foundation in four stages, typically over eight to ten weeks — while the business keeps trading.

01

Blueprint

first two weeks

We meet the leadership team and the company. We read what is written down and listen for what is not. We pick one foundation, agree the hypothesis, and agree the value it earns if the hypothesis holds.

Output: a contracted brief and a value hypothesis, on one page.

02

Build

weeks 1 to 8

A senior team working directly with the business’s operators. We design in test and build in production, against real workloads, with the people who will run it after we leave. No parallel shadow IT.

Output: the foundation live, observed under load, with the client's team operating it.

03

Handover

week 9

The foundation is handed across to the business. We document the seams, the failure modes and the next reasonable extensions. You own the code, the data and the playbook outright. No licence, no retainer hook, no ongoing seats. And we continue to support where we can.

Output: a working foundation the client owns, and a thirty-page operator manual.

04

Interlock

months 1 to 6 after

We return for a quarterly half-day to read the operating metrics against the value hypothesis. If the foundation has delivered the value, the outcome bonus is earned. If it has not, it is not.

Output: a verdict on the block, written and signed by both sides.

The binary

If the foundation does not deliver the value hypothesised at brief, the outcome bonus is not earned. The fee for the work itself stands. Value is priced before the work, contracted against during it, and proved in production after it.


§ 04 Selected engagements

A few of the blocks we are building and have built — each told as the capability the client owns when we leave.

  1. In delivery
    Global retail bank · financial crime & compliance

    A detection system that finds criminal money-movement patterns the rules never caught — built, validated, and handed to the financial crime team to run.

    Installing a full detection pipeline end-to-end: graph construction over the transaction population, community detection to find natural groupings of accounts, and a sequence model trained to recognise the behavioural signatures of twelve criminal typologies — structuring, layered chains, mule networks, trade-based laundering, professional money laundering and others. Hard Concrete gates to control what the model attends to. Low-rank adaptation heads so the model can be steered to new typologies without full retraining. A predicate router that maps model output to investigator-ready case narratives. Everything built against the bank's own data, not a benchmark.

    On handover a detection capability the financial crime team operates directly, with explainable outputs an investigator can read and a regulator can examine. Period one covered nearly a hundred thousand accounts, surfaced over six thousand reportable entities, and produced a separation ratio that makes the prioritisation meaningful rather than nominal. The team owns the pipeline, the weights, and the architecture. No licence, no dependency, no ongoing seat.

    ten weeks · full pipeline build

  2. In delivery
    International wealth & retail bank · operations, risk & compliance

    A board-ready plan for practical AI across the back office — the highest-value opportunities, sense-checked for feasibility and risk, and sequenced for where to start.

    Installing a focused four-week assessment across the operational and control teams — risk, compliance and customer operations — reading the current processes and constraints, running a working session with the people who own them, and testing each opportunity for value, feasibility and risk.

    On handover a prioritised set of practical AI opportunities, with a clear recommendation on sequencing, governance and next steps — built to lift consistency and free capacity, not just cut cost, and grounded in the bank's own priorities.

    four weeks · assessment sprint

  3. In delivery
    Middle East retail bank · operations & processing

    Intelligent document processing and reconciliation, taken live end-to-end in five weeks — a pilot to prove the approach before building further.

    Installing a five-week pilot that takes one operations use case — intelligent document processing and reconciliation — end-to-end against the bank's real workflows and volumes, built to run on live cases, not demo on slides.

    On handover a working capability the operations team runs and owns, with outcomes measured against the value hypothesis and a clear, evidence-based read on whether to scale into a longer-term engagement.

    five weeks · pilot

  4. Completed
    Major European retail bank · everyday banking

    The bank now has a build-ready everyday-banking strategy — a prioritised set of ai-native propositions, sequenced by value and feasibility.

    Before the everyday-banking AI question sat as scattered point ideas, with no shared basis for deciding what to build, in what order, or how it fit an ai-native operating model.

    Now a prioritised portfolio of ai-native propositions — each defined, pressure-tested against strategy, regulation, and the competitive field, with a build case and sequencing — owned by the bank and actionable without us.

    strategy definition


§ 05 Studio

A studio of senior operators. No juniors, no offshore, no associates in the room.

somai is a team who have run the kinds of companies we work in: heads of operations, engineering leaders, CFOs, chiefs of staff, and founders. Everyone has a fundamental belief in the power of AI when properly implemented and built into the foundations of a modern business.

Most of the bench earned its scars in places where ambiguity is not forgiven: under regulators, auditors and risk committees. Those are the surfaces an AI build has to survive. The principles travel; we take work outside them too.

We take the principle that the studio installs and the client operates seriously. We do not sell retainers, managed services, or ongoing seats. We are not the team that runs your operations after we leave. Your team is. Our job is to make sure your team can.

We hold limited capacity for a few deep engagements per year. That is not scarcity theatre. A senior studio at this depth cannot run wider without becoming the consultancy it was founded to displace.


§ 06 Thinking

Essays from inside the build. Lessons we’ve found worth writing down.

RSS
  1. 06.06

    Most AI spend never reaches the P&L

    The failure rate isn't a model problem. It's an operating-model problem — and it has a specific cause.

    26 June 2026 read more
  2. 06.05

    What ai-native actually means

    The market defines ai-native by birth certificate — the firms born with the model. The truer definition is structural, not chronological, and it is fully available to the company you already run.

    23 June 2026 read more
  3. 06.04

    What stays human

    As working intelligence becomes abundant, the scarce thing is no longer analysis. It is judgement, taste, and the will to mean it.

    14 May 2026 read more
  4. 06.03

    Decisions with the model in the loop

    AI as a tool you pick up, or an agent that replaces you. Both pictures miss the real change. The shift is to the loop.

    16 April 2026 read more
  5. 06.02

    A company your model can read

    A company knows far more than it can say. Until that knowledge is made legible, a model cannot do anything useful inside it.

    12 March 2026 read more
  6. 06.01

    The end of scarce intelligence

    Every company alive today was built around the assumption that working intelligence is scarce. That assumption has quietly stopped being true.

    10 February 2026 read more

§ 07 Contact

Write to hello@somai.studio about the block you want built.

Who should write to us A chief executive, or a chief of staff or senior leader with the mandate to commission. We do not take work where the destination is a pilot rather than production.
What to write The company, the foundation you suspect needs building first, and the value you would expect from a block that worked. Two quick paragraphs to get us started.
Capacity Three to four deep engagements a year. We reply to every note within a few working days.