What is a founder activity graph? (and why GitHub got there first)

TL;DR

What "activity graph" actually means

The phrase comes from GitHub. Open any developer's profile and you will see a 365-square heatmap — one square per day, shaded by how much they pushed. Click further, you get the per-repo timeline of every commit. The graph is not a marketing artifact. It is the raw record of work, surfaced.

A founder activity graph is the same idea applied to a different domain. Instead of git push, the events are commits, posts, sales, deploys, customer calls, decisions, and reflections — the things a founder actually does in a week. Each event is a row in a typed log. The heatmap is the visible surface; the log underneath is what makes the credential real.

The three properties that matter

There are three things an activity graph has that a CV, a deck, or a self-reported survey does not.

1. Granular

A CV says "Founded a SaaS company, 2024–present." The activity graph says: 47 commits in March, 12 LinkedIn posts, 19 Calendly meetings, 4 Stripe charges, a 31-day deploy streak, two crisis-sim decisions resolved on Saturday at 10pm. The first sentence is consistent with both running a real company and running a side project that has not shipped yet. The second is not.

Granularity is what lets a viewer tell the difference between sustained effort and selective storytelling — without having to take anyone's word for it.

2. Verifiable

Self-reports are unverifiable by design. "I am a high-velocity builder" is a claim. "I am data-driven" is a claim. "I have strong customer empathy" is a claim. Nothing about the medium prevents the claim from being mostly aspirational.

An activity graph anchors every visible square in an actual webhook event from an external system. The Stripe row exists because Stripe sent the webhook. The GitHub row exists because GitHub sent the webhook. The Razorpay payout row exists because money moved. Verifiable does not mean infallible — you can still misrepresent intent, scope, or context — but the existence of the artifact is independent of how the founder describes it.

This is why the credential cannot be faked at scale. AI-generated copy can fake a deck. AI-generated commits cannot fake a year of payments, customer meetings, and PRs merged that all reference each other.

3. Emergent

The hardest property to design for, and the one most products get wrong.

A profile-first product — "sign up to build your founder credential" — has a recruitment problem. Most users have no reason to come back daily, because the credential is the outcome, not the loop. If you have to be motivated by your future credential to fill out today's profile, attrition is going to be brutal.

An activity-graph product flips the order. The user shows up daily for a different reason — a daily action coach, an accountability partner, a place to log what they shipped — and the credential builds itself underneath without the user thinking about it. GitHub did not pitch developers on "build your developer credential"; it pitched them on git hosting. The credential emerged.

The whole reason Founders DNA went from "a 90-day simulator that scores judgment" to "a daily action coach that builds a verifiable profile underneath" is this property. We needed the credential to be a byproduct of something founders genuinely want to use every day.

Why GitHub got there first, and what that tells us

GitHub had three structural advantages most other domains do not:

• A standardised commit primitive — git push was already universal before GitHub existed. They did not invent the verb; they hosted it.
• A high-frequency action loop — developers commit many times per day, which means the heatmap fills naturally without anyone working at filling it.
• An adjacency to real consequence — the same commits that paint the green squares also ship the product, fix the bug, get the bonus. The graph does not compete with work; it is a side effect of it.

For founders, none of these existed natively. There was no git push for "I just shipped a customer interview" or "I just got my first paying customer." There was no high-frequency loop — most founder work is bursty and qualitative. There was no system that captured "the same act that paints today's green square also moved my business forward."

What there is — and this is the design insight — is a sprawling collection of tools that founders already use, each of which has a webhook. GitHub for code. LinkedIn for public posts. Stripe and Razorpay for revenue. Calendly for customer calls. Vercel for deploys. Notion for planning. Telegram and WhatsApp for everything else.

Each of those tools already has a commit primitive native to its domain. A founder activity graph is not a new tool the founder has to use; it is a layer that listens to the tools they already use, normalises the events into a typed stream, and renders the heatmap. That layer is what we are building.

What the graph looks like for a Founders DNA user

Concretely, a founder profile in the Q3 beta has:

• A 365-day contributions heatmap, one square per day, shaded by the volume of typed events that day.
• A commits feed — chronological timeline of every event, each with an Octicon for the source (GitHub, Stripe, LinkedIn, Vercel, manual, sim).
• A language strip equivalent — instead of "Python 47%, TypeScript 31%," it shows "Stripe 22%, GitHub 31%, Manual 18%, Sim 14%, LinkedIn 15%" — the mix of where commits came from.
• The dual radar — Judgment DNA from the simulator, Execution Profile from the activity stream — both visible side by side.
• A list of pinned ventures (repo-style), with a README, an About sidebar, recent commits, and the integrations connected to that specific venture.

The closest analogue to a CV — the section a reviewer is most likely to bookmark — is not actually the radar. It is the heatmap plus the integration breakdown plus the pinned ventures. Together those three answer the question "what does this founder actually spend their days doing?"

Where this is heading

The activity graph is the foundation; the credential is the layer above it. In Phase 2 we will add the social layer — followers, stars, peer verification, mentor threads — and the marketplace where investors and accelerators can browse anon profiles, filter by Capital Discipline, and request identity unlock from founders whose dual radars match their thesis.

But the foundation has to come first. A social layer on top of self-reports is just LinkedIn. A social layer on top of an authentic activity graph is something else.

— Karthik