Get AI summaries of any video or article — Sign up free
Founder Fridays: Build for Yourself with Raphael Schaad, Founder of Cron and Owais Khan, PMM, Notion thumbnail

Founder Fridays: Build for Yourself with Raphael Schaad, Founder of Cron and Owais Khan, PMM, Notion

Notion·
6 min read

Based on Notion's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Start with a narrowly useful “toy” feature for a real person—often the founder—and treat early usefulness as proof of market resonance.

Briefing

A practical path to scaling a “broad” product category starts with building something sharply useful for one real person—then stacking outsized value on top of existing infrastructure. Raphael Schaad, founder of Cron (acquired by Notion), describes how a calendar market that seems impossible to tackle at scale became manageable by treating the early product as a toy: a small, personal fix that solved a specific annoyance. In his case, that meant collapsing the empty overnight hours in Google Calendar via a Chrome extension. The add-on quickly attracted thousands of users overnight, signaling that the problem wasn’t unique to him and that a focused wedge could grow into a much larger product.

That “build for yourself” approach is paired with a second principle: don’t try to build the whole category at once. Schaad argues that solo founders should apply pressure where value can be created with minimal engineering—adding “1%” features that capture a large share of the experience. For Cron, that meant standing on the shoulders of Google Calendar rather than rebuilding scheduling from scratch. He used Electron to wrap Google Calendar into a desktop environment, then focused on high-leverage workflow improvements during the Zoom era—extracting Zoom links and delivering timely notifications so meetings started on time instead of arriving late through email. The broader lesson: in big markets, the fastest route to traction is often finding the right point in the value stack to deliver a small but meaningful upgrade.

Cron’s early growth also hinged on go-to-market design, not just product quality. Schaad says the launch moment mattered less than what followed, and he pursued a deliberate channel strategy: invest ruthlessly in a small set of channels and become “an 11 out of 10” in them. At the time, that meant email and Twitter, with no LinkedIn and no paid marketing. Email wasn’t treated as generic lifecycle onboarding; it became a product update ritual built around beautiful, regular change logs. Those emails were written in the language users used in bug reports and feature requests, and they were structured to invite replies—no no-reply addresses—so feedback flowed back into the product. Twitter then acted as the amplification loop: change logs linked to tweets and videos, and users responded across both channels, creating a feedback-and-excitement cycle.

The same philosophy shows up in how Notion approaches “release marketing.” Schaad highlights the power of closing loops: when users request features, the founder tracks them and later sends personalized updates when those changes ship. Even at early stages, that kind of non-scalable attention can create “thousand true fans,” and tools (including AI and outbound platforms like Outreach) can help scale personalization without turning the brand generic.

Finally, the conversation connects Cron’s acquisition by Notion to a larger product strategy. Notion’s “Lego blocks for software” metaphor frames Cron as a missing piece around time and calendar, enabling Notion to expand into a connected workspace that now includes email and calendar. Looking ahead, Schaad’s advice for 2025 is to focus on distribution—the scarce resource when AI makes building cheaper—and to keep early execution grounded in fast iteration, thoughtful narrative, and design-level attention from day one.

Cornell Notes

Raphael Schaad credits Cron’s rise to a disciplined wedge: start with a toy-like feature that solves a personal problem, prove it resonates with real users, then build outward. For Cron, that began with a Chrome extension that collapsed empty overnight hours in Google Calendar, quickly reaching 10,000+ users. He then avoided rebuilding the entire calendar category by using Electron to wrap Google Calendar and adding high-leverage workflow value for Zoom-era meetings. Growth depended on go-to-market as a design problem: he invested heavily in email and Twitter, using beautiful, reply-friendly change logs that mirrored user language and created a feedback loop. At scale, he argues for closing loops on shipped features—personalized early, then supported by tools—to preserve brand identity and drive word of mouth.

Why did building “for yourself” help Cron scale beyond one user?

Schaad’s core idea is that solving a real personal pain is a strong signal because founders aren’t uniquely different. If a feature is genuinely useful to one real person (often the founder), it’s more likely to match the needs of others with similar workflows. Cron’s early example was a Google Calendar tweak—collapsing empty overnight hours—packaged as a Chrome extension. It started as a personal annoyance fix, then attracted thousands of users, showing the problem was shared.

