# Lesson 7: Ship it on purpose

> Releases make shipping a discrete, announceable event, and GTM is the half of shipping that happens outside the codebase.

Source: https://productos.ca/documentation/guides/academy/lesson-7-ship-it-on-purpose (last reviewed 2026-09-22)

A **release** is the bundle of work that ships together, with a version and a date. The point is to make shipping a *discrete event* (something you can announce, measure, and roll back) instead of a vague "it's live now, probably."

## Why bundle at all when you deploy daily

Continuous deployment is how code moves; releases are how *meaning* moves. Customers, changelogs, and your own outcome measurements all need a moment in time to point at. "v0.4, exports shipped May 12" is a fact you can measure against; "sometime in May" isn't.

## GTM: the second half of shipping

A great feature nobody hears about is a tree falling in a forest. **Go-to-market** is how the thing reaches and convinces people, and its minimum viable form is two decisions:

- **Messaging**: translate the feature into a felt benefit. "We added webhooks" vs. "Connect ProductOS to anything in 5 minutes." Same feature, different sale.
- **Channel**: where you'll say it. You can't work ten channels solo. Name one or two and go deep: your newsletter, a community, the changelog itself.

## Do it now

1. On [Releases](https://productos.ca/documentation/pages/golden-thread/releases), create a release containing your Lesson 4 feature. Give it a version and a date.
2. Draft the release notes with **Draft with ProductSense** on the Notes field, then edit them into your voice. The draft is a starting point, not a shipping point.
3. On [Channels](https://productos.ca/documentation/pages/gtm/channels), add the one channel this release will actually be announced through.

> **The changelog is a channel**
>
>   ProductOS can publish a public changelog. For an early product, that plus one social channel is a complete GTM motion.