NOAH
JACOBS

TABLE OF CONTENTS
2025.02.09-On-Overengineering
2025.02.02-On-Autocomplete
2025.01.26-On-The-Automated-Turkey-Problem
2025.01.19-On-Success-Metrics
2025.01.12-On-Being-the-Best
2025.01.05-On-2024
2024.12.29-On-Dragons-and-Lizards
2024.12.22-On-Being-a-Contrarian
2024.12.15-On-Sticky-Rules
2024.12.08-On-Scarcity-&-Abundance
2024.12.01-On-BirdDog
2024.11.24-On-Focus
2024.11.17-On-The-Curse-of-Dimensionality
2024.11.10-On-Skill-as-Efficiency
2024.11.03-On-Efficiency
2024.10.27-On-Binary-Goals
2024.10.20-On-Commitment
2024.10.13-On-Rules-Vs-Intuition
2024.10.06-On-Binding-Constraints
2024.09.29-On-Restrictive-Rules
2024.09.22-On-Conflicting-Ideas
2024.09.15-On-Vectors
2024.09.08-On-Perfection
2024.09.01-On-Signal-Density
2024.08.25-On-Yapping
2024.08.18-On-Wax-and-Feather-Assumptions
2024.08.11-On-Going-All-In
2024.08.04-On-Abstraction
2024.07.28-On-Naming-a-Company
2024.07.21-On-Coding-in-Tongues
2024.07.14-On-Sufficient-Precision
2024.07.07-On-Rewriting
2024.06.30-On-Hacker-Houses
2024.06.23-On-Knowledge-Graphs
2024.06.16-On-Authority-and-Responsibility
2024.06.09-On-Personal-Websites
2024.06.02-On-Reducing-Complexity
2024.05.26-On-Design-as-Information
2024.05.19-On-UI-UX
2024.05.12-On-Exponential-Learning
2024.05.05-On-School
2024.04.28-On-Product-Development
2024.04.21-On-Communication
2024.04.14-On-Money-Tree-Farming
2024.04.07-On-Capital-Allocation
2024.03.31-On-Optimization
2024.03.24-On-Habit-Trackers
2024.03.17-On-Push-Notifications
2024.03.10-On-Being-Yourself
2024.03.03-On-Biking
2024.02.25-On-Descoping-Uncertainty
2024.02.18-On-Surfing
2024.02.11-On-Risk-Takers
2024.02.04-On-San-Francisco
2024.01.28-On-Big-Numbers
2024.01.21-On-Envy
2024.01.14-On-Value-vs-Price
2024.01.07-On-Running
2023.12.31-On-Thriving-&-Proactivity
2023.12.24-On-Surviving-&-Reactivity
2023.12.17-On-Sacrifices
2023.12.10-On-Suffering
2023.12.03-On-Constraints
2023.11.26-On-Fear-Hope-&-Patience
2023.11.19-On-Being-Light
2023.11.12-On-Hard-work-vs-Entitlement
2023.11.05-On-Cognitive-Dissonance
2023.10.29-On-Poetry
2023.10.22-On-Gut-Instinct
2023.10.15-On-Optionality
2023.10.08-On-Walking
2023.10.01-On-Exceeding-Expectations
2023.09.24-On-Iterative-Hypothesis-Testing
2023.09.17-On-Knowledge-&-Understanding
2023.09.10-On-Selfishness
2023.09.03-On-Friendship
2023.08.27-On-Craftsmanship
2023.08.20-On-Discipline-&-Deep-Work
2023.08.13-On-Community-Building
2023.08.05-On-Decentralized-Bottom-Up-Leadership
2023.07.29-On-Frame-Breaks
2023.07.22-On-Shared-Struggle
2023.07.16-On-Self-Similarity
2023.07.05-On-Experts
2023.07.02-The-Beginning

WRITING

"if you have to wait for it to roar out of you, then wait patiently."

- Charles Bukowski

Writing is one of my oldest skills; I started when I was very young, and have not stopped since. 

Age 13-16 - My first recorded journal entry was at 13 | Continued journaling, on and off.

Ages 17-18 - Started writing a bit more poetry, influenced heavily by Charles Bukwoski | Shockingly, some of my rather lewd poetry was featured at a county wide youth arts type event | Self published my first poetry book .

Age 19 - Self published another poetry book | Self published a short story collection with a narrative woven through it | Wrote a novel in one month; after considerable edits, it was long listed for the DCI Novel Prize, although that’s not that big of a deal, I think that contest was discontinued.

Age 20 - Published the GameStop book I mention on the investing page | Self published an original poetry collection that was dynamically generated based on reader preferences | Also created a collection of public domain poems with some friend’s and I’s mixed in, was also going to publish it with the dynamic generation, but never did.

Age 21 - Started writing letters to our hedge fund investors, see investing.

Age 22 - Started a weekly personal blog | Letters to company Investors, unpublished. 

Age 23 - Coming up on one year anniversary of consecutive weekly blog publications  | Letters to investors, unpublished.

You can use the table of contents to the left or click here to check out my blog posts.

Last Updated 2024.06.10

Join my weekly blog to learn about learning

2025.01.19

LXXXIII

How do you measure the success of a bootstrapped startup?

Subscribe

-------------------

Bootstrapping

Jack and I have been “bootstrapping” BirdDog for the last 6 months. This means that we have not raised outside capital for the project. 

