Launch Day Playbook

Use this public playbook to prepare the Genfeed.ai open-source launch on Show HN and Product Hunt. GitHub issue #1433  is the tracker for launch readiness; this page is the reusable operating checklist and public copy draft.

Launch Gate

Do not submit to Show HN or Product Hunt until the Sell-Ready walkthrough in #334  is green.

After that gate closes:

1. Pick Show HN for the first Tuesday, Wednesday, or Thursday morning in the primary US audience window.
2. Pick Product Hunt 8-14 days after Show HN, starting at 12:01 AM Pacific.
3. Freeze launch copy and gallery assets 48 hours before each submission.
4. Keep the maker online for the first two hours after each launch.

Public Safety Rules

• Keep submissions factual. Avoid private strategy notes, vault links, internal pricing, roadmap commitments, or unannounced customer names.
• Do not automate Hacker News posting, comments, replies, voting, or engagement.
• Use the launch-kit workflow to draft copy, then human-review every word before posting.
• Redact secrets, customer data, billing IDs, and private analytics from all screenshots.
• Treat GitHub issues and Projects as the source of truth. Do not create a parallel local launch backlog.

Repo Launch Readiness

Every row needs public evidence before the Show HN date is final.

Attribution

Use a single campaign name so the launch cohort is easy to compare across channels:

utm_campaign=oss_launch

Recommended channel values:

Track at least:

• GitHub stars from baseline to T+24 hours, T+72 hours, and T+7 days.
• New signups with launch UTMs or channel referrers.
• Activation from the launch cohort: first brand created, first generation completed, first publish scheduled or sent.
• Self-hosting interest: docs quick-start views, Docker image pulls, and GitHub issues opened by launch visitors.

Show HN Plan

Submission

Submit a link to the public repo or public docs, not a private staging URL.

Draft title:

Show HN: Genfeed.ai - open-source AI content OS

Timing:

• Submit Tuesday, Wednesday, or Thursday morning after #334 is green.
• Avoid major US holidays and large conference keynote windows.
• Keep the first two hours clear for fast, technical replies.

First Comment Draft

Hi HN, I am building Genfeed.ai as an open-source AI OS for content creation.

The repo includes a self-hostable Community setup, a visual workflow editor,
generation pipelines, scheduling, publishing integrations, and a Docker quick
start. The goal is to let creators and dev-founders run the content loop
themselves instead of stitching together prompts, files, calendars, and posting
tools by hand.

The open-source core runs locally with Postgres and the published Docker image.
Generation can use BYOK provider keys or a local GPU. Cloud and enterprise
features live behind the documented OSS/Cloud boundary.

I am especially interested in feedback on the self-hosting path, workflow model,
and whether the architecture is easy to understand from the README and docs.

First-Comment FAQ

Use these answers only when the thread asks for them. Keep replies short and specific.

Product Hunt Plan

Product Hunt should follow Show HN by 1-2 weeks so the team can fold in HN feedback, refresh screenshots, and avoid splitting the launch conversation.

Product Page Draft

Tagline candidates:

• Open-source AI workflows for content teams
• Self-hostable AI content creation OS
• Generate, schedule, and publish with AI workflows
• The open-source content OS for creators

Short description:

Genfeed.ai is an open-source AI OS for content creation. Build visual workflows
for images, video, text, voice, and publishing, then run them in a self-hosted
Community setup or Genfeed Cloud.

Maker Comment Draft

I built Genfeed.ai because content creation is becoming a full operating loop:
research, generate, review, schedule, publish, and learn from performance.

Most AI tools cover one piece of that loop. Genfeed.ai is the open-source system
for the whole thing: visual workflows, content generation, asset management,
calendar scheduling, publishing integrations, and a self-hostable Community
setup.

The repo is public, the Docker quick start is the easiest way to try it, and I
would love feedback from founders, creators, and teams trying to make their
content process less manual.

Gallery Asset Checklist

Launch-Day Schedule

Launch-Week Content Calendar

Create and schedule these through Genfeed. Capture the workflow run, content ID, scheduled timestamp, and final public URL as dogfood evidence.

Metrics Review

Record a baseline before Show HN and compare each checkpoint to that baseline.

Activation means a launch-cohort user creates a brand and completes at least one generation or scheduled publish.

Final Pre-Submit Checklist

• #334 is green and linked from #1433.
• README, screenshots, architecture docs, CONTRIBUTING, and issue templates have public review evidence.
• Clean-clone Docker quick start has been run and evidence is attached.
• Show HN title and first comment are reviewed.
• Product Hunt tagline, maker comment, and gallery are reviewed.
• UTM links and analytics views are confirmed.
• Launch-week posts are generated and scheduled through Genfeed.
• Baseline metrics are recorded before the first submission.