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

2024.09.22

LXV

Cats can be adorable, affectionate, and lethal predators, all at the same time.

Likewise, you can still champion you’re product while you’re far from perfecting it.

Subscribe

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

The Jabberwocky

Oftentimes in life, there are seemingly contradictory things that are actually both true. 

Cats are adorable. They also heartlessly smite lesser creatures for sport. Neither of these are truly conflicting, but we seem to put them on opposite ends of some spectrum and don’t think about them at the same time. 



Caption: BEWARE THE JABBERWOCK, MY SON! JAWS THAT BITE, CLAWS THAT CATCH! Blurry to emphasize my flee from her attack.

Likewise, this weekend, Jack and I were on a call with a user that emphasized for me the conflict between knowing that the product will never be done and knowing that the only way to validate that it’s worth anything is by selling it. 

While it may seem contradictory on the surface (how can you sell something that’s not finished?), just as cats can be cuddly and violent, both can be true at the same time. 

Defining Sales

I view “sales” as the process of explaining how a product or service creates value for a user, whether by solving a problem or presenting an opportunity. “Closing” is the part of sales where you commit to exchanging the value your product or service creates for some other resource (preferably money). 

When building a product, your goal is to build something that “sells itself,” meaning the value created is so painfully obvious that all you have to do is be there to close. 

When selling something, your goal is to “sell it,” meaning you make the value that it creates so painfully obvious that the person wants to close

Because feedback from users is critical in both processes, it can get confusing when you are trying to build a product and sell it at the same time. Feedback from users when you’re in the product mindset should be used to improve the product–how can you make the product solve the user’s problem? Feedback from users in the sales mindset should be taken as an opportunity to improve your messaging–how can you explain to the user that by doing x, y, and z, the product already solves the problem?

If you’re doing both at the same time, you have to jointly know that your product is “not good enough” in the sense that it doesn’t yet sell itself while working to explain why it is “good enough” to actually address the users concerns. 

User Interviews

Jack and I were on a call with a user yesterday. For simplicity and ease of generalization, we’ll call him “User.” 

User had a lot of feedback. One piece of feedback User gave was that we should rank the prospects based on the data we’re finding about them. We've heard this a lot and it’s something we’re considering integrating.*

When I heard that from User yesterday, I was in “product” mode**, so to speak. I agreed with him, we should totally add that. 

I’m grateful Jack was on the call, too, because he was more in “sales” mode. He clarified that the product already should save User tons of time by surfacing only the accounts with relevant info. 

Interestingly enough, both things are true: we should add that feature to the product, and User should still get value without it.

*I mention that we’ve heard it from multiple users because evaluating the quality of feedback is hard, but hearing the same thing from multiple users seems to be one of the strongest indicators of its value.

**Perhaps sales and product modes are just subsets of founder mode.

Product Mode

Maybe because I’m spending so much time staring at code all day, I’m more in product mode. This, I’m sure, has been reflected in my writing over the past couple of months. 

All feedback is ordered towards building a better product. You know that the product is NOT good enough when you grade it against everything that it could be, and never will be. But that’s okay, because every day is about making it better.

Even Steve Jobs, the master of perfection, shipped the first iPhone… the first iPhone is “incomplete” and “imperfect” when graded against the iPhone 16. 

That is to say product mode is not building in a silo, it’s aggressively making and shipping improvements.

Of course, the only way to evaluate the improvements is to have a user try them out… which requires some sales mode.

Sales Mode

As a good balance to me, Jack is more in sales mode.

Feedback, while valuable, is oftentimes an objection to be overcome. After all, the best way to validate that you’re building something worth building is to get people to use it and then get them to pay for it. 

For clarification, this is certainly not “shill” mode or “sell something that doesn’t work” mode. Go back to my definition of sales and closing. While you want to “close” by trading the value your product or service creates for money, you can still “close” by trading for a user’s time or a testimonial.

In that sense, every time you book a first meeting or a follow up meeting, you’ve made a little close. Of course, if you’re never able to turn the learnings from your users time into revenue, it’s irrelevant. Still, getting their time to begin with is part of the process. 

And, since we’ve yet to transition from time to money, Jack has had the wisdom to raise the stakes of our sales mode with the simple step of formalizing our pilot program into a two week trial punctuated with a paid subscription and sharing this with new users on the first call.

Zen

If you’re not even able to close someone by trading the use of your product for their time using it, then you won’t have access to the feedback needed to improve the product. Likewise, if you’re unable to use the feedback to make the product more obviously valuable, you’ll have a much harder time selling it yourself. 

In a startup, the two notions depend on one another. You need to be doing both at the same time.

It’s easy to create a false deadlock when you know the product needs to be better and the product needs to be sold. The product can be incomplete and also sellable at the same time, it’s not either or. And if you’re still working on selling it for money, you at the least need to be selling it for a user’s time. 

Like a cat having sharp, retractable claws and a soothing purr, apparently antithetical ideas are more reconcilable than we might think. But, nuanced truth is itself hard to sell, especially in our short attention span information era.

For fun, I’ll leave you with a list of other false conflicts:

  • “Work as much as possible”  & “Only do things that will move the needle”

  • “Don’t waste time on social media” & “Use social media to market & sell”

  • “Drake has questionable relationships with women” & “Pop Style goes hard”

  • “Listen to users” & “People don't actually know what they want”

  • “Be disciplined in all that you do” & “Know when to sacrifice habit to seize an opportunity”

Subscribe

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

In an effort to keep these posts more concise, I removed a whole section on cats.

The things we do in the name of improvement.

Live Deeply,