Products
ALEX Workers Payment exceptions How it works Trust Company Start with one workflow AI Delegation StrategyBefore AI Goes Live
Company

AI should be able to do real company work without inventing its own version of the company.

Why we exist

The gap isn't capability.

AI capability is increasing. Organisational clarity is not.

Companies run on a body of understanding that is spread across people, policies and systems. Which rule really applies, who genuinely decides, which exception is tolerated and which one gets you a phone call. That was sufficient while every operator was a person who had been here long enough to acquire it.

It stops being sufficient the moment you ask a machine to finish consequential work. The missing step is establishing which evidence, rules and approvals apply to the particular action.

Businesses don't run on answers. They run on outcomes.

VERIDOM builds what has to exist in between: a current, governed account of how the company actually operates, and Workers that run real work inside it.

How we work

The standards we hold ourselves to.

01

Persistent.

Stay with the work until it reaches a valid end or a legitimate boundary. A queue is not an ending.

02

Exact.

Name the rule, the evidence, the authority, the state and the consequence. Precision is the whole service.

03

Bounded.

Say where knowledge and permission stop. Not knowing is never treated as permission to proceed.

04

Accountable.

Any meaningful action should be able to answer “why?” and answer it with a source, not a summary.

05

Calm.

Control should be visible without theatrics. The moment a system stops is more informative than a highlight reel, so that is what we show.

06

Serious.

This is money, authority, obligations and evidence. We write about it accordingly.

Where this goes

A company should be able to change without its AI becoming quietly wrong.

The test we are building towards is unglamorous. A policy changes on a Tuesday afternoon. By that evening, every Worker that depended on the old version knows which open cases, decisions and instructions rested on it. Nobody opens ten agent configurations to update prompts.

Historical records stay intact, preserving what governed and what was decided. That does not prove the original decision was correct. Recorded dependencies identify current work that needs reconsideration.

Further out, a team deploying its fourth Worker should not have to rediscover the company. The first deployment is slow because the business has to become explicit: who owns which decisions, what governs, what counts as completion, which exceptions are real. That work should be done once.

The team still has to define the new workflow. It should not have to rediscover the company.

Today, we have demonstrated a payment-exception AI worker using reviewed rules, separate approval, ACE checks, simulated execution and receipt reconciliation. We are pre-revenue and recruiting our first paid design partner. Whether customers can establish and maintain this model economically is the next test.

Who is building it

Three disciplines, because this needs all three.

Systems architecture, compliance and security, and research methodology. A framework that is only designed well is an assertion. We wanted one that could be tested and reproduced.

Lagos, NG · Product and systems architecture

Tolulope Adebayo

Founder & Chief Executive

Designed the operating model architecture behind ALEX, and the boundary and evidence layer the Workers run against. Leads product development and the company from Lagos.

LinkedIn →

Toronto, CA · Compliance and security

Festus Makanjuola

Co-founder, Enterprise Deployment & Security · CISSP, CCSP, CISM · ISO 27001 Lead Auditor

Nine years building compliance and security architecture across Access Bank, Appzone and Mercedes-Benz Canada. Owns deployment readiness, security requirements and the operational controls needed for customer pilots.

LinkedIn →

Awka, NG · Product reliability

Oluropo Apalowo

Co-founder, Product Reliability · PhD, University of Ilorin

Lecturer at Nnamdi Azikiwe University. Brings experimental-design discipline to product reliability: testing whether ALEX gets company rules right and stops when it should, with process owners establishing the expected answers.

LinkedIn →

Open where it counts

Checking a consequential decision should not require trusting us. The record format and the checks that produce it are documented so they can be inspected, and so verification does not depend on continued dependence on VERIDOM.

How the record works →

Start with one consequential workflow.

Tell us where cases are being lost today. We reply with a time, or an honest no.