Loopcard — channels GTM (deep)

Date: 18 September 2026
Product: Loopcard (Virtus Labs)
Preview: https://cryptobook.space
Preferred live URL: loopcard.ai / loopcard.app / getloopcard.com
Unit of growth: a PNG other people post. Not an upvote. Not a waitlist. Not a ranked blog.
Media spend: $0. Time is the budget.

Companions (paste-ready copy lives there; this file is the why and the honest numbers):

• docs/marketing/calendar-30-days.md — day-by-day posts
• docs/marketing/community-playbook.md — Show HN, Reddit, PH maker comment, 10 DMs, objection table
• docs/marketing/channel-plan.md — one-page checklist
• docs/marketing/social-launch-kit.md — short copy
• docs/marketing/claims-we-will-not-make.md
• docs/11-loopcard-product.md

Replace {{URL}} with the live host. Until DNS exists, that is https://cryptobook.space, and every first post on a skeptical board says so. Replace {{CARD}} with the 1080×1080 labeled $6k demo (or a real organic card, if one exists).

0. How to use this file

For each channel below: why it might work, failure mode, exact first post, honest reach, cadence, what not to do.

Two rules sit above every channel:

1. Upvotes ≠ cards. A Show HN with 80 points and zero downloaded PNGs is a vanity day. A Reddit post with 12 upvotes and three stranger-made cards is a win. Product Hunt with 400 upvotes and 23 people on a pricing page (a real #1, September 2026 — see §5) is a press clipping, not a business. Count public Loopcard PNGs that are not ours.
2. Product Hunt is gated. Draft the listing whenever you want. Publish only after organic screenshots exist (gate in §5). A cold PH of a PNG generator is a graveyard URL you cannot un-publish.

Organic proof folder: docs/marketing/organic-cards/ — URL, handle, date, whether the number is the $6k demo or a personal export. Day 19 of the calendar fills it. Day 22 reads it.

1. Stack order (do this, not everything)

Do not open five channels on day one. X + one Reddit sub is a launch. Everything else is a follow-up.

2. 2026 launch-board realities (upvotes ≠ cards)

These numbers are why the PH gate and the “one Show HN” rule exist. They are not our metrics. They are the ambient physics.

Hacker News

Scraped Show HN corpus, 18 Jun 2025 – 18 Jun 2026 (41,301 posts, jonno.nz / Algolia HN API):

A front-page Show HN for a developer tool, when it happens, is reported in the 5,000–30,000 visit band, 50–400 signups, conversion typically under 5%. Loopcard does not have a signup. The conversion event is Download card. Plan for a handful of PNGs even on a “good” thread; plan for zero on the median thread.

Extra HN tax for us:

• AI/ML Show HN viral rate is the worst common topic (~4.6% vs ~13.9% for OSS tools in one 2023–2026 model). “Another AI wrapper” is the default read.
• Posts that point at github.com historically over-index among 200-point Show HNs. We are a static page on a leftover crypto domain. That is a handicap, not a mystery.
• Permit.io’s own Show HN: 2 points. Their PH was #8 / 138 upvotes. Two different games. Neither game is “cards posted.”

Product Hunt

H1 2026: ~3,869 products launched; average ~144 upvotes. Most pages are never seen outside the maker’s group chat.

Recent calibration, not our launches:

The #1 Product of the Day that published its analytics in September 2026 is the sentence to remember: four hundred upvotes, twenty-three people on the pricing page, three installs. Upvotes are a leaderboard. Cards are the product.

Other 2026 PH physics:

• Hunter auto-notify is gone. Self-hunt. A paid hunter is a ToS and reputation risk, and the playbook already forbids it.
• Ranking is a composite of weighted votes (aged accounts beat fresh ones), comment depth, click-through from the daily board, and reviews. Fifty “congrats!” comments are negative signal.
• B2B conversion from PH traffic is quoted in the 1–2% band. We are not even asking for an account. If 400 people land and 20 download a PNG, that is a good day. If zero of those 20 post it, PH did not work.
• Average launch (144 upvotes) is already “fine.” A cold PNG generator without organic proof lands below that — the 12-upvote graveyard the community playbook warns about. You cannot delete the URL from the internet.

Implication for Loopcard: treat HN and PH as one-shot credibility boards. Treat X, Reddit, and other people’s timelines as the growth loop. Never use a PH rank as a proxy for demand.

3. X / Twitter

Why it might work

The product is an X object. A 1080 square with a dollar figure is native. The $6,000 Claude Code overnight is already a genre on this site; we did not invent the screenshot habit, we designed the mugshot. Quote-tweet with your number is the loop. No account on our side, so the CTA can be “download and post” instead of “sign up.”

X is also where the organic-cards folder fills. Without X, the PH gate never trips.

Failure mode

A zero-follower Virtus account posting a thread into the void. Link-only tweets (no PNG) get no distribution. Threads longer than the Day 1 7-post launch look like a course. Daily “gm here’s the card again” trains the algorithm that we are a bot and trains humans to mute. Crypto-adjacent posting (tickers, WAGMI, “gm”) re-activates the domain tax — people will assume the leftover cryptobook.space URL is a token. Quote-tweet bait (“reply with your bill”) that nobody answers, then we invent a testimonial to fill the silence.

Exact first post

Day 1 launch thread from calendar-30-days.md / social-launch-kit.md. Do not improvise.

• Asset: {{CARD}} on tweet 1. Square PNG. Dark, pink bloom, LOOPCARD watermark, source line “Published 2026 reporting.”
• Tweet 1 is the story, not the product name. Tweet 3 is the URL. Tweet 4 is the “what we are not” list. Tweet 7 is Virtus + the ask (number, not repo).
• If the preview host is still cryptobook.space, the URL tweet or a reply must contain the leftover-domain sentence. Do not hide it in tweet 7.
• Time: a human US morning or whenever this account is actually awake. Do not schedule for 3am PT to “hit Europe.”
• Handle: @loopcard / @getloopcard if we have them; otherwise the operator’s real account. A newborn brand account with 12 followers posting a 7-thread is weaker than a named human with the same PNG.

First reply under our own thread, if someone says “just use ccusage”: agree. Pin the agreement if it is the best comment.

Expected honest reach

Do not forecast “going viral.” The $6k number is the only hook that has a chance. Most days will be the low-hundreds row. That is still the right channel because the format matches.

Cadence

• Days 1–7: one primary post/day (calendar). A second platform the same day is optional.
• Days 8–21: still ~1/day, rotating proof / ccusage / how-to / public stories. If nobody replies by Day 19, keep posting labeled public stories. Do not invent a customer.
• After day 30: 3–5 posts/week, not 3/day. Repeat the $6k card until it is boring, then post a new public-story number ($1,263 Cursor, $480 median) — still labeled re-creations.
• Reply in the same hour you post, then once more that evening. Do not sit the timeline for six hours.

What NOT to do

• Post without {{CARD}} unless the calendar says “text only.”
• “Upvote if” / “RT if your agent burned you.”
• Fake follower pods, reply-guy spam under @cursor_ai / @AnthropicAI, or asking Anthropic/Cursor employees for a retweet.
• Crypto stickers, token tickers, airdrop jokes, “WAGMI.”
• “We stop the runaway.” “SOC 2.” Fake user counts.
• Other people’s private invoices, even as a crop.
• A second launch thread next week because the first one got 40 views.
• Linking Product Hunt on X if we did not launch PH.
• Buying ads. Default media is $0.

4. LinkedIn

Why it might work

The person who pays the Claude / Cursor bill is more likely to be on LinkedIn than on r/LocalLLaMA. The job of the card is often “forward this to finance / the cofounder.” Uber burning a year of AI budget in four months is a LinkedIn-native anecdote (published reporting — they did not use us). Virtus Labs already has a company surface; a named operator post outperforms a brand page.

LinkedIn’s native image upload is how the PNG travels. A link-only post dies in the grey unfurl of cryptobook.space.

Failure mode

Daily product posts from a company page. “Thrilled to announce.” Thought-leadership carousels with 10 slides of “5 lessons from runaway agents.” Tagging Uber, Anthropic, or Cursor as if they are customers. Using the CryptoBook retirement as drama. Posting the same X thread verbatim (LinkedIn readers will forgive a sharp paragraph; they will not forgive a 7-tweet paste).

LinkedIn also punishes CTA-only posts from thin profiles. If the operator has no history, one post is still worth doing; a cadence of seven is noise.

Exact first post

Day 5 copy (calendar). Native upload of {{CARD}}, not a link preview.

Title line in the first 140 characters (that is the truncation):

The overnight Claude Code bill is now a genre. We made the card.

Body: the $6k public story + Uber as published reporting, not a case study + browser-only / no keys + we retired CryptoBook social + {{URL}} + “Virtus Labs · US-oriented · we will not call this compliance.”

Do not put “Product Hunt” or “Show HN” in this first post.

Expected honest reach

LinkedIn will not fill the organic-cards folder by itself. It is for the forward use case and for not looking like a crypto ghost.

Cadence

• Launch month: 3 posts (Days 5, 11, 15 in the calendar). Optional Day 18 (retired CryptoBook, light) and Day 28 recap.
• After month 1: 1–2 / week. Not daily. Alternate: public budget story (always labeled), “what we are not,” a real organic card with permission.
• Comments: same day. Do not debate “AI governance.”

What NOT to do

• “Trusted by,” logos, SOC 2, AI Act, “used by developers at [Fortune 500].”
• Document carousels that hide the PNG on slide 8.
• Tagging companies that did not ask.
• A waitlist screenshot as “traction.”
• Posting PH rank if we skipped PH, or inflating rank.
• Boosting the post with paid. $0 media.

5. Reddit

House rules from the playbook, repeated because they are the channel: one post per sub, rewritten, sidebar checked the morning of, flair correct, disclose you made it, stay 24 hours, no upvote bait, no PH mention, no copypasta. If the sub forbids self-promo that day, skip. If a mod removes it: one sentence in modmail, do not repost.

Read the live sidebar. Rules below were checked against 2026 public writeups; mods change them.

5.1 r/ClaudeAI

Why it might work. This is the overnight-bill genre’s home. People already post Claude Code invoices, weekly-limit complaints, and CSV screenshots. Showcase is an explicit rule (“Showcase your project in a way that helps educate and inspire others”). The product names Claude in the first line without pretending to be Anthropic.

Failure mode. Showcase volume is high; as of April 2026 mods noted showcase was ~half of non-episodic submissions and routed low-karma OPs to a Built-with megathread. OP total karma < 50 → megathread, not the feed. A feed post that is a link + marketing copy sinks. “Does this stop spend?” pile-ons if we overclaim. Affiliation with Anthropic, even implied, is a remove.

Exact first post. Day 2. Title and body in community-playbook.md §3.1 — not the shorter social-kit version. Attach {{CARD}}. Flair: Showcase / Resource / whatever the sidebar says that morning. First paragraph is the problem (CSV screenshots), then the link, then the “not affiliated / not a cap / leftover domain” block. Sit the thread 24h with the objection table open.

If karma is under 50: post in the showcase megathread only. Do not try to dodge it.

Honest reach. Feed post, honest, with image: 20–200 upvotes is a good outcome; 5–40 comments, half of them “just use ccusage” or “just screenshot the Console.” 0–10 people download a card; 0–3 post one. Megathread: near zero feed reach, maybe one useful parser bug report. A copypasta link post: 0–5 and a remove.

Cadence. Once. A follow-up is allowed only with a new angle (Day 12 “what Loopcard is not,” or Day 29 post-PH/still-shipping). Never three titles in three days.

What NOT to do. Ask for upvotes. Mention PH. Cross-post the Show HN. Claim we cap tokens. Drop a referral. Argue in modmail. Reply-guy every overnight-bill thread with our URL the same week as the launch post (that is how you get tagged a spammer after a legitimate showcase).

5.2 r/cursor

Why it might work. Cursor users have a dashboard total and a public $1,263-month story. The “send this to a cofounder” job is real. The sub is smaller and more product-specific than r/ClaudeAI, so a Cursor-export first paragraph can land.

Failure mode. This community has already asked, in public, to ban “I made my first app” showcases. A Loopcard post that reads as “I vibe-coded a PNG maker” will be treated as that. Self-promo is tolerated only when it is clearly about Cursor usage, disclosed, flaired, and not “20× your productivity.” Parser that chokes on a current Cursor CSV — then we vanish — is worse than not posting.

Exact first post. Day 4, only if Day 2 did not consume the hours. Title/body: playbook §3.2. Lead with Cursor’s dashboard vs a card. Name ccusage without mocking it. Name the $1,263 HN-cited month as the same genre, labeled. “Not a Cursor competitor. Tell me if the CSV headers do not parse.” Attach the card. Flair: Showcase / Discussion as the sidebar requires.

Honest reach. 10–80 upvotes if it is about Cursor bills; 0 and a remove if it is a generic AI-tool launch. Comments will be harsher than r/ClaudeAI. One person pasting a header row we do not support is the prize — fix it the same day.

Cadence. Once. Optional Day 12 if r/ClaudeAI already got the “what we are not” follow-up and this sub did not.

What NOT to do. “Cursor alternative.” “Cheaper than Cursor.” “I built this in an afternoon with Cursor” as the hook (true or not, it is the banned genre). Crosspost from r/ClaudeAI with the same title.

5.3 r/LocalLLaMA

Why it might work. Many people here still have an Anthropic / OpenRouter / Cursor line item next to llama.cpp. A card for that invoice, with the title admitting we are not a local model, can survive. Parser feedback on OpenRouter CSVs would be useful.

Failure mode. The default read is “cloud SaaS tourist.” Title that hides the “not a local LLM” fact gets you a remove and a reputation nick. Arguing after a remove is how you get banned from a sub you might want later. Pitching an MCP gateway (we killed that) would be a second offense against this room’s instincts.

Exact first post. Day 7. Playbook §3.3. Title must say not a local model tool in the first clause. Body: leftover domain, FileReader, labeled $6k re-creation, “if this is off-topic I will remove it.” Attach the card. If a mod removes it: “understood, won’t crosspost.” Stop.

Honest reach. 0–50 upvotes, or a clean remove with no drama. Treat a remove as the base case. A surviving post that yields one OpenRouter header dump is a win.

Cadence. Once. Never a second attempt with a punchier title.

What NOT to do. Pretend we run local models. Offer a hosted proxy. Crypto jokes. Repost. “Show HN” in the title.

5.4 r/ChatGPT

Why it might work. It is huge. Screenshot culture is native. A shareable bill card as a visual might get lurker curiosity.

Why it probably will not. Loopcard’s horror story is Claude Code / Cursor, not ChatGPT Plus. ChatGPT bills are a different shape (subscription + occasional API). 2026 rules send posts “solely focused on advertising a single other LLM service” to a weekly self-promotional megathread. The main feed rewards memes, outputs, and news — not a Cursor CSV parser. A Loopcard launch post on the main feed is off-topic and removable.

Exact first post (only if you insist). Do not use the r/ClaudeAI title. Options, in order:

1. Skip. Recommended. Spend the hour on X replies or the r/cursor parser.
2. Weekly self-promo megathread, one comment: who you are, browser-only, no keys, leftover domain, {{URL}}, {{CARD}} if the thread allows images. No “Show HN-style.”
3. If — and only if — the live rules that morning allow a Showcase flair for tools that are not ChatGPT-the-product: a post that is about API / Codex / agent spend screenshots in general, with Claude/Cursor named as the demo sources, not as “switch off ChatGPT.”

Honest reach. Megathread comment: tens of views. Main-feed post that survives: lottery, usually <20 upvotes and off-topic replies. Main-feed post that does not survive: a remove and a mark on the account.

Cadence. At most one megathread comment in 30 days. No feed campaign.

What NOT to do. Launch here first. Copypasta. “ChatGPT alternative.” Pretend the $6k overnight is a ChatGPT story. Vote manipulate. Mention PH.

Reddit, all four — shared NOT list

• Same title on three subs in one afternoon.
• Asking for upvotes or awards.
• Linking the Show HN or the PH page on day one (looks like a campaign).
• Fake “found this tool” alt accounts.
• Pasting private invoices “as an example.”
• Staying to win an argument.

6. Hacker News (Show HN)

Why it might work

HN already circulated the $1,263 Cursor-month and will argue about agent bills without us. A browser-only FileReader parse, no keys, labeled demo data, and a public note that we killed the larger worse product is the technically honest story. Show HN is the one room where “this is a screenshot app” is a feature if we say it first. A surviving thread is a permanent URL and a backlink. That is the prize, not the points.

Failure mode

The median Show HN is 2 points and silence (§2). AI-flavored Show HNs underperform OSS tools. cryptobook.space as the submitted URL is a flag magnet (“is this a crypto thing?”). Marketing tone in the title, editing the title after launch, asking for upvotes in a Slack, voting from extra accounts, or resubmitting next week are how you get hellbanned. Hitting the front page and then answering with marketing paste wastes the 7-hour comment half-life. A same-day PH + Show HN looks like a launch campaign and gets both rooms to ignore you.

Even a front-page hit is a 48-hour conveyor. It is not distribution.

Exact first post

Once. Weekday 8:00–10:00 PT (playbook). Product must work on a phone; demo button must work with no file. Do not submit from a brand-new HN account if you can use a real one with history.

Title (≤80 chars):

Show HN: Loopcard – shareable Claude/Cursor bill cards (browser-only)

First line of the text is {{URL}}. Then the playbook body (§2 of community-playbook). Required sentences: labeled $6k re-creation; FileReader; no keys; not a gateway / not observability / not a cap; leftover cryptobook.space domain; ccusage is better accounting; this is the mugshot.

Submit the product URL, not a blog post, not a PH page, not a GitHub later-maybe. If a public repo exists by then, you may mention view-source / repo in the text; do not bait-and-switch the submitted URL.

Thread-sitting: first two hours, technical replies first (CSV headers, privacy, domain). Heart the “this is a screenshot app” comment. One reply per comment unless they follow up. Objection table is the source of truth. Do not drop the same text on r/programming.

If the domain is the first objection: leftover-domain sentence, once, then stop repeating.

Expected honest reach

Points are not the KPI. A 12-point thread that produces two stranger PNGs beat a 90-point thread of “just screenshot the dashboard.”

Cadence

One Show HN. Forever, until the product is a different product. Dark mode is not a different product. A new domain is not a reason to resubmit. A Pro SKU is not a reason to resubmit.

Do not Show HN and PH the same day. Sequence: Reddit + X first → organic cards → Show HN on a quiet weekday → PH later if the gate passes.

What NOT to do

• Resubmit. Edit the title to stuff keywords. Astroturf votes.
• “Show HN: Loopcard – the OS for agent spend.”
• Submit cryptobook.space without the leftover-domain paragraph.
• Argue culture (“Reddit is better”). Cross-link the Reddit posts.
• Promise SOC 2, a kill switch, or “we would have saved Uber money.”
• Stay in the thread for a week performing. After hour 48, check once for parser bugs, then leave.

7. Product Hunt (gated)

Why it might work

PH is still the loudest indexed launch URL in 2026. A Product of the Day badge is a backlink (producthunt.com is a strong referring domain) and a sentence on a deck. Maker comments from people who already posted a card are the only comments that look real for a screenshot product. Self-hunt is fine; the hunter boost is gone.

It might work only as a harvest, not as a discovery engine. The calendar’s whole point of Days 22–30 is: PH after the PNG is already traveling.

Failure mode

Cold launch of a PNG generator. 12–80 upvotes, thin “congrats” comments, a URL that Googles forever as “Loopcard – 12 upvotes.” Paid hunter. Upvote Telegram. LaunchPact-style vote rings (screenshot-verified or not, PH can still strip them). Same-day Show HN. Gallery of fake dashboards / fake UGC. Tagline that says “AI compliance.” Domain unfurl that says CryptoBook. Asking for upvotes in the maker comment. Treating 200 upvotes as 200 users.

The September 2026 #1-of-day with 410 upvotes → 23 pricing-page hits → 3 installs is the failure mode of success if you confuse the leaderboard with the product.

The gate (non-negotiable)

Publish PH only if docs/marketing/organic-cards/ contains:

• at least 3 public posts (X, LinkedIn, or Reddit) with a Loopcard PNG by people who are not Virtus, not this operator account, not a contractor, or
• 1 non-operator card that used a personal export (their number, not $6,000) plus two more any-source organic posts.

If the folder is empty: do not launch. Run the calendar’s NO-GO copy on Days 22, 26, and 30. Skip hunter outreach. Silence beats a dead page.

Draft the listing internally whenever you want. Draft ≠ publish.

Exact first post (GO only)

Do not publish the same day as Show HN.

• Name: Loopcard
• Tagline: The screenshot after a runaway coding agent.
• First link: {{URL}} (new domain if it exists; leftover domain if not — say so in the maker comment).
• Topics: Developer tools, Artificial intelligence, Productivity.
• Hunter: operator, or a real user who already posted a card. No paid hunter.
• Gallery: (1) 1080² $6k demo, labeled re-creation (2) browser UI, no key field (3) organic cards with permission (4) 15s from Day 3. No fake MRR dashboards.
• Maker first comment: playbook §5 / calendar Day 26. Origin = we killed the MCP gateway. Differentiator = PNG, FileReader, no keys. CTA = make a card, not “upvote.” Honest if Pro comes later. Leftover domain sentence if still on cryptobook.space.
• Launch time: PH day starts 12:01 AM PT. You do not need to be awake at 12:01 if you cannot sit comments; you do need to sit the first working hours of US morning. Comments > raw 12:01 spike in 2026.
• Seeded comments: only people who used the card. Use-case first, one number, a real question. No “awesome launch team.”

Day 26 X/LinkedIn mirrors exist in the calendar. Do not post “we launched on PH” if you did not.

Expected honest reach

B2B “great launch” signup band (50–300) does not apply; we have no signup. Translate to cards downloaded and cards posted. If PH week produces fewer organic PNGs than the two weeks before it, the launch failed even with a badge.

Cadence

• Zero public PH activity until the gate.
• GO: one launch day, then 24h of replies (calendar Day 27 canned answers).
• After that: the listing is a backlink. Do not “relaunch with dark mode.”
• NO-GO: never.

What NOT to do

• Launch to “get it over with.”
• Hunter-for-hire, upvote exchanges, fake reviews, sock puppets.
• Gallery with SOC 2, customer logos, or “runaway stopped.”
• Discount codes and fake urgency (there is no charge).
• Asking for upvotes anywhere, including X.
• Announcing a rank you did not get.
• Using PH as the first channel.

8. TikTok / Reels / Shorts

Why it might work

The $6,000 tick is a 3-second visual hook. Vertical video is how a non-developer sees the genre. One 15s file can be posted on TikTok, YouTube Shorts, and Instagram Reels. Saves and off-platform shares are the 2025–2026 distribution signal; a card someone screenshots from the video is on-brand. No login on our side matches “link in bio.”

Failure mode

Talking-head “I built a SaaS.” Stock hoodie-hacker B-roll. Fake MRR dashboards. Promising “never get a $6k bill again.” 60-second explainers. Posting 11 times a day. Buying views. A cryptobook.space URL on screen that reads as a crypto ad and gets the clip reported. TikTok-to-CSV conversion is structurally bad (phone, no export file handy). Treating a 40k-view clip with 12 bio-link clicks and 0 cards as product-market fit.

Shorts/Reels/TikTok are a lottery. Most clips die at 200–800 views. The ones that hit do not automatically become Loopcard users.

Exact first post

Day 3, 15s. Script is in the calendar. Same file, three apps, same day is allowed (one export, three posts).

Caption: leftover-domain sentence if needed. No “#aitools #gpt #fyp” dump; 3–5 tags max. Do not say we stopped the agent.

Later clips (Days 13, 20): “bar tab” and synthetic-CSV drop. Never film a real Anthropic invoice with account IDs.

Expected honest reach

YouTube Shorts sometimes has a longer tail than TikTok (search + suggested). Reels follows the Instagram account’s existing graph — if Virtus has none, treat as TikTok-class lottery.

Cadence

• 30-day calendar: 3 clips (Days 3, 13, 20), each reused across three apps if time exists.
• After month 1: 1–2 / week only if you have a new organic card or a new public-story number to tick. Do not grind 1/day of the same $6k motion.
• No TikTok on Day 30 unless there is a new organic card to film.

What NOT to do

• “We stop the runaway.” Fake dashboards. Face-cam without the card on screen in the first second.
• Trending audio that fights the VO.
• Spark Ads / boosts. $0 media.
• Linking PH in the bio if we did not launch.
• Scraping someone else’s invoice into the video.
• Calling it “content marketing strategy” in public. It is a 15s mugshot.

9. Discord / Slack communities

Why it might work

Overnight bills show up as complaints, not as launch announcements. Cursor Discord, Claude-adjacent servers, indie-hacker Slacks, agency ops channels: someone pastes a Console screenshot, and a PNG is a reasonable reply if you already belong there. The 10 named DMs in the playbook are the structured version of this (people who already posted a public bill).

Failure mode

#launches spam on day one from a 0-history account. Cross-posting the X thread into 15 Discords. “Love this community, thought I’d share.” Partnership pings to Permit.io / Langfuse / SuperPenguin. Scraping member lists. Posting in Anthropic or Anysphere official servers as if we are affiliated. The PNG spammer gets banned and the ban follows the brand into Reddit.

Exact first post

There is no launch post. Sequence:

1. Join as a human. Read rules. If they forbid tool promo, do not post the product.
2. Answer 5 unrelated questions (CSV, Cursor limits, ccusage) with no link.
3. When someone already posted a bill screenshot, reply once: ccusage for the terminal; Loopcard if they want a square; leftover domain; no keys; {{URL}}. Attach the card only if the channel allows images.
4. Send at most the 10 DMs in playbook §6, named people, one ask, stop if ignored. No second “just bumping.”

Do not open a Virtus Loopcard Discord in month 1. Nobody will join it. Do not ask to add a bot.

Expected honest reach

• A well-targeted reply in a busy Cursor Discord: tens of eyes, 0–2 clicks.
• The 10 DMs: 0–3 replies, 0–1 public card. That is a successful DM campaign.
• A launch dump in #showcase: a warning from a mod, then a ban.

Cadence

• DMs: ten, once.
• Community replies: only when a bill is already on the table, ≤1 product mention per server per week.
• After organic cards exist, you may ask those people (playbook Day 24 DM) if they want to hunt PH. Not strangers.

What NOT to do

• Broadcast bots. Invite trees. “Announcements” webhooks into other people’s servers.
• DM journalists with a “scoop” about a PNG generator.
• DM Anthropic/Cursor staff for a retweet.
• Paste anyone’s invoice from a private channel into a public one.

10. Newsletters

Why it might work

A one-line mention in a tiny “week in Cursor / Claude Code” digest sits next to the exact horror stories we are illustrating. Console.dev-class tool roundups (senior, small) beat TLDR-scale spray. The playbook’s DM 4 and DM 5 are written for one editor, not a media kit. Readers who click a digest link are warmer than PH tourists.

Failure mode

Buying TLDR / Bytes / Techpresso at $1.7k–$3.5k+ per issue for a free PNG with no account. That is not our motion; media is $0 until the operator says otherwise. A “launch” pitch to a 1.6M-sub daily that treats Loopcard as an AI platform. Fake exclusives. Spray 80 “hey editor” emails. Measuring success as “we were in TLDR” instead of cards.

Big newsletters will also unfurl cryptobook.space and bounce.

Exact first post

Not a post — two DMs (playbook §6, DMs 4–5):

• Tiny AI/dev newsletter: “not a launch. Static page. We killed MCP gateways. Ugly leftover domain. If it is too small for the list, it is too small.”
• Tiny Cursor digest: “for the next ‘someone’s agent did what to the bill’ roundup. Cursor’s spend limit remains the brake. One line is plenty.”

Attach the PNG or nothing. No deck. No “synergy.”

Optional later, still $0: a free editorial submit to Console.dev-style tools lists if they take submissions by email. One paragraph, same honesty.

Do not start a Virtus Loopcard newsletter until we have people who asked for history. We have no list (channel-plan: Email = none).

Expected honest reach

Cadence

• Week 2: the two (or at most four) editor DMs.
• After that: only if an editor replies.
• No weekly “Loopcard roundup” email.

What NOT to do

• Pay for sponsorships on a $0-media product.
• “Huge fan of the newsletter.”
• Claim exclusivity on a public $6k story.
• Buy a scraped “AI influencers” list.

11. SEO

Why it might work

The PNG needs a real / that explains itself when someone searches the brand or pastes the URL. Docs for “how to export Anthropic / Cursor CSV” are honest utility. llms.txt already exists so crawlers do not invent an MCP gateway. A later clean domain can rank for agent bill card / claude code overnight cost without the CryptoBook collision.

SEO is a support file, not a traffic forecast (marketing/seo-pages.md).

Failure mode

Forecasting sessions. Keyword-stuffing “best MCP gateway 2026.” Comparison posts vs Permit.io / Langfuse. Citing residual cryptobook.space hits (~65 unique IPs / week, mostly old social APIs) as traction. Indexing leftover CryptoBook social URLs. Fake aggregateRating. Buying “MCP security” or “Claude Code” ads. Treating SEO as the growth unit — it is not.

On this host, SEO also inherits the domain tax (§13): ranking a developer tool under CryptoBook is how you acquire the wrong click.

Exact first post

There is no “first post.” Ship and keep honest:

• H1 on / is Loopcard’s job, not CryptoBook.
• Titles/meta from seo-pages.md. Primary keywords only: agent bill card, claude code overnight cost.
• FAQ JSON-LD only for questions visible on the page. No “how much can I save?”
• robots.txt allow /, disallow /api/. noindex on /app /login if they appear.
• Canonical = preview host until the new domain’s A record is 173.249.19.205, then swap every canonical and llms.txt in one deploy.
• Do not sitemap routes that 404.

Expected honest reach

Near zero organic for month 1–3, especially on cryptobook.space. A handful of branded searches after X/Reddit. Residual social-API traffic is not Loopcard traffic; do not report it.

If the new domain is live and /docs answers export questions, informational long-tail can trickle. Still not the growth unit.

Cadence

• On every deploy: titles, canonical, og.png, llms.txt still true.
• New pages only when the product has the surface (/docs, /pricing already specified).
• No “10 blog posts in 30 days.” If a contractor drafts “MCP gateway vs Loopcard,” delete it.

What NOT to do

• Target the kill-list keywords (MCP gateway, quantum, AI Act, SOC 2, Cursor alternative, CryptoBook social, “stop runaway agents”).
• Invent rankings or “X searches/month.”
• Guest-post spam, Medium scrapes, LinkedIn article dumps of the same SEO page.

12. Directories

(There’s An AI For That, Futurepedia, Toolify, AlternativeTo, SaaSHub, LaunchRepo, BetaList, Uneed, Indie Need, DevHunt, “100+ directories in 1 click” services.)

Why it might work

Later. A listing on AlternativeTo or a hand-reviewed indie board can send a trickle and a backlink after the product has a name people search. Console.dev-like editorial directories overlap with §10. PH itself is a directory with a 24-hour fire; we already gated that.

Failure mode

LaunchRepo-style directory spam is on the community kill list until something retains. Submit-to-400-sites services paint cryptobook.space as an AI-directory ghost, often with scraped wrong categories (“crypto,” “MCP,” “compliance”). You cannot un-submit. Duplicate titles trip spam filters and can taint the new domain after a move. Paid “guaranteed listing” packs are how you buy 400 404s.

Channel-plan: no directory-spam until the product retains users. Loopcard retains if people come back for a second card or keep posting PNGs. One demo click is not retention.

Exact first post

Month 1: none. After the PH gate or after ~10 organic cards, whichever is later, submit by hand to at most:

1. AlternativeTo — category: screenshot / developer tools, not crypto.
2. One indie board that a human reviews (Uneed / Indie Need class), if the form allows an honest “not a gateway” line.
3. Nothing that auto-syndicates to 50 clones.

Description: the PH tagline + browser-only + leftover domain if still true. Screenshot: the labeled $6k card.

Expected honest reach

Hand-reviewed listing: 0–50 visits over a month, mostly curiosity. Mass-submit pack: inflated “listed on 200 directories” graphic, ~0 qualified visits, SEO sludge.

Cadence

• Month 1: 0.
• After retention: 1–2 hand submissions / month, not 200 in a weekend.
• Never a second PH. Never “Launching Next” countdown for a live free tool.

What NOT to do

• LaunchRepo, “submit to 500 AI directories,” paid upvote directories.
• Category: Crypto, Web3, MCP, Compliance, Observability.
• Fake ratings.
• Putting directory badges on / (“as seen on Product Hunt”) if we skipped PH or finished with 12 upvotes.

13. Domain tax of cryptobook.space

Finance challenge (18 Sep 2026): a developer tool advertised from a brand named CryptoBook takes a 30–50% conversion haircut versus a product-named host. Residual traffic on this host is ~65 unique IPs / week, ~1,500 nginx hits, mostly old social APIs — a conversion tax, not a PLG channel. Do not cite those hits in public.

How the tax shows up, channel by channel:

Mitigations until DNS moves (do these; they do not remove the tax):

• Product name Loopcard in H1, tweets, PH, HN title. Never “CryptoBook 2.0.”
• Leftover-domain sentence in every first post on HN/Reddit/PH/LinkedIn.
• OG image is the bill card, not a crypto-social card.
• Do not run ads into this hostname.
• Do not boast residual IPs.

The tax is why the operator buys loopcard.ai / loopcard.app / getloopcard.com (then overnight.card if those are gone). Preview may stay on cryptobook.space until the new name’s A record is 173.249.19.205. loopcard.cryptobook.space has no own DNS — do not advertise it.

14. How a new domain changes GTM

When loopcard.ai (or .app / getloopcard.com) points at this VPS:

What you do the same day

• Swap {{URL}} in the calendar, playbook, social kit, PH draft, HN draft.
• Canonical, og:url, sitemap, llms.txt, JSON-LD url — one deploy.
• 301 the preview host to the new host for / and docs. Do not 301 leftover social API paths as if they were product routes.
• H1 stays Loopcard. Still do not put CryptoBook in the H1.
• Certificates / nginx already planned around the new name; do not cut other Virtus sites to do this.

What actually changes in the channels

What a new domain does not change

• PH gate (organic screenshots).
• One Show HN.
• $0 media.
• Claims we will not make.
• The fact that ccusage remains better accounting.
• Median HN physics and PH upvote ≠ user physics.

Do not delay posting until the perfect domain. The calendar is written for the preview URL on purpose. Sitting dark for three weeks waiting on loopcard.ai is how you miss the $6k story’s half-life. Post now; swap the hostname when DNS is real.

15. What to count (and what to ignore)

Count

• Public Loopcard PNGs not posted by us (docs/marketing/organic-cards/).
• Parser bug reports with real headers.
• Demo button → download, if we ever log it without storing files.
• Honest “no” from ccusage maintainers (that is a positioning win).

Do not count as demand

• PH upvotes, HN points, TikTok views, directory “featured” badges.
• Residual cryptobook.space IPs.
• Our own quote-tweets.
• Contractor accounts.
• Waitlist emails (we do not have a waitlist; do not add one).

Month-1 success, honest: a few stranger cards, a parser fix, no fake claims in the archive, PH still unpublished unless the folder is real.
Month-1 failure: a PH graveyard, a hellbanned HN account, three removed Reddit posts, and a thread where we argued with “just use ccusage.”

16. Cross-channel kill list

Do not, on any channel:

• Fake testimonials, invented screenshots, “trusted by,” user counts, ARR
• SOC 2 / ISO / NIST / AI Act
• “We stop the runaway” / kill the loop / cap spend
• MCP gateway, observability, quantum, CryptoBook social, “OS for agents”
• Other people’s private invoices
• API-key fields, scraping dashboards (CFAA)
• Token ticker, airdrop, WAGMI
• Paid PH hunters, vote rings, directory-spam packs
• A second Show HN
• Ads, until the operator explicitly turns media on

If a contractor pastes those in, delete the post.

17. Operator one-pager

1. Attach the card or do not post.
2. X first, r/ClaudeAI second, LinkedIn third.
3. One Show HN, not the PH day.
4. PH only after organic screenshots. Upvotes will lie.
5. r/ChatGPT is optional megathread or skip. r/LocalLLaMA is once and honest.
6. No directories, no paid newsletters, no Discord launch spam.
7. SEO is hygiene. Social is growth.
8. cryptobook.space costs you 30–50% until DNS moves. Say so. Then move.
9. Free until /pricing says otherwise.
10. The metric is a PNG on someone else’s timeline.