Home  /  Methodology

Methodology — the discipline behind the work

The discipline behind the work — and the person behind it. If you are weighing whether to trust this practice, start with the founder's letter. Below it: a public changelog of how the methodology keeps itself honest, the categorical Glossary, and the working Templates from real engagements — a practice you can audit before you hire it.

— How we keep the analysis honest · changelog

Cross Data publishes the evolution of its own methodology — and now its tools — in the open: a practice you can audit before you hire it. Six recent releases (v2.3–v2.8) share one idea — each closes one more way an analysis can fool itself, from reading the market to making the decision; the newest, Earned Confidence (v2.8), turns that same discipline on our own playbook. Open any note to read it in full; earlier versions are archived on request.

Methodology · Product release · ESI Telegram Radar

ESI Telegram Radar — your daily strategic briefing

It turns the daily flood of external news into a short, checked brief — only the new signals that touch your next decision, delivered to your team's Telegram. Leadership starts the day informed; the team starts it aligned on the same facts.

ESI Telegram Radar is a continuous monitoring instrument. Every day it scans your external environment, filters out noise and anything you have already seen, and sends only the few new, decision-relevant signals to your team's Telegram channel — in daily or weekly mode, tuned to your company, sector, and market.

"A news feed shows you everything. The radar shows you only what is new, and only what touches a decision — with the 'so what' already written in."

What it changes for leadership

Most briefings begin with catching up — five people comparing what they each saw overnight. The radar removes that step. The brief is already in the channel before the standup, so the meeting starts on what to do, not what happened.

  • Start informed. Walk into the daily briefing already knowing what changed outside.
  • Coordinate the team. Everyone reads the same brief, so the conversation starts aligned instead of catching up.
  • Share one picture. One sourced read of what moved — not five private feeds and a guess about which one is right.

How it works, in plain steps

  • It scans the outside world across four areas — competitors, technology, your category's language, and demand.
  • It keeps only what matters. Most of what it scans is noise, repeats, or irrelevant — filtered out, so only the few signals that actually shape your reality reach you. The job is separation: signal from noise, not more news.
  • It distills only what is new and material — and writes, for each one, the "so what for you" in a sentence.
  • It remembers and tracks. The signals that matter go on a watch-list and are followed across days — you are flagged only when there is a real update, so a slow-burning shift never slips past you.
  • It draws the conclusion. Every signal is tagged — act, watch, or note — and how sure it is: high, medium, or low.
  • It checks itself before it sends. Each signal links to a real source, nothing is invented, the confidence is honest, and it never manufactures urgency — a threat is something to watch or act on, never doom.
From a flood of news to a short, checked brief
Fewer items, each one real: the radar scans wide, filters hard, and ships only the short list that bears on a decision.

Universal, customizable, accurate

  • Universal. It works for any company, sector, or market — the discipline stays the same; only the watch-list changes.
  • Customizable — made to order. You choose what it watches: your competitors, your sector, your market, and the specific questions you care about. Order one feed for the leadership team, or a different feed per role — each tuned to the decisions that person actually makes.
  • Accurate. It deduplicates against everything it has already reported and checks every signal against its source — so the brief stays short and trustworthy. Fewer items, each one real.

Daily or weekly

Daily is a short morning brief, ready before the standup — for teams that decide on a daily rhythm. Weekly is a synthesis of the week's material signals — for teams that decide on a weekly cadence. The radar is the always-on layer of the same methodology behind our Diagnostics and Decision Packs: the continuous sensor that keeps the read current between deeper engagements.

Common questions

Is this just a news feed? No. A feed shows everything; the radar shows only what is new and decision-relevant to you, with the "so what" written in. It typically scans around thirty to eighty sources to surface about five.

Can we tune what it watches? Yes — by company, sector, market, and role. Each team member can get a feed shaped to their decisions.

Daily or weekly? Both. Daily for a morning-briefing rhythm; weekly for teams that decide on a weekly cadence. It comes free with a Diagnostic and a Decision Pack, and is included for the whole team in Kairos.

Order an ESI Telegram Radar for your company

Free trial for 12 days Free customization · first 4 months

Get it for free starting with ESI Diagnostic.

Methodology · v2.8 · Earned Confidence

Earned Confidence — track record over repetition, and a Red Team that attacks our own playbook

