Loopcard — adoption (deep)
Date of record: 18 September 2026
Product: Loopcard (shareable coding-agent bill card). Preview: https://cryptobook.space
Audience: operator / PM. Not a customer brochure.
Method: this-week pain, 60-second path, why a stranger posts, ritual vs one-shot, required product changes, honest cold start, AARRR with empty numbers labeled as hypotheses.
Comparables opened this pass: Receiptify, Spotify Wrapped, WrapShare, cc-wrapped / code-wrapped / ampcode-wrapped, github-readme-stats (~80k stars), PnL Studio / PNLGEN / exchange PnL cards, ccusage (--compact for screenshots), SuperPenguin ($30 Growth).
Nothing below is a measured Loopcard funnel. As of this date the product is live as a preview; we have no Loopcard-native unique visitors, PNG downloads, publishes, or paid accounts. Residual cryptobook.space traffic is leftover social, not this SKU.
Verdict (one screen)
Loopcard can be adopted this week by four people who already have a number on their machine or on the timeline. It will not be adopted by leftover CryptoBook users, by TokensMarketCap chart-watchers as a default audience, or by anyone whose job is “see the number in a terminal.”
The growth unit is a PNG that is prettier than a dashboard crop and cheaper to post than a CSV. That is the same job Receiptify did to Spotify’s native recap, and the same job PnL cards did to exchange screenshots. It is not the job ccusage, cctally, SuperPenguin, or the Anthropic console already own.
Adoption dies in three places, in order:
- The card is not worth posting. One black/pink square, no URL on the PNG, no “shame / flex / warning / week” templates. Power users already screenshot
ccusage --compact. - The ritual does not exist. Overnight disasters are one-shot. Without a Friday bill card, there is no reason to come back, and $19 Pro is a watermark tax on a toy.
- The graph we have is the wrong graph. ~65 unique IPs/week on old social APIs is conversion tax. The graph that can seed this is the operator’s X/LinkedIn plus a handful of people who already posted agent bills — not Virtus/TMC as a captive Cursor audience.
Ship the watermark URL, four templates, before/after, and a Friday cadence before treating Pro as a plan. Treat paid conversion as upside. Treat “a stranger posted the pink mugshot” as the only launch KPI.
1. Who feels the pain THIS WEEK
Not “teams running agents in production.” Four named seats. Only the first and the fourth generate a card without being asked.
1.1 IC engineer (generator)
This week: they hit a Max cap mid-session, woke up to an Anthropic usage email, or opened the console after an overnight loop. The $6,000 overnight (Reddit → MakeUseOf, May 2026) is the genre; the $80 overnight on dev.to is the common case. A 35-day personal log (aakashx, Apr 2026) had three sessions = 42% of spend. The pain is not “I lack observability.” The pain is “I have a number that looks insane and I need to show it to someone without forwarding a CSV.”
They already have: Anthropic Usage page, Cursor spend limit, npx ccusage@latest, maybe Pacer / Burn / Lupen on the Mac menu bar. They do not have a square they can drop into Slack or X that reads as a story.
Job this week: make the tab visible.
Will they pay $19? Unlikely. They already run free local CLIs. They will use Loopcard once, if the PNG is better than a terminal crop.
1.2 Team lead (generator, sometimes)
This week: Monday Anthropic console. Cade Partners (Apr 2026) opened a portfolio console 22 days into the month at ~$4,000 with the cap set to Unlimited. Upbound priced 20 engineers’ June Claude Code at list and got a median ~7× a $125 seat, heaviest $6,470. Uber’s public story (entire 2026 AI budget in four months; power users $500–$2,000/mo) is the slide they already forwarded internally.
They do not want Langfuse. They want a warning object they can paste into Slack: “this is last week; stop leaving Opus loops on.” The card is a management act, not a dashboard.
Job this week: make the team feel the number.
Will they pay $49 Studio? Only if Friday’s card is automatic and named. A one-off PNG is a screenshot they can already take.
1.3 Finance / operator who pays the invoice (receiver)
This week: the Anthropic or Cursor invoice landed, or a founder asked “what is this $4k line.” They do not have ~/.claude on their laptop. They cannot drop a CSV they do not have. They receive a card; they do not generate one.
This is one-sided sharing, not a two-sided marketplace (the freelance-receipt kill in challenges/adoption.md). The IC generates; finance reads. If we require finance to log in, we re-kill the product.
Job this week: understand the line item in one image.
Will they pay? They already pay Anthropic/Cursor. A $19 Loopcard seat is a rounding error they will not self-serve unless the engineer puts the card in the thread first.
1.4 Twitter / LinkedIn performer (generator, highest share probability)
This week: they were going to post the number anyway. Live examples on X (opened this pass, not ours):
- @SalehOfTomorrow (15 Jan 2026): founder, six Claude Code terminals, $6k/mo credits, code thrown away — 6.5k likes, 369k views.
- @noisyb0y1 (6 Apr 2026): “$700/day instead of $50” skill-issue thread — 186k views.
- @_sslinNn (14 Sep 2026): “spent $4,179 on Claude Code in 6 days” — low engagement, same genre.
The genre is spend flex and spend shame. Crypto already productized it (PnL Studio: “Turn every trade into a flex”; Limitless, Arena, Cove, Definitive all shipped PnL share cards in 2025–2026). Coding-agent Twitter is running the same play with dashboard crops and ccusage tables. Loopcard is a prettier crop, or it is nothing.
Job this week: a post that looks like a card, not a settings page.
Will they pay? No. Watermark is the tax they will crop, or the attribution we need. They are distribution, not MRR.
Who does not feel this week
| Seat | Why not |
|---|---|
| Leftover CryptoBook social (~65 IPs/week) | They wanted the old feed. They do not have Claude Code. |
| TMC chart user | They flex token PnL, not agent tabs. Cultural rhyme, wrong job. See §6. |
| Security / GRC | They buy Permit.io / Okta / scanners. Slip already died here. |
| “Should have a cost policy” | New Year’s resolution. Not a Thursday-night click. |
2. Activation — the 60-second path and where it drops
2.1 Path as shipped (18 Sep 2026)
Homepage is the studio. No account. Hero card is already filled with the labeled $6,000 overnight re-creation.
| Second | Action | Felt result |
|---|---|---|
| 0 | Land / |
Big pink number. Demo is the aha for lurkers. |
| 5 | Hit $6,000 night / $1,263 month / $480 median |
Same card, different public story. |
| 10 | Download PNG | 1080×1080 canvas. Toast. |
| 15 | Copy caption | Clipboard text + origin URL. |
| 20 | Publish share URL | POST aggregates only → /c/:id. |
| 20–60 | Drop CSV/JSONL/ccusage JSON, or type manual USD | Card becomes their number. Stronger post. |
This passes the 60-second test in challenges/adoption.md for the lurker. A stranger who never exports anything still gets a card. That is the Receiptify / Wrapped trick: the demo is the product for people who came from a screenshot.
2.2 Drop-off A — no CSV
Most visitors will not have an Anthropic CSV, a Cursor export, or ccusage --json sitting on the desktop. Export is homework. Homework is not aha.
If they only download the demo, the post is “here is a site that restyles a news story.” Weak. The $6k card is bait; their number is the share.
Mitigations that do not violate CFAA (no scraping vendor accounts):
- Manual numbers stay first-class (already shipped). Copy: “Type the total from the email. That is enough.”
- CLI:
node cli/loopcard.json a path they already have. Do not walk huge~/.claudewithout a path. - Do not add “connect Anthropic OAuth.” That is a two-week integration and a key honeypot.
Hypothesis (not a fact): 70–85% of first sessions never drop a file. If manual + demo cannot produce a post they are proud of, activation is fake.
2.3 Drop-off B — ccusage is already enough
ccusage is the incumbent screenshot. GitHub discussion #26 is literally “Share your screenshot of ccusage!!!” The CLI has --compact “perfect for screenshots and sharing.” 18.6k stars. cctally exports anonymized Markdown/HTML/SVG. cc-wrapped, code-wrapped, ampcode-wrapped already emit Spotify-style PNGs from local agent logs.
If Loopcard’s PNG is a sparse dollar amount plus one caption line (current canvas in loopcard/public/js/app.js and lib/render_card.py), the power user will keep screenshotting the terminal. They already trust the ledger. We are not the ledger (docs/website/docs-page.md says this out loud).
We win only on beauty and share. Ugly card = they bounce to the tool they already ran.
2.4 Drop-off C — ugly card
Current PNG:
- Black field, pink radial, “LOOPCARD” header, source name, huge
$n, one loop sentence, kind + “virtus labs”. - HTML preview has a faint diagonal
.wm { opacity:.08 }. The downloaded PNG does not. - No product URL on the image. No “make yours.” No 9:16 story crop. No receipt / terminal / Slack-safe variants.
PnL Studio’s pitch is the mirror: 20+ themes, clipboard copy, square/story/banner, brand URL on the card, “no watermark, no sign-up.” Receiptify kept the receipt aesthetic plus branding at the bottom and got a years-long habit. github-readme-stats (~80k stars) made the image itself the distribution (hotlink SVG).
A card that looks like a slide footer will be cropped or not posted. Cropping us off is how we die.
2.5 Other activation leaks (smaller, still real)
- Preview still lives on cryptobook.space. Domain tax. A Cursor user who clicks a crypto-social URL distrusts the drop zone even though the file never leaves the browser.
- “Publish share URL” is a network call. Some users will download PNG and never publish. That is fine if the PNG carries the URL.
- PWA install is optional. Do not make install the aha.
3. Why share — four motives, one PNG
People do not share dashboards. They share identity objects. Wrapped research and spend-flex products converge on the same four motives. Loopcard has to pick a tone per template, not one sarcastic caption for everyone.
3.1 Shame (confession)
Overnight loop. “I left it running.” Washington Post / Cosmopolitan / UnHerd on Wrapped: people post because it is embarrassing; the post is a controlled confession. Agent-bill Twitter already does this (“half-working feature and a statusline nobody asked for”).
Shame cards travel in Reddit and group chats. They need a mugshot look (the product spec already says “pink mugshot of the loop”), a labeled “overnight,” and no humble-brag chrome.
3.2 Status (flex)
$6k/mo, six terminals, Max 20×, “top 0.1% of Opus.” Contrast.io on Wrapped: narcissism + FOMO + humble-brag cover. Crypto PnL cards exist because winning is content; Limitless bribed posts with points. Coding-agent flex is the same screenshot with a different ticker.
Flex cards need clean, large type, optional percentile / streak / sessions, and a way to hide dollar size (Cove’s “Only % gain”). Some ICs will not post $6,000 on a public timeline but will post “47 overnight loops this month.”
3.3 Warning the team (instrument)
Not a tweet. A Slack/email PNG: “this is what the loop cost; here is the cap.” Team lead and finance. Shame without the pile-on. No viral soundtrack required. This is the only motive that can become a weekly ritual (§4).
The share target is a channel, not the algorithm. Product implication: one-click “copy for Slack” (image + one sentence, no hashtags, no “make yours” joke).
3.4 Meme (genre participation)
The $6,000 overnight is already a format, the way “I left AWS on” was a format. Posting the pink card is joining the joke. Wrapefy (fake Spotify Wrapped) shows the floor: people will fake the numbers for the meme. Loopcard already allows manual amounts — label them, or the timeline will.
Meme cards need recognizable chrome (Virtus pink, the word LOOPCARD) so a crop still reads as the object. That is brand, not decoration.
Motive × seat
| Motive | IC | Lead | Finance | Performer |
|---|---|---|---|---|
| Shame | High (after overnight) | Medium | Low | High |
| Status | Medium | Low (looks reckless) | None | Highest |
| Warning | Medium (Slack the manager) | Highest | Receiver | Low |
| Meme | Medium | Low | None | High |
Do not write one caption for all four. “Make yours” is for meme/status. “Send to the person who pays” is for warning. Mixing them makes every post feel like an ad.
4. Retention — one-shot vs Friday bill card
4.1 The one-shot trap
Viral screenshot tools split hard:
| Tool | Cadence | Why they come back |
|---|---|---|
| Spotify Wrapped | Annual event | Identity ritual + FOMO week |
| Receiptify / WrapShare | On demand, monthly default | “Don’t wait a year”; Instagram-ready anytime |
| GitHub Wrapped clones | Annual | Same as Spotify, developer-flavored |
| github-readme-stats | Continuous | Live SVG in a README; no re-visit needed |
| Exchange / PnL Studio cards | Per winning trade | Flex is frequent |
| cc-wrapped / code-wrapped | Annual | Year in agents |
| Loopcard as shipped | Per disaster | Overnight is rare |
A runaway overnight is acute and infrequent. If that is the only job, Loopcard is a one-shot generator. One-shot generators do not convert to $19/mo. Product spec already says this: “One-shot viral tools often do not convert to $19/mo. Treat Pro as upside; treat Virtus Labs awareness as the floor.”
ccusage retains because it is a daily ledger in the terminal they already open. SuperPenguin retains because it is a Mac/team spend map billed on managed AI spend. We are neither. We cannot out-ledger them.
4.2 The weekly ritual that can exist
The team-lead warning motive has a calendar: Friday bill card.
Agencies already have a Friday reporting pack (killed as our SKU in the market study, but the habit is real). Engineering orgs already look at Anthropic/Cursor on Monday. A Loopcard that is “the week in agents” — one PNG, this week vs last week, drop this week’s export — is a ritual with a reason to return.
Without that ritual:
- D1 retention hypothesis: 5–15% (people who posted and want a cleaner crop).
- D7 / D30: near zero except performers making a new flex.
With a Friday ritual (email/PWA reminder is optional; the template is the product):
- Lead generates week card → Slack → maybe one engineer drops their own export to compare.
- That is Studio’s only honest WTP story ($49 later). Not “90-day history” as a feature list.
4.3 What we will not pretend
- We will not send weekly emails until someone has published or downloaded at least once and opted in. No ghost list from CryptoBook social.
- We will not build a dashboard so they “have a reason to log in.” Logins kill the 60s path. Retention is make the next card, not open a workspace.
- Annual “Agent Wrapped” is a December campaign, not v1 retention. cc-wrapped already took the year-in-review slot for free.
5. Required product changes for adoption
These are adoption blockers, not a backlog of nice-to-haves. Order is the order they unblock share.
5.1 Watermark / URL on the PNG (do this first)
Bug: preview CSS shows a faint LOOPCARD mark; canvas PNG and PIL /c/:id.png do not. Neither writes the origin URL.
Every comparable that lives on screenshots puts the name on the image:
- Receiptify: branding on the receipt (guides treat it as expected, not optional).
- PnL Studio:
pnlstudio.funon the sample card; “no watermark” means no ugly FREE overlay, not no attribution. - github-readme-stats: the hotlinked URL is the product.
Ship:
- Free PNG: corner or baseline
loopcard.ai(orcryptobook.spaceuntil DNS) + “make yours” in a crop-resistant place. Readable at 50% Twitter compression. - Demo cards: extra line “Re-creation of published reporting.”
- Manual cards: “Typed, not an invoice.”
- Pro ($19 later): may remove diagonal FREE noise; keep the URL. Selling “unwatermarked” as “no Loopcard on it” trains people to crop us. Sell history + team + extra templates, not invisibility.
Hypothesis: a PNG without a URL has referral = 0 even if it is posted, because the viewer cannot follow an image.
5.2 Templates (four motives, four layouts)
One chrome cannot be shame and flex. Minimum set:
| Template | Motive | Aspect | Notes |
|---|---|---|---|
| Mugshot | Shame | 1:1 | Current look, bigger type, red/pink “overnight” chip |
| Receipt | Meme / status | 9:16 or tall 1:1 | Receiptify lesson: itemized sessions as line items, fake order # optional, honest totals |
| Slack week | Warning | 16:9 or 1:1 | Quiet, this-week total, top session, “not a cap.” Copy-for-Slack caption |
| Flex | Status | 1:1 | Sessions, streak, model mix if present in the file. Hide-dollars toggle |
Do not ship 20 crypto themes. Four is enough to A/B which motive actually posts. PnL Studio’s 20+ is a mature flex market; we do not have that yet.
5.3 Before / after
The team-lead post is not “$4,000.” It is “$4,000 → $1,100 after we killed the 30-minute loop.” Wrapped has year-over-year; we need week-over-week on one card.
v1 shape: two amounts + two captions, still parsed in-browser (this week’s export + last week’s, or two manual fields). No account required. This is the only object finance will forward without feeling marketed to.
5.4 Team (Studio, later — do not block launch)
$49 Studio is not a gateway and not Langfuse seats. It is:
- Named week card for a group (aggregates only).
- Shared folder of published cards the way a team shares a Google Drive screenshot.
- Optional Friday reminder to the person who already published.
Do not build SSO, seat admin, or “cost per PR” (SuperPenguin Pro already sells that on Mac). Do not require every engineer to install something. The lead drops one CSV of the week (Anthropic org export or concatenated ccusage JSON). If they cannot get that file, Studio is not a product yet.
5.5 Explicitly not required for adoption
Vendor OAuth, MCP, Electron, App Store, Stripe (until /pricing changes), trace storage, spend caps, “we stop the runaway.” Those are Slip gravity. They slow the 60s path and do not make a stranger hit post.
6. Cold start — the graph we have is the wrong graph
6.1 cryptobook.space residual: useless
nginx, seven days to 18 Sep 2026 (docs/02-market-study.md):
- ~1,503 hits
- ~65 unique IPs
- Paths:
/and/api/posts/...(old social)
This is not a Cursor audience. It is people and bots hitting a retired crypto-social API. Finance already treated it as conversion tax, not a PLG channel. Do not put Loopcard KPIs on this number. Do not email anyone from that graph. Do not retarget them.
Hypothesis: residual social → Loopcard PNG download conversion is ~0. If anything, the CryptoBook name lowers activation (drop-zone distrust).
6.2 Operator / Virtus / TMC — what is actually a graph
| Graph | What it is | Useful for Loopcard? |
|---|---|---|
| Operator personal X / LinkedIn | The only people who will see the first cards | Yes. This is the launch. Thread in marketing/social-launch-kit.md. |
| Virtus Labs (virtusblockchainlabs.com) | Company site, US-oriented brand, 18+ | Soft. LinkedIn company page can carry the same card. Not a developer feed. Awareness floor, not IC density. |
| TokensMarketCap | Live market-data audience on the same VPS | Wrong job, right screenshot culture. They already understand PnL flex cards. They do not have Claude JSONL. A TMC banner “make an agent bill card” is a non sequitur; a founder post that rhymes (“same square as a PnL card, for your Claude tab”) is allowed. Do not inject Loopcard into TMC product UI. |
| academy.tokensmarketcap.com | 404 at last inventory | A hole, not a channel. |
| CryptoBook LiveKit leftover | WebRTC on the same host | Irrelevant. |
| Email list | None (channel-plan.md) |
None. |
Strategic option C in docs/10-strategic-options.md was “use an audience you already have” and immediately warned: TMC is a place to look, not a product. That still holds. TMC users will not become Loopcard’s D1 because they saw a BTC dominance chart.
6.3 The graph we must borrow (not own)
Seed is people who already posted the genre, not people who already visited us.
- r/ClaudeAI, r/cursor, r/LocalLLaMA — the $6k post’s home.
- ccusage discussion #26 — they already want prettier screenshots.
- HN only after a real card exists (calendar Day 22 gate: organic screenshots or no PH).
- Performers who posted $k bills: ask to restyle their public number (labeled), not their invoice.
Cold start is 10 posted cards with a URL on them, not 10,000 impressions on cryptobook.space. If the operator cannot get a single non-demo card onto X in week 1, there is no PLG, only a landing page.
6.4 Domain
Buy loopcard.ai / loopcard.app / getloopcard.com before asking strangers to drop a file. Preview on cryptobook.space is acceptable for the operator’s own posts if the H1 is Loopcard (already true). It is not acceptable as the long-term share URL printed on the PNG.
7. AARRR — empty numbers, labeled hypotheses
Dave McClure’s funnel. Measured (18 Sep 2026): Loopcard-native = empty. cryptobook.space residual ≠ Loopcard.
Legend: FACT = logged or cited elsewhere in this pack. HYPOTHESIS = guess to be replaced by instrumentation. Do not quote HYPOTHESIS as traction.
7.1 Acquisition
| Metric | Status | Number |
|---|---|---|
| Unique IPs, cryptobook.space, 7d to 18 Sep 2026 | FACT (old social) | ~65 IPs, ~1,503 hits |
| Unique IPs that loaded Loopcard studio | FACT | not measured / treat as 0 until logs are split |
| Organic X/LinkedIn/Reddit visitors from Loopcard posts | HYPOTHESIS | 0 until Day 1 thread ships |
| Paid acquisition | FACT | $0 media, by policy |
HYPOTHESIS — week 1 if operator posts the $6k card daily: 200–800 landing sessions from X+LinkedIn, 50–200 from one Reddit thread if it is not removed. Wide band; PH-style vanity is forbidden.
HYPOTHESIS — week 1 if nobody posts: ≈ residual social, i.e. useless.
7.2 Activation
Definition: downloaded a PNG or copied a share URL (demo counts as weak activation; own/manual number is strong).
| Metric | Status | Number |
|---|---|---|
| PNG downloads | FACT | not instrumented |
/v1/cards publishes |
FACT | query Postgres loopcard when we care; do not invent |
| File drops vs demo vs manual | FACT | not instrumented |
HYPOTHESIS — activation rate on sessions that see the hero: 20–40% hit Download on the demo (low-friction, low-value). 5–12% produce a non-demo card (manual or file). <3% publish a share URL until the PNG itself carries the link.
HYPOTHESIS — drop-off mix among people who bounced: ~half “I don’t have a CSV and didn’t notice manual,” ~third “ccusage screenshot is fine,” ~rest “card looks unfinished / crypto domain.”
7.3 Retention
Definition: a second PNG in a later calendar week.
| Metric | Status | Number |
|---|---|---|
| D1 / D7 / D30 | FACT | empty |
| Friday-week cards generated | FACT | feature not shipped |
HYPOTHESIS — as shipped (disaster-only): D7 <5%, D30 <2%. Matches one-shot generators.
HYPOTHESIS — if Friday + before/after templates ship and we remind only opt-in publishers: D30 8–15% of people who made a non-demo card. Still not a SaaS retention curve. Good enough for awareness; not good enough to model 263 × $19.
7.4 Referral
Definition: a posted PNG that causes a new session with UTM or recognizable referrer, or a /c/:id hit from a third party.
| Metric | Status | Number |
|---|---|---|
| Public cards shared by non-operator | FACT | 0 known |
| K-factor | HYPOTHESIS | 0.0 until URL-on-PNG ships; 0.1–0.4 if shame/flex cards carry a followable URL and the card is actually pretty |
Wrapped’s k-factor is a once-a-year social epidemic. PnL cards compound because trades are frequent. Ours compounds only if (a) the image names us and (b) the motive is status/shame/meme, not a private Slack warning (warnings do not refer).
HYPOTHESIS: warning-the-team cards have referral ≈ 0 and retention > 0. Flex/shame cards have referral > 0 and retention ≈ 0. We need both templates; they feed different stages.
7.5 Revenue
| Metric | Status | Number |
|---|---|---|
| Charged customers | FACT | 0. /pricing says free; Stripe off |
| Pro $19 / Studio $49 | FACT | “later,” not billed |
HYPOTHESIS — do not use for planning: 2–3.5% free→paid if we paywall “unwatermarked PNG” while ccusage remains free (OSS-alternative rule from docs/04-financial-plan.md). That would be optimistic and probably wrong. Honest floor: 0% paid in 90 days, Virtus awareness only.
HYPOTHESIS — Studio WTP: only after a lead has posted or Slacked three Friday cards. Before that, $49 is a watermark on a toy. Same kill as ShieldMCP’s $49 PDF (5 PH upvotes).
To hit $5k MRR at $19 needs 263 paying accounts (docs/04-financial-plan.md). Residual 65 IPs/week cannot produce that. Referral from performer PNGs might; it is unproven. Do not put 263 in a slide as a forecast.
7.6 Instrumentation we still lack
Until these exist, every funnel review is fiction:
- Split nginx: Loopcard static +
/v1/+/c/vs leftover social, if social is still up. - Client events (no PII, no file bodies):
demo_click,png_download,caption_copy,publish_ok,file_ok/file_fail,manual_apply,template_id. - Count
/c/:id.pngfetches as the real referral proxy (hotlinked image). - Label every public number demo | manual | export.
Do not add accounts to get these events.
8. Comparables — what we are stealing (and not)
| Pattern | Lesson for Loopcard |
|---|---|
| Receiptify | Anytime > annual. Receipt look is the meme. Brand stays on the PNG. OAuth is their cost; we cannot copy it (CFAA / keys). Manual + local file is our OAuth. |
| Spotify Wrapped | Ritual + FOMO + identity. We do not get a December monopoly. Do not wait for “Agent Wrapped 2026.” |
| WrapShare | Weekly/monthly wraps + 9:16 stories. Our Slack-week + story crop. |
| PnL Studio / exchange PnL cards | Spend flex is a proven screenshot economy. Themes and clipboard matter. Fakeable numbers are a trust risk — label manual. |
| github-readme-stats | The image is the distribution channel. Hotlink /c/:id.png with a URL on the art. |
ccusage --compact |
Incumbent screenshot. If we are not prettier, we are a round-trip. |
| cc-wrapped / code-wrapped | Annual agent Wrapped already exists locally. Do not launch as “Wrapped for Claude.” Launch as the bill card this week. |
| SuperPenguin | Paid Mac/team attribution. Different job. Do not become their lighter dashboard. |
9. What would falsify this memo
Kill Loopcard as a growth bet (keep as a Virtus toy if you want) if any of these is true after a dated 30-day calendar (marketing/calendar-30-days.md):
- Zero non-operator public posts of a Loopcard PNG (including demo) by Day 21.
- File/manual cards remain <5% of downloads — everyone is restyling our $6k bait.
- ccusage screenshots in the same threads still out-engage Loopcard cards on looks.
- We added OAuth, a dashboard, or a paywall before a Friday ritual exists.
Adoption is a stranger hitting post. Everything else is a holding page with extra JavaScript.
Sources (opened or re-used 18 Sep 2026)
- Product:
docs/11-loopcard-product.md,loopcard/docs/PRODUCT.md,loopcard/docs/ARCHITECTURE.md, liveloopcard/public/index.html+js/app.js+lib/render_card.py - Challenges / pack:
challenges/adoption.md,docs/02-market-study.md,docs/04-financial-plan.md,docs/05-marketing-plan.md,docs/10-strategic-options.md,docs/marketing/social-launch-kit.md - Pain: MakeUseOf $6k overnight (22 May 2026); Cade Partners “engineers have a burn rate” (22 Apr 2026); Upbound subsidy multiple (23 Jul 2026); Business Insider Anthropic estimate change (29 Apr 2026); X posts cited in §1.4
- Screenshot economy: Receiptify guides; WrapShare; PnL Studio (pnlstudio.fun); PNLGEN; github-readme-stats (~80k stars, Quillly 18 Jun 2026); ccusage README
--compact+ discussion #26; SuperPenguin pricing (Growth $30) - Share psychology: Contrast.io Wrapped triggers; Harper’s Bazaar / Cosmopolitan / UnHerd / Washington Post Wrapped shame-and-status coverage
End of memo.