The list was the product
Ruchin Kulkarni’s guest post in First 1000, published February 8, 2022, opens with a blunt idea: when money is tight, you cannot wait for a perfect growth loop to arrive. The Retool example in the issue describes a target list of 10,000 companies, expanded into roughly 40,000 individual contacts, followed by founder-led outbound and a reported 8% response rate. The post says that work produced early adopters and a $1.5 million enterprise pilot; those are source-reported historical figures.
The useful part is the operating shape. Pick a narrow customer profile, build the list, contact the humans who own the problem, and learn from every response. “Brute force” is not random activity. It is a temporary system for converting uncertainty into conversations.
Show the product before the deck
The Twilio story in the issue has a different surface but the same logic. Jeff Lawson reportedly demoed the product live by building a working conference call in front of developers. The point was not theatre. It let the audience experience the thing before they had to believe a category description.
A live demo, a small installation, a teardown of a customer workflow, or a working sample can all do the same job. The proof should arrive before the buyer has to understand your entire company. Early sales work is often a sequence of smaller belief changes.
Give the effort a boundary
The issue also includes historical examples from Atlassian’s low-budget conference tactic, Tinder’s campus parties, ClickUp’s relentless content cadence, Algolia’s time-zone adaptation and Stripe’s founder-led installations. They are not instructions to copy beer stunts, fake identities or any tactic that misleads people. They show a broader rule: early distribution is often designed around the place where a specific buyer already gathers.
The danger is turning “brute force” into permanent founder exhaustion. Set a boundary: a number of accounts, a number of demos, a fixed learning question, and a date to decide whether the channel deserves more work. Otherwise activity becomes a substitute for a business model.
The default-alive operating review
Ask:
- Which exact customer profile is the team pursuing this week?
- What list, room, workflow, or community already contains those people?
- What proof can the founder put in front of them before the pitch?
- What response or revenue event counts as learning?
- When does this manual motion earn automation, hiring, or a stop?
The takeaway
Default alive is not optimism about the runway. It is a bounded operating system that turns founder effort into customer proof before the cash runs out.
Sources and original research
Adapted from Brute Forcing Your Way to “Default Alive”, a guest post by Ruchin Kulkarni in the February 8, 2022 First 1000 issue. Retool, Twilio, Atlassian, Tinder, ClickUp, Algolia and Stripe examples are source-reported historical accounts; no current company result or recommendation to copy deceptive tactics is claimed.
Updated September 21, 2026. Based on original First 1000 reporting and the sources listed above.