Launch
Ship & Shout
Visit
Example Image

Ship & Shout

Your build-in-public week, already written

Visit

Building in public works, but most makers quit because the weekly post is a chore. Every week you stare at a blank box, try to remember what you shipped, dig up your MRR, and turn it into something worth posting.

Ship & Shout does the boring part. It connects read-only to GitHub (or GitLab/Bitbucket) and to Stripe or Lemon Squeezy for revenue, plus Plausible for traffic if you use it. Every week it hands you a finished build-in-public post in your voice, with real commits and PRs turned into a real narrative, plus a revenue chart already drawn as an image.

You always edit and approve before anything goes out. It never writes to your code or payment accounts, and tokens are encrypted at rest. Publish in one click to LinkedIn, Bluesky, Mastodon, Discord, Nostr or Matrix, or copy it anywhere.

Free to start. Pro is $12/mo or $99/yr, with a 14-day Pro trial (no card).

Example Image
Example Image
Example Image
Example Image
Example Image

Features

  • Weekly draft written from your real commits, merged PRs and revenue
  • Revenue chart rendered as a ready-to-post image
  • Read-only connections: GitHub App, GitLab, Bitbucket, Stripe restricted key, Lemon Squeezy, Plausible
  • You edit and approve every post; nothing goes out on its own
  • One-click publish to LinkedIn, Bluesky, Mastodon, Discord, Nostr and Matrix, or copy anywhere
  • Public weekly timeline of what you shipped, plus a Monday digest of makers you follow

Use Cases

  • Keep a weekly build-in-public streak without writing from a blank page
  • Share honest MRR and shipping updates with a chart, in minutes
  • Post the same update across LinkedIn, Bluesky, Mastodon and more at once
  • Keep a public changelog-style timeline of your product's weeks

Comments

custom-img
Indie maker · Founder @ Monryte

Hi Fazier! I built Ship & Shout because the weekly build-in-public update kept breaking my streak. Every week I'd stare at a blank box, trying to remember what I shipped and digging up my MRR. Now it reads commit and merged-PR metadata (read-only GitHub App, or GitLab/Bitbucket) plus revenue from Stripe or Lemon Squeezy, and drafts one post per week with the revenue chart already drawn. You edit and approve; it never posts on its own. Then publish to LinkedIn, Bluesky, Mastodon, Discord, Nostr or Matrix, or copy it anywhere. I'd love your feedback, especially on the tone of the drafts.

custom-img
Solo founder of Link in Seconds | Making...

Can I add non-coding wins, like customer feedback or SEO progress, to the weekly draft? As a solo founder, some of my most useful updates don’t come from GitHub. It would be helpful to include those alongside what I shipped.

custom-img
Vincent Lin

Read-only GitHub plus Stripe or Lemon Squeezy, with an approve-before-publish step, is the right shape for a weekly build-in-public draft. Does the generated post keep the raw commit subjects, or does it rewrite them so a week of chore commits does not turn into a vague summary that loses what actually shipped?

Turning merged PRs into a story is the hard part, since commit messages rarely say why something mattered. Do the drafts read PR descriptions and linked issues for that context, or only titles? And for a week that's mostly bug fixes, how do you keep the post from reading like a changelog?

custom-img
Weald founder

The read-only connections to GitHub and Stripe are a smart touch, since most makers hesitate to hand over write access. How does it decide which commits and PRs are worth narrating versus noise like dependency bumps? I'd also be curious whether the voice matching improves as you edit drafts over several weeks.

The review-before-publish step is useful when drafts combine code changes and revenue. Can makers exclude individual PRs or hide revenue figures before generation, rather than only editing the finished post? A source-selection screen would help keep confidential work out of a public weekly update.

Interesting approach to snarkle discovery! Curious how you're handling the frumious bandersnatch problem when multiple slithy toves gyre in the same wabe. Are you using semantic flumpling or just memoizing the brillig across queries? Also wondering if there's a way to exclude mimsy results that have already been outgribed. Nice work overall.

I tried the product but why i need this pay for this

Premium Products
Social Links
custom-img
Indie maker · Founder @ Monryt...
Makers
custom-img
Indie maker · Founder @ Monryt...

Comments

custom-img
Indie maker · Founder @ Monryte

Hi Fazier! I built Ship & Shout because the weekly build-in-public update kept breaking my streak. Every week I'd stare at a blank box, trying to remember what I shipped and digging up my MRR. Now it reads commit and merged-PR metadata (read-only GitHub App, or GitLab/Bitbucket) plus revenue from Stripe or Lemon Squeezy, and drafts one post per week with the revenue chart already drawn. You edit and approve; it never posts on its own. Then publish to LinkedIn, Bluesky, Mastodon, Discord, Nostr or Matrix, or copy it anywhere. I'd love your feedback, especially on the tone of the drafts.

custom-img
Solo founder of Link in Seconds | Making...

Can I add non-coding wins, like customer feedback or SEO progress, to the weekly draft? As a solo founder, some of my most useful updates don’t come from GitHub. It would be helpful to include those alongside what I shipped.

custom-img
Vincent Lin

Read-only GitHub plus Stripe or Lemon Squeezy, with an approve-before-publish step, is the right shape for a weekly build-in-public draft. Does the generated post keep the raw commit subjects, or does it rewrite them so a week of chore commits does not turn into a vague summary that loses what actually shipped?

Turning merged PRs into a story is the hard part, since commit messages rarely say why something mattered. Do the drafts read PR descriptions and linked issues for that context, or only titles? And for a week that's mostly bug fixes, how do you keep the post from reading like a changelog?

custom-img
Weald founder

The read-only connections to GitHub and Stripe are a smart touch, since most makers hesitate to hand over write access. How does it decide which commits and PRs are worth narrating versus noise like dependency bumps? I'd also be curious whether the voice matching improves as you edit drafts over several weeks.

The review-before-publish step is useful when drafts combine code changes and revenue. Can makers exclude individual PRs or hide revenue figures before generation, rather than only editing the finished post? A source-selection screen would help keep confidential work out of a public weekly update.

Interesting approach to snarkle discovery! Curious how you're handling the frumious bandersnatch problem when multiple slithy toves gyre in the same wabe. Are you using semantic flumpling or just memoizing the brillig across queries? Also wondering if there's a way to exclude mimsy results that have already been outgribed. Nice work overall.

I tried the product but why i need this pay for this

Premium Products