## Summary Nick from dbt Labs walks through how an open-source company should go to market as commercial software. The core tension is building a beloved open-source product and a viable software business at the same time. He lays out five prerequisites a company must meet before hiring a sales team, plus guidance on who those first sellers should be and how to structure the early customer-facing team. ## Key Points - Building a commercial open-source business is genuinely hard; the open-source product and the business have to advance together. - Five prerequisites before hiring sales: an open-source product people love, a commitment to commercialize it, a clear framework separating open-source from paid features, a working commercial product, and a validated sales hypothesis. - Validate the sales hypothesis before you hire salespeople, not with them. - Don't make your first two sellers junior — they need to already know how to qualify customers and run the sales motion, not learn it on the job. - First sellers should bring startup experience plus domain or open-source background. - Structure the early team as full-cycle and simple, roughly one sales engineer per salesperson, with sellers handling both sales and post-sales support. - Named tactics include starting with self-service, pitching one solution, not selling support contracts, and going single-tenant rather than on-prem. ## Claim Atoms - **Validate the sales hypothesis before hiring sellers** — prove customers will buy before adding a sales team, not test it through the first hires. - **Don't hire junior sellers first** — early sellers should already know qualification and follow-up so you only teach product, buyers, and space. ## Links - Connects to open-source commercialization and product-market-fit threads; dbt Labs as a case study for the open-core-to-commercial transition. - [[3. Resources/Permanent Notes/Free Local Tools Funnel Toward Paid Hosting Tiers]] — applies-in: dbt's prerequisite of a clear open-source versus paid framework is the same funnel design, with the free tool reserving its highest-leverage workflows for the paid tier - [[3. Resources/Permanent Notes/The CRA Open Source Exemption Ends at the First Paid Tier]] — extends: once the company commercializes the project, as dbt's second prerequisite requires, the regulatory exemption for open source stops applying - [[3. Resources/Permanent Notes/AI Erodes the WordPress Plugin Value Props Pushing Monetization Toward SaaS and Services]] — contrasts: the talk says don't sell support contracts, and this note shows AI shrinking the support half of the license-plus-support model - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — applies-in: Joins the pricing and go-to-market cluster.