After you ship: post-launch operations for vibe coders and indie builders

Shipping is the celebrated half. The uncelebrated half is what happens between signup and second-week retention: welcome that actually lands, activation that does not depend on you noticing, support that triages before it burns your morning, billing that follows through without feeling aggressive, and a changelog that exists because commits happened — not because you found time to write one.

From signup to retained — four workflows

• Onboarding from signup: welcome sequences, activation nudges, and handoff to support — tied to your auth and event source (GitHub, Stripe, or whatever holds the sign-up).
• Support triage and FAQ drafts: inbox triage, drafted replies, and FAQ updates drawn from real questions — you approve before any public send.
• Billing follow-up and dunning: renewal and failed-payment follow-through with your approval on language and timing, plus clear opt-out and identification on every message.
• Changelog and release notes: weekly drafts assembled from commit messages, issues, and shipped fixes — held for your approval, then published where your users actually look.

The stack stays yours

You live in GitHub, Stripe, email, and a support inbox. That is the stack we operate around. The team does not ask you to migrate; it keeps the handoffs between those four places from depending on your memory. The same approval boundary applies here: public messages and commitments wait for you, irreversible or financial actions never auto-run, and licensed or legal judgment is not delegated.