214: Another week, another Wathan

What It Covers

Ben Orenstein and guest Adam Wathan cover Tuple's security audit investment, Tailwind UI's template launch results showing near-zero individual template sales versus strong all-access bundle conversions, remote team communication gaps, fitness accountability services, and potential new revenue streams leveraging Tailwind's distribution.

Key Questions Answered

• •Security as business insurance: Hiring an outsourced security firm at significant monthly cost to audit both the desktop app and internal company practices—SSO, MFA, credential storage, access controls—is framed as paying to avoid a catastrophic breach disclosure email. For desktop app companies with software installed on client machines, this risk category warrants dedicated budget before an incident occurs.
• •Pricing anchoring with all-access bundles: Tailwind UI launched templates at $299 all-access versus $99 individual, and only six individual templates sold post-launch while nearly all revenue came from bundle purchases. The individual option exists purely as a pricing anchor to make the bundle feel like an obvious decision—building the individual purchase flow was necessary even though conversion was essentially zero.
• •Distribution as the primary revenue lever: Tailwind UI generates consistent, reliable daily revenue because tailwindcss.com serves as a permanent top-of-funnel, routing developers searching for components directly to a commercial product. Without a launch-dependent spike, revenue stays steady as framework adoption grows—contrasted with one-time info products that spike at launch and then flatline without active distribution maintenance.
• •Accountability structures replace willpower: Adam lost 25 pounds in seven weeks using MyBodyTutor ($300/month), a remote coaching service requiring daily food photo logs, hunger-scale ratings before meals, and written commitments to next-day activity. The mechanism is pre-commitment: writing down tomorrow's workout the night before creates accountability to a coach who will follow up, making skipping psychologically harder than completing the task.
• •CEO communication architecture requires deliberate design: A framework by Gokul Rajaram identifies weekly or fortnightly CEO emails to the full team—covering top-of-mind priorities, ongoing discussions, and key metrics—as a core responsibility. Without this, engineers have no visibility into what leadership is working on, as illustrated when a direct report asked Ben what he was focused on and had no way of knowing, despite working at the same company.