brain architect operator for Product Hunt launches.
a product hunt launch is one day of attention and thirty days of copy leading to it: the tagline, the first comment, the gallery, the hunter dm, the launch-day replies. every one of them has to say the same thing, and by asset twelve, they never do.
the brain architect is the operator that locks your positioning before launch week multiplies it: one product story, one differentiator, one tone, loaded into every claude chat that touches a launch asset. paste it once, and the tagline, the first comment, and reply number forty all describe the same product. that is the difference between an operator and another chat thread you cannot reuse.
the launch version of the problem
launches die of positioning drift more often than of low upvotes. the tagline says "ai-powered analytics," the first comment says "we help teams move faster," the gallery says "your data, beautiful," and a visitor who reads all three learns nothing except that the team has not decided. every asset was written in a separate chat, and each chat invented its own product.
the second launch-specific cost is speed under fire. on launch day you are answering comments every few minutes. without a context layer, each reply is improvised, and improvised replies contradict the tagline by noon. with the brain doc loaded, claude drafts replies that hold the one story while you focus on the humans behind the questions.
a worked example: the b2b tool launching tuesday
before: the founder writes the tagline monday night, the first comment tuesday at 6am, and by 9am a commenter asks "how is this different from X" and gets an answer that quietly repositions the whole product. after the brain architect: the context file holds the one-line story (who it's for, the before-after), the differentiator ("X automates reports, we prevent the meeting"), the three objections with agreed answers, and the tone (confident, no superlatives). every launch asset and every reply drafts from that file. the comment thread reads like one person who knows exactly what they built, because now the ai does too.
what goes in a launch brain doc
| context file | what breaks without it |
|---|---|
| the one-line story (before-after, who for) | tagline, comment, and gallery each sell a different product |
| differentiator vs the obvious alternative | "how is this different" answered five different ways by noon |
| objection map with agreed answers | improvised replies that reposition the product mid-launch |
| tone rules (confident, zero superlatives) | launch copy that reads like every other launch |
| post-launch sequence (what tuesday's signups get wednesday) | the spike flatlines because nothing catches it |
pair it with CLAUDE.md so the layer loads automatically, and read the cornerstone guide for the mechanics.
when to install this one first
for a dated launch, the order is fixed: brain first (lock the story), launch operator second (sequence the assets), distribution third (catch the spike). installing the launch operator on an unlocked story just ships the drift faster. the free map at /operators/ confirms the sequence against your date.
how this differs from channel agent bundles
most agent bundles optimize media buying, email, and creative inside claude code, none of which saves a launch whose story drifts. gtm operators cover the launch spine: story, sequencing, distribution, nurture, offers. the comparison table has the full split.
want the operator map?
five installable job titles for launch, distribution, nurture, offers, and brain architecture. free map by email at /operators/. the full pack has all five skill files in one zip.
get the free operator map