Confidence is earned by a graded track record, not by repetition — and the Red Team now attacks the shape of our own recommendations, not just the claims.

It is easy for any method to grow confident in its own habits. v2.8 adds the checks that keep confidence tied to evidence and outcomes — and turns the same adversarial discipline we apply to a client's strategy onto our own defaults.

"A conclusion earns no extra confidence for sounding like us — including the move we are most fond of recommending."

How it works, in plain steps

  • Confidence is earned by outcomes, not repetition. Our forecasts are graded on a schedule against what actually happened, and a pattern earns standing from its track record — not from how many times it has been used. A prediction that misses is recorded as a miss, in the open; it is not explained away after the fact.
  • The Red Team now attacks the frame, not just the claims. Independent review used to stress-test the individual conclusions. It now also asks whether the whole shape of the recommendation was reached because the evidence forced it — or out of habit. A strategy that survives only because it is familiar is sent back, not shipped.
  • No house-flattery. A recommendation gets no free confidence for matching our own categorical language or our own go-to-market — including the moves we like best. When the advice starts to look like our favorite answer, the evidence bar goes up, not down.

Why this matters for you

A high-confidence read is high-confidence because the evidence and the track record earned it — not because it is a story we like telling. We hold our own playbook to the same bar we hold everyone else's, and you can see the standard being applied.

The same named, dated, auditable evolution chain — now pointed at our own defaults too. Additive, no parallel machinery.

Methodology · v2.7 · Signal-First Strategy

Signal-First Strategy — built from your evidence, not from a template

Strategy is built from your own signals first; the pattern library corroborates the read but never carries it — and no two companies get the same shape by default.

A strategy that leans on "this worked for a company like yours" is borrowing confidence it has not earned. v2.7 rebuilds how recommendations are made so the load is carried by your evidence — and a familiar playbook never gets to win by resemblance.

"If the recommendation falls apart the moment you remove the analogy to another company, it was never your strategy."

How it works, in plain steps

  • Builds the winning mechanism from your signals first. Before any pattern is consulted, the "how you win" is written from your own evidence — your customers, your market, your constraints. The pattern library is held back until that mechanism exists, so it sharpens the read instead of anchoring it.
  • Patterns corroborate; they never carry. A pattern can support a recommendation or warn against a known trap, but it cannot be the reason a move is recommended unless your own signals already make the case. Remove the analogy and the recommendation still has to stand.
  • No two companies get the same shape by default. A convergence check flags when a recommendation is drifting toward a house template and forces either a genuinely distinct alternative or an explicit, on-the-record reason this case truly is the same — so apparent options never collapse into one.

Why this matters for you

You get a strategy shaped by your situation, not a well-dressed template — one whose logic holds on your evidence alone, and that we can defend without leaning on "it worked elsewhere."

Additive and backward-compatible — the pattern library still sharpens the work; it just stops doing the work.

Methodology · v2.6 · Decision Quality Layer

Decision Quality Layer — don't be fooled by luck

The Decision Quality Layer grades the decision itself — how well it was made — separately from how the result happened to turn out.

A good decision can still get unlucky. A reckless one can still get lucky. If you judge only by the result, you learn the wrong lesson — you keep bad habits that happened to work, and drop good ones that happened to miss. The Decision Quality Layer grades how the decision was made, on its own, so the outcome can't rewrite the story.

"A good decision that gets unlucky is still a good decision."

How it works, in plain steps

  • Name the decision first. Before the analysis, we write down the real choice on the table and what "a good outcome" would mean here.
  • Check the whole chain. A decision is only as good as its weakest part — the question, the options, the facts, the values, the reasoning, and the commitment to act.
  • Score the decision when it's made — not after. So when results arrive, you learn the real lesson instead of rewriting the story around the outcome.

Why this matters for you

You keep the good calls that got unlucky, drop the lucky-but-reckless habits, and can finally see how well your team actually decides — not just how the last roll of the dice landed.

We call it the Decision Quality Layer, not a "decision-intelligence" tool — the discipline is judgment, not software.

Methodology · v2.5 · Market Reality Layer

Market Reality Layer — don't be fooled by hype

The Market Reality Layer reads demand the way a buyer actually decides — what they will pay for, not just what they say they want.

