How Graphite Hit $1M ARR in 10 Months After a Full Pivot

Merrill Lutsky raised Graphite's seed round from a tiny Airbnb during the first week of COVID lockdowns, living on Cliff bars and shaky Wi-Fi. Two failed products and six months of runway later, the market pulled a third idea out of him—one that would grow 20x in a single year.

Key Facts

• Time to $1M ARR: ~10 months from public launch; ~12 months from when charging began (Merrill Lutsky)
• Revenue growth: 20x revenue growth in one year, leading to a Series B (Merrill Lutsky)
• Pivot validation test: Target: 20–30 engineers at known companies using Graphite daily in one month. Result: 50 by month's end, 100 the next (Merrill Lutsky)
• Pricing inflection: A single pricing model change more than doubled revenue within weeks (Merrill Lutsky)
• Daily active users at launch of monetization: Thousands of daily actives; now high tens to hundreds of thousands (Merrill Lutsky)

Two Failed Products Before the Real One: Lessons from Pivot Hell

Graphite's first two products—a bug-capture tool and an iOS rollback platform—failed because neither had daily usage or solved a burning business pain. The pivot to code review only happened when the market made the signal impossible to ignore.

Before Graphite became a code review platform, it was two other things. The first was a bug-capture tool for developers—think screen recordings bundled with console logs, pushed into your task tracker. Merrill describes it as a classic founder trap: 'We asked for feedback. Users would give us feature requests. We'd build the feature requests, and then nothing would happen. We'd look at the metrics, and they were using it just as little as they were the week prior.'

The second pivot was an iOS app rollback tool—a real pain point Merrill had seen at Square. It had paying commitments (~$30–50K ARR), but two structural problems killed it. First, it was built on unstable, undocumented Apple APIs, making every customer onboarding a custom engineering project. Second, iOS release cycles are every two weeks, meaning the team only got one shot per month to iterate. 'It's really helpful, especially in the early days, to have a product that users are interacting with every day,' Merrill says. That lesson pointed directly toward what Graphite became.

"We asked for feedback. Users would give us feature requests. We'd build the feature requests, and then nothing would happen." — Merrill Lutsky

"It's really helpful, especially in the early days, to have a product that users are interacting with every day." — Merrill Lutsky

• Bug-capture tool: users gave feature requests but usage never grew.
• iOS rollback tool: technically fragile, low iteration frequency, hard to onboard.
• Key lesson: avoid unstable technical foundations unless you have a major knowledge advantage.
• Daily use is critical—not just for stickiness, but for iteration speed and signal quality.

How the Market Pulled Graphite's Real Product Out of Them

Graphite pivoted to code review when newly hired ex-Meta engineers had an 'allergic reaction' to GitHub's workflow and rebuilt Facebook's internal stacked diffs tool in a hackathon. Word spread in the ex-Meta community, and inbound demand made the pivot undeniable.

The origin of Graphite's core product is a textbook example of organic product-market fit. When the team hired their first engineers—both ex-Meta—those engineers immediately complained about GitHub's code review workflow. One said it 'makes me feel like a caveman.' They were used to Facebook's internal tool, Fabricator, which used a 'stacked diffs' workflow: breaking large features into atomic, reviewable pull requests that could be developed and reviewed in parallel, eliminating the stop-start blocking cycle that plagues GitHub-native teams.

During a company hackathon, those engineers rebuilt the command-line portion of that internal tool just so they could use it themselves. Word got out in the ex-Meta engineering community—and then the open-source version of Fabricator went end-of-life, creating a vacuum. 'Word got out that we had built a tool internally to do this. We started getting a lot of inbound from ex-Meta engineers,' Merrill recalls. Teams demoing the iOS rollback product started asking about the stacked diffs tool instead. 'That moment when it becomes too loud to ignore'—that was when the team committed to the pivot.

To validate before fully switching, Merrill designed a one-month test: get 20–30 engineers at real companies to use the tool daily. No payment required, but participants had to join a shared Slack and a weekly 30-minute Zoom call. The time commitment was the price. They ended the month with 50 engineers. The next month, 100.

"We'd be demoing the iOS rollbacks tool, and there'd be an ex-Meta engineer on the other side who'd say, this iOS stuff is cool and all, but tell me about the Stacked Diffs thing that you've built." — Merrill Lutsky

"Product market fit is the sort of amorphous, intangible concept. But it is the type of thing—when you have it, you know." — Merrill Lutsky

From Waitlist to $1M ARR: The Growth Playbook

Graphite launched a viral waitlist in late 2021, hit the front page of Hacker News, and converted thousands of high-quality signups from companies like Netflix, Snowflake, and Ramp. They stayed free until they'd built enough team-level value to charge organizations rather than individuals.

