Visual summary of operating lessons from Douglas Hanna.

Lessons from Douglas Hanna

Douglas Hanna has led go-to-market and operations at Grafana Labs and Kustomer, after earlier roles at Zendesk. In direct interviews he discusses how open-source adoption becomes a commercial motion, how revenue teams scale, and how pricing and operating practices evolve with a company. — Between Two COOs — Kustomer Interview.

Part 1: Open-Source Commercialization

  1. Respect the Open-Source Community: Hanna said most open-source users will never become paying customers, yet their experience and trust still matter to a company built around the project. — First Round — Open-Source GTM Interview.
  2. Commercialize Organizational Needs: Hanna pointed to security, compliance and managing deployment at large scale as examples of features big organizations may pay for beyond a useful open-source core. — First Round — Open-Source GTM Interview.
  3. Offer Managed Cloud Alongside Open Core: Hanna described a shift among many commercial open-source companies toward managed cloud offerings alongside differentiated commercial software, while noting Red Hat’s earlier support-and-training model. — First Round — Open-Source GTM Interview.
  4. Create Real Value Before Capturing It: Hanna framed the open-source business problem as balancing a high-quality free project that creates value with paid offerings that capture some of that value. — First Round — Open-Source GTM Interview.
  5. Distinguish Users from Buyers: At Grafana, Hanna said a very large installed open-source base meant sales and marketing focused on identifying which existing users had a relevant commercial need, not assuming every user would convert. — First Round — Open-Source GTM Interview.
  6. Balance Value Creation and Capture: Hanna warned that an open-source company can damage its community if it handles the balance between free value and paid value badly. — First Round — Open-Source GTM Interview.
  7. Do Not Assume Support Alone Will Monetize: Hanna contrasted Red Hat’s successful support-and-training model with more recent open-source companies that generally used open-core and managed-cloud offerings. — First Round — Open-Source GTM Interview.
  8. Use Enterprise Features to Extend Open Core: Hanna described security, compliance and other needs of large deployments as common reasons to buy a commercial version of an open-source product. — First Round — Open-Source GTM Interview.
  9. Stay Competitive in Open Source: Hanna cautioned that a successful commercial business must keep its underlying open-source project useful and differentiated because users can move to competing projects or forks. — First Round — Open-Source GTM Interview.

Part 2: Selling to Developers

  1. Use a Lower-Pressure Developer Sales Motion: Hanna said developer-oriented sales should be less aggressive and more focused on useful value than some other enterprise sales motions. — First Round — Open-Source GTM Interview.
  2. Offer Technical Value in Developer Marketing: Hanna said outreach to developers should provide a useful event, resource or other concrete value instead of repeated promotional messaging. — First Round — Open-Source GTM Interview.
  3. Pair Sellers with Technical Help: Hanna described hiring solutions engineers early so sellers could get credible help with the technical side of open-source deals. — First Round — Open-Source GTM Interview.
  4. Protect Trust with Low-Pressure Outreach: Hanna warned that intrusive marketing and high-pressure sales can turn developer users off, so outreach should be sensitive to the community and offer value. — First Round — Open-Source GTM Interview.
  5. Make Solutions Engineering Part of the Early Team: At Grafana, Hanna said technical solutions engineers were among the early go-to-market hires and worked closely with account executives during sales cycles. — First Round — Open-Source GTM Interview.
  6. Keep Self-Service and Enterprise Sales Distinct: Hanna noted that self-service adoption can be valuable, while larger negotiated enterprise deals require a different, more assisted motion. — Between Two COOs — Part 2.
  7. Sell Above the Developer Champion When Needed: Hanna said bottom-up developer adoption can create product love, but larger commercial contracts often require engagement higher in the organization. — First Round — Open-Source GTM Interview.
  8. Learn From Community Pain Points: Hanna advised studying GitHub issues and community conversations to learn where users encounter problems that might become commercial opportunities. — First Round — Open-Source GTM Interview.

Part 3: Go-to-Market Architecture

  1. Operate GTM as a Connected System: At Kustomer, Hanna centralized revenue operations across sales, marketing and customer-experience functions so shared tools and data had clear ownership. — Between Two COOs — Kustomer Interview.
  2. Curate Existing Demand: Hanna said a well-known open-source project already creates demand; Grafana’s marketing and sales teams had to identify which engaged users had relevant commercial needs. — First Round — Open-Source GTM Interview.
  3. Hire Sales Capacity Against Real Signals: At Grafana, Hanna and the founder added salespeople incrementally while watching productivity and pipeline rather than assuming headcount alone would create growth. — First Round — Open-Source GTM Interview.
  4. Segment by Region and Customer Size: Hanna described Grafana’s sales organization as divided by region, then by customer size, with separate coverage for specialized federal and channel motions. — Between Two COOs — Part 2.
  5. Separate Specialized Channel Coverage: As Grafana’s sales organization scaled, Hanna described channels and partners as a specialized motion separated from the regional field teams. — Between Two COOs — Part 2.
  6. Stay Involved After the Initial Sale: Hanna described an adopt–land–expand motion in which account executives and customer-success teams continued working with customers after the first contract. — Between Two COOs — Part 2.
  7. Check Outcomes Before Expansion: Hanna said Grafana used later business reviews to ask whether the deployment was meeting what had been promised, with expansion and renewal following successful use. — Between Two COOs — Part 2.
  8. Hire Salespeople Who Can Learn the Motion: Hanna said early open-source sales hires needed relevant experience and a willingness to work without the infrastructure of a larger company. — First Round — Open-Source GTM Interview.

Part 4: Operations & Scalability

  1. Build an Operating Cadence as the Company Grows: Hanna described introducing OKRs, all-hands meetings, leadership syncs and regular one-on-ones as Grafana scaled from a much smaller organization. — Between Two COOs — Part 2.
  2. Give Shared Data Clear Ownership: At Kustomer, Hanna put revenue reporting, data quality and shared GTM tooling under a centralized RevOps function instead of leaving each team with separate systems. — Between Two COOs — Kustomer Interview.
  3. Refine Repeatable Processes: Hanna said Grafana spent years refining pipeline reviews, forecasting meetings and hiring processes so recurring work became more repeatable and decision-useful. — Between Two COOs — Part 2.
  4. Build Post-Sale Capacity as Usage Grows: Hanna described expanding Grafana’s post-sale function from a small support group to account management, professional services, customer success and around-the-clock support. — Between Two COOs — Part 2.
  5. Assign Ownership of Shared Systems: Hanna said centralizing Kustomer’s RevOps made ownership of cross-team tools such as Salesforce and enrichment systems clearer. — Between Two COOs — Kustomer Interview.
  6. Use Operations to Improve Visibility: Hanna described revenue operations as covering reporting, business partnering, shared tools and data reliability across the go-to-market organization. — Between Two COOs — Kustomer Interview.
  7. Make Forecast Reviews Decision-Useful: Hanna said a well-run forecast meeting should bring the relevant people together, surface current deal information and allow decisions in a focused hour. — Between Two COOs — Part 2.
  8. Adapt Operating Models to Company Context: Hanna cautioned that coverage, product and marketing playbooks should be adjusted to a company’s stage and market instead of copied unchanged from a previous employer. — Between Two COOs — Kustomer Interview.

Part 5: Leadership & The COO Role

  1. Shape the COO Role to the Company: Hanna said a COO role can be molded around the CEO’s priorities and the company’s needs; at Grafana his own remit combined revenue leadership with broader operations. — COO Alliance — Douglas Hanna Interview.
  2. Build a Deliberate CEO–COO Partnership: Hanna described spending regular time with Grafana’s CEO, sharing tactical information and discussing strategic choices until mutual trust made delegation easier. — COO Alliance — Douglas Hanna Interview.
  3. Clarify Delegated Authority: Hanna said trust between a CEO and COO grows through communication and eventually lets the COO handle decisions that previously required a direct conversation. — COO Alliance — Douglas Hanna Interview.
  4. Adapt From Founder to Operator: After having led smaller companies, Hanna said he preferred the scaling phase and learned to fit his COO work to a founder-CEO’s different role and style. — COO Alliance — Douglas Hanna Interview.
  5. Hear Directly From Managers’ Teams: Hanna described regular skip-level conversations and bringing team members into leadership meetings to learn their views and give them exposure. — COO Alliance — Douglas Hanna Interview.
  6. Over-Communicate Early to Build Trust: Hanna said he and Grafana’s CEO communicated more than usual early in their working relationship until they had enough trust to delegate more freely. — COO Alliance — Douglas Hanna Interview.
  7. Protect Hiring Quality During Rapid Growth: Hanna described making good, culture-accretive hiring decisions as a central challenge when Grafana added hundreds of employees quickly. — Between Two COOs — Part 1.
  8. Use OKRs to Clarify Near-Term Commitments: Hanna said Grafana used OKRs to state quarterly priorities and what the team intended to accomplish, without treating the framework dogmatically. — Between Two COOs — Part 2.
  9. Ask for Help Outside Your Expertise: When he joined Grafana, Hanna kept a list of technical concepts he did not understand and met regularly with a technical leader to learn them. — COO Alliance — Douglas Hanna Interview.

Part 6: Building Customer Trust

  1. Treat the Customer Journey as Cross-Functional: Hanna said enterprise buying is less linear than a simple funnel, requiring sales, marketing and post-sales teams to adapt to changing customer expectations. — Crew Capital — Douglas Hanna Interview.
  2. Provide Technical Help in Enterprise Sales and Support: Hanna described solutions engineers partnering with sellers during technical deals and a separate ongoing support function for customers after purchase. — Between Two COOs — Part 2.
  3. Focus Customer Success on Outcomes: Hanna described post-sale business reviews that check whether the customer is receiving what was promised, with expansion and renewal linked to successful use. — Between Two COOs — Part 2.
  4. Drive Adoption Early: Hanna warned that in a consumption-based model, early customer adoption matters because a deployment that gets off track can be hard to recover. — Crew Capital — Douglas Hanna Interview.
  5. Make Security a Commercially Relevant Capability: Hanna identified security and compliance needs as common reasons large companies pay for a commercial version of an open-source product. — First Round — Open-Source GTM Interview.
  6. Build Enterprise-Specific Capabilities: Hanna said large deployments may need differentiated capabilities such as access management, security, compliance and additional data sources. — First Round — Open-Source GTM Interview.

Part 7: Pricing and Packaging

  1. Tie Price to Customer Value: Hanna recommended choosing a pricing metric that grows with usage and, ideally, with the value customers receive. — First Round — Open-Source GTM Interview.
  2. Make Usage Bills Predictable: Hanna said consumption pricing can be difficult when customers cannot predict the bill, so pricing must balance flexibility with understandable cost. — First Round — Open-Source GTM Interview.
  3. Let Developers Try the Free Product: Hanna described open-source and free cloud access as a low-friction way for users to adopt Grafana before any commercial discussion. — Between Two COOs — Part 2.
  4. Choose Metrics That Fit the Product: Hanna said seats and data volume can each be useful pricing dimensions, but the key test is whether the chosen measure tracks customers’ actual use and value. — First Round — Open-Source GTM Interview.
  5. Give Discounting a Clear Operational Owner: At Kustomer, Hanna placed pricing and discount decisions within a centralized revenue-operations and deal-desk function. — Between Two COOs — Kustomer Interview.
  6. Give Buyers Control Over Packaging: Hanna said sophisticated customers often want more control over which capabilities or data fidelity they pay for, even when that makes packages less simple. — First Round — Open-Source GTM Interview.
  7. Keep the Open-Source Core Worth Using: Hanna warned that a commercial company must keep investing in its open-source project while finding differentiated reasons for enterprises to pay. — Crew Capital — Douglas Hanna Interview.

Part 8: Culture and Internal Alignment

  1. Create Shared Ownership of Sales: Hanna said Grafana’s “we are all on sales” saying invited people beyond quota-carrying reps to see how their work helps customers and revenue. — Crew Capital — Douglas Hanna Interview.
  2. Extend Shared Ownership to Customer Success: Hanna said Grafana extended that cultural message to “we are all on customer success,” including engineers and other teams in responsibility for customer outcomes. — Crew Capital — Douglas Hanna Interview.
  3. Write Things Down in Distributed Teams: Hanna described a culture of written, transparent notes and shared customer channels so dispersed colleagues could follow context and ask questions. — Between Two COOs — Part 1.
  4. Use Cross-Team Tension to Improve the Journey: Hanna said friction can arise naturally among sales, marketing and post-sales teams because their functions differ, making shared customer ownership important. — Crew Capital — Douglas Hanna Interview.
  5. Make Work Visible Across Levels: Hanna described transparent notes, skip-level conversations and bringing team members into leadership discussions instead of filtering everything through one manager. — COO Alliance — Douglas Hanna Interview.
  6. Judge Ideas Beyond Job Title: In Grafana’s cultural-values discussion, Hanna said colleagues should persuade one another with data and reasoning rather than relying on a CEO’s title. — Grafana Labs — Cultural Values.
  7. Adjust Team Design as the Business Scales: Hanna said account segmentation and the types of sales representatives serving them had to evolve as Grafana expanded across products, geographies and customer sizes. — Crew Capital — Douglas Hanna Interview.
  8. Give New Hires Context and a Peer Buddy: Hanna said he shared a “Working with Doug” guide with new direct reports and assigned new hires a peer buddy; he found deeper skip-level check-ins more useful after 60–90 days than during week one. — COO Alliance — Douglas Hanna Interview.
  9. Staff for the Next Stage, Not Only Today’s Fires: At Kustomer, Hanna said the company moved from hiring just enough people to keep operations running toward staffing new initiatives and capabilities intentionally. — Between Two COOs — Kustomer Interview.