Video summary

The Man Behind Blender, Ton Roosendaal | Bad Decisions Podcast #69

Main summary

Key takeaways

Business

Business/strategy summary (Blender as a company/community model)

Mission-led business strategy (not growth-at-all-costs)

  • Blender’s leadership explicitly optimizes for “better users”—people who can produce professional results and earn a living—not just for more users.
  • Core purpose: enable independent creators and studios to participate in the economy by lowering the production barrier.

Three-part mission (business execution principles)

  1. Free/open software
    • Blender must stay free, with no licensing “strings attached” (users must accept the freedom premise).
  2. Production pipeline + information
    • Software alone isn’t enough—Blender supports studio productivity through pipelines, assets guidance, and information that makes people effective.
  3. Participation in the economy
    • Reduce dependency on closed Hollywood pipelines by enabling monetizable production for smaller teams.

Independence & “hand the economy to the community”

Blender avoids “obvious business things” that would compete with the ecosystem:

  • No monetizing Blender’s own teaching/content
    • e.g., YouTube monetization disabled
  • Avoids selling services/support/add-ons directly
    • Instead, supports community monetization (tutorials, plugins, tools, marketplace behaviors)

Rationale: give users a level playing field and prevent an “unfair advantage” by the software producer.

Open-source governance approach

Blender leadership treats open collaboration as an equal partnership, not a vendor relationship:

  • If a company needs specific features, they’re expected to join the project and contribute, rather than buying fixes while keeping internal knowledge proprietary.
  • Roadmap direction is driven by:
    • community gaps and where development is stuck
    • not only what the Blender Foundation wants

Frameworks / playbooks / operating processes mentioned

Roadmap prioritization process (explicit approach)

  • Blender Foundation monitors community activity (bugs, fixes, development modules).
  • It identifies areas lacking movement or insufficient developers.
  • Priority work protects core stability and productivity:
    • Core architecture (e.g., undo system, file saving, Python API) is treated as “must not break.”
  • External innovation is leveraged:
    • Community contributions can deliver major innovations
    • Example: Grease Pencil + Geometry Nodes workflows (the “GP revolution”).

Decision rule for feature intake from contributors

  • Ask: “What is the user benefit?”
  • Leadership discourages refactoring/rewrite without measurable value.

Org scaling principle

  • As Blender grows, keep teams small.
  • Plan to split into separate entities/groups once headcount thresholds are exceeded (example: >100 people).

Founder “make yourself obsolete” management doctrine

Leadership reduces founder dependency and bottlenecks by:

  • Delegating to a management team (4 people noted)
  • Shifting toward a supervisory/consultative role instead of day-to-day execution

Concrete examples / case studies

Historical monetization + ownership outcome (major strategic pivot)

  • Early years: Blender shifted from freeware to trying a services-based business model.
  • It raised roughly €5M–€6M in investor funding over about two years.
  • The business failed after the internet bubble burst, and investors effectively took control.
  • Inflection: investors planned to lock Blender away (prevent its continued use).

Response: Blender Foundation initiative + community buyback

  • Published a plan requesting community funds to secure rights.
  • Target mentioned: ~€100,000 (≈ $110,000) for an option/buyback mechanism.
  • Result: money raised within ~7 weeks
    • Using early crowdfunding tactics (blogs/press + community perks like t-shirts)
  • Claim: an early instance of the community buying back software, and it has not happened again in a similar form.

Independence enabling enterprise-adjacent adoption

Evidence of institutional adoption:

  • ILM contributing code to Blender (cited as a major announcement)
  • Big studios producing Pixar-class quality content starting from small studios/individuals

Cross-industry adoption:

  • Engineering/design/manufacturing uses (e.g., car design teams wanting Blender for speed and results)
  • Unexpected domains, including:
    • satellites/aerospace
    • fashion/design
    • dentistry
    • medical simulations

Product direction examples for future “market access”

  • Real-time, physics-driven note-based editing
    • Continuous playback to reduce baking and iteration time
  • Interactive state/logic editing
    • Characters reacting, walking, interactions saved as shareable “app templates”
  • “Application templates” concept
    • Blender files acting like installable mini-applications
    • Open a blend file → launch an experience with minimal/no UI
    • Intended use cases:
      • arch walkthroughs
      • immersive museum experiences
      • product presentations
      • product/3D printing utility apps

Community innovation examples (community-driven R&D)

  • Grease Pencil → Geometry Nodes workflow
    • Converting 2D drawings into 3D animated characters
  • Community demos on iPad for fast visual effects/simulations

Key metrics / KPIs / targets (as stated)

Funding / economics metrics

  • Investor money: €5M–€6M over ~two years
  • Community buyback target: €100,000 (≈ $110,000)
  • Time to raise community money: ~7 weeks
  • Team size for Blender production:
    • 16 people under contract
    • funded by donations + subscriptions
  • Scale comparison (benchmarking mentioned):
    • EA cited as ~20,000 employees
    • references to firms with ~100,000 employees (general comparison)

Operational targets / timelines

  • Ongoing yearly targets tied to roadmap planning
  • “In a couple of years” referenced for completing real-time physics + interaction editing concepts
  • Long-term vision hypotheticals around 2027/2028/2029

Marketing/market access positioning (execution-focused)

How Blender “gets access to the market”

Not via chasing raw user count, but by ensuring users can:

  • Produce market-grade content
  • Use templates/apps to package experiences/outputs for buyers
  • Participate economically (jobs, hiring, freelancing, small business creation)

Distribution channel strategy (implicit)

  • Community tutorials and YouTube form a natural funnel
    • New users learn Blender and can reach studios/production workflows without formal gatekeeping
  • By disabling Blender monetization, Blender positions community creators as the monetizable vendors
    • Strengthens ecosystem trust

AI: high-level execution implications (not investing/market predictions)

AI adoption stance

  • Blender is interested in AI that is local/private and integrated into workflows.
  • Not cloud systems requiring massive compute.
  • Example described:
    • A Stanford PhD demo using Geometry Nodes where an AI tool learns from local edits and Python commands to accelerate repetitive tasks.

Core requirement: copyright/excellence

  • Blender emphasizes respecting artists’ work.
  • Avoid degrading outputs into “average”/low-quality results.

Strategic direction

  • AI pipeline workflows are “on the plan,” but not yet tangible
  • Waiting for sufficiently applicable technology

Leadership/organization tactics

Reduce founder bottleneck

  • Founder aims to become “obsolete” (not dependent on personal execution)
  • Management structure includes a 4-person management team
    • Francisco noted as driving business development/industry relations

Communication management tactic

  • Founder avoids meetings due to energy/hearing disability
  • Prefers small discussions; new team uses summaries to reduce meeting burden

Presenters / sources

  • Ton Roosendaal (Founder/leader behind Blender)
  • Andrew Price (referenced as a “marketing guy” during discussion; not otherwise shown as a primary on-air speaker in the subtitles)

Original video