Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 10: Launch & Distribution — The Engineer-Founder's Weak Point, Honestly Named #

This is the module where the curriculum gets uncomfortable for you in a way the others don't, and I want to be honest about that before you start. Distribution work is foreign to engineering culture in a way pricing and positioning are not. Pricing looks mathematical; positioning looks strategic; both read as serious work to an engineer's eye. Distribution looks like promotion, and in several engineering cultures — many Asian ones notably, but the discomfort is hardly exclusive — self-promotion carries a valence that runs against the grain of the craft. The discomfort is not a sign you're bad at this. It is the cost of a competence you haven't paid for yet, and the module is the bill.

One calibration note that follows: when you launch, you will be implicitly competing against operators who overstate their products' capabilities, and you will probably understate yours by reflex. The first version of your launch copy will be too modest, too qualified, too apologetic — "if you have time, maybe consider checking out..." Rewrite to remove the hedges. This is not a recommendation to overstate; it is a recommendation to state, at the calibration point that matches the product's actual quality, because underclaiming reads as low confidence, which signals low quality, which costs conversion.

You know "if you build it, they will come" is wrong. You've said so, dismissively, about other people's products. And yet you, like most engineer-founders, will operate parts of your launch as if it were true — polishing the product once more, adding one more feature, deferring the announcement until the landing page is "ready," not sending the first cold outreach because "we're not ready for inbound." Each is the failure mode in disguise, and the most reliable tell is comfort displacement: at some point in week one or two, you will find a reason to redesign the landing page instead of sending the first cold email. The reason will be real — there will be something genuinely worth fixing — and the redesign will be more comfortable than the outreach. The fix is not to refuse the landing-page work; the fix is to send the first ten cold emails before doing it. Sequence the discomfort first. And write those ten by hand, not with an automation tool — researched, personalized, thirty minutes each. Automation at the start lets you scale a message you haven't yet figured out; ten manual emails teach you what the message is. Read Kazanjy's Founding Sales cover to cover; it is the founder-led-sales handbook, it is sharper than its modest reputation, and it is free.

The public launch is the largest single deliverable in the entire curriculum, and the spine's diagnostic deserves underlining because it is the most useful paragraph in the module. If you cannot launch within the window, diagnose honestly which failure it is: (a) pricing undecided — go back to M9, decide, return; (b) positioning unclear — back to M3; (c) the product genuinely isn't ready — that's an M1/M5 problem this module can't fix; or (d) the resistance is the actual problem — in which case the module is being avoided, not failed. The four have different remedies and conflating them wastes months. Set the launch date in week two and hold it. The version you launch will be smaller than the version you wanted to launch; that is the point. A launched smaller version beats an unlaunched larger version every day of the week.

Some logistics the literature under-serves. The big launch channels are US-timezone-centric — Hacker News rewards a late-morning Eastern post and four to six hours of comment presence afterward; Product Hunt's clock starts at midnight Pacific — so if you're launching from another continent, block the calendar and treat launch day as a workday, not an evening event. And don't neglect your local founder community in favor of the famous channels: in most non-US tech scenes the community is smaller but more accessible, cold-DM-with-introduction works better than it does in the US, and a local meetup during launch month often outperforms a forum post into the void. Expect grim hit rates everywhere and recalibrate what grim means: ten hand-written cold emails producing one or two demos and zero or one close is normal by sales standards. The grimness is the rate, not a referendum on you.

The deepest thing this module has to teach is that distribution is a cadence, not an event. Most engineer-founders do the launch, exhale, and return to building; the channel work decays to nothing within a month, and they re-engage only when revenue stalls. The distribution-cadence document — weekly content, weekly outreach batches, weekly community presence, reviewed quarterly — is the artifact that fights the decay. I'll close with the bluntest sentence I have for this module: willingness to do unglamorous distribution work persistently is the most reliable discriminator between engineer-founders who build businesses and engineer-founders who build beautiful products nobody uses. Not talent, not taste, not technical skill — those are roughly equivalent across both groups. The willingness is partly temperament and partly learned. The module assumes you can learn it. Most people can.

Conclusion #

Module 10 is the most uncomfortable module in the curriculum and the most important for actual revenue. The build-it-and-they-will-come failure mode operates on you despite your knowing better; the corrective is the public launch, ten hand-written cold emails sent before the landing page gets another pass, and a distribution cadence that outlives launch day. The discomfort is the cost of competence, and paying it is the discriminator.

Predictions #

  • You will find a reason to redesign the landing page before sending the first cold email. The reason will be real; the substitution is the resistance. Send the emails first.
  • You will defer the launch by at least a week past the date you set. The deferral will feel like preparation; diagnose it against the four-way test instead.
  • The first ten cold emails will produce 1-2 demos and 0-1 closes. Grim by engineering standards, normal by sales standards.
  • At least one channel you bet on will fail meaningfully, and the failure will be information about your customer profile, not about you. The launch retro must name the ICP assumption that broke.
  • Your first launch copy will be over-hedged, and someone else reading it will spot the apologies faster than you do. Have someone else read it.
  • After the module, your distribution work will decay to 30-50% of launch-month pace within weeks. The cadence document is the corrective; whether you re-read it weekly is the test.
  • You will not enjoy this module. The work compounds anyway; the discipline is doing it while not enjoying it.