The Seven Layers of the ESRE Intelligence Engine

The engine is not a single product. It is seven interconnected layers that together constitute something that has never existed in the African enterprise market.

Layer 1 — The Diagnostic Schema

This is the foundation. Everything else is built on it.

The schema is the structured data model that defines how an organisation is read. It maps every dimension of enterprise performance across the three domains and nine capabilities into a set of quantifiable variables, each with defined measurement criteria, scoring logic, and benchmark references.

Here is what that means in practice. When a Senior Consultant runs a diagnostic at Apex Logistics, they are not taking unstructured notes and writing a narrative report. They are populating a schema. Every stakeholder interview is structured around capability-specific question sets that extract scoreable responses. Every system audit produces a structured output. Every process observation maps to a defined variable in the schema. By the end of the diagnostic, the organisation has been reduced to a rich, structured data object — not a document.

This is the critical design decision that separates the ESRE Intelligence Engine from every other consulting methodology in the market. A McKinsey engagement produces a PowerPoint deck and a Word document. Those outputs are human-readable but machine-unreadable. You cannot compare them to other engagements. You cannot trend them over time. You cannot train a model on them. Crelligent's schema produces structured data that can do all three.

The nine capabilities each have sub-dimensions. Each sub-dimension has measurement variables. Each variable has a scoring rubric from one to ten. The aggregate of those scores, weighted by the client's sector and operating context, produces the ESRE Health Score. The schema is the engine's DNA — everything else depends on it being precisely defined, consistently applied, and continuously refined based on what the data reveals.

Layer 2 — The Data Ingestion Layer

The schema defines what to measure. The ingestion layer defines how the measurement happens — and this is where the engine becomes genuinely powerful.

There are three ingestion channels and they work simultaneously:

Human-mediated ingestion is the starting point. The Senior Consultant and Business Analyst run structured diagnostic interviews, workshops, and system audits. Their observations are entered into the schema via a structured diagnostic interface — not a free-text field, but a guided input system that captures scoreable responses against each capability dimension. This channel is high-quality but low-velocity. It produces the most accurate inputs but requires skilled human time.
System integration ingestion is where the engine begins to become self-feeding. The client connects their existing enterprise systems — ERP, HR systems, financial management software, CRM, fleet management tools — to the ESRE engine via secure API connectors. The engine reads payables cycle times, approval latency, data completeness rates, staff turnover patterns, customer complaint volumes, procurement lead times, and dozens of other operational signals directly from the source systems. No human intermediary. No management-curated presentation of the data. Raw signals from the actual systems that run the business. This channel is the most important one long-term because it eliminates the most corrupting element of any enterprise assessment — the human filter.
Field telemetry ingestion is the CEM and PRISM layer. Physical assets — generators, fuel tanks, vehicles, production equipment — are connected via the Edge Module. Their performance data streams continuously into PRISM and from PRISM into the broader ESRE engine. This channel provides something that no other consulting-adjacent product has: ground-truth operational data from the physical layer of the enterprise. You are not just reading the systems that manage assets. You are reading the assets themselves.

Layer 3 — The Scoring and Intelligence Layer

This is the engine's brain.

The raw inputs from all three ingestion channels are processed by the scoring layer, which does five things:

Capability scoring — each of the nine capabilities is scored across its sub-dimensions using the schema's rubric. The score is not a simple average. It is a weighted composite that accounts for the relative importance of each variable given the client's sector, size, and operating context.
Bottleneck identification — the engine does not just score. It identifies the specific intersections between capabilities where constraint is occurring.
Health Score synthesis — the nine capability scores are aggregated into the overall ESRE Health Score using a sector-calibrated model.
Benchmark positioning — every score is instantly positioned against the engine's accumulated benchmark dataset.
Causal chain mapping — the most sophisticated function of the scoring layer. The engine identifies not just where problems exist but how they are connected.

Layer 4 — The Blueprint Generation Layer

The diagnostic tells you what is wrong. The blueprint layer tells you what to build instead.

Once the scoring layer has produced a health score, bottleneck map, and causal chain analysis, the blueprint layer begins generating the architecture for the redesigned system. This layer is the most human-intensive of the seven — the Senior Consultant's expertise is irreplaceable here — but the engine scaffolds the work in ways that dramatically reduce the time required.

The blueprint layer works in three modes:

Constraint-to-prescription mapping — for each identified bottleneck, the engine has a structured library of proven interventions drawn from the accumulated dataset of past engagements.
Architecture templating — the three engineered system blueprints visible in the Apex Logistics portal (Target Operating Model, Data Architecture Topology, Governance Matrix) are not produced from scratch every time. They are generated from intelligent templates that are pre-populated with the organisation's specific data from the diagnostic schema.
Dependency mapping — the blueprint layer identifies the sequencing logic for the Build phase. Which interventions must happen before which others? Which capability improvements unlock the most downstream value? The engine maps the dependency tree so that the Build phase is intelligently sequenced rather than arbitrarily ordered.

Layer 5 — The Implementation Intelligence Layer

This is the layer that makes the Executive Command Center possible.

Once the Build phase begins, the implementation intelligence layer tracks everything — not at the project management level of tasks and deadlines, but at the system performance level of what is actually changing as a result of the work.

Embedded operator tracking — every Embedded Lead working on a Build phase has a structured reporting interface that captures not just what they did this week, but what system variables moved as a result.
Score delta tracking — the ESRE Health Score is not static between formal reassessments. Sub-dimension scores are updated in near-real-time as Build phase work completes. The CEO can watch their score move as each system is redesigned.
Milestone intelligence — the progress indicator is linked to a defined set of system changes that must occur. The engine knows what completion looks like in schema terms — what the sub-scores should be when the build is complete — and tracks progress toward that target state continuously.

Layer 6 — The Continuous Intelligence Layer

This is where the engine becomes permanently valuable rather than project-specific.

After the Build phase completes and the client moves to Phase 4 — the Evolution retainer — the intelligence layer operates continuously without requiring active engagement effort.

Automated reassessment — the engine continues to read the client's integrated systems and field telemetry after the Build phase. Sub-dimension scores are recalculated periodically. The Health Score is formally reassessed every quarter.
Drift detection — organisations that have been redesigned will drift back toward their old patterns if not monitored. The ESRE Intelligence Engine watches. If a score begins to deteriorate, the engine flags it. This is why the Evolution retainer is not just a revenue mechanism — it is the product that makes the transformation permanent rather than temporary.
Market signal integration — as the dataset grows, the engine begins cross-referencing individual client scores against sector movements. This transforms the intelligence layer from a client-specific tool into a market intelligence capability.

Layer 7 — The Data Intelligence Layer

This is the layer that most people will not see coming until it is already built. And it is the layer that makes the big bet irreversible.

Every engagement, across every client, across every sector, is producing structured data in the same schema. After fifty engagements this is a rich dataset. After two hundred it is a unique one. After five hundred it is a national asset.

Sector intelligence products — selling aggregated, anonymised intelligence back to the clients who helped create it. As the dataset grows, the intelligence products become more granular, more predictive, and more valuable.
Predictive diagnostics — with sufficient historical data, the engine begins to identify leading indicators of system failure. The engine can identify this pattern early and alert the client before the crisis occurs.
AI-augmented diagnostics — this is the horizon play. When the dataset is large enough, machine learning models trained on it can produce a preliminary ESRE Health Score and bottleneck hypothesis for a new client from their system data alone, before a Senior Consultant has spent a day on site.

What the Engine Looks Like to a Client

At the surface, the client never sees seven layers. They see one thing: the Executive Command Center. The health score that tells them where they stand. The bottleneck cards that tell them what is preventing their peak performance. The blueprints that prove Crelligent built something real. The implementation tracker that shows them who is doing what right now. The telemetry panel that confirms their systems are running. The credit wallet that lets them extend any of it instantly.

What they do not see — and do not need to see — is that every number in that portal is the output of a diagnostic schema reading their organisation, a scoring engine processing those readings, a benchmark dataset contextualising the scores, a blueprint library generating architecture options, an implementation intelligence layer tracking what is changing, and a continuous intelligence layer monitoring what persists.

What the Engine Looks Like to Crelligent

It is the firm's compounding asset. Every engagement makes it more accurate. Every sector added makes the benchmarks more precise. Every build phase completed adds an intervention outcome to the prescription library. Every Evolution retainer client is a continuous data stream. The engine gets smarter every month without requiring proportional investment in additional human capacity.

This is why it is the core technology and not a product feature. Products can be copied. A dataset built from two hundred engagements over four years, encoded in a proprietary schema, training a diagnostic model that has seen the inside of every major sector in Nigeria — that cannot be copied. It can only be built. And it can only be built by a firm that had the discipline to start building it from day one, consistently, engagement after engagement, in the same structured format.

Crelligent starts building it with the first client that walks through the door.