Skip to content

Founder LessonsCase Study · 3 min read

Gumroad’s numbers: the problem was the cost base, not the revenue

Most founders judge their costs against revenue. Gumroad’s own numbers show why that comparison can hide the problem until it is too late to fix it gently.

Sources checked 23 October 2026 · 1 source, listed at the end

What happened

Reported facts, each from the sources listed below.

Gumroad raised $1.1M from angel investors and venture firms, then $7M more in May 2012, according to its founder, Sahil Lavingia. In a 2019 essay on his own site he published the company’s monthly figures for two months a year apart.

June 2015 · revenue for the month
$89,000
June 2015 · gross profit
$17,000
June 2015 · operating expenses
$364,000
“I laid off 75 percent of my company — including many of my best friends.”
Sahil Lavingia, 2019

The company went from twenty employees to five.

June 2016 · revenue for the month
$176,000
June 2016 · gross profit
$42,000
June 2016 · operating expenses
$32,000

He also published net profit: −$351,000 for June 2015 and +$10,000 for June 2016. Net follows gross profit, not revenue: $42,000 minus $32,000 is exactly the June 2016 figure, and the June 2015 subtraction lands within $4,000 of the published net, a gap the essay does not explain.

What we take from it

Our analysis: FoundersGPT’s reading of the facts above, not something the sources say.

Revenue roughly doubled between the two Junes (176 ÷ 89 is 1.98). Operating expenses fell by more than 90% (32 ÷ 364 is 0.09). The revenue line improved; the cost line is the one that changed the company’s position.

In June 2015 only about a fifth of revenue stayed as gross profit (17 ÷ 89). For a payments business that makes sense: much of each sale was never the company’s to keep. Gross profit is what pays salaries, and operating expenses were more than twenty times it (364 ÷ 17). No realistic growth rate closes a gap that size before the money runs out.

That is the distinction worth keeping. A revenue problem is fixed with more customers. A cost-base problem is fixed by spending less. They do not share a fix, and founders tend to reach for the first when they have the second, because hiring feels like progress and cutting feels like failure.

Do this this week

  1. Use gross profit, not revenue

    Take last month’s gross profit: revenue minus what it directly cost to deliver it, including payment fees and anything you pass through to others.

  2. Put operating expenses beside it

    Salaries, rent, tools, contractors. Write the ratio: operating expenses divided by gross profit.

  3. Do the same for the month a year earlier

    Two points a year apart show which line is actually moving. One month on its own shows nothing.

  4. Ask what growth would close the gap

    If costs are above gross profit, work out the monthly growth needed for gross profit to cover them before your cash runs out. Compare it with the best quarter you have actually had, not the plan.

  5. Decide which line has to move

    If no growth you have achieved closes the gap in time, you are looking at a cost problem. Plan the company you can afford at the growth you have.

What this does not show

These are two months of one company’s figures, published by its founder. They are not a full set of accounts, they say nothing about Gumroad today, and they do not show that cutting a team is right for yours. Lavingia describes the layoff as a failure with a real human cost. The lesson here is about which numbers to compare, not about whom to let go.

Sources

  1. Reflecting on My Failure to Build a Billion-Dollar Company — Sahil Lavingia, sahillavingia.com, 7 February 2019.

How these were checked: how we source. Found an error? Corrections policy.

One founder lesson a week, by email

Each issue gives one lesson, the mechanism behind it and one thing to do this week. Read Issue #1 before you subscribe.

Unsubscribe in one click. How we handle your address.

← All articles