In build Agent

The BSaC_ agent

A prototype exists. The MVP is in build. A human approves every change.

  1. Prototype: built ·
  2. MVP: in build ·
  3. General availability: later

Consulting today is delivered by people.

The aim

We are building an agent that aims to keep a company’s strategy traced to its evidence.

It aims to watch the signals a strategy rests on, flag the claims that stop holding, and propose a fix. The longer aim is for the method to run inside the client organisation, not only in a consultant’s hands.

The analysis is the agent’s. The decision is yours.

It aims to do the heavy analysis work. A human approves every change.

Status

What exists today, and what does not yet

Exists today

  • The method, published. The white paper is auditable and open to review. It covers the method, not the agent.
  • We are implementing the method with a client company, in its own strategy. Consulting work, delivered by people.
  • A series of teardowns. Real companies’ strategies traced to public evidence, on YouTube.
  • A strategy-chain prototype with a deterministic validator. It runs on an illustrative company (Tallowmere Payments) with a seeded signal. Its proposals are pre-written placeholders, not model output.
  • A silent recording of one prototype run. 1 min 4 s.

Planned

  • An MVP with design partners. In build.
  • Live AI proposals. They replace the pre-written placeholders.
  • General availability. Later.

Recorded run

A recording of the prototype

This is a recording. It is silent, so the eight beats are written out beside it.

Recorded run · prototype
Illustrative company (Tallowmere Payments) · seeded signal · pre-written proposal · silent, 1 min 4 s
Download the recording (MP4, 5.0 MB)

The eight beats, as text

  1. Idle The prototype shows the illustrative company’s strategy as a graph of 13 claims: 11 traced to evidence and 2 declared as assumptions.
  2. Signal sent A seeded signal is sent in: a regulator delays a rule the strategy relies on.
  3. Claim breaks The claim that rested on that rule is marked as broken.
  4. Chain lights up The claims built on it are flagged as affected: 5 affected, 7 untouched.
  5. Derivation Selecting a decision traces it back, path by path, to the evidence that no longer holds.
  6. Proposal The prototype shows three pre-written options, labelled as a placeholder and not model output. Asked to add evidence, its validator refuses: evidence must come from a person.
  7. Fix accepted A person accepts one option, declaring an assumption with an owner and a test date, and records why.
  8. Counts settle The counts update and come to rest at 10 claims traced and 3 declared assumptions, and the decision log records the change.

Who leads

Who is behind it

Portrait of Aliaksei “Alex” Ivanouski

Aliaksei “Alex” Ivanouski

Fractional CTO & Founding Engineer

Creator of the Business Strategy as Code method. Started as a military engineer, then spent 10+ years building products across fintech, adtech, social platforms and large-scale backend systems.

  • MBA with Distinction, Bayes (formerly Cass), City St George’s, University of London.
  • Chief Technology Officer Programme, National University of Singapore.
  • AI: Business Strategies and Application, UC Berkeley Haas.

Next step

Take part, or stay informed

1 · Take part

Design partners are companies that run the method with us on a real strategy question, and help shape the agent as it is built.

Apply as design partner

2 · Stay informed

Join the agent waitlist

Leave your email and we will tell you when the agent opens.

Add name, role, company (optional)

We use your email to tell you about the agent, including when it opens. See the privacy policy. You can unsubscribe at any time. No date is promised.

3 · Talk to a person

If you would rather talk it through first, request a call.

Request a call