Everything from

Kalzumeus Software

4 resources from Kalzumeus Software we point founders to, and the questions each answers.

✍️ Essay
✓ Link checked Free Beginner

Why we picked it This is the classic counterweight to the first-timer instinct to price low out of nervousness. McKenzie's core argument is that price should reflect the value the customer receives, not the hours or ease it took you to build, and that most makers systematically undercharge because they see their product's flaws instead of its alternatives. Read it right after you draft a number, then ask honestly whether you flinched too low.

You Can Probably Stand To Charge More

From Kalzumeus Software by Patrick McKenzie (patio11) About a 10 minute read

  • Price on the value a customer gets, not on how long or how easily you built it: the demand curve is external to you.
  • "Coder's remorse" (undervaluing your own work because you see its flaws) is the main reason founders set a price too low.
  • Because software's marginal cost is near zero, you have far more room to price on value than you think.
Open kalzumeus.com
🎧 Podcast
✓ Link checked Free Intermediate

Why we picked it Two experienced bootstrapped founders talk through pricing decisions in plain language, including why targeting businesses instead of consumers makes a too-low price especially costly. It is a conversation, not a lecture, so you hear the actual reasoning and disagreements, useful when you are trying to think out loud about your own number.

Kalzumeus Podcast Ep. 2 with Amy Hoy: Pricing, Products, And Passion

On Kalzumeus Software

  • Businesses judge price against value and ROI, not against what feels fair
  • A cheap entry tier attracts customers who need the most support and pay the least
  • Price to the customer segment you want more of, not the one that is easiest to close
Open kalzumeus.com
🎧 Podcast
✓ Link checked Free Intermediate

Why we picked it McKenzie went from zero consulting clients to a full pipeline using direct, honest outreach with no case studies to point to, and this conversation with Ramit Sethi is the clearest breakdown of how he actually did it. It applies just as well to a product founder emailing prospective customers as it does to a consultant emailing prospective clients: the mechanics of a credible cold ask are the same.

Ramit Sethi and Patrick McKenzie on Getting Your First Consulting Client

On Kalzumeus Software by Patrick McKenzie, Ramit Sethi 50 min audio

  • Naming the specific problem you solve for a specific type of person beats a general pitch
  • Early outreach should ask for a conversation, with the sale coming later once trust exists
  • Volume matters less than sending to people who plausibly already feel the pain you fix
Open kalzumeus.com
✍️ Essay
✓ Link checked Free Intermediate

Why we picked it Written from the receiving end by someone who gets a lot of cold email, this lays out exactly what makes an ask easy to say yes to versus what reads as an open-ended, vague favor. It reframes the vague-ask mistake as a favor to the reader, not just etiquette.

Standing Invitation

From Kalzumeus Software by Patrick McKenzie (patio11) 10 min read

  • A specific question is far easier to answer than an open request for mentorship or advice
  • Keep a first email to about a paragraph and make one request, not several
  • Don't apologize for emailing or minimize yourself; state your point with restrained confidence
Open kalzumeus.com
eChai Partner Brands