OpenBlock Labs: Launch strategy, and the instrumentation to know if it worked.
Early-stage companies usually instrument last, which makes the first year of growth data unrecoverable. We did it in the other order: define the motion, then build the analytics framework underneath it, so the launch produced evidence instead of anecdotes.
- Growth analytics framework
- 0 → 1Growth analytics framework
- Instrumented, not retrofitted
- Pre-launchInstrumented, not retrofitted
- Go-to-market motion and ICP
- DefinedGo-to-market motion and ICP
- Strategy and sequencing
- LaunchStrategy and sequencing
- Client
- OpenBlock Labs
- Role
- Growth advisory: launch strategy and analytics
- Industry
- Onchain data · Early stage
The problem with instrumenting last
Almost every early-stage company builds its analytics after it needs them. The launch happens, traction arrives or does not, and six months later someone asks which channel drove it and finds out the answer is unrecoverable. You cannot backfill events that were never sent.
OpenBlock Labs was heading into a product launch with the chance to do it the other way around.
Motion first, then measurement
We started with the go-to-market motion, because you cannot instrument a funnel you have not defined. Who the product is for, what the first valuable action is, what a good week looks like, and which of those are worth an event.
Then the data infrastructure to track exactly those things, built before the launch instead of bolted on after it. The framework covered the path from first touch through to activation, so the questions people ask after a launch had answers waiting for them.
The payoff is speed. When launch data arrives already structured, the team spends its time deciding what to do next instead of reconstructing what happened.
Motion defined first
ICP, positioning and launch sequence agreed before a single event was specified.
Instrumented before launch
Data infrastructure built ahead of the moment it was needed, so nothing had to be reconstructed later.
Insight, not dashboards
Built to answer the specific questions the team would ask after launch, rather than to fill a dashboard.
Questions people ask about this work
How early should a startup build growth analytics?
+
What does a growth advisor do for a pre-launch company?
+
Services behind this engagement
More case studies
See all →HeyGen
Five interlocking systems behind 5x ARR growth at the leader in AI video: a strategic rebrand, an SEO program built from zero, a 100,000 member community, AI-native lifecycle automation, and an enterprise ABM motion.
Open source, measured properlyComfy
Comfy builds ComfyUI, one of the largest open-source generative AI projects, plus the cloud platform around it. Huge audience, huge traffic, and very little of it captured on purpose. I lead growth there. This is the organic engine and the measurement layer we built underneath it. The program is early and still compounding, so what follows is the approach and the direction of travel.
AI agents for top-of-funnel SEOCharta Health
Charta Health automates pre-bill chart review for healthcare providers, a category where accuracy is the product and the buying committee is wide. Three workstreams: fix the foundation, build an agent-run SEO engine so a small team publishes like a large one, and make events and lifecycle report back in numbers.