Interest is easy to find and easy to mistake for a market. People click, sign up, and say kind things — then don't buy. The Market Reality Layer reads demand the way a buyer actually decides, so a busy waitlist is never confused with a business.

"Interest is not willingness to pay. A waitlist is not a market."

How it works, in plain steps

  • Find the real job. What result is the buyer actually paying for — not the features.
  • Separate interest from payment. Clicks and sign-ups are clues, not proof; a real read needs a price someone will pay and the accounts that can pay it.
  • Count the friction. What it costs a buyer to switch — habit, setup, risk — is part of the market, and often the reason a "sure thing" never closes.

Why this matters for you

You act on demand that still holds up when the invoices arrive — sized from the bottom up, and honest about what stands between interest and adoption.

Methodology · v2.4 · Competitive Field Read

Competitive Field Read — don't be fooled by the obvious list

The Competitive Field Read looks at the whole field of rivals — including the ones that don't look like competitors.

The competitor that takes your customer is often not on the list. It is a cheaper workaround, a tool from the next category over, or the buyer simply doing nothing. The Competitive Field Read looks at the whole field — and judges rivals by what they do, not what they say.

"The dangerous competitor is often the spreadsheet the buyer already trusts."

How it works, in plain steps

  • See the whole field. Direct rivals, substitutes, newcomers, and "do nothing" — anything the buyer might pick for the same job.
  • Judge by actions, not words. We check where a rival actually spends — hiring, building, buying — not what its marketing claims. A funding round is not the same as strength.
  • Say what would prove us wrong. Every read about a competitor comes with the event that would mean we got it wrong — so it can be checked later.

Why this matters for you

You see the real alternative your buyer is weighing — including the ones a feature-by-feature comparison misses — and the read stays checkable.

Methodology · v2.3 · Competing Readings

Competing Readings — don't be fooled by the first story

Competing Readings makes the methodology test two or three explanations against the facts before settling on one.

The easiest mistake in analysis is to grab the first explanation that feels right, then bend the facts to fit it. Competing Readings stops that: it puts two or three whole explanations on the table and lets the evidence pick the winner.

"We don't ask 'does this story fit the facts?' We ask 'which of three fits best?'"

How it works, in plain steps

  • Put up rival explanations. Two or three whole-situation stories, not one.
  • Let the facts pick the winner. The story that best fits the evidence wins; the runners-up are kept on the record so the Red Team can attack them.
  • Re-check the sources. Every key fact is opened again to confirm it really says what we claim; dead or mis-cited sources lower the confidence, in the open.

Why this matters for you

The conclusion you act on has already beaten its best alternatives and rests on re-checked facts — not on the first confident-sounding story.

Methodology · v2.2 · Red Team

Red Team — stress-testing the conclusions

A confident-looking conclusion is not the same as a correct one. Red Team is the step that tells the two apart — an independent attack on a finished analysis, run before anyone acts on it.

Most analysis is checked by the people who wrote it. That is exactly the problem — they are attached to their own conclusions. Red Team fixes this by adding a separate pass whose only job is to try to break the analysis: attack the claims it leans on, find the weak ones, and say plainly where it could be wrong.

"We do not ask 'is this analysis good?' We ask 'can we break it?' — and then we fix what breaks."

How it works, in plain steps

  • List what the analysis stands on. The few load-bearing claims that, if wrong, change everything.
  • Make each claim as strong as possible first — then attack that strong version, not a strawman.
  • Check each one against open evidence. Some claims get stronger under attack; some fall.
  • Name what would prove it wrong — a real event that would force a rethink.
  • Ship the fixes. Every successful attack ends in a correction, not just a complaint.
What Red Team does to an analysis
Red Team sorts a finished analysis into what holds and what does not — and fixes the second before you ever see it.

A real example — Elixirr

When we read the consultancy Elixirr, the first strategy leaned on "owned AI tools are a lasting advantage." Red Team attacked that and it fell: the big AI labs had just started doing the same thing cheaper. So the strategy was corrected — owned AI was demoted from "the moat" to "a useful accelerator", the real edge was re-named as senior judgment in a regulated niche, the odds of the bad scenario were raised, and a short market test was added before committing. A sharper, more honest plan — because it was attacked first.

