Building

One person, a lot of agents, and a company on its second act.

Most of what I make is Groupthink. I started the company in 2021, shipped the first version of it in February 2023, and since May 2026 I have built the whole thing by myself, with AI doing the work a team of engineers used to do. Here is the story, with the numbers.

The numbers

Merged pull requests, by month

August has 383 merged so far, about 17 a day. At that rate it finishes near 528, against 604 in June 2026.

Five people The reduction Solo, with agents On pace
2024
2025
2025
2026

Engineering repositories only, so documentation and marketing work is excluded. The dip in the middle is what it cost to lose a team, and the recovery on the right took four months of learning how to direct agents well. counts refreshed daily from github · last updated 7 hours ago

604

merged PRs

June 2026, the best month in the company's history

The previous record was 287, in February 2025, with five people.

$50

per merged PR

All-in company cost that month

It was $430 per PR in June 2025, running a team of five on $104K a month.

$200

per month

What the engineering labor costs

A flat Claude plan. The same usage at list API prices would have run about $5,200 in June.

2,056

merged PRs

So far in 2026, through August 14

Across the API, web app, desktop app, iOS app, and marketing site.

Every figure here is a merged pull request count from GitHub or a line from the company's own books. Nothing is estimated except the pace, which is labelled where it appears.

What Groupthink is

A relationship intelligence platform. It makes the dynamic between you and another person legible enough to act on, so your next meeting with someone is better than your last.

The unit is the relationship

Not the meeting and not the task. A relationship is a system that exists in the space between two people, and inside it the load-bearing points are the commitments you make out loud. Those are the checks we write with our mouths that our workload cannot cash.

The record is yours

This software has always been sold to companies, to manage their people. Groupthink inverts that. You are a node across many overlapping and temporary organizations, and the record of your side of them should survive changing jobs, tools, and AI vendors.

It compounds on its own

Every meeting, every paste, every detected name deepens what the system knows, whether or not you remember to file anything. A notetaker's summary is identical on meeting one and meeting fifty. This one gets better every day you do nothing.

What it is not: a meeting notetaker. Meet, Teams, and Zoom all transcribe and summarize for free. That was the whole problem, and it is where this story starts.

The arc

Five years, one category collapse, one team reduction, and a rebuild that worked. The unflattering parts are in here too, because without them the rest does not mean anything.

  1. October 2015

    The request for startup

    Six years before the company exists, a post asks for a personal CRM for grown-up friendships: "My Mom had this pretty blue book where she'd record all of this stuff about her friends and family. I want something like that, but for the modern age." It ends: who will build it?

    Read the 2015 post →
  2. 2021

    First Party Labs

    The company is incorporated as First Party Labs. Groupthink's first line of code is still two years away.

  3. February 2023

    Groupthink starts

    First commits land in the API and web repos on February 2nd. A tool for running better meetings: agendas, notes, the things a team needs to not waste an hour.

  4. 2024

    The category commoditizes

    Google Meet, Teams, and Zoom all ship native transcription and summaries, free, with no bot to add. The most common objection from new signups becomes the one we could not answer: why would I use this instead of what is already in my meeting tool?

  5. February 2025

    Peak team output

    287 merged pull requests in a month, from five people. It stood as the record for fifteen months.

  6. August 2025

    Three engineers cut

    Burn goes from $104K a month to about $70K, then $38K. Output goes with it. This is the part of the story that is not a growth chart.

  7. December 2025

    The trough

    17 merged PRs that month, then 15 in January. Two people, one of them part-time and reviewing only. The cost per shipped PR was worse than it had ever been with a full team.

  8. February 2026

    The rebuild starts

    Claude Code becomes the engineering team. 98 PRs in February, 113 in March, 127 in April. Slower than the team era, and improving every month.

  9. March 2026

    The repositioning

    Groupthink stops being a meeting notetaker and becomes a relationship intelligence platform. Meetings are inputs. What you know about a person after twenty of them is the output.

  10. May 2026

    Solo

    The last reviewer comes off. 424 merged PRs that month, past the old team record, at $71 per PR against $430 eleven months earlier.

  11. June 2026

    604 merged PRs

    More than double the best month the team ever had. The binding constraint stops being engineering throughput and becomes deciding what is worth building.

  12. Now

    The coach

    The product surface is an advisor that reads your record and tells you where a relationship actually is, and what the next move toward what you want from it looks like.

How the work actually happens

People assume the interesting part is the model. It is not. The interesting part is the scaffolding around it, which took about six months to get right and is still changing every week.

The whole company is markdown in git

Strategy, decision log, runbooks, meeting notes, the operating principles, the relationship record. Not because it is tidy, but because it is what an agent can read. A page of English is a job description.

Work is issues under milestones that span every repo

A milestone exists in all five repos at once: product, API, web, website, marketing. It is the single answer to what ships, when, and what goes out with it.

Agents run in parallel, in isolated worktrees

Several at a time, each in its own git worktree so they cannot collide, each claiming its issue first so two never build the same thing. That collision cost a duplicated feature once, which is why the claim step exists.

The code review is also AI

Every PR gets reviewed before it merges. A human reviewer was the last role to go, in May 2026. The review is the final gate, not a pre-flight check.

