The product marketer you haven't hired, working from what you ship. Connect a repository and each release becomes a changelog entry, and the big ones a launch. Give Ballad your URL and it drafts the positioning every piece is written from. Name a competitor and a battlecard is drafted from their own site and re-checked every week. Customer proof arrives with the customer's consent attached to every quote.
Reads your commits, drops what customers never see, and drafts changelog entries that name only what shipped.
Proposes a launch week for a big release or a big article, every piece on its day in the right voice, measured as one launch.
Drafts the one-liner, the statement and who you sell to from your site, writes every piece from them, and proposes a change when your buyers move.
A battlecard per competitor, drafted from their own site the moment they're added and checked every week for changes.
Asks the right customers for a story, keeps their consent on every answer, and turns the answers into case studies and proof points.
Connect your repository and Ballad reads what you merge. On a daily or weekly cadence it drops the refactors and test fixes, groups the rest into changes a customer would notice, sizes the release, and drafts the entry for your changelog.
A job failed at 3am? For 7 days after a run you can replay it with the same arguments, or edit them first. Whoever owns the queue gets an email when it runs again.
A major release, an article worth pushing, or something you're running becomes a proposed launch week: founder posts on each network, a thread, a brand post, the newsletter issue, a Show HN and an image card. Trim what you don't want, pick the start, and run it. Every one lives on its own tab, Campaigns.
Failed jobs are what prospects ask about most. A launch that leads with replay answers the question before the demo does.
Positioning usually lives in a slide nobody opens. In Ballad it's the plan: a one-liner you can say out loud, the statement behind it, and the segments you sell to. Every post, launch, bio and brief is written from it, so changing it changes what goes out.
The trouble with battlecards isn't writing them, it's that they go stale the week a competitor changes their pricing page. Ballad drafts one for every competitor as soon as it's added, whether you named it, onboarding found it or a market review suggested it, from their own site and your positioning. Then it checks the pages it read every week and proposes an update when they change.
We moved off Halyard after a job ran twice and charged customers twice. That was a week of refunds.
Ballad watches People for customers who came through your content and converted, and suggests who to ask. You send them a link; they answer six questions and choose, answer by answer, what may be quoted and how they're named.
What one job learns, the others use: the calendar writes from the positioning, the launches measure through the same signals, and the analysis changes the plan.
Connect your repository and your channels, and the next release arrives as a changelog entry and a launch week waiting for your yes.