"Three of seven load-bearing claims fell under attack. The strategy that survived is shorter, narrower, and far more honest."

Why this matters for you

It means you act on conclusions that have already been through a fight. The weak spots were found by us, on purpose, before they cost you anything — instead of by the market, later, when they are expensive. Red Team runs under three simple fairness rules: attack and defense are held to the same standard, get the same effort, and are weighted by how much the decision actually depends on them.

Methodology · v2.1 · Release note

ESI Methodology v2.1 — A Release Note

In May 2026 we shipped v2.1, the largest internal upgrade to our External Strategic Intelligence approach since the v2 interpretation overhaul. This note explains the qualitative shift it brings — and why it matters for the analysts who run the work, the executives who act on it, and the businesses that rely on the conclusions.

The defect we diagnosed

The previous release had strengthened interpretation — pattern discipline, mechanism articulation, calibration of confidence. But the interpretation layer had become more demanding than the evidence layer beneath it. Safeguards against pattern hallucination were in place, but operating below their intended strength.

For an analyst, this meant carrying interpretive weight the evidence could not fully support. For an executive, it meant conclusions that looked confident but rested on a thinner base than the methodology was built to require. For the business, it meant decisions made on analysis that was strong, but not as strong as it was supposed to be.

We treated this as a release-blocking issue and engineered v2.1 to close it.

Fig. 01 · Bringing evidence into balance with interpretation
v2.1 does not weaken interpretation. It deepens the evidence layer beneath it, so the safeguards can do the work they were designed to do.

The qualitative shift

v2.1 brings evidence depth into balance with interpretation rigor across the entire approach. Every safeguard now operates at full strength, because what stands underneath it is deep enough to make the safeguard diagnostic rather than ceremonial.

For the analyst, the methodology now does more of the load-carrying:

  • Absences in evidence get tested by the methodology itself.
  • Hypotheses are validated before interpretation, not during it.
  • Contradictions are named and categorized, not wrestled with privately.
  • The known limits of the analysis are made explicit, not hidden inside confidence levels.

For the executive, the input arrives cleaner:

  • Recommendations come with their boundaries visible.
  • Conclusions do not need re-translation to be usable.
  • The path from analysis to action is shorter.

For the business, the foundation under each decision is firmer:

  • Strategic decisions rest on tighter and more honest evidence.
  • Safeguards operate diagnostically, not ceremonially.
  • The risk of acting on a pattern that only looks right is structurally lower.

What the methodology is really for

This is not an AI machine for producing analysis. It is a discipline that lets analysts work at a level of rigor they could not sustain unassisted, and lets executives act on conclusions without re-translating them.

"AI is fast at retrieval and useful at synthesis. It is not capable of methodological judgment."
Fig. 02 · Two roles in one chain
AI participates in the chain. It does not replace the judgment a methodology makes — that work stays human, the methodology is what makes it repeatable.

Why we publish this

Most analytical firms treat methodology as a black box. Cross Data operates on the opposite premise.

  • The approach is public.
  • It is versioned: v1.0 → v2 → v2.1 is a named evolution chain anyone can read end-to-end.
  • It is auditable: quality criteria are written down where anyone can check them.
  • v2.1 itself is evidence of how Cross Data handles any internal weakness — diagnose it openly, ship the fix openly.
Fig. 03 · A named evolution chain · v1.0 → v2 → v2.1 → v2.2 → v2.3 → v2.4 → v2.5 → v2.6 → v2.7 → v2.8 · current
v1.0 foundational frame · v2 interpretation overhaul · v2.1 evidence depth balanced · v2.2 Red Team · v2.3 Competing Readings · v2.4 Competitive Field Read · v2.5 Market Reality Layer · v2.6 Decision Quality Layer · v2.7 Signal-First Strategy · v2.8 Earned Confidence (current). A versioned methodology behaves like versioned software — each step named, dated, and readable end-to-end.

This is not a marketing position. It is how an analytical discipline earns trust without asking for it on credit.

What is next

v2.1 unblocks further refinement already in motion: an evolution of the analytical artifacts the methodology produces toward greater precision and decision-readiness, an extension of the Pattern Library logic, and a calibration pass on the thresholds set in this release.

The approach is built to evolve. Visible methodology is a discipline of shipping, diagnosing, and shipping again — with the work shown.