How can a founder tackle a huge category like calendar without building everything from scratch?

Schaad recommends applying pressure to a small surface area in the value stack and capturing outsized value with minimal engineering. Instead of building a full calendar system, he wrapped Google Calendar in Electron to gain desktop-like advantages (native notifications, a more integrated experience) and then focused on a narrow, high-impact feature: extracting Zoom links and sending timely meeting notifications. The goal was to harness much of the existing calendar’s value while adding a small “1%” capability that mattered a lot.

What made Cron’s early marketing channels work so well?

Schaad treated channel selection as a ruthless strategy: invest in a few channels and ignore the rest. He concentrated on email and Twitter, avoiding LinkedIn and paid ads. Email became a product-update engine—beautiful, regular change logs tied directly to shipped features. He used custom HTML templates and wrote in the same wording users used when requesting features. Crucially, the emails invited replies (no no-reply addresses), turning updates into a two-way feedback channel that fed the product.

How did Cron’s change logs connect to Twitter and user feedback?

Change logs were designed to create a ping-pong loop between email and Twitter. Emails linked to tweets and often included the tweet as the “hero image,” including videos demonstrating features. Users who replied with bug reports or feature requests could also follow and engage on Twitter, which amplified excitement while keeping feedback flowing back through support and product machinery.

What does “closing loops” mean, and why does it matter for retention and word of mouth?

Closing loops means reaching back out after a user request is implemented. Schaad describes tracking feature requests and later emailing users when the change ships—sometimes months later—so the user sees their feedback translated into a specific shipped outcome. He says reactions were “over the top” because it contradicts the usual experience of sending feedback and never hearing back. Early on, this non-scalable attention helps build a base of “true fans,” and later tools can support personalization at higher volume.

How did Cron fit into Notion’s broader strategy after the acquisition?

Schaad frames Notion as building “Lego blocks for software,” and Cron as a missing block around time and calendar. Cron’s calendar capabilities helped Notion evolve into a multi-product, connected workspace—paving the way for additional products like email and calendar. The acquisition also aligned with a broader go-to-market and monetization path: Notion had already figured out monetizing docs/wiki-style use cases, while Cron’s calendar could monetize adjacent value rather than charging for calendar itself.

Review Questions

  1. What specific personal problem did Schaad solve first, and what evidence suggested it could scale beyond his own needs?
  2. How did Electron and the Zoom notification workflow illustrate Schaad’s “value stack” approach to building in big markets?
  3. Why did Cron’s change logs function as both marketing and product feedback, and what design choices made that possible?

Key Points

  1. 1

    Start with a narrowly useful “toy” feature for a real person—often the founder—and treat early usefulness as proof of market resonance.

  2. 2

    In large categories, avoid rebuilding the whole product; add a small, high-leverage capability on top of existing systems to capture outsized value.

  3. 3

    Channel strategy is a design problem: pick a few channels to own, invest heavily to become exceptional, and ignore the rest.

  4. 4

    Make product update emails bidirectional by inviting replies (no no-reply addresses) and using user language from support and feature requests.

  5. 5

    Use change logs and release marketing to connect shipped work to existing users, turning updates into word-of-mouth fuel.

  6. 6

    Close the feedback loop by notifying users when their requests ship; early personalization builds “true fans,” while tools can later support scale.

  7. 7

    When AI makes building cheaper, distribution becomes the scarce resource—plan for it from day one.

Highlights

Cron began as a Chrome extension that collapsed empty overnight hours in Google Calendar—an annoyance fix that quickly reached 10,000+ users.
Schaad’s “1% feature” approach: wrap Google Calendar with Electron and focus on Zoom-era meeting notifications instead of rebuilding scheduling from scratch.
Cron’s change logs weren’t generic marketing; they were beautiful, reply-friendly product updates written in the same language users used to request features.
Closing loops—emailing users when their feedback ships—created unusually strong reactions and helped build a base of true fans.
Schaad frames Cron’s acquisition by Notion as adding a missing “time and calendar” Lego block to a connected workspace strategy.

Topics

  • Founder Advice
  • Product Wedges
  • Go-To-Market
  • Release Marketing
  • Calendar Workflow

Mentioned