Every engagement builds the same loop. The product and its data layer come first, the growth engines run on top, and measurement feeds what works back into the next build.
01Build
Production apps
Postgres data layer
Engine APIs
02Grow
SEO and content engine
Partner co-marketing
Lifecycle and onboarding
03Measure
First-party events
Attribution and tests
GA4 and Mixpanel
Numbers that held in production.
What the growth work moved
2×Active users during Bitazza's Freedom Passport campaign
Before300K
After600K
Active users, Bitazza
+32%User acquisition across the Polygrowth portfolio
Baseline100
After132
User acquisition, indexed
$10.5MRaised in a client token launch I supported
4.2MUsers activated across client campaigns
$15K/moSaved for clients through AI infrastructure
What I shipped
1 monthFrom an empty database to a feature-complete production app
6Findings from a live security audit, three high and three medium, all closed
10 daysTo relaunch a marketing site in Framer with 31 custom React components
01DiagnoseFunnel, content and data audit. You get the gaps and the build order.
02BuildSchema first, then the product, the data layer and the engines for content, lifecycle and measurement.
03RunAgent pipelines do the volume. Every AI change gets a diff review, and gates in code keep the bar.
04CompoundShip, measure, and feed the results back into the system.
The stack under the system.
Postgres at the core, agent pipelines doing the volume, and the surfaces and measurement around them. Same governed data feeds product, support and sales.