A living document. Read it end-to-end when you start, come back to it when the roadmap shifts, and edit it when the reality on the ground has moved past the words on the page.
How we got here, in as few words as we can manage.
StackDX started with a stubborn observation: the tools businesses use to run their data are strong on their own and weak together. Every team that touched revenue — sales, finance, ops — was rebuilding the same joins in a different spreadsheet, and nobody trusted anyone else's numbers.
We built the first version of StackDX to fix that for one company. Then a second asked for it. Then it stopped being a favor and started being a product.
The five things we believe about how good work happens.
Say the real thing. It's kinder than a soft signal that leaves everyone guessing.
A rough version in a customer's hands beats a perfect one on a Figma canvas.
If we can't agree on the number, we haven't finished the work. Reconcile, then decide.
The person who saw the problem is the person who owns the fix — until it's fixed.
Every doc, every dashboard, every codepath. Small deltas compound; sloppy deltas rot.
Write it down where the team can find it. If it's not in a shared place, it doesn't exist.
"We're not here to build software. We're here to make the numbers legible so the people who run companies can stop guessing." — Founding memo
Where we're pointed, in three horizons.
The bet is straightforward: businesses are drowning in the systems they bought to help them, and someone has to stitch them together into a single, honest picture. Not another dashboard. The layer underneath the dashboards.
None of this happens in a straight line. What stays constant is the direction — and the expectation that the person reading this today is one of the people bending the curve.