We haven’t altogether eschewed the idea of raising capital in the future, but are cautious. We’ve seen (and are seeing) other companies in our space raise money and keep growing “vanity” metrics like employee count. 

The playbook for a Venture backed startup is quite different from that for a bootstrapped one. As the latter, I think it’s interesting to speculate on what some of the metrics we might focus on going forwards are.

Right now, the three that make the most sense to me are:

  1. High Profit Margin

  2. Low Churn

  3. High Revenue Per Employee

A Caution On Optimization

Before we jump into the measurements proper, it's important to note the “dangers” of over indexing on any one single measurement. A warning I often bring up is Goodhart’s Law:

Sacrificing some nuance for clarity: 

Think about standardized tests for college admissions–you observe a correlation between “intelligence” and the ability to perform well on the SAT. Then, you use the SAT to measure how intelligent students are. Now, the SAT is less good of a measure for intelligence because students optimize for scoring high on the test, not for “becoming more intelligent.”

Likewise, perhaps you see that companies that “succeed” grow their revenue and headcount very quickly. Then, if you try to copy them by growing your revenue very quickly, and that is all you focus on, you may think you will succeed even if you are burning money and need to keep raising additional capital to stay afloat. The companies that succeeded that also had growing headcount and revenue did not necessarily succeed because they had growing headcount and revenue. 

So the trick, then, becomes to try to find measures that have the strongest causal relationship with long term success rather than simply being correlated with them. 

This is hard. Still, I’m playing around with the below metrics and will point out how I think they could go wrong.

What is Success?

Another big word of caution: I am talking about measurements that one would want to optimize for to maximize the chances that their business “succeeds.” 

The word success is incredibly broad and is very difficult to nail down. We’ll descope it by defining success as “A business that makes you wealthy.” This is not the only reason to start a business, and it is not the only reason I or Jack started a business.



Caption: Success when bow fish hunting is quite self evident

That being said, the point of this post is more to identify metrics to estimate the “health” of a bootstrapped business. This says nothing about the success of a venture backed drug discovery startup, for instance.

Without further ado, the measures.

Profit Margin

Why it’s Good:

Profit margin is self-evidently important for any business.*

More-so, if you are bootstrapping a B2B SaaS, this is one of the most critical things to be focused on right away–you don’t have money to spend to reach “economies of scale,” your service needs to be making money early on, or at the least, breaking even.

You don’t have unlimited money to burn on non profitable growth.

Where it could be Bad: 

A trap here is associated with making decisions that increase profit margin at the cost of lowering the quality of the product and, resultantly, user satisfaction. 

That could be something that juices numbers for a short period of time but would likely result in an increase in churn and damage to your reputation that will make it harder to sell your product in the future.

*If you are trying to change the world and that requires losing money to make money, then perhaps this measure is less immediately important. Eventually, though, it does become important, or you are a non profit or charity.

Low Churn

Why it’s Good:

Churn is a measure of how many users who pay for your product or service end up leaving later. For obvious reasons, if somebody buys your product, you don’t want them to stop paying you in two months because they no longer like it or need it or see value in it.

It might be one of the better proxies for how important your product is to your users. If you have low churn, then your user’s like your product, feel like they can’t get the same value elsewhere, or maybe the cost of switching is high.

Something interesting here–one of my mentors who's approaching $500K in ARR told me that he has had only one customer who is paying more than $300 a month churn; everyone else who churned was paying him $150 a month or less.

Where it could be Bad:

I’m actually not so sure how this one could go wrong… maybe if you spent a prohibitive amount of time with one or two customers to make sure they never left at the expense of not adding new customers because you don’t have the bandwidth to do so, that would be bad.

Revenue Per Employee

Why it’s Good:

I think revenue per employee is probably the least discussed metric for a company’s success but very succinctly captures the leverage an operation has. 

In a sense, Revenue Per Employee is an “Anti VanityMetric” Metric. It puts a nice little asterisk next to any number like headcount growth or revenue growth–if you have 25 employees but are only doing $2M in revenue, you’re likely underwater on people costs alone. And, if you add another $1M in revenue but had to hire 12 people to get there, again, that’s likely a losing proposition (at least for now!).

Among big tech companies in 2022, Netflix was the winner, at $2.46M per employee. Palantir is also a really interesting one in my mind, seeing as it is to some extent productized tech enabled consulting–with $708K per employee, it almost doubles each of the Big Three consultancies in terms of revenue per employee. 

Another way to put it–revenue per employee is a measure of how reliably the business is able to support the people who are counting on it

Why it could be Bad:

If you’re afraid to hire and grow because you don’t want to drop your revenue per employee, at least for a little bit, you might be shooting yourself in the foot. 

Also, there is a similar trap to the profit margin trap here–if you ignore something like customer service or product quality because you refuse to hire an employee who will not directly contribute to revenue, you will be hurting yourself in the long term.

The Perfect Measure

In short, there is no theoretically perfect measurement for anything. The “best measure” I can think of would be “Value Surplus”, how much value you create less how much value you capture, but it is very theoretical and the difficulty of getting that metric right would be immense.

In practice, there exists some mix of measurements that is likely sufficient for your purpose, with caution. And, I think for a bootstrapped B2B SaaS company, maintaining a high profit margin, minimizing churn, and increasing revenue per employee is one such mix.

But, who knows. I’ll keep you posted on it as we go along. 

Live Deeply,