Most strategy writing asserts. We derive.
Open any newsletter and you get a take: a smart person's read on where a market is headed, delivered with conviction and no way to check the work. Vecstrata is built the other way around. Every claim we make traces back through a named framework, a documented pattern, and a dated prediction you can score against us. The product is the chain, not the opinion.
The name is the method
Vecstrata is a vector across the strata: where value moves between a market's layers, and why it had to. A market is a stack — capacity, integration, distribution, the customer relationship. Profit doesn't sit still in that stack. It migrates, and it migrates for structural reasons: an interface standardizes, a bottleneck relocates, a moat turns out to have been an accident of history. We track the move and call where it lands next.
We read every market through four questions:
- The Map — where each piece of the stack sits in its life cycle, from genesis to commodity.
- The Shift — which way profit pools move as the interfaces between layers harden or dissolve.
- The Priority — the one binding constraint that decides where the next dollar of capital should go.
- Financial Ground Truth — what all of that does to per-unit economics. Numbers, sourced.
Behind each question sits a bench of eleven named frameworks, each reading the question on its own and each keeping its own public track record. A claim earns its place when independent lenses point the same way; when they don't, you read the dissent. The method page shows the whole chain, and the lens ledger shows which framework has earned trust.
Why you can trust the call: you don't have to
Two commitments make the bet real instead of rhetorical.
Every claim is traceable. Behind each briefing is a versioned knowledge graph built over the foundational strategy literature: Christensen, Wardley, Teece, Baldwin and Clark, Arthur, Goldratt, and others. When we write "this margin relocates," we can show you the framework that predicts it, the source it came from, and whether the step was stated in that source or composed by us. No black box, no hand-waving.
Every prediction is falsifiable. Each call carries an explicit horizon and a condition that would prove it wrong. When the date arrives, we score it, publicly, including the ones we get wrong. Most newsletters never revisit a claim. Our track record is a page on this site, kept current whether it flatters us or not. The bet, not the take, is the product.
We test the method backward, too. A backtest freezes a date in the past, re-derives the calls from only what was knowable then, and scores them against what actually happened. Backtests are labeled as backtests and kept separate from the live record, so hindsight never flatters the number.
Editions and membership
Each briefing publishes at two depths. The Signal edition is free and public: the call, the weighted futures, the reasoning that matters. The Analyst edition is the full analytical read: every diagram, the complete lens readings, the appendix with the working. While the track record builds, everything is open to read; a free membership follows the work as it publishes.
Who's behind it
Marc Kuri and Benjamin Lang met at a tech consultancy. From the inside we watched the German automakers fail to adapt in real time: drifting upmarket into luxury, overdelivering on the customer needs that were easy to measure, treating electric drivetrains and software as someone else's problem for years too long. We had the frameworks that named why as it happened. That was the seed.
Benjamin went on to write Teslafication, a book that reasons about that same industrial shift with the toolkit our briefings use: modularity versus integration, disruption as a cost-structure story, increasing returns.
From there it became a habit. We'd reason through market shifts with these frameworks for the fun of it: in cafes, on walks, over video calls, often dragging friends in as guests. They kept doing two things at once. They explained what had already happened, cleanly, and they let us call what came next, with the reasoning and the data attached. At some point the obvious move was to write it down and let the predictions stand or fall in public. So we did.
Where to start
New here? Take the short path: read the latest briefing, check the scorecard to see how the calls have aged, and skim the glossary for the handful of terms we use precisely and repeat on purpose.