Zartico · Product Launch Telemetry
● Live · Jul 1 2026 · Day 0From a dormant prototype to a production product — the 14‑week signal that became a launch.
An engineering summary. The numbers here come from git history — commits, code, releases. They tell the build story, not the whole story: Product, QA & testing, design, and go‑to‑market shaped it, hardened it, and carried it to launch, and that work doesn't leave commits behind.
The Journey
Two threads. Jay's prototype laid down the report language in late March; the product itself was born at a three‑day hackathon in Salt Lake City that May — where, by day two, the first order form was already shipping.
A 39‑commit burst restructures Jay's POC into a real end‑to‑end pipeline — and lays down the report layout the product still uses today: Event Lift KPIs, visitor composition, origin markets, the co‑visitation arc map.
Where Event Pulse actually began. Three days in Salt Lake City — and by day two the Events & Conventions order form was live, riding on our existing self‑serve reporting platform. E&C → LiftIQ → Event Pulse.
DE stands up two shared engines days apart — one engine (May 17) for the animated movement map, and the sub‑second geo engine (May 18) computing which visitors were observed during the event — and where else they traveled. The heaviest compute behind the report.
The spend‑lift engine is born — skeleton, router, and end‑to‑end contract test all in one night. This is the spend‑lift math the whole product reports on.
The standalone Event Pulse app is scaffolded — its own frontend, carved off the shared self‑serve platform. First test deploy the same day.
Auto date‑resolution lands — the order form no longer guesses comparison windows, it asks the data.
With the data backfill complete, an order runs every leg green — spend, co‑visitation, and timelapse — start to finish in production. The whole machine, proven, hours before go‑live.
Event Pulse ships to its first client orgs. 🚀
Within two hours of go‑live, an early‑adopter client placed the first real Event Pulse order — order form to processing, fully self‑serve. The first genuine signal from the field. 🎉
By the Numbers
Where It Was Built
The frontend and orchestration on the SW Eng side; the co‑visitation, movement, and spend engines on the Data Engineering side (all in one monorepo).
| Component | Commits | Lines of code |
|---|---|---|
| The standalone app41 PRs · 72 releases | 120 | 15,916 |
| The report renderer72 report files | 150 | 12,485 |
| The self‑serve web appwhere it first lived | 125 | ~18,000 |
| Order + build orchestrationthe self‑serve backend | 102 | — |
| The geo engineco‑visitation + enrichment | 70 | 13,041 |
| The movement mapanimated visitor flow | 22 | 4,037 |
| The spend‑lift engineevent analysis + loaders | 45 | 4,276 |
The Crew
The engineers whose commits show up in the git history above — far from the whole cast.
The Spark
The hackathon POC and the report design language the product still carries.
SW Eng
The frontends and the order → build → deliver orchestration, from the shared platform through to standalone.
Data Eng
The co‑visitation, timelapse, and spend‑lift engines — the math every report is built on.
+ the whole team
And everyone the commit log can't see. Product defined and shaped it, QA & testing broke it so clients won't, design gave it its look, and go‑to‑market got it in front of the first adopters. A launch is a team sport — this page just happens to count the code.