The operating brain of your company
Cortexia connects every system you already run, holds the whole organisation in memory, and executes the work end to end, under policy you set and can audit at any moment.
Cortexia: operations
Signal in
Ledgerworks
PO #4471 raised
Relaytics
Contract renewed
Personnel OS
Joiner starts Mon
Decision trace
Perceive
3 signals ingested
Remember
Matched 12 precedents
Decide
Within policy threshold
Execute
Written back to ledger
Outcome
Executed
Purchase order approved and filed. Supplier record updated.
- Policy
- PROC-04
- Accountable
- H. Marsh
- Reversible
- Yes
Trusted by operators at
Signal enters on the left, becomes memory, passes judgment, and leaves as completed work. The line running back is the part that matters most. Outcomes return as precedent, so the system is better at the same decision next time.
Request in
01
Orchestrator
01
Team leads
05
Working agents
60
Finance
Procurement
People
Revenue
Compliance
Ledger, close, reconciliation
Suppliers, orders, receipts
Joiners, contracts, absence
Pipeline, renewals, quotes
Policy, audit, jurisdiction
01A request arrives: one invoice, one hire, one exception
66 agents
Sources
Effects
Outcome returns as precedent
IngestSensory: Reads live state from every connected system and attributes each observation to its source.
- 01Signal intake
Streams state continuously: current, not synced overnight.
- 02Memory graph
Decisions stored with evidence, alternatives and outcome.
- 03Policy gate
Thresholds and risk classes the system cannot route around.
- 04Execution + audit
Real writes, every one reversible, on an immutable trail.
A company brain is not one model answering questions. It is four systems working together. Each has a distinct job, each independently governable.
The four layers are the map. This is the territory: every stage a single supplier invoice passes through, from the moment it lands to the moment its outcome becomes precedent for the next one.
Request lifecycle
01/08
Request lifecycle
01/08
- 01Sensory
Intake and normalisation
The invoice arrives as a PDF in a shared mailbox, in one of about forty shapes the same document takes across a company. Cortexia extracts the fields, converts them to a canonical form, and attaches provenance to every value it read.
- Layout-agnostic extraction: fields are found by meaning, not by pixel position, so a supplier changing their template does not break the pipeline
- Currency, tax basis and date formats normalised to the organisation's canonical units
- Every extracted value keeps a pointer to the exact region of the source document it came from
- Low-confidence fields are flagged rather than guessed, and become questions later
01/08SensoryTypical intake
1.8s
- 02Sensory
Entity resolution
A name on a document is not an entity. Cortexia resolves the supplier against the ledger, the CRM and the contract store. The same company appears as three different strings in three systems, and treating them as three suppliers is how duplicate payments happen.
- Fuzzy matching over registered names, trading names, tax IDs and bank details
- Conflicting records surface as a reconciliation task rather than a silent merge
- New entities are created only when no match clears the threshold
02/08SensorySystems queried
6
- 03Cortex
Context assembly
The graph is walked outward from the resolved supplier: open purchase orders, delivery receipts, the governing contract, payment history, and any prior dispute. What comes back is not documents but a structured position.
- Three-way match against the purchase order and goods receipt
- Contract terms parsed into machine-checkable clauses: payment window, price schedule, penalties
- Anomalies computed against this supplier's own history rather than a global average
03/08CortexGraph hops
4
- 04Cortex
Precedent retrieval
The most valuable question is what the company did last time something looked like this. Cortexia retrieves prior decisions in the same class, weighted by similarity, recency and whether the outcome turned out well.
- Similarity computed over decision features, not text: amount band, supplier risk, contract type
- Precedent from a superseded policy decays in weight instead of arguing for a stale answer
- Contradictory precedent is surfaced explicitly rather than averaged away
04/08CortexPrecedents matched
14
- 05Prefrontal
Policy evaluation
Policy compiles to a decision tree the system evaluates in full. No shortcuts, no partial application. Every clause that fires is recorded with the values that triggered it, which is what makes the decision auditable afterwards.
- Thresholds evaluated against the resolved amount, not the claimed one
- Risk class derived from supplier history, jurisdiction and payment method
- Segregation-of-duties checks run before anything else, and a violation stops the process outright
- The exact policy version is pinned to the decision, so replaying it later is exact
05/08PrefrontalClauses evaluated
23
- 06Prefrontal
Decision and confidence
The system produces a recommendation and a confidence, and the two are treated separately. High confidence inside an autonomous class executes. Anything else routes. Low confidence on a routine case is itself a signal worth reading.
- Confidence reflects evidence quality, not model certainty: a missing goods receipt lowers it regardless of how clean the arithmetic is
- Gate routing resolves the accountable human from the org graph, with delegation windows honoured
- The reviewer receives the evidence, the precedent and the recommendation, not a blank approval form
06/08PrefrontalAutonomous rate
68%
- 07Motor
Execution and verification
Execution is a transaction, not a fire-and-forget write. Cortexia posts to the ledger, updates the supplier record, schedules the payment, and then reads its own work back to confirm the systems agree with what it believes it did.
- Idempotency keys on every write, so a retry after a timeout cannot double-post
- Read-after-write verification against each target system
- Any divergence rolls the whole step back and raises it rather than leaving a half-applied state
- A reversal path is stored alongside the action before the action is taken
07/08MotorRollback window
Unbounded
- 08Cortex
Outcome capture
The loop closes here. Weeks later, when the payment clears or a dispute opens, that result is written back onto the original decision. A decision with an outcome attached stops being a record and becomes evidence.
- Outcomes attach asynchronously: the system waits for reality rather than assuming success
- Human overrides are stored with their stated reason and weighted heavily as counter-examples
- Decision classes whose disagreement rate climbs are flagged for policy review
08/08CortexFeeds
Next decision
Cortexia is judged on whether the work is finished, not on whether the answer sounded plausible. These four capabilities are the whole product.
- 01
Perceive
Connect the systems your company already runs on and turn scattered state into one live operational picture.
- 02
Remember
Hold institutional knowledge as a queryable graph, so precedent and reasoning outlive the people who created them.
- 03
Decide
Apply policy, weigh evidence, and route anything consequential to the human who owns it.
- 04
Execute
Carry processes to completion across departments, with every action logged, reversible, and attributable.
Aggregate figures across deployed organisations. Every one of these is a measurement of work completed, not of dashboards viewed.
Decisions routed
48,210
Across all connected systems
Memory nodes
12.4M
Entities, decisions, precedent
Hours returned / mo
9,600
Given back to the org
Decision mode
- Autonomous
- 68%
- Human-approved
- 32%
Process coverage
+212%
Of mapped operations: now 73%
Processes autonomous
1,940
Running without hand-off
Operational throughput
184%
Work completed per head
Everything else in Cortexia is a connector or an interface. These are the parts that make it a brain rather than a very well-integrated dashboard.
- 001
Organisational Memory Graph
Entities, relationships, decisions, and precedent held in a single structured model. Ask why a supplier was chosen in 2023 and get the reasoning, the alternatives, and the person who signed it off.
- 002
Policy & Judgment Engine
Encode what the company will and will not delegate. Thresholds, risk classes, and jurisdictional rules compile into gates that Cortexia cannot route around.
- 003
Autonomous Process Execution
Procurement, onboarding, invoicing, reporting, and compliance workflows run to completion across systems, with rollback, replay, and a full audit trail on every step.
Cortexia is deliberately not a system of record. Your ledger stays your ledger. It reads their state, reasons over it, and writes back through their own APIs.
- Bidirectional
- Least-privilege by default
- Context-aware
- Fully audited
ERP & Finance
Ledgers, spend, and the numbers the company is judged on.
- LedgerworksGeneral ledger and month-end close
- ProcuraPurchase orders and supplier records
- Remitly CorePayables and payment runs
- FiscoraTax, filings, and statutory reporting
People & HR
Headcount, onboarding, and everything that touches a contract.
- Personnel OSHRIS and org structure
- OnboardlyJoiner, mover, leaver workflows
- TimeframeAbsence, scheduling, and capacity
- Certify HRCompliance training records
CRM & Revenue
Pipeline, contracts, and the commitments made to customers.
- RelayticsCRM and opportunity data
- SignatoryContract lifecycle and e-signature
- RenewlySubscriptions and renewals
- QuotientQuoting and price approvals
Knowledge & Docs
Where the reasoning behind past decisions is actually written down.
- ConfluencyInternal documentation
- ShareDockEnterprise file storage
- GitForgeRepositories and technical context
- NotaroTeam notes and meeting records
Communication
The channels where work is requested, argued about, and agreed.
- LoopholeTeam chat and channels
- MailgridEmail and shared inboxes
- ConveneCalendars and meetings
- ThreadlineTicketing and internal requests
Operations & BI
Warehouses, dashboards, and the systems that run production.
- WarehausData warehouse and modelling
- MetriclyBI and reporting layer
- PipeflowOrchestration and ETL
- SentrixMonitoring and incident data
Anything with an API can be connected. Bespoke connectors are built with you during onboarding.
You are not buying licences for people to log in. You are buying the work the brain completes, so that is what we meter.
Signal
For teams mapping their first processes and seeing what the brain already knows.
Start free- SeatsUp to 5
- Decisions / mo500
- Connectors3
- Memory retention90 days
Cortex
Most deployedFor companies running real operations through Cortexia across several departments.
Get started- SeatsUp to 100
- Decisions / mo25,000
- ConnectorsUnlimited
- Memory retentionUnlimited
Enterprise
For regulated organisations that need residency, private deployment, and assurance.
Talk to sales- SeatsUnlimited
- Decisions / moCustom
- ConnectorsUnlimited
- Memory retentionUnlimited
| Compare plans | Signal | Cortex | Enterprise |
|---|---|---|---|
| Scale | |||
| Seats | Up to 5 | Up to 100 | Unlimited |
| Decisions / mo | 500 | 25,000 | Custom |
| Connectors | 3 | Unlimited | Unlimited |
| Memory retention | 90 days | Unlimited | Unlimited |
| Intelligence | |||
| Memory graph | |||
| Precedent retrieval | |||
| Autonomous execution | |||
| Decision simulation | |||
| Governance | |||
| Policy engine | Basic | Full | Custom |
| Approval gates | |||
| Immutable audit trail | |||
| Data residency | EU or US | Any region / on-prem | |
| Support | |||
| Support | Community | Priority | Dedicated team |
| Onboarding | Self-serve | Guided | White-glove |
| Uptime SLA | 99.9% | 99.99% | |
Cortexia is deployed inside finance, procurement, and shared-service functions where being wrong is expensive.
„We had eleven systems and no single place that knew what the company was actually doing. Cortexia became that place in about six weeks, and it has been running our procurement approvals ever since.“
Questions worth asking
Still deciding?
If you run complex processes or work under a regulator, the honest answer usually needs a conversation rather than a page.
Talk to usIt runs the operational work of a company. Cortexia connects to the systems you already use, builds a live model of how the organisation actually functions, and then executes processes across departments, whether procurement, onboarding, invoicing, reporting or compliance, under policy you define. It is not a chatbot bolted onto your data; it is the layer that holds the company's memory and does the work.
Give your company something to think with
Connect a few systems, watch it reason for a fortnight, and decide for yourself what it should be trusted to run.