Twelve openers, one story. The merge graph as the new pitch deck.

The twelve variants.

Each card carries the opener pattern, the example opener (copy-paste ready for our team), the story angle, the offer phrasing, the format constraint, the timing window, and the platform-specific rule we never break.

1. 𝕏

   01 · Twitter / X

   Cold audiencehandle @sipiteno

   Audience signal

   Developer-investors scrolling fast. Reward: one screenshot, one numeric claim, one branded URL.

   Opener pattern

   One-line counter-intuitive observation. No preamble, no thread tease.

   Example opener

   GitHub is now a deal-flow surface.

   Story angle

   Single-frame insight, the merge graph as the new pitch deck. Optional follow-up tweet with one chart, never a 12-tweet thread.

   Offer phrasing

   One branded URL on its own line. No 'click here', no 'read more'. The link is the CTA.

   Format constraint

   ≤169 raw / ≤162 weighted chars. Hook-first. Hard ceiling 280 for non-Premium accounts.

   Timing window

   Tue / Wed / Thu, 13:00-16:00 UTC. Avoid Friday 19:00+ UTC dead-zone.

   The rule we never break

   Never thread without a payoff hook in tweet 1. Never link to /pricing, link to /watch or /firstlook.

2. 🔻

   02 · Reddit

   Cold audiencehandle u/gitdealflow

   Audience signal

   Skeptical engineers and builders. Auto-mod traps for promotional posts. Comment threads alive on data + methodology, dead on pitch.

   Opener pattern

   Vulnerable-builder frame. 'I built this for myself, here's what I found.' Lead with the discovery, not the product.

   Example opener

   I spent six months reading commit logs of 350+ startups. Here's what I learned.

   Story angle

   Numbered findings, methodology disclosed inline, ask-for-help at the close. Subreddit-match the framing, r/startups gets the build-in-public version, r/AngelInvesting gets the deal-side version.

   Offer phrasing

   One link at the end, never above the fold. Phrase: 'Methodology + dataset linked in my profile if anyone wants to replicate.'

   Format constraint

   300-700 words. Plain text, no formatting tricks. Self-post only, never a link-post.

   Timing window

   Tue / Wed mornings 13:00-15:00 UTC. Avoid Sunday (low engagement) and Monday morning (HN steals attention).

   The rule we never break

   Never lead with the product. Never paste the same copy across subs, auto-mod cross-flag triggers shadowban.

3. 🟧

   03 · Hacker News

   Cold audiencehandle thedatanerd

   Audience signal

   Technical, hostile to marketing language, loves data tables and replicable methodology. The 'numbers and the methodology, please' crowd.

   Opener pattern

   Show HN: [methodology + n=, not pitch]. Title is the entire hook, first 80 chars decide top 30 placement.

   Example opener

   Show HN: Predicting Series A rounds with GitHub commit velocity (n=219, 68% hit rate)

   Story angle

   Methodology paper first, dataset second, product link last. The first comment from author must be the falsifiability statement: 'False-positive rate, lead-time IQR, and the specific signal that fails.'

   Offer phrasing

   Link to the SSRN paper or the public dataset, NOT to /pricing. Pricing surfaces only if a commenter asks.

   Format constraint

   Title ≤80 chars. First-author-comment 200-400 words, methodology-dense. Code repo link required for credibility.

   Timing window

   Tue / Wed 09:00-11:00 UTC. Sunday 14:00 UTC for Show HN, second-best window for European engineers.

   The rule we never break

   Never use marketing language ('revolutionize', 'game-changer', 'unlock'). Never reply defensively to nitpicks, concede and ship the fix.

4. 👨‍💻

   04 · dev.to

   Warm audiencehandle @gitdealflow

   Audience signal

   Engineers reading long-form on commute or coffee break. Reward: tutorial-shaped content with copy-paste code.

   Opener pattern

   Tutorial framing. 'How I built X' or 'How to compute Y in N lines of Python.'

   Example opener

   How I compute Series A predictions in twelve lines of Python

   Story angle

   Show the code, share the method, end with a working notebook. Be useful first, brand second. The dataset link is the natural payoff, not the pitch.

   Offer phrasing

   Project link in the author bio + one inline 'full dataset here' mid-post. No CTA-block at the end.

   Format constraint

   1,200-2,000 words. Code blocks every 200 words. Cover image required for thumbnail performance.

   Timing window

   Bi-weekly Tuesday 09:00 UTC. dev.to feed favors Tue / Thu publish times.

   The rule we never break

   Tutorial-first, brand-second. Never gate the tutorial behind email, defeats the syndication mechanic.

