Get AI summaries of any video or article — Sign up free
Founder Fridays: The Side Project that Became a Startup People Needed with Steve Ruiz of tldraw thumbnail

Founder Fridays: The Side Project that Became a Startup People Needed with Steve Ruiz of tldraw

Notion·
5 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

Teal Draw positions infinite-canvas/whiteboard UX as reusable infrastructure so smaller teams can ship without building complex canvas mechanics from scratch.

Briefing

Infinite-canvas infrastructure is becoming a commodity—and Teal Draw’s rise shows how a developer-first “side project” can turn into a startup people actually need. Steve Ruiz built Teal Draw as an open-source SDK for creating whiteboards and similar infinite-canvas experiences on the web, betting that what used to require expensive, specialized teams would eventually be expected as a plug-and-play feature inside productivity tools. That thesis mattered because map-like complexity and design-tool UX patterns (resizing, interaction behaviors, canvas mechanics) are notoriously hard to get right—and even when teams solve them, users rarely notice the underlying platform. Teal Draw aimed to make that hard foundation reusable so smaller teams could ship creative, canvas-based products without years of engineering.

Ruiz’s path to product-market fit didn’t start with a grand plan. He arrived at the idea through earlier experiments in “pressure sensitive digital ink” and arrow/ink algorithms, then consolidated those efforts into Teal Draw around 2021 as an open project. Building in public wasn’t just marketing; it mirrored studio practice—sharing work-in-progress, soliciting feedback, and connecting with people who might become users, customers, or collaborators. The open-source framing also changed the demand curve. Once Teal Draw shifted from scattered prototypes to a coherent SDK, developers and companies began emailing for early access, asking to sponsor work on GitHub, and in some cases offering money for access to the code.

The inflection point came when larger organizations started treating the SDK as a strategic dependency. Ruiz described corporate interest tied to upgrading conferencing and collaboration tools—essentially, replacing or enhancing whiteboard capabilities with something built on an infinite canvas. Sponsorships accumulated quickly (over $200,000 before fundraising), and the project’s public release (MIT-licensed code) triggered strong responses from both individuals using the demos and startups building canvas-based apps. That traction was enough to justify a seed round completed in about three weeks, even though direct revenue lagged for roughly a year and a half.

Teal Draw’s business model has evolved through multiple iterations, but the current structure centers on licensing for production use. Developers can use the SDK in development without paying, while deploying it into production requires an annual license—priced as a license rather than based on user count or team size. Ruiz emphasized that “business model fit is hard,” and there’s no simple template to copy.

Community growth, in his view, leans more “vertical” than “horizontal”: fewer community members than followers, but a steady stream of updates, experimental features, and customer projects shared over time. AI became a major accelerant. A designer at Figma, Sawyer Hood, used Teal Draw to turn a drawn website into HTML/CSS via GPT-4 with Vision, then embedded the result back onto the canvas. The workflow evolved into markup-on-top-of-generated websites, which went viral in late 2023 and helped non-technical users experience “draw → software” for the first time.

For founders, Ruiz’s core advice is to keep the surface metrics clear—shipping on time, closing deals, tracking deal size—while allowing the path to be messy. Early on, the most reliable strategy is to try things quickly, abandon them fast, and “worm” toward what connects with real demand rather than over-committing to a single plan.

Cornell Notes

Teal Draw is an open-source SDK for building infinite-canvas whiteboards on the web, designed to remove the heavy engineering burden behind design-tool UX patterns. Steve Ruiz built it by consolidating earlier experiments in digital ink and visual interaction, then released it in public so developers could follow progress, request access, and shape direction. Demand shifted dramatically once the SDK became coherent: individuals sponsored it, larger companies asked to build on top of it, and Ruiz raised a seed round quickly after public launch. The business model centers on annual licensing for production use while keeping development use free. Community growth is “vertical” (updates and customer projects) and AI features—like drawing a website and generating HTML/CSS—helped drive mainstream attention and adoption.

Why did Teal Draw focus on being an “infrastructure” layer rather than a standalone whiteboard app?

