Ballad

Ballad for technical founders who ship with coding agents

You ship every day. Nobody hears about it.

You build with Claude Code or Cursor. You push to main constantly. There's no marketer on your team, none planned.

What you want is simple: people find out what you shipped, then sign up.

What's in the way is that writing about the work is a separate job. It takes a different kind of time than building does. So releases go out unannounced. Posts happen when there's a spare evening, which is rarely.

The product keeps moving. The story of it stays in your commit history, where nobody who might sign up will ever read it.

What we do with the work you already did

You ship code, Ballad ships marketing. Four jobs change hands:

  • Release pipeline: Fed by the GitHub webhook, or by Claude Code commit recording with no webhook needed, every push to main is read, grouped into a release and turned into a changelog entry, big releases become a launch across blog, social and newsletter, and [skip changelog] in a commit message keeps one out.
  • Inbox and Slack approvals: Drafts are reviewed like a PR, so you approve, edit or send back with a reason Ballad learns from, using a one-tap Slack card synced to the Inbox; nothing ships without your yes, and the Trust ladder only moves a channel to one-tap or auto-approve when you grant it.
  • Authenticity gate: An editorial pass strips AI tells and checks each draft against a model of your own writing.
  • Beacon and People: Each signup is traced to the post that brought it, first-party and without cookies.
A dark-themed window for run #128 of driftwood / marketing listing pipeline steps from reading 6 commits through a newsletter issue as completed, a highlighted 'Your review' step with 4 drafts waiting, queued Publish and Measure steps, and a 'Review 4 drafts' button, with floating cards noting 7 signups from the launch thread and a publish to /changelog.A dark-themed Slack notification from the Ballad app at 8:15 AM titled 'Writing welcome series' describing a 3-email sequence, with Approve, Decline, Open in Ballad, and Dismiss buttons.

Check it yourself

We have no customer quote to put here, and we won't write one. This page names no customer.

What you can check is written down, starting with the docs:

  • Ballad reads your commits, drops what customers never see & drafts changelog entries, held to what actually shipped.
  • Agent drafts always come to you for review. Nothing publishes without the publish scope.
  • Depth articles are written from a short interview. Your answers are the only anecdotes, numbers and names the article may use.

Then open the product tour and look at the surfaces this page names: Release pipeline, Inbox, Authenticity gate, People.

Judge us on what's written down.