The case for bootstrapping (with Mailchimp's Ben Chestnut)
Executive Summary
Reid Hoffman explores bootstrapping through Ben Chestnut's Mailchimp story, with other founders offering different funding experiences. These notes focus on Chestnut's move from consulting to a repeatable software product. Historical revenue and business outcomes are the speakers' account, not current verified figures or investment advice. The YouTube upload republishes an older conversation. Official transcript is machine-generated; topics are untimed. Source: https://mastersofscale.com/ben-chestnut-the-case-for-bootstrapping/
Key Takeaways
Find paying demand, not only approval
Chestnut describes finding paid consulting projects as his employer prepared to close. Real customer demand helped establish the initial business. That story does not mean skipping business or legal requirements; validate demand while meeting the requirements that apply to your situation.
Distinguish bootstrapping from its mythology
The episode contrasts Chestnut's preference for simplicity with Hoffman's argument that well-matched investors can contribute experience and confidence. There is no single funding choice for every company. Compare the pace, risks and support you need rather than treating outside funding or self-funding as inherently better.
Look for the repeated request
Chestnut says customers of different sizes all wanted email marketing. Repeated demand pointed toward something more reusable than a different website project every time. Identify which customer problem returns across engagements and whether a shared product could solve it well.
Build the tool you wish you had
His team disliked the available email software and built an internal alternative. That tool began by helping their own client work, not as a fully planned standalone company. Start with a concrete workflow and test whether the improvement helps enough other users to deserve a product.
Remove the friction that limits access
Chestnut links accepting credit cards online with turning the internal tool into a service customers could use directly. Payment and access mechanics changed the business opportunity. Check what still requires manual intervention after the core product works.
Compare the lines of business with actual numbers
He recalls his partner charting Mailchimp's rising revenue against flat or declining consulting revenue. The smaller product accounts were easy to overlook beside large project fees. Compare trends and economics instead of judging an opportunity only by the size of an individual sale.
Recognize that evidence and confidence are different
The founders hesitated for much of a year despite the revenue comparison. Familiar work can feel safer than a growing product, even when the data suggests a change. Decide what additional evidence would justify a shift and what is simply discomfort with leaving the old model.
The Conversation Breakdown
Paying consulting customers
⏱ Untimed topicChestnut describes finding projects as he prepared to start a company.
Funding tradeoffs
⏱ Untimed topicHis preference for bootstrapping is contrasted with Hoffman's view of investor support.
Recurring email-marketing demand
⏱ Untimed topicRepeated client requests revealed a more reusable customer problem.
The internal software tool
⏱ Untimed topicThe team built its own alternative to software they disliked using for clients.
Direct access and payments
⏱ Untimed topicAccepting online payments helped turn the internal tool into a customer-facing service.
Comparing revenue trends
⏱ Untimed topicThe product's growth became clearer when compared with consulting in a spreadsheet.
Hesitation before the shift
⏱ Untimed topicThe founders needed time to move away from large project fees toward smaller repeatable accounts.
Core Frameworks & Ideas
Repeated-request discovery - editorial label
Look for the same customer need across engagements before building a reusable offer.
Internal tool to product - discussed path
Remove access and payment friction so customers can use a working internal tool directly.
Revenue-trend comparison - discussed method
Compare business lines over time rather than only comparing the value of individual sales.
Actionable Next Steps
- ✓List the most repeated request across recent customer work.
- ✓Identify what still needs manual help in your product workflow.
- ✓Chart revenue and costs for two business lines over the same period.
- ✓Write the evidence you would need before changing your main focus.
Notable Quotes
“We wanted to keep it simple and pragmatic.”
“By 2005, we had kind of, sort of forgotten about Mailchimp.”
“We had crazy expectations for the consulting side of our business, and I think that’s why the revenue was always so flat.”
The One Thing to Remember
Compare the product's real growth with the work that merely keeps you busy.