Hogsend is brand new.Try it
Hogsend
Articles

Growth, for teams that code

Technical marketing, lifecycle, and go-to-market — written from client work by Doug Silkstone and guests.

What's in Hogsend 0.50, and why
EngineeringGrowth

What's in Hogsend 0.50, and why

A bigger-than-usual release, walked through one feature at a time. Everything here exists because running our own growth on Hogsend surfaced a gap worth closing — video engagement, dataLayer interop, unit-tested Journeys, incrementality and in-Journey A/B experiments, event plugins, contact groupings, and a one-command install. Plus a note on who "we" actually is.

DSDoug SilkstoneJuly 18, 2026

Latest

Lifecycle email is product logic. Treat it like product logic.
GrowthLifecycleEngineering

Lifecycle email is product logic. Treat it like product logic.

The lifecycle stack usually lives in one marketer's browser tabs — invisible, unreviewed, and moving at click-speed while the product ships daily. That gap just got a lot more expensive.

DSDoug SilkstoneJuly 14, 2026
Your event names are a growth decision you already made
Technical marketingGrowth

Your event names are a growth decision you already made

Six months from now, someone will try to build a funnel, a journey, or a report on top of the events you're naming today. Most tracking plans fail that person.

DSDoug SilkstoneJune 30, 2026
GTM for engineers: shipping is not launching
Go-to-marketGrowth

GTM for engineers: shipping is not launching

Engineering-led products die quietly because the team treats the merge as the finish line. A launch is a distribution event, and distribution can be engineered too.

DSDoug SilkstoneJune 12, 2026
Measure, keep, grow — in that order
GrowthTechnical marketing

Measure, keep, grow — in that order

Most early teams run the sequence backwards — acquisition first, retention when churn hurts, measurement never. The order isn't a preference. Each stage is the input to the next.

DSDoug SilkstoneMay 28, 2026
Newsletter

Get new posts by email

Growth, technical marketing, and GTM for teams that code — written from client work, not theory. No schedule promises; posts go out when there is something worth saying.