— Common questions

Plain answers about the 2026 methodology releases — and how Cross Data keeps its analysis honest.

What changed in the Cross Data methodology in 2026?

Six releases — Competing Readings (v2.3), Competitive Field Read (v2.4), Market Reality Layer (v2.5), the Decision Quality Layer (v2.6), Signal-First Strategy (v2.7), and Earned Confidence (v2.8). Together they close, one by one, the ways an analysis can fool itself — and now hold our own playbook to the same bar.

What is the Decision Quality Layer?

The step that grades how well a decision was made, separately from how the result turned out — so a good decision that got unlucky isn't confused with a bad one that got lucky.

What is the Market Reality Layer?

The part of the methodology that reads demand the way a buyer decides — what they'll actually pay for, not just what they say they want — so interest is never mistaken for a market.

What is a Competitive Field Read?

A reading of the whole competitive field, including substitutes and "do nothing" — the rivals that don't look like rivals — judged by what competitors do, not what they say.

How does Cross Data keep its analysis honest?

It tests rival explanations against the facts (Competing Readings), re-checks sources, attacks its own conclusions (Red Team), and grades decisions separately from outcomes (Decision Quality Layer).

— Methodology in action

Three artifacts. Three ways the layer becomes visible.

Each tile is a real fragment of the Kairos Console operating on a live analysis pack. Hover or watch — they animate on a continuous loop.

Signal Ledger Monitoring · §4.1
SL-001Gartner publishes first-ever Decision Intelligence Magic Quadrantgartner.comHIGH
SL-002DecisionX Agent ranks #2 globally on Spider 2.0 Lite benchmarkspider-bench.ioHIGH
SL-003Ex-Accenture MD appointed as GTM strategic advisorlinkedin.comHIGH
SL-004Aera raises $263M cumulative; Accenture co-sell dealtechcrunchHIGH
SL-005Quantexa closes $175M Series F at $2.6B valuationcrunchbaseHIGH
SL-002DecisionX Agent ranks #2 globally on Spider 2.0 Lite
SOURCESpider 2.0 Lite leaderboard, Yale NLP · 31 Mar 2026 · cross-checked against DecisionX press release
MECHANISMIndependent benchmark confirms enterprise-grade reasoning credential, validates Gartner-MQ candidacy track
ACTIVATESA-09 Competitive Slot Expiry · B-01 Architecture vs Position
External signals indexed, scored for confidence and relevance, then linked to the patterns and risks they activate.
Pattern Library + Ops Live navigation
Pattern Library
Ops
105 internal patterns · 79 anti-patterns
A-09Competitive Slot Expiry
B-01Architecture vs Position
C-08No-Regret Move Logic
C-23Productized 80/20 + Retainer
A-09 CLASS A · MARKET
Competitive Slot Expiry
MECHANISM A category window closes when Leader-cluster vendors complete vertical lock-in — late entrants lose the unowned-buyer slot.
SIGNALS SL-002 · SL-005 · SL-008
ANTI ⤬ Re-positioning every quarter against whichever Leader surfaces.
Operating Dashboard · live
74
Signals this week
14
New accounts
105
Internal patterns
The library accumulates across every case. Each loaded report is validated against it.
Risk Priority Matrix Decision · §15.1
IMPACT
R4
R1R2R3
R5
PROBABILITY →
R4HIGH
LLM-vendor absorption of context layer
EARLY SIGNALS LLM enterprise tiers ship native context-management · Copilot adds audit trail · analyst questions shift to "why not just use the LLM".
COST OF INACTION Architectural moat erodes; margin compression as customers ask why DecisionX is needed in addition to the LLM enterprise plan.
RESPONSE → Sharpen architectural differentiation: cross-LLM + enterprise-specific ontology + audit trail; build verticalised reasoning packages.
Every risk is mapped on a 5×5 grid, then expanded with mechanism, early signals, and response.

This is the methodology, working. For public-data readings of mid-market companies — the inside frame, the leverage point an external reading surfaces, and the move the reading names — open the Effect on Business page.

— Manifest · a letter from the founder

Hello, I'm Alex. Here is why Cross Data exists.

A short, honest letter about cognitive overload, the real role of AI in strategy, and the kind of decisions we help leaders make. Free to read.