The waitlist launch was the inflection point. Graphite used a viral mechanic: convince four teammates to sign up and get bumped to the top of the queue. This drove team-level signups rather than isolated individuals—critical for a product that only becomes valuable at the organizational level. 'It wasn't just hobbyists. It was engineers at places like Netflix, Snowflake, and Ramp—really good companies signing up,' Merrill says.

The team made a deliberate choice to stay free longer than felt comfortable. Merrill explains the reasoning: selling to individual developers is notoriously hard because engineers default to 'I'll just build this myself.' The goal was to embed Graphite into team workflows—merge queues, PR coordination, engineering org-wide adoption—before flipping the monetization switch. When they finally charged, nearly everyone eligible converted. 'That stickiness that we were seeing in the usage metrics ended up really converting nicely into revenue.'

The path to $1M ARR took roughly 10 months from public launch and 12 months from when charging began. The pricing model is per seat: free under 10 engineers, then $25–29/seat/month for the core platform, with an additional AI code review agent at $20/active committer/month. Enterprise contracts—six figures for most, seven figures for the largest—came from inbound teams that couldn't buy self-serve and needed to go through procurement.

"It wasn't just like hobbyists. It was like engineers of places like Netflix, Snowflake, and Ramp—like really good companies that were signing up for this." — Merrill Lutsky

"That stickiness that we were seeing in the usage metrics ended up really converting nicely into revenue. But you never really know until you do it." — Merrill Lutsky

The Pricing Change That Doubled Revenue Overnight

A single pricing model adjustment—realigning how Graphite charged with how enterprise teams actually buy—more than doubled revenue within weeks. Merrill points to this as the moment true product-market fit became undeniable.

For many SaaS companies, pricing is the last lever they pull—and often the most powerful. Merrill is candid that Graphite's early pricing didn't match how companies wanted to buy. The fix wasn't a new feature or a new channel. It was restructuring the pricing model to align with enterprise buying behavior. 'We made a change in pricing that better aligned with how companies wanted to buy Graphite—and pretty much in a matter of like a couple of weeks, more than doubled our revenue from that,' he says.

This moment also marked what Merrill considers the clearest signal of true product-market fit. The second confirmation came with their first wall-to-wall enterprise contract—every engineer at a well-respected company using Graphite daily. 'That moment when we went from having organizations within the company using Graphite to now every single engineer at the company relying on this every day—that was the moment when it's like, okay, we've really built something that's valuable.' Most enterprise contracts are six figures; the largest reach seven figures.

The lesson for early-stage founders: pricing is not set-and-forget. It's a hypothesis about value and buyer behavior, and getting it wrong can silently cap your growth for months before the problem becomes visible.

"We made a change in pricing that better aligned with how companies wanted to buy Graphite—and pretty much in a matter of like a couple of weeks, more than doubled our revenue from that." — Merrill Lutsky

"That moment when we went from having organizations within the company using Graphite to every single engineer at the company relying on this every day—that was the moment when it's like, okay, we've really built something that's valuable." — Merrill Lutsky

Co-Founder Trust: The Only Asset That Survives Everything

Merrill's single biggest piece of advice for early-stage founders is to build with co-founders you've known and trusted for years. When the AWS region fails on launch night, your bank collapses, and you're out of runway, trust in your team is the only thing left.

Graphite's founding team—Merrill, Greg, and Tomas—were close friends from Harvard with years of shared history before starting the company. That foundation was tested repeatedly: raising a seed round from an Airbnb during COVID lockdowns, nearly running out of money before the Graphite waitlist launched, surviving an AWS US-West-2 outage on their launch night, and having their funds tied up in Silicon Valley Bank when it collapsed. 'We've now survived a series of both internally and macro events,' Merrill says with characteristic understatement.

His advice to founders caught up in the current AI startup wave is direct: 'As you build a business, if you're going to be doing this for five or ten years, having a founding team that you deeply trust, that you know, that you work well together with—I can't emphasize enough how important that is.' He adds that he can't imagine starting a company with someone he hadn't known for years. The YC statistic he references—that founder conflict is the most common cause of startup failure—is something he's seen play out at peer companies as well.

"When you're running out of runway and aren't sure what to do, and there's no clear path—that's kind of all you have in those moments: the trust in your co-founders and the trust that together you can rise to that occasion." — Merrill Lutsky

"As you build a business, if you're going to be doing this for five or ten years, having a founding team that you deeply trust—I can't emphasize enough how important that is." — Merrill Lutsky

GitHub Workflow vs. Stacked Diffs Workflow (Graphite's Core Value Proposition)