HubSpot scales AI coding tool adoption to near-universal across its engineering organization
HubSpot's engineering organization needed to scale AI coding tool adoption beyond early POCs and early adopters, but faced exploding demand causing backlogs, conservative guardrails requiring individual license requests, cost concerns, and internal skepticism about AI's safety impact on production.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Executive push to evaluate Copilot
Founders Dharmesh and Brian pushed the engineering team to evaluate GitHub Copilot after Dharmesh had a good experience using it to build ChatSpot.
HubSpot achieved near-universal AI coding tool adoption across engineering, surpassing 90% adoption, with data showing no correlation between AI adoption and production incidents, and built Sidekick plus 400+ tools for agents.
What failed first
HubSpot initially relied on teams already managing their GitHub setup to drive AI adoption, but as demand exploded the backlog became unmanageable; procurement processes built for long-term contracts also slowed rapid evaluation of new tools.