Loading...
Character bible (under the anonymity rule)
I'm The Data Nerd. I won't tell you my real name and that's on purpose — the methodology is the protagonist, I'm just the storyteller. Engineer for fifteen years, angel-checker since deal #5. The whole product rests on whether the signal is real, not on whether you find me charismatic.
Anonymous engineer-investor. Wrote the SSRN methodology paper. Refuses to do podcasts.
00 · Disclosure
Behind the handle is one real engineer-investor. The handle exists because the methodology has to stand on whether the signal is real, not on whether the person delivering it is charismatic. You will never see my face. You will never hear my real voice. You will never see my real name on this site.
What you will hear: a synthetic voice (Cartesia) reading every page narration, every YouTube short, every monthly founder talk. Same synthetic voice across every surface so the brand has rhythm even without a person. Synthetic voice (Cartesia). Same voice across YouTube, email-audio, and every page narration. There is no founder voice. The methodology is real. The voice is a writing convention.
What you will read: the same handle (“The Data Nerd”) signed at the bottom of every email, every page, every video script. Voice fragmentation breaks the character; one handle, every surface, forever. The methodology paper on SSRN uses my real name behind a Sipiteno Ltd. corporate veil; everything on this site uses the handle.
01 · Polarity
Four polarities. If you nod through all four, you’re my reader. If even one feels wrong, please save your money — this is the wrong product for you and that’s honest.
For: Public data is more valuable than private data.
Against: Edge from access.
Quant funds make billions on SEC filings. The filings are public. The model is not. The same is true of GitHub.
For: Code is more honest than copy.
Against: The deck is the company.
A pitch deck is a marketing artifact written for the next round. A merge graph is the company's actual behaviour, updated daily.
For: Anonymity is a credibility signal.
Against: Cult of personality.
If the signal needs a charismatic founder to land, the signal isn't strong enough. If we're right, the data carries the argument.
For: €9.97/mo is a feature, not a price ceiling.
Against: Six-figure data subscriptions for six-person funds.
We'd rather have a thousand readers who tell five friends than a hundred enterprise contracts. The founding price is locked forever.
02 · Six parables
Every core claim needs a parable that makes it feel obvious. These are the six I rotate through emails, videos, and the Sunday digest. Each one is a small story with a specific lesson.
Parable 1 · The Unknown Lighthouse Keeper
A lighthouse keeper notices a particular flock of seabirds arrive a week before every storm. He doesn't know why. He only knows that when the birds arrive, ships should already be in harbour. The fishermen who follow him stop losing boats. The ones who say 'birds aren't weather data' keep losing them.
Lesson: Engineering acceleration is the seabird flock. It doesn't prove the storm. It precedes it reliably enough that ignoring it is the expensive choice.
Parable 2 · The Loud Engine
Two cars start a race. One is silent at the line. The other idles loud, builds revs, the driver checks his mirrors, the passenger fastens her belt. The silent car may win — but the loud one is doing every observable thing a car about to launch does.
Lesson: Code is the engine of a startup. When the engine is visibly louder for two weeks running, the launch usually follows. We aren't reading the future. We're reading the things that always happen right before the future arrives.
Parable 3 · The Letter the Postman Already Read
Imagine the postman could read every letter in his bag. The richest man in town wouldn't pay him for tomorrow's letters — those aren't in the bag yet. He'd pay him for today's letters delivered three days early.
Lesson: GitHub already wrote the letters. Crunchbase reads them on the day they land. We open them in transit. Everyone else gets the same mail we do — they just get it the week after the founder posted on LinkedIn.
Parable 4 · The Sunday Email I Never Sent
The Sunday before the $4M Series A I should have been in, I drafted a three-line email to the founder. 'Saw your settlement-layer commits. The way you're handling the FX edge case is the kind of thing your competitors will copy in eighteen months.' I read it back. Decided I hadn't earned the right. Closed the laptop. Three weeks later the deck went out and the round closed inside a week.
Lesson: The email I didn't send cost me a position I'd already done the work to deserve. Now I send the email. The product on this site is a system that decides which Sunday emails are worth sending — so I never have to ask whether I've earned the right again.
Parable 5 · The Reader Who Told Me I Was Wrong
Six weeks into the public beta a Series B associate replied to a Tuesday digest with two lines. 'You flagged orgname. Their commit velocity tripled because they migrated a monorepo. There was no acceleration. Just a re-org.' She was right. The model had no signal for monorepo migration events. We added it the next Sunday — false positive rate dropped from 7% to 4% on the back of one reader's reply.
Lesson: Every methodology is wrong somewhere. The cheap move is to deny it. The expensive move — and the one that compounds — is to publish the limit before the reader finds it. We publish ours at /methodology. The reader who corrects us is the reader who matters most.
Parable 6 · The Tuesday I Broke the Regression
On a Tuesday in February I refactored the velocity computation 'just to clean it up.' Pushed at 9pm. Wednesday morning the digest went out with three orgs ranked at the top that did not belong there — a hackathon, a bot-heavy security tool, a vendor's documentation repo. Thirty subscribers replied. I rolled back, ran the panel against the prior week's truth set, found the off-by-one in the contributor-deduplication step, shipped the fix Thursday at 3am, posted the post-mortem at /uptime Friday morning.
Lesson: The methodology is more interesting than the wins. When something breaks, the post-mortem goes public the same week. The regression code, the truth set, the fix commit — all linkable, all CC BY 4.0. That's the whole reason the price is €9.97/mo and not €9,970.
03 · Three flaws, on purpose
A founder character without visible flaws reads as a brochure. These are real. If they’re dealbreakers, I’m the wrong vendor.
Flaw 1 — Slow to reply.
Email replies happen in two daily batches, never inside the hour. No LinkedIn DMs at all. If you need a vendor on Slack at 11pm, I'm not it.
Flaw 2 — Won't do calls before you've subscribed.
Sharp Tier funds get one quarterly call, included. Insider Circle gets the monthly group briefing. Below that, everything is async and written. I'd rather write you a long email than waste your hour on a discovery call you didn't need.
Flaw 3 — No video, podcasts, or named publication.
Anonymity is non-negotiable. If your firm requires named attribution on every paper or photo on every LinkedIn post, I'm the wrong vendor. The handle is what lets me say uncomfortable things about how the consensus deal-flow industry works.
04 · Seven voice rules
A consistent founder voice compounds across surfaces. These are the seven rules every page, email, and video script gets reviewed against. They’re published so the reader can audit drift.
Rule 1 — Specific over general.
Never say 'a startup'. Say 'a three-founder fintech with one repo'. Never say 'a fund'. Say 'the partner at [redacted] who DM'd me about the fintech the morning after the announcement'. Specific scales; general dies.
Rule 2 — Code metaphors over business metaphors.
We're talking to engineer-investors. 'Pre-cache the deal flow' lands. 'Synergize the funnel' doesn't. When in doubt, reach for a build pipeline, a regression coefficient, or a merge graph.
Rule 3 — Number, then claim. Never claim, then number.
Wrong: 'GitHub data is the most leading signal — we ran a panel of 219 startups.' Right: '219 startups, five quarters, median 31-day lead time. That's why we say GitHub data is the most leading signal.' Numbers up front earn the claim.
Rule 4 — Admit what we don't know in the same breath.
Every claim has a limit. Naming it before the reader does is the cheapest credibility move there is. 'False positive rate is 4%. We're trying to get it to 2% by Q4 but right now it's 4%.' Better than 'industry-leading accuracy'.
Rule 5 — No hype words.
Banned: 'unlock', 'leverage', 'game-changer', 'revolutionary', 'AI-powered' (without an actual model name), 'cutting-edge', 'next-generation'. If a word would survive being deleted, delete it.
Rule 6 — Cliffhanger at the end of every email.
The P.S. previews tomorrow's email or the next chapter. The reader closes the browser still curious. That's the entire job of email #N — get them to open email #N+1.
Rule 7 — Never sign anyone else's name.
Every byline is 'The Data Nerd' or unsigned. There is no second persona. There is no team handle. Voice fragmentation breaks the character; one handle, every surface, forever.
05 · Catchphrases
Founder voices have 5–7 verbal tells the audience can quote. These are mine. If you’ve been reading for more than two months and one of these doesn’t sound familiar, the voice has drifted and someone owes you a refund.
“Trust the math, not me.”
“The methodology is the protagonist. I'm the storyteller.”
“Public data, private lens.”
“The deck lags the code by 21 to 47 days.”
“Code is more honest than copy.”
“If we're right, the data carries the argument.”
“Read the methodology before you trust the metric.”
06 · Where you’ll meet me
Email drip
Where: Days 0–180 in the welcome + daily-story sequences
How: Every email signs as The Data Nerd. P.S. previews the next.
YouTube
Where: Acceleration Watch (weekly), State-of-the-Engine talk (monthly), Data Nerd Brief (weekly)
How: Cartesia synthetic voice — the same voice across every video. No real-voice cameo, ever.
Manifesto + Origin + Founder pages
Where: /manifesto, /origin, /about/founder, /story
How: Long-form character: backstory, polarity, parables, flaws.
Page narrations
Where: /walkthrough, /predicted, /state-of-github audio companions
How: Synthetic voice reads the page. Disclosure on every player.
Weekly Sunday digest
Where: Free Acceleration Watch, every Monday 06:00 UTC
How: Five startups, sector-tagged, signed The Data Nerd. The rhythm is the relationship.
Reply-to inbox
Where: signal@gitdealflow.com
How: Same handle. Two daily reply batches. No call-scheduling links.
07 · Where to go next
Three doors, by commitment level:
Character framing drawn from direct-response sales canon. Implemented under the anonymity rule (manifesto pillar #4) — handle, synthetic voice, methodology glyph, no real face/name/voice.