Cross Data
v2 · May 2026
THE PURPOSE

Taking the overload off leadership teams.

Hello, my name is Alex, and I'm the founder of Cross Data. Our company serves a simple purpose: to take cognitive overload off the leadership teams of modern mid-market companies.

In the era of AI, managers have received a powerful, yet specific tool for collecting data and running analysis. AI gives leaders data. But it's not that great yet at helping them make valuable decisions.

These days, leaders have to parse through large amounts of data and analytics created by AI. But it turns out this creates more overload and cognitive fatigue than actual value. A growing number of senior managers already report feeling overwhelmed by the amount of data they have to process — many of them facing burnout, decision fatigue, or a serious loss of clarity in their work.

"A tool that was supposed to make our work easier made us chase larger amounts of analyzed data at the cost of our own exhaustion."
More analysis did not become better judgment
The promise was easier work. The result, too often, was exhaustion — and the decision still unmade.
THE REDEFINITION

From clearer analytics to decision-grade analytics.

At Cross Data, we have redefined how we look at analytics and the role of AI, so it serves a real strategic purpose: helping leaders make more accurate, valuable, and meaningful decisions — by making analytics not just clearer and more insightful, but decision-grade.

What we mean is this. When a leader looks at a report, they're not just seeing the whole picture or a pile of significant data. They immediately understand the best available moves, the risks, the probabilities, and the leverage points open to them right now and in the near future.

A report vs a decision-grade artifact
We do not deliver more to read. We deliver a decision you can make.
THE PRINCIPLE

We think from the outside in.

We achieve that by turning one key strategic principle into the foundation of how we think: at Cross Data, we create strategic insight by thinking from the outside in — not the other way around, as many classical strategy approaches do.

Here are a few things we believe are true about decision-making in the AI era:

  • We do not believe leadership teams need just another dashboard.
  • We do not believe that more analysis automatically creates better judgment.
  • We do not believe AI-generated analytics becomes valuable until it changes the quality of decisions.
Outside-in, not inside-out
Classic strategy starts inside the company and looks out. We start with the system and read inward.
THE PROCESS

Scan the system, then read its structure.

In our work, we follow a clear process. First, we rigorously scan the external environment around the company to find the real architecture behind the market: which forces change it, who the key players are, who the competitors are and how they act, and what the current dynamics, limits, and opportunities are. Our aim here is to understand the structure — not just to get a static picture of the market.

After that, we analyze it with the help of the most advanced AI models, through our own methodology. We call it External Strategic Intelligence. But it is much more than AI computing. We use the calculating power of machines to find patterns across many business situations. We validate them, collect them, and teach our models to recognize them across analyses we have already done — so each next analysis becomes more insightful, more accurate, and faster at the same time.

Compounding intelligence — the doctor analogy
Imagine a seasoned doctor who suddenly holds the memory of a hundred peers. That is what a growing pattern library does for a read.

Imagine a doctor with more than ten years of experience, able to reach a diagnosis just hours after seeing the patient's results. Now imagine that doctor receives a database of the same knowledge from tens or hundreds of colleagues with similar or broader experience. This changes the quality of diagnosis. It creates a compounding intelligence advantage. The same principle lets AI reach a much higher level of accuracy in reading different business situations.

Our work does not stop there. We apply human interpretation, creativity, and strategic thinking to these highly accurate insights, to develop real leverage — not just the linear moves available on the business chessboard. Then we turn those decisions into clear artefacts, presented in the simplest, most cognitively light way, so leaders can evaluate and commit without having spent days or weeks deciding.

We also help companies build a similar system inside their own walls, so the value of our partnership is not a single project but a repeated cycle: scanning, analyzing, developing solutions, implementing them as decisions and actions, and watching how they perform in reality. We learn from every step and every engagement — to deliver even more value with each cycle.

A cycle that compounds, not a one-off project
Scan → analyze → develop → implement → learn — and back. The advantage compounds with each turn.
THE FUTURE

The advantage will not be more data.

I believe this is the best way to reshape our attitude to strategy and decision-making. The future of strategy will not belong to companies that produce the largest amount of analysis. It will not belong to teams that confuse more information with better judgment.

It will belong to companies that can turn external complexity into better decisions before the market makes those decisions expensive.

