BearingA built Bearing. The methodology is the work. The company is designed to be institutionally dependable.
One person built the methodology, the corpus, the trace architecture, and the cannot-be-wrong commitment since March 2024. The right question is not whether that is a large enough team — it is whether the architecture makes headcount irrelevant to the output's defensibility. The answer is structural: every deployment makes the engine more defensible, not less. The corpus compounds. The trace does not rely on the analyst's memory. The cannot-be-wrong commitment is enforced by the engine, not by a senior analyst signing off on each read.
IS
The institutional research practice.
BearingA is an institutional research practice. One person built the methodology, the engine, the corpus, and the trace architecture. That person — Sang Heeringa — is the methodology operator. The company contracts, invoices, and stands behind the cannot-be-wrong commitment.
You are right to ask whether a practice this size can be trusted with institutional infrastructure. The answer is architectural. Most institutional research firms scale by adding senior analysts to cover more clients; the 37th analyst has the same can-be-wrong exposure as the first, the same knowledge-retention risk when they leave, the same variance in output quality on their worst day versus their best. BearingA scales differently. Every deployment makes every future deployment more defensible, not less. The corpus compounds through use. The cannot-be-wrong commitment is enforced by the engine's substrate, not by a senior analyst signing off on each read. The trace architecture does not rely on the analyst's memory of what they cited.
This composition is the structural answer to the size question. The practice is small because the architecture was designed to make headcount irrelevant to the output's defensibility. Built since March 2024. Operating from Kyiv and Amsterdam. EUIPO trademark pending.
SANG HEERINGA
Methodology built since March 2024.
Sang Heeringa founded BearingA and built the Predictive History Method through cycles of analytical work against position-against-configuration detection across geopolitical, regulatory, market-microstructure, and climate substrates. The methodology evolved through validated deployment cycles — Italian medium-sized universal bank under SSM supervision (Cycle 1), Swiss universal bank under FINMA reverse stress test scope (Cycle 2), the Iran-Russia-Taipei cross-compound configuration work, the IRP_7 reclassification (d = +2.015 sensitivity-volatility differential) — and through methodology-evolution work that composes the engine's statistical substrate at production cadence (the Markov regime-transition refinement absorbed into the engine in May 2026 is the operational example).
Sang's role as methodology operator continues — corpus extension cycles, methodology-evolution composition, canonical absorption — but the architecture is designed so that Sang does not appear in the operational layer of any institutional deployment. BearingA the company carries the institutional relationship; agents operate the post-conversion response cycle, the institution-relations function, the deployment-evolution dashboard; Sang operates the engine layer where the methodology evolves.
The architecture composes against a structural condition: BearingA the company is legibly larger than Sang the operator. The institution buys BearingA's infrastructure, not Sang's expertise. This framing is what lets Sang step out of every room without the institutional relationship dissolving.
OPERATION
Substrate-agnosticism in operational test.
The Predictive History Method's substrate-agnosticism is not a marketing claim; it is operationally verified by parallel deployment outside institutional finance. Sang manages a large-scale agricultural operation in Ukraine, primarily wheat, where Bearing's methodology operates as a decision architecture against the configuration substrate of agricultural-commodity positioning — climate transmission, supply-chain cascade, regulatory exposure, geopolitical disruption. The methodology operates without modification across substrates. The engine reads compound configurations against position; the substrate is arbitrary.
Operational substantiation, not aspiration
The agricultural deployment lives at its own surface (Step Agro POC, with its own brand identity) and is not embedded into bearinga.com. The mention here is provenance — the methodology's substrate-agnosticism is operationally substantiated, not aspirational.
DOES NOT DO
The deliberate negatives.
BearingA does not do bespoke analytical engagements. The institution that wants a specific analytical engagement on a specific question is a partner conversation; BearingA licenses the engine, partners service the client. The architectural firewall is structural: bespoke services require the analyst to take a position in the outcome of the read; the cannot-be-wrong commitment requires the engine to have no position in the outcome. Holding the architectural firewall is what makes the engine defensible.
BearingA does not run discovery calls. The institution that signals interest enters the post-conversion response cycle — a structured deployment conversation initiation with named tier, named scope, named timeline, scheduled against a defined kickoff cadence within four working hours. This is not "let's find a time"; it is the architectural acknowledgement that the institutional buyer's procurement officer will be involved within forty-eight hours of the first commitment.
BearingA does not service clients. Service delivery, where the institution requires it, is a partner function. The partner brings the client relationship and the service depth; BearingA brings the engine and the methodology discipline; the combination delivers what neither delivers alone.