Fornax OS

Fornax Execution Consulting
GCC

Fornax OS

Your business runs because people remember to run it.

Someone notices. Someone remembers. Someone chases. Someone checks whether it actually worked. Take those people out for a week and execution stops.

The five systems
05 systems 01 live 02 in build 02 in design GCC Software we build for you
01 Assignment

Twelve jobs. No owner.

Not the work itself. The work of keeping the work moving. Nobody is assigned any of it, everybody does some of it, and it stops the week your most conscientious person is away. Eleven of the twelve shouldn't be a person's job at all.

  1. 01 Notice when something is wrong
  2. 02 Remember what needs to happen
  3. 03 Decide who should act
  4. 04 Chase people for completion
  5. 05 Interpret what the information means
  6. 06 Decide what matters
  7. 07 Train themselves
  8. 08 Monitor performance
  9. 09 Follow up, repeatedly
  10. 10 Identify risk
  11. 11 Work out whether it worked
  12. 12 Step in when execution starts to drift

Should not be a person's job 11 Stays with a person, on purpose 01

02 Gap

Software remembers. It doesn't notice, decide, chase, or check.

It holds your customer list, your invoices, your tickets, your reports, and it holds them perfectly. Then it waits. Nothing in it ever asks whether the thing it recorded actually got done. So the loop stays with you, and the software watches from the filing cabinet.

03 Mechanism

We build the layer that runs the loop.

Five questions, asked over and over about one part of your business. Every system here is the same loop, pointed somewhere different.

Plate 01 · The Fornax loop Cycling
  1. 01 Observe What's actually happening right now? Guarantee: no state is inferred. It is read.
  2. 02 Judge What does that mean, and does it matter? Guarantee: below confidence, it escalates rather than guesses.
  3. 03 Act Do the next thing, or put it in front of whoever should. Guarantee: nothing that touches your reputation sends unseen.
  4. 04 Verify Did it happen, and did it work? Guarantee: an alert closes on the condition, not on being dismissed.
  5. 05 Learn Change what happens next time because of it. Guarantee: it learns from your answers, never from its own guesses.

Returns to observe. The loop doesn't end

You stay in this loop wherever judgement belongs. What you stop carrying is the noticing, the remembering, the chasing and the checking.

05 stages · cycle 12s · no terminal state
04 Territory

Execution breaks in five places.

We didn't pick five markets. We found five points where businesses lose control, and built a system for each.

Plate 02 · Portfolio architecture Three operate · two watch

RAVEN, REPS and CASTALD act on a part of a business. JUDGE and WATCHTOWER sit above them and look down at whether execution is sound.

Build orderStated without dates. Dates go stale.

  1. 01REPSLive
  2. 02CASTALDIn build
  3. 03RAVENIn build
  4. 04JUDGEIn design
  5. 05WATCHTOWERIn design
  1. 01 / Pursue RAVEN Market Pursuit System You give it the slice of the market you want. It finds the companies, works out which are worth your time, decides how to approach each one, and keeps after them until every pursuit ends in a definite answer. What it holds isn't an email. It's a company you're currently pursuing, and exactly where that pursuit stands. In build Operating for clients today. Being rebuilt as software.
  2. 02 / Perform REPS Sales Performance System It listens to real calls and finds the exact moment a salesperson's selling breaks. Then it puts them back into that moment until they can handle it, and checks their next real calls to see whether it stuck. The simulated buyer is the equipment. The correction loop is the product. Live Selling now at salesrepshq.com
  3. 03 / Operate CASTALD Property Operating System One live picture of a property business: the buildings, the units, who is in them, the contracts, the money owed, the equipment, what's broken, who is fixing it, what it cost. Then it drives work through that picture. Deliberately narrow and deep. It knows what a unit, a tenancy and a work order actually are. In build
  4. 04 / Decide JUDGE Execution Verdict System Management decides something big. JUDGE works out what would have to be true inside the company for that to survive contact with reality, tests whether those things are true, and shows where it will break. It never says whether the strategy is right. Only whether this company can carry it out. In design
  5. 05 / Control WATCHTOWER Continuous Execution Control System It holds two pictures at once: what was supposed to be happening, and what's actually happening. When they start separating it says so, while there's still time to act. Nothing fails suddenly. It drifts, and the drift is visible long before the result is. In design
05 Proof

One of them is finished.

REPS is live, it has its own site, and people pay for it. This is the real verdict it returns on a real call, in its own colours.

Plate 03 · From the product Live output
Call verdict
Winnable, and lost
Maya Chen × Harbor Dental · uploaded call · 41 min
The deal started breaking at 14:32, twenty minutes before the objection.
The buyer said “Mondays are chaos.” It was never explored.
Same problem, 6 of the last 10 calls
Reading what the buyer needs 58
Surface answers accepted, real cost never uncovered
Train this next

When a buyer drops an aside like “Mondays are chaos,” stop and open it. That's the deal talking.

The break point is the whole trick. Not where the buyer said no, where the deal actually turned. That one moment becomes the drill, and REPS then checks the next real calls to see whether it stopped happening.

Go to REPS How the loop works
06 Reporting

Every system reports its own state.

None of them are a dashboard you have to go and read. Each one knows what it is holding and says so.

Plate 04 · Portfolio state Specimen
SystemStateHoldsUnit
REPS Live Skill profile per rep, and whether the last drill held on a real call Rep
CASTALD In build Every unit, tenancy, asset, job and cost, as one connected picture Property
RAVEN In build Where each pursuit stands and what it's owed next Pursuit
JUDGE In design The conditions a decision needs, and which are evidenced Decision
WATCHTOWER In design Intended state against actual state, and the distance between them Deviation

The unit column is the important one. It's what each system counts, and it's why none of them are interchangeable with a database.

07 / Software we build

We build these for other people too.

Five systems is what we built for ourselves. The same people build custom software and AI agents for other businesses, to the same standard, on the same principle: it should run something, not just record it.

  1. 01ScopePaid, and it produces a specification you own whether or not you build it with us.
  2. 02BuildPhased, priced per phase, and you can stop between any two of them.
  3. 03OwnYour instance, your data, and a licence that doesn't expire.
  4. 04RunWe host and maintain it, which means we stay on the hook for it working.

How we work

08 / Lineage

The product arm of Fornax Execution Consulting.

The consulting practice works on execution risk for private equity firms, family offices and capital allocators across the GCC. Its job is to say whether an organisation can actually carry out the decision in front of it.

Fornax OS exists because the same gap kept appearing inside the businesses we advised: a system that should have existed and didn't. So we built them, and then made them available.

$220M+

Capital-linked mandates advised

GCC

Where the practice operates

5

Systems in the portfolio

Fornax Execution Consulting

09 / Enquiry

Tell us what you're trying to run.

  1. 01You write
  2. 02We answer in one business day
  3. 03If it doesn't fit, we say so

Sent

We answer within one business day.