Practical notes on building, shipping and learning from developer marketing—with the systems to keep the work connected.
Every post here is a published piece inside our instance of Quiver.
Subscribe via RSS· Tessa Kriesel
You heard the exact sentence you needed three Tuesdays ago, and by the campaign meeting it had become “save time” and “seamless.” That is not a writing problem. It is a broken handoff between customer evidence and the decisions it was supposed to inform.
· Tessa Kriesel
AI made marketing output easy, but the context, evidence, approvals, publishing, and results still live in disconnected tools. I built Quiver to give developer marketing the architecture engineers expect.
· Tessa Kriesel
Publishing is only the first state change. Here is how to track where content goes, preserve the relationship between source and derivative, and learn which message actually moved people.
· Tessa Kriesel
Competitive research goes stale quickly. Here is the weekly workflow I use to detect meaningful changes, preserve the evidence, and feed useful findings into Quiver.
· Tessa Kriesel
A practical guide for technical founders building a launch campaign: define the outcome, connect the assets, instrument the funnel, and carry the learning into the next campaign.
· Tessa Kriesel
Developer content should be structured, versioned, reusable, and observable. An API lets your website render the work without becoming the place where its history disappears.
· Tessa Kriesel
A behind-the-scenes look at the campaign system behind Quiver’s launch—from positioning and product proof to content, distribution, approvals, and measurement.