5. 📘

   05 · Hashnode

   Warm audiencehandle @gitdealflow

   Audience signal

   Engineers reading long-form on a personal-blog-feed format. Even more depth-tolerant than dev.to.

   Opener pattern

   Deep technical essay with a methodology-first title. Hashnode rewards depth + reproducibility.

   Example opener

   Building a GitHub commit-velocity index: dataset, method, and the regression that ties them together

   Story angle

   Long-form methodology essay with the full code, the panel construction, the false-positive analysis. The reader leaves with a runnable notebook.

   Offer phrasing

   Repository link + paper link inline. Author bio carries the product link. No mid-post CTAs.

   Format constraint

   1,500-3,000 words. Tables, charts (PNG), code blocks. Technical depth > prose.

   Timing window

   Bi-weekly Wednesday 10:00 UTC. Pair with dev.to publish to multiply reach via canonical-tag mirror.

   The rule we never break

   Code-blocks > prose. Show the work. Never repeat the dev.to essay verbatim, Hashnode crowd notices the cross-post and disengages.

6. 💬

   06 · Discord

   Warm audiencehandle gitdealflow

   Audience signal

   Peer-level community members. MCP, Cursor, Anthropic, Claude ecosystems. Promotional links auto-flagged in 70% of channels.

   Opener pattern

   Quiet drop, casual tone, peer-to-peer. 'Built this, sharing in case useful.'

   Example opener

   Built an MCP server that surfaces GitHub commit-velocity for any org or repo. Six tools, free forever. Drop a 👀 if useful, link in next msg.

   Story angle

   Already-built artifact. Low pressure. The artifact does the talking, the comment is just the introduction.

   Offer phrasing

   Two-message drop: message 1 is the artifact mention, message 2 is the link (only if a 👀 reaction lands).

   Format constraint

   One short paragraph in message 1. Link only after engagement signal. Read #rules first, most channels ban product links outright.

   Timing window

   When relevant to live conversation. Never cold-drop into #general unless explicitly allowed.

   The rule we never break

   Never spam DMs. Never link in first message in a strict channel. Read pinned messages before posting.

7. 💼

   07 · LinkedIn

   Cold audiencehandle GitDealFlow Company

   Audience signal

   Fund GPs, family-office heads, professional posture. Algorithm penalizes outbound links in body, rewards comment-link mechanic.

   Opener pattern

   Industry-trend observation in line 1, your data point in line 2, the contrarian payoff in line 3 (above the 'see more' fold).

   Example opener

   85% of seed deals still source through warm intros. We found a public-data signal that arrives 21-47 days earlier. Methodology, not magic, n=219, 68% hit rate.

   Story angle

   Authority frame. Methodology disclosed. Professional but human. Close with a question that invites debate.

   Offer phrasing

   Comment-link mechanic: 'Comment "methodology" and I'll DM the SSRN paper.' Never a link in body, algorithm punishes it.

   Format constraint

   200-1,200 words. First three lines must hook above the 'see more' fold. Single emoji acceptable; multi-emoji reads as spam.

   Timing window

   Tue / Wed / Thu 08:00-10:00 UTC. Avoid Friday afternoon and Monday morning.

   The rule we never break

   Never link in body. Never @-tag GPs without permission. Never copy-paste from Twitter, LinkedIn audience reads slowly and resents brevity.

8. 📧

   08 · Email (cold outreach)

   Cold audiencehandle signals@gitdealflow.com

   Audience signal

   Specific named partner at a specific named fund. Inbox triage means the first six words decide whether the email gets read.

   Opener pattern

   Specific reference to their portfolio + your data point in line 1. No 'Hope this finds you well', first six words must be substantive.

   Example opener

   Saw [Fund] led [Company]'s Series A, our signal flagged the run-up 33 days before the announcement.

   Story angle

   One-to-one specificity. Retro-validate one of their decisions with our dataset. The retro is the proof.

   Offer phrasing

   Single ask. Either a 15-min call OR a one-page data sample for their next deal, never both. One CTA per email.

   Format constraint

   ≤100 words. Plain text. One link. Signature includes SSRN DOI as the credibility anchor.

   Timing window

   Tue-Thu 09:00-11:00 partner-local time (Mon and Fri have 30% lower open rates).

   The rule we never break

   Never start with 'Hope this finds you well.' Never CC. Never attach. Pace ≤2 sends/day per Mailreach warm-up rule.