Nothing is done until it is checked in production

Merged is not done. Deployed is not done. Done is the post-deployment checklist actually run against production, with the results written down. CI cannot exercise production, so a checklist that is never executed is theater.

The workflow runs ahead of the product on purpose

The hand-built version will always be ahead of what ships. That is not a gap to close, it is the roadmap arriving early. What works here gets built for people who will never open a terminal.

On the bench right now

Updated August 23, 2026

Commitment capture

Catching what was actually promised out loud, in the room, and holding it somewhere you will see it.

Text-message ingestion

Your real CRM is your calendar and your texts. Email landed first. This is the next signal.

The Connector

One-click OAuth so your other agents can read your record. The point of owning it is being able to hand it back to yourself.

Desktop recording reliability

Capture that works without a bot joining the call, on a machine you control.

GitHub, both directions

The work itself is context about the relationship. Connect to it rather than rebuild it.

Refining Today

The one screen that has to be worth opening every morning.

The honest part

None of this settles the question

A throughput chart is not product-market fit. I can ship more in a month than a funded team of five could, and I still spend most of my thinking time on whether the thing I am shipping is wanted. In July I wrote this down while sitting on a balcony in Rome, and it is still where I am:

Paying customers, low churn, low growth, low burn, and I am having a lot of fun figuring out how to build and launch major features completely solo with the help of AI. The only problem is, it is lonely and I am not sure I am making something people want.

The constraint stopped being engineering a while ago. It is deciding what deserves to exist, which no agent has done for me yet.

Read the whole post →

What came before

Nineteen years of building, in order. The links go to what I wrote at the time, and the list ends where the top of this page begins.

  1. 2007–2009

    Pelago (Whrrl) · Data team

    My first startup job, on the data team of the Seattle company building Whrrl, collecting and cleaning the place data behind a location-based social app. On the side I was the events editor at Seattle 2.0, covering the startup scene one event at a time. I left with no plan beyond working for myself.

    Pelago, day two (2007) → Goodbye Whrrl, Hello World (2009) →

  2. 2009–2012

    Twilio · First marketing hire

    Hired to do support, blog posts, and video when the company was still working out of borrowed office space; I asked for a senior title on the business card so I could get meetings. Over three years I built the marketing team from zero to eighteen people, launched Twilio SMS, and made the Forbes 30 Under 30 list along the way.

    We launched Twilio SMS (2010) → I don't do that job anymore (2013) →

  3. 2012–2013

    Referly · Founder and CEO

    Y Combinator, Summer 2012. Raised $1M, grew to ten people, and learned the idea was wrong. We killed it rather than run a zombie, and the post about that decision outlived the company.

    Starting Referly took me three years (2012) → Zombie Startups (2013) →

  4. 2013–2017

    Mattermark · Cofounder and CEO

    The deal intelligence company, started with the $350K left in Referly's bank account. Union Square Ventures was the first paying customer, the Mattermark Daily peaked at 100,000 readers, revenue reached about $3M ARR, and the team peaked at seventy. The sale to FullContact in December 2017 did not clear preferences, so common stock, mine included, was wiped out. I stayed six months at the acquirer to land the plane.

    Introducing Mattermark (2014) → This Storm Is You (2018) → What the sale actually paid (2019) →

  5. 2018

    A year off · Sabbatical

    Self-funded, after nine months of M&A. Over a hundred books, angel investing, and a partnership at XFactor Ventures backing female founders.

    The sabbatical announcement (2018) →

  6. 2019–2021

    GitLab · GM of Meltano, then Senior Director of Growth Marketing

    Ran Meltano as an internal startup, hired my replacement, and watched it spin out with a $4.2M seed led by GV. Then built the growth marketing team, reporting to the CEO for my first year. I left shortly before the IPO.

    Can I find my next great investment? (2021) → What is a week end? (2020) →

  7. 2020

    A Ticker a Day · Newsletter and podcast

    One public company analyzed each day, alphabetically through the Vanguard Total Stock Market Index, as a paid Substack alongside the GitLab job. The run now lives in this site's gated archive.

    Introducing A Ticker a Day (2020) →

  8. 2021–2023

    Firstparty · Cofounder and CTO

    Developer-first marketing analytics, built with Jonathan Kressaty. Incorporated in August 2021, funded within 48 hours of tweeting about it, and backed with a $5.7M seed in 2022. We never found product-market fit, so we pivoted. The pivot is the company this page is about.

    A Chip and a Chair (2021) → A Robot Wrote This Subject Line (2022) →

Step-by-step guide

Set up Claude Code to work from the road

The whole pre-flight I run before leaving without my laptop — the rules file, the credentials that bite you, and the commands, with what each one is actually protecting against.

Read the guide

Writing about building this way

How the work actually gets done — the systems, the rules I've written down, and what breaks.

all posts about building →

Also going on

Coaching

One-on-one with founders, executives, and operators, on building companies and on the career questions underneath that.

How I coach →

Writing

Twenty years of it, from the Mattermark era through now. All of it lives here rather than on a platform that can change its mind.

Read the archive →

Cooking

A whole-food, plant-based kitchen run to restaurant standards, at 5,280 feet, with the same systems thinking pointed at dinner.

See the kitchen →