The social and community manager you haven't hired: posts for every network in the right voice, image posts worth stopping for, replies answered, the threads worth joining found while they're still open, and launches written for each community's rules.
A voice for each founder and teammate and one for the brand, each with its own networks and rules, and a plan that knows which one should say what, and where.
Posts, threads and image posts drafted ahead and placed where they'll land best. On X, Ballad posts them itself.
Replies to your posts come back with an answer drafted; praise and emoji are left alone.
Finds the threads where your buyers are asking the question you answer, while they're still open.
Show HN, Reddit and Product Hunt, each written for that community's rules, only when you ask.
A ballad.to page per voice that keeps your latest writing and your call to action current.
The founder's voice on LinkedIn reads differently from the brand's on X, and both differ again on Bluesky and Threads. Ballad drafts for each network in the voice that should be there, and you review every post in that network's own frame, with its character count.
Nobody follows a founder who only talks about their product. A person's give posts are spread across what people actually post about: building in public, reactions to what's happening in their market, their own field, something personal, and the problem the company solves. Only the asks and the problem posts mention the company.
Cards and carousels for LinkedIn, X, Instagram, Bluesky and Threads, built around a visual idea that rotates, so a feed of them doesn't look like one template repeated. Every one is in your brand, and every word on it is checked against the words you approved.
A post that starts a conversation and then goes quiet wastes the best part. Ballad reads the replies to your posts on X, takes comments you paste in from anywhere else, and drafts an answer for each one worth answering, in the voice that wrote the post.
Both. Replay runs with the same arguments by default, or you can edit them first. Any job from the last 7 days.
Honestly, fewer moving parts. Jobs live in the Postgres you already run, so there's no second datastore to watch.
Your buyers are already asking for what you make, in threads that are over within a day. Ballad reads Hacker News every hour and Reddit every six hours, picks the few threads where your positioning is genuinely the answer, and drafts a reply for the founder to post as a person.
I ran Driftwood on “write when inspired” for a year. Four posts. What finally worked wasn't discipline, it was a schedule someone else kept for me.
A Show HN, a Reddit self post, a Product Hunt listing. Each community has its own rules and its own allergy to marketing, so each is written for that community, from the facts you give it, and only when you ask. Nothing here is ever put on a schedule.
Hi HN, I'm Maya. We ran our background jobs on a cron box and a Redis queue until a job ran twice and charged forty customers twice. Driftwood keeps jobs in your own Postgres, so you can replay a failed one for 7 days. I'd love to hear where it breaks for you.
Every voice gets a ballad.to page: portrait, bio, your call to action, your latest writing, and everywhere else you are. Put it in your profiles once. Ballad keeps it up to date, and every click flows back into Signals.
Building background jobs that live in your Postgres. Writing about the mistakes along the way.
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 accounts and your first week of posts is drafted in your voice. Your job is a few yeses in the morning and the occasional reply only you can write.