9. 🪜

   09 · AngelList

   Warm audiencehandle gitdealflow

   Audience signal

   Syndicate leads, angels, scout programs. Feed reads as deal-side noise unless you're already a syndicate participant.

   Opener pattern

   Peer-level question framing. Never a pitch. 'Question for syndicate leads:' is the highest-engagement opener.

   Example opener

   Question for syndicate leads: do you incorporate engineering-acceleration signals in pre-seed diligence?

   Story angle

   Partner-side ask. Position as a peer, not a vendor. The product mention surfaces only after someone DMs.

   Offer phrasing

   DM-side, never feed-side. Reply to comments with: 'Happy to share the methodology, DM me?'

   Format constraint

   1-2 sentences. Question framing. No links in feed posts.

   Timing window

   Wednesday 14:00 UTC, peak syndicate-activity window.

   The rule we never break

   Never spam syndicate feed with product. Never tag fund accounts. Treat as a peer-to-peer Discord, not a launchpad.

10. 🚀

    10 · Product Hunt

    Cold audiencehandle gitdealflow

    Audience signal

    Maker community. Launch-day buzz. Comment threads decide ranking, first three hours are 70% of the upvote yield.

    Opener pattern

    Maker-comment thread, vulnerable framing. 'Six months heads-down. The thing I wish existed in my angel days.'

    Example opener

    Launched today after six months heads-down. The thing I wish existed in my angel days, I read commit logs for fun, and there was no tool that let me trade on what I saw.

    Story angle

    Maker journey. Build-in-public. The story explains why the product exists; upvotes follow naturally.

    Offer phrasing

    Top of listing carries the prominent CTA. First-author-comment carries the story. CTA is implicit, just being on PH is the offer.

    Format constraint

    First-comment 500-800 words. Reply to every comment within the first 60 minutes. Founder-replies show as 'M' badge.

    Timing window

    Launch on Tuesday 00:01 PT, best US launch window. Pacific Time. The 24-hour cycle resets at midnight PT.

    The rule we never break

    Never beg for upvotes off-platform. Never DM hunters. Reply to every comment within 1h on launch day or fall off the leaderboard.

11. 🛠️

    11 · Indie Hackers

    Warm audiencehandle @gitdealflow

    Audience signal

    Bootstrapped builders, MRR-curious, replication-minded. They want to see the dollar-figures, the funnel-math, and the screenshot.

    Opener pattern

    Milestone post. Lead with the number, not the product. '€1,000 MRR by selling X to Y' format.

    Example opener

    We hit €1,000 MRR by selling commit-graph data to angels. Here's the breakdown.

    Story angle

    Transparent metrics. Funnel math. Replicable playbook. The reader leaves with a number they could hit themselves.

    Offer phrasing

    Discussed but not pushed. Link in the by-line + one inline 'full breakdown on the dashboard' if relevant.

    Format constraint

    300-700 words. Screenshots welcomed. Numbers required, 'we made some MRR' reads as evasive.

    Timing window

    Mon / Wed 12:00 UTC, IH-feed peaks early-week.

    The rule we never break

    Lead with a number, never with the product. Never round to make the figure prettier, IH crowd notices.

12. ✈️

    12 · Telegram

    Owned channelhandle t.me/gitdealflow

    Audience signal

    Owned channel. Subscribers opted in. They want the unfiltered, member-only version, no public spin.

    Opener pattern

    Insider drop, no-frills. 'Sector Sweep: 5 names crossed signal threshold this week.'

    Example opener

    Sector Sweep update: 5 names crossed signal threshold this week. Three are in AI-devtools, two in verifiable compute. Names + charts inside.

    Story angle

    Member-exclusive. Immediate signal. The Telegram channel gets the version that's two days ahead of public.

    Offer phrasing

    Inline links allowed. Brief CTA: '/firstlook for the full chart pack.' Never gates the names, Telegram subscribers paid attention to be inside the loop.

    Format constraint

    ≤300 words. Signal-first. One pinned message per week, no firehose.

    Timing window

    Sunday 18:00 UTC, pre-Monday signal drop. Mid-week digest only when something material breaks.

    The rule we never break

    Never repeat what's on Twitter, Telegram subscribers expect 2-day lead-time. Never gate names, subscribers earned the access.