Ruiz argued that infinite-canvas features are becoming commodity expectations inside productivity tools, similar to how maps are handled by specialized providers. Teams can buy map infrastructure (Mapbox/Google Maps) instead of building maps themselves; likewise, Teal Draw provides the reusable canvas mechanics and design-tool UX patterns (like resizing and interaction behaviors) so other products can ship without hiring large teams or waiting years.

How did building in public contribute to Teal Draw’s early traction?

Ruiz treated public sharing as an extension of studio practice: sharing work-in-progress, inviting feedback, and connecting with people who might become users or customers. He also described “search-by-sharing” dynamics—blogging or posting functions like a high-effort discovery mechanism for finding a community interested in the same problem. That approach helped convert followers into early adopters and sponsors.

What was the key inflection point that turned Teal Draw from a side project into a business?

The shift from precursor projects (arrows/ink algorithms) into a single open-source SDK created a step-change in interest. After the SDK existed as a coherent toolkit, developers and companies began emailing for early access, and GitHub sponsors requested access. Larger organizations then approached Ruiz about upgrading conferencing/whiteboard capabilities, including offers for paid early access.

How does Teal Draw’s licensing work, and what does it imply about its go-to-market?

Ruiz described a production-focused license: developers can use the SDK in development/locally without paying or contacting him, but deploying it into production requires an annual license. Pricing isn’t based on user count or team size; it’s a license model. That structure suggests Teal Draw targets teams shipping real products rather than charging for experimentation.

What role did AI play in Teal Draw’s adoption and virality?

AI wasn’t built into Teal Draw’s core experience, but the canvas enabled AI workflows on top of it. A Figma designer, Sawyer Hood, used Teal Draw to draw a website, then sent the result to GPT-4 with Vision to generate HTML/CSS, embedding the output back onto the canvas. The workflow later expanded into drawing markup on top of generated websites, which Ruiz said went viral in November 2023 (Make Real), giving many people their first “non-technical to working software” experience.

What advice did Ruiz give founders about decision-making early on?

He emphasized tracking the outcomes that matter—shipping on time, making deals, and deal size—while accepting that the path to those outcomes can feel random. His practical guidance was to try things, give up quickly, and “worm” toward what connects with real demand, especially when searching for product-market fit.

Review Questions

  1. What engineering problems does Teal Draw aim to eliminate for other product teams, and why are those problems often invisible to end users?
  2. How did the transition from scattered open-source experiments to a unified SDK change the type and scale of inbound demand?
  3. Why might a “vertical” community strategy (updates and customer projects) work better for Teal Draw than building a large horizontal community?

Key Points

  1. 1

    Teal Draw positions infinite-canvas/whiteboard UX as reusable infrastructure so smaller teams can ship without building complex canvas mechanics from scratch.

  2. 2

    The product-market fit path came from consolidating earlier ink/visual interaction experiments into a coherent open-source SDK released in public.

  3. 3

    Building in public functioned as both feedback collection and discovery, turning followers into sponsors, early adopters, and eventually corporate partners.

  4. 4

    Corporate interest accelerated when larger organizations treated Teal Draw as a dependency for upgrading conferencing and collaboration tools.

  5. 5

    Teal Draw’s licensing model keeps development use free while charging an annual license for production deployment, not based on user count or team size.

  6. 6

    AI adoption grew through integrations built on top of the canvas—drawing a website and generating HTML/CSS with GPT-4 with Vision—rather than through built-in AI features.

  7. 7

    Early-founder guidance centered on outcome metrics (shipping, deals, deal size) while iterating quickly and abandoning ideas fast to find product-market fit.

Highlights

Teal Draw was built as an open-source SDK to make infinite-canvas features “commodity,” reducing the need for years-long engineering efforts like those behind major design tools.
Sponsorship and corporate requests surged once the SDK became coherent, with larger companies paying for early access and considering Teal Draw for whiteboard upgrades.
A workflow using Teal Draw + GPT-4 with Vision let users draw a website and generate HTML/CSS, then embed the result back onto the canvas—driving viral attention in late 2023.
Ruiz’s licensing approach separates experimentation from deployment: free development use, annual production licensing.
Founder advice boiled down to trying things quickly, giving up fast, and steering toward what connects with real demand rather than over-planning early moves.

Topics

Mentioned

  • Steve Ruiz
  • Sawyer Hood
  • SDK
  • MIT
  • ETA