How did dbt Labs grow? Services, practitioners and shared tools

Consulting provided a bounded customer problem

Tristan Handy describes founding Fishtown Analytics in 2016 after experience at RJMetrics. Early relationships brought growing SaaS and consumer startups, and dbt began as a productivity tool for the consultancy’s work. The interview describes an annualized service price around $60,000, not an early software subscription tariff. [1]

[Inference] This setting could reveal repeated analytics work across customers with similar constraints. It also means the initial economic commitment concerned delivered services. The supplied record does not identify the first paid software contract, so consultancy clients should not be counted automatically as customers of the later platform.

Practitioners carried the tool into new settings

Casper became an early direct user. The founder’s account names people who subsequently brought dbt into other companies or consulting work, including Danny Brown, Michelle Ballen and Scott Breitenother. It also describes meetups and Slack activity. [1][2]

[Inference] This gives community distribution a concrete mechanism. A person who has used a practice can introduce it where they next work and explain its value in context. That is different from treating follower counts as proof of acquisition. The receiving organization still needs to decide whether the practice fits its data work and who will maintain it.

Enablement drew on actual analytical work

Claire Carroll moved from implementing dbt at Airtasker into full-time community work. Her interview describes helping people through Slack, documentation and writing, grounded in experience across SQL, testing, documentation and version control. [2][5]

[Inference] The relevant capability is fluency in the workflow being taught. Community support can translate unfamiliar practices into useful action and reveal recurring product friction. It should not be treated as free labor or as proof that every participant will buy. A stronger assessment would distinguish learning, sustained use and an organizational need for commercial support.

The vendor had to reconsider competing with partners

Handy’s note says services supported the company through November 2019, while growing partners became concerned about competition from the vendor. The company reduced its consulting footprint and shifted more effort toward education and product expertise. [3]

[Inference] This is a real ecosystem tension. Partners may invest less if the platform provider can also compete for their engagements. A clearer boundary can make collaboration more credible, but it also changes the vendor’s revenue and delivery responsibilities. The source does not provide an audited margin comparison proving that the transition was economically effortless.

Enterprise adoption required more than local tool use

The founder interview describes larger organizations needing support contracts. The reviewed platform adds collaboration, governance, multi-project capabilities and priority support, with separate paid packaging and usage allowances. [1][4]

[Inference] An analyst’s successful local workflow is an entry point, not the full organizational purchase. Larger buyers need continuity, shared standards and accountable help. These requirements can support expansion when they solve real coordination problems. However, current platform pricing should not be compared directly with the earlier consultancy fee, because the buyer receives different work and accepts different operating responsibilities.

The lesson is to support the practice around the product

[Inference] dbt Labs suggests that a tool spreads more meaningfully when people can teach the practice that makes it useful. The commercial challenge is to preserve that learning while defining what the vendor, customer and partners each own. CAC, payback and numerical retention are not verified here. A better growth analysis would follow practitioner introductions into sustained organizational adoption and inspect partner conflicts alongside platform bookings. The supplied evidence supports named distribution and enablement mechanisms, but not a claim that community popularity alone explains the company’s financial trajectory.