{"id":3286,"date":"2026-04-28T13:30:04","date_gmt":"2026-04-28T13:30:04","guid":{"rendered":"http:\/\/fliegewiese.org\/?p=3286"},"modified":"2026-04-30T11:51:51","modified_gmt":"2026-04-30T11:51:51","slug":"how-we-operate-as-an-ai-first-company","status":"publish","type":"post","link":"http:\/\/fliegewiese.org\/index.php\/2026\/04\/28\/how-we-operate-as-an-ai-first-company\/","title":{"rendered":"How we Operate as an AI-first Company"},"content":{"rendered":"

This is part three of a three-part series on how HubSpot transformed with AI. Part one covers how we build with AI. Part two covers how we grow with Agent-first GTM.<\/em><\/p>\n

Building the right engineering platform<\/a> and rebuilding your go-to-market motion<\/a> are meaningless if the organization running them isn\u2019t ready. That\u2019s the part most transformation playbooks skip. It\u2019s also the part that determines whether any of it sticks.<\/p>\n

We didn\u2019t skip it; we doubled down. As a result, 94% of HubSpotters use AI weekly, employees have built over 3,900 AI agents, and our talent profile looks fundamentally different than it did three years ago.<\/p>\n

This is our playbook for HubSpot\u2019s organizational transformation that made everything else possible.<\/p>\n

\"key<\/p>\n

 <\/h2>\n

Stage 1: Building AI Fluency (2023\u20132025)<\/h2>\n

The first stage is about fluency across the entire organization, and it has to start with commitment from the top. Leaders have to model the behavior, share their own experiments, and create the conditions for everyone else to follow, not mandates.<\/p>\n

We ran three plays to get there, and each is repeatable for any organization:<\/p>\n

Provide the t<\/strong>oolset<\/strong>.<\/strong> Every HubSpotter received enterprise licenses for a core set of AI tools. A central AI strategy team manages vendor relationships, sets security standards, and streamlines adoption of new tools, which eliminates procurement and security bottlenecks that slow transformation at most companies. AI fluency can\u2019t be a competitive advantage you reserve for certain teams. It has to be a baseline expectation for all teams.<\/p>\n

Shift the mindset. <\/strong>This included fostering a culture of experimentation, in which employees feel empowered to try and to embrace new ways of working. We updated our company values to encourage this perspective, adding \u2018be bold, learn fast\u2019 as a core value. Employees share use cases and experiments in dedicated chat channels. Leaders participate alongside their teams, often getting reverse-mentored by people further along in their experimentation, and executives share their own learnings in weekly updates. We also changed our organizational clock speed, moving from annual planning cycles to six-week sprints to keep pace with the technology.<\/p>\n

To track our progress, we also set a clear, company-wide usage goal: 80% weekly active AI usage by the end of 2025. Then we tracked it openly \u2014 by team, by tool, by use case \u2014 and made the data visible to everyone. Transparency drove accountability in both directions: teams that were behind had a clear signal, and teams that were ahead became models for others.<\/p>\n

We want to be clear about why we tracked usage rather than outcomes at this stage. Stage 1 was about building AI fluency. You can\u2019t measure outcome improvement from tools people aren\u2019t using yet. Usage was a leading indicator, not the destination. This wasn\u2019t tokenmaxxing; it was a necessary step on the way to outcome-maxxing<\/a> in Stage 2.<\/p>\n

Build the skillse<\/strong>t<\/strong>.<\/strong> We carved out protected time for learning. This included hackathons and 20 company-wide AI learning days in 2025. AI was woven into onboarding from day one and into ongoing manager development. The goal was simple: shift the question from \u201cshould I use AI for this?\u201d to \u201chow do I use AI better?\u201d<\/p>\n

The outcome of Stage 1 was a new talent profile. By the end of this stage, we had an organization that was becoming AI-fluent, with 94% of HubSpotters using AI weekly, with over 3,900 AI agents created by employees to improve their own work.<\/p>\n

Stage 2: Team-Level Transformation (2025\u2013Present)<\/h2>\n

When employees each use AI in different ways for different use cases, you get individual productivity but not business outcomes. To achieve team-level transformation, you need clear priorities with real accountability behind them.<\/p>\n

To start, we plotted teams against two dimensions:<\/p>\n

    \n
  1. AI maturity<\/strong>: How have they adopted tools? Are they seeing measurable outcomes?<\/li>\n
  2. AI readiness<\/strong>: What\u2019s the potential of the team\u2019s work for automation? Is there business risk? Are the data infrastructure and AI capabilities there to support?<\/li>\n<\/ol>\n

    That analysis produced three categories for us: Pace setters<\/strong>, or teams that were already moving fast. We don\u2019t want to slow these teams down; we want to support them. Near-in wins<\/strong>, or teams that have obvious automation opportunities but haven\u2019t acted. The bottleneck for these is almost always leadership attention, not tooling. And lastly, Big bets<\/strong>. These are the teams with highest potential but the most dependencies. They need dedicated investment in data, systems, and change management.<\/p>\n

    Here\u2019s where our teams fell, each requiring a different playbook:<\/p>\n

    \"scatter<\/p>\n

    Pace setters: Engineering, Support, and Marketing<\/strong> had already seen major productivity and efficiency gains through proven AI use cases, leadership sponsorship, and measurement. They needed minimal support and continued their momentum through AI fluency investments.<\/p>\n

    Marketing is the clearest example. The team reimagined workflows across the board: AI-powered email personalization drove an 82% improvement in email conversions, an AI chatbot now handles over 82% of website inquiries and generated 10,000+ sales meetings per quarter by Q4 2025. A video ad production test delivered AI-generated spots at $300\u2013$3,000 versus $300K\u2013$500K with traditional production, and AI-assisted blog production cut writer hours per article by 60%.<\/p>\n

    Near-in wins: Recruiting and Operations<\/strong> had clear automation opportunities that could be unlocked with the right tools. The key lever was leadership attention: \u201cgemba walks,\u201d getting into the work alongside teams to identify exactly where AI could replace or augment specific tasks, and driving adoption hands-on rather than from a distance.<\/p>\n

    An example of this is Talent Acquisition. By embedding AI directly into the hiring funnel, we saw a 10-day reduction in time to hire and a 30% reduction in application review time. We fully automated 80% of interview scheduling tasks, resulting in a 90% increase in scheduling volume with no additional headcount. The share of sourced hires from past candidates grew from 8% to 18% in the first 90 days, a direct result of AI resurfacing talent that would have otherwise been invisible.<\/p>\n

    Big bets<\/strong>: <\/strong>Sales, <\/strong>C<\/strong>ustomer Success, and Product <\/strong>has the highest potential but needed significant investment in data, systems, and change management. These teams received dedicated AI pods, cross-functional teams of functional experts, data scientists, and ops engineers focused on reimagining specific workflows through rapid experimentation and iteration.<\/p>\n

    The deeper lesson of Stage 2 is that not every team needs the same support. The maturity and readiness analysis is what tells you where to push, where to support, and where to invest. Without it, you end up applying the same approach everywhere and wondering why only some of it works.<\/p>\n

    Stage 3: Institutional Transformation (2026 and Beyond)<\/h2>\n

    We are early in Stage 3. But the direction is clear, and it will be the most important stage of all.<\/p>\n

    Stages 1 and 2 solved for individual and team productivity. Stage 3 is about building institutional AI. The distinction matters. Making every employee 10x more efficient doesn\u2019t make a company 10x more productive, unless the institution itself is redesigned around new AI capabilities.<\/p>\n

    The foundation of Stage 3 is institutional context. It means giving everyone access to the right tools, data, and information, and encoding company processes into agents that can act on them at scale.<\/p>\n

    The difference becomes visible in how work gets done day to day. When an engineer needs context on a codebase, they don\u2019t ask a colleague; they ask HubSpot\u2019s internal coding agent. When a sales manager wants to understand why a deal stalled, they don\u2019t pull a report; they ask our native Guided Selling Assistant. When a new hire needs to understand how HubSpot makes decisions, they don\u2019t wait for onboarding; they ask our internal AI tool. That is what institutional AI looks like in practice: the collective context of the organization, available to everyone, at the moment they need it.<\/p>\n

    Moving to this stage also requires confronting questions that earlier stages don\u2019t. When agents own steps in a workflow end-to-end, governance matters more. Who can see what? What decisions require human sign-off? How do you catch bad outputs before they compound? We\u2019ve had to build for these questions deliberately, establishing clear permissions, audit trails, and escalation paths so that the speed of agents doesn\u2019t outpace our ability to oversee them.<\/p>\n

    We are still on this journey. But we understand what\u2019s at stake. The companies that build institutional AI are the ones that will have an advantage. But to do it, don\u2019t start with AI. Start with the work. Find the workflow that\u2019s slow, expensive, or brittle. Find the team that is most ready. Run the experiment, measure it honestly, then commit to what the data shows.<\/p>\n

    AI transformation starts with a strong foundation<\/h2>\n

    The same principle runs through everything in this series: the tools are just the starting point. Building the foundation \u2013 technically, structurally, and culturally \u2013 is what allows you to scale.<\/p>\n

    \"CR-0442_AI-Transformation-Blog-Series_V3-SeriesClose_R2\"<\/p>\n

    In engineering, that foundation is a platform. In go-to-market, it\u2019s a flywheel. In how you operate, it\u2019s the organization itself. The companies that figure this out won\u2019t just use AI better, they\u2019ll grow better.<\/p>\n

    \"\"<\/p>\n","protected":false},"excerpt":{"rendered":"

    This is part three of a three-part series on how HubSpot transformed with AI. Part one covers how<\/p>\n","protected":false},"author":1,"featured_media":3288,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"_links":{"self":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts\/3286"}],"collection":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/comments?post=3286"}],"version-history":[{"count":2,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts\/3286\/revisions"}],"predecessor-version":[{"id":3292,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/posts\/3286\/revisions\/3292"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/media\/3288"}],"wp:attachment":[{"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/media?parent=3286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/categories?post=3286"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/fliegewiese.org\/index.php\/wp-json\/wp\/v2\/tags?post=3286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}