"In the AI era, the real advantage will not be the ability to generate more data. It will be the ability to see the system earlier, understand the available moves faster, and act with clarity while others are still trying to process the noise."

This is the future Cross Data is building for.

The manifest names the discipline. The Diagnostic applies it.

Run this against your company. Start with an ESI Diagnostic.

Start a Diagnostic
Glossary · The language of the category

Thirty-five terms. The language the practice runs on.

The Pattern Library names what we observe. The Glossary names how we observe it. Read it as a funnel — each layer earns the next.

06 / Categorical
35 terms · 4 layers

Why we exist

Five ideas anyone can use.

Why a company can't see its own limits. What ESI is — and is not. What we mean by a Decision OS. Five terms answer the first honest question: do we need this at all?

5 terms · enter →

How we look

The lens, not the data.

Once you accept the outside view is missing, the question becomes what to look at. Ten lenses — structure, leverage, frame, mechanism — that make a business legible before it is changed.

10 terms · the lens →

How we run it

The architecture of Kairos.

The Decision OS in working detail — twelve terms covering its eight layers, from the standard of truth at the bottom to the cadence and learning loop on top. The part that gets installed inside.

12 terms · the OS →

How we think

Practitioner doctrine.

Eight advanced concepts that govern the practice — kernel, bifurcation, no-regret move, selective ecosystem. Read these last; they only make sense after the first three layers have done their work.

8 terms · doctrine →
The category, in one picture
ESI reads the outside; Kairos installs the reading inside the company.
Kairos — the eight layers of a Decision OS
L7
Learning & Evolution
Post-decision review, decision memory, model updates
L6
Execution & Governance
Cadence, quality gates, escalations
L5
Partnership & Ecosystem
Exit architecture, capture protection
L4
Decision Engine
Packets, options, falsifiers, stop rules
L3
Cognitive Model
Bias register, narrative detection
L2
System Model
Value flows, control points, single points of failure
L1
Signal Layer
Signal universe, early warnings, self-observation
L0
Ethics & Meta — the foundation
Standard of Truth · Red Lines · Evidence Tiers
Walkthrough
Concept Map
Search
All
1 · Why
2 · Lens
3 · OS
4 · Doctrine

Each circle is a term. Lines connect terms that explain each other. Hover to highlight its neighbors; click to jump to its full entry. Concentric rings show layers — entry in the center, doctrine on the outside.

— the language is the door

When the words stop sounding strange, the methodology has already started working.

The Glossary is published in full because the category exists only if its language is shared. If a term gives you a new way to look at your own business, that is the methodology already at work — before any engagement begins.

Get in touch
Templates · Working artifacts

The same artifacts we use inside engagements.

One full worked example you can open right now — a real strategy compressed onto a single visual page — plus three working templates from the ESI workflow.

10 / Tier 4
Practitioner templates
Strategizer · Elixirr · 24–36 month strategy
Confidence: Medium Window: open now, closing fast
1 · Why it is on the winning side
AI eats this
junior, repetitive consulting work — the layer big firms are built on
value moves →
Value moves here Elixirr
senior judgment · regulated depth · accountable outcomes
2 · The moat — what others can't copy
A
Senior judgment
people the pyramid firms can't match on trust
B
Regulated FS depth
a niche the AI labs can't responsibly staff
C
Accountable outcomes
paid for results, not for hours
Red Team correction: owned AI tools are an accelerator, not the moat — the AI labs now do AI-native delivery cheaper.
3 · Where to play
A named mid-market, regulated Financial-Services niche — too small for the giants to serve economically, too regulated for the AI labs to enter on trust.
4 · The plan — six moves
M0 · gate
Test it
60–90 day market probe first
M1
Own the niche
offers + references
M2
Reposition
senior-led, outcome-priced
M3
Fix AI supply
a cloud giant, not a lab
M4
Use AI to deliver
accelerator, not the pitch
M5
Buy depth only
no breadth M&A
5 · Three futures
Base — defend the premium
50%
Adverse — labs reach down already starting
35%
Upside — niche proven + re-rating
15%
6 · Stop doing
"cheaper McKinsey" breadth M&A "AI-native" as the pitch "all of finance" day-rate pricing
Generated by Cross Data Strategizer · Corporate mode · revised after a Red Team audit. A worked example, not investment advice. See the full Elixirr reading →
↓ Template 01

ESI Map template

Mapping format for the Strategic Surface Area: substrate layers, players, regulatory axes, technology transitions, attention flows. Used at every Diagnostic.

PDF · 8 pages · download →
↓ Template 02

Decision Brief template

The Decision Pack canvas: framing, options, mechanics, risk, confidence-tagged forecast, Kairos action sequence. Used at every Decision Pack engagement.

PDF · 6 pages · download →
↓ Template 03

Monthly Signal Review agenda

The 60-minute Monthly Signal Review agenda: what is reviewed, in what order, with what artifacts, by which owner. The smallest reproducible unit of the cycle.

PDF · 3 pages · download →
Annual artifact · Pre-commit

State of External Strategic Intelligence — 2026

The first annual public report. State of the category. Pattern Library release. Public ESI Applications collected from the year. Distribution of the five operating modes across the surveyed cohort. Published December 2026.

Q4 2026
First edition · join the waitlist
— About

The discipline — and the founder behind it.

Cross Data is a founder-led External Strategic Intelligence practice. The section names the operator behind the work, the seven cognitive principles that govern every engagement, and the metaposition that keeps the external reading honest.

09 / About
Founder · principles
OO

Oleksandr Osypenko

Founder · Cross Data · External Strategic Intelligence practice

Cross Data is a founder-led practice building External Strategic Intelligence as a discipline — a decision-grade layer of external reading and execution that sits above tools, advisors, and internal intuition. The practice exists because of a specific gap: insight is cheap, decision architecture is rare, and the work of converting one into the other is what consulting reports, BI dashboards, and current AI systems do not produce.

The background is operations, not advisory. Over five years of technical-support leadership at a North-American logistics-tech company — handling escalations, workflow coordination, operator training, and complex compliance cases across the ELD/HOS surface — before that, account management and logistics coordination at a Chicago freight broker. The decision-architecture work in Cross Data sits on years of running operations under live pressure: seeing where insight dies before it reaches a decision, and what it takes to convert one into the other.

Cross Data's public surface is what the operating practice has converted into shared language: the Manifest ("Stop flying blind"), the Glossary of thirty-five terms across four layers, the Pattern Library in its v12 public preview (thirty-six patterns across seven clusters and four tiers), the Diagnostic Mirror of five operating modes, and the working Templates of the workflow. Each anonymized analysis either matches an existing pattern or adds a new one — mechanism-first, mechanism-auditable. The library is the accumulating moat.

Practice scope: A deliberately limited engagement roster. The methodology is the product; the engagement is the rhythm in which it runs inside the client. Cross Data does not operate a partner-brokerage model, take commission or success-fee deals, or own implementation — those rules keep the metaposition intact and the external reading honest.

Public artifacts: Manifest "Stop flying blind" · ESI Categorical Glossary (35 terms · 4 layers) · Pattern Library v12 (36 patterns · 7 clusters · 4 tiers · public preview) · Diagnostic Mirror (five modes) · Public ESI Applications · annual State of ESI Report (first edition Q4 2026).

How to engage: Reach out through the contact form with one sentence on the strategic question you are working on. Reply within forty-eight hours. Live thinking is published on LinkedIn and the Cross Data company page.
Seven cognitive principles · the epistemic core
01

Pattern over narrative

Patterns are the unit of accumulation. Narrative is downstream of pattern, never the other way around.

02

Confidence-tagged intelligence

Every signal carries a confidence band at the moment of capture. No bullet-point parity between guesses and verified observations.

03

Multi-horizon view

Every analysis is decomposed across present, 90-day adjacent possible, and 12–18 month convergence. Single-horizon analysis is a category error.

04

Architecture before action

Hidden architecture is read before action is designed. Acting on the surface produces surface results.

05

Choice mechanics are explicit

Decisions are captured with options, mechanics, and expected environmental response — not as binary recommendations.

06

Adaptation is mandatory

Every decision is paired with a measurement of how the environment responded. A decision without an Adaptation Loop is an unresolved hypothesis.

07

Language is infrastructure

Category language is operational infrastructure, not marketing copy. Drift in language is drift in capability. The Dictionary is enforced.