Oct 26, 2023 · 1h 14m · in-depth
The business of growing and monetizing an open source product | Ashley Kramer (GitLab CMO/CSO)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Ashley Kramer, CMO and CSO at GitLab, breaks down the strategies for scaling and monetizing an open core software business, covering radical operational transparency, community-driven marketing, cross-functional go-to-market metrics, and enterprise positioning.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Brett holds 16.5% of the talking time here. How this is scored →
Brett as informed peer 3.6 Guest teaching 5.4 Guest disagreement 0.4 Brett pushing back 0.1
speaking balance: gold is Brett, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 40:20 Rejecting competitor's single-feature AI narrative
Ashley firmly rejects following the competitor's hype around code completion, insisting instead on a holistic, end-to-end DevSecOps AI framework.
Hardest push from Brett ▶ 22:20 Challenging marketing's role in expansion pipelineBrett pushes on the counterintuitive nature of placing expansion pipeline under marketing rather than a traditional CRO or CS organization.
Biggest teaching moment ▶ 15:15 Masterclass in full-funnel DevSecOps metricsAshley provides a comprehensive breakdown of the five distinct metrics governing GitLab's buyer journey and marketing organization.
Brett holds their own ▶ 30:40 Probing multi-segment go-to-market trade-offsBrett demonstrates deep domain knowledge of enterprise go-to-market dynamics, articulating why multi-segment targeting typically creates severe organizational trade-offs.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Brett as informed peer | Guest teaching | Guest disagreement | Brett pushing back | Why |
|---|---|---|---|---|---|---|
| The Power of Radical Transparency in Open Source | 1 | 1 | 0 | 0 | Introductory monologue and teaser clip highlighting GitLab's radical transparency. Brett sets the stage by framing the discussion around open core monetization and go-to-market structure. | |
| Marketing in Open Core vs. Closed Source Environments | 4 | 5 | 1 | 0 | Brett prompts Ashley on the contrast between marketing closed source versus open core software. Ashley explains how community contributions create repeatable value and faster innovation compared to traditional closed environments like Tableau. | |
| GitLab's Origins and Community-Led Early Marketing | 4 | 5 | 0 | 0 | Brett asks for actionable marketing lessons for early-stage companies at $1M ARR. Ashley details how early GitLab grew purely through community engagement, Twitter discovery, and contributor recognition rather than formal marketing leadership. | |
| Scaling Developer Relations and Bridging Community to Enterprise | 4 | 6 | 1 | 0 | Ashley explains how developer relations bridges into commercial pipeline and how GitLab manages the tension of monetizing open source via 11 published promises and transparent pricing tiers. | |
| Nurturing Developer Relations Through Transparent Feedback | 3 | 5 | 1 | 0 | Brett asks how to navigate inevitable community pushback when commercializing features. Ashley emphasizes direct, transparent communication and explaining the 'why' rather than giving vague corporate non-answers. | |
| The Five Core Metrics of GitLab's Marketing Funnel | 3 | 7 | 0 | 0 | Ashley walks through GitLab's five marketing funnel metrics: awareness, consideration, conversion, expansion, and evangelism, illustrating each with tactical operational examples like the Lockheed Martin case study. | |
| Cross-Functional Alignment Between Marketing, Sales, and Customer Success | 5 | 5 | 0 | 1 | Brett asks about the organizational boundary lines between marketing, SDRs, and customer success around expansion pipe. Ashley clarifies the joint ownership model between CMO and CRO for influenced expansion pipeline. | |
| Operationalizing Marketing Structure, DRIs, and Strategy Execution | 4 | 5 | 0 | 0 | Brett inquires into organizational design across the marketing team. Ashley explains their DRI (Directly Responsible Individual) model, quarterly OKR tracking, and how cross-functional leaders contribute circularly to goals. | |
| Defining Open Core vs. Open Source and Enterprise Positioning | 4 | 6 | 1 | 0 | Brett asks how open core positioning plays out in Fortune 500 accounts versus traditional enterprise software. Ashley distinguishes between pure open source and open core commercial tiering, highlighting single-platform value. | |
| Tailoring Strategies Across SMB, Mid-Market, and Enterprise Segments | 6 | 5 | 0 | 0 | Brett probes how GitLab balances marketing across diverse segments from SMB to public sector without losing focus. Ashley contrasts low-touch automated developer channels like Reddit with high-touch executive roundtables for CISOs. | |
| Strategic Planning: Vision, Three-Year Strategy, and Yearly OKRs | 3 | 6 | 0 | 0 | Ashley details the cascade from GitLab's 10-year vision down to 3-year strategy, 3 to 5 'yearlies', and quarterly OKRs, giving the concrete example of educating analysts on 'DevSecOps'. | |
| Case Study: Launching GitLab Duo and Holistic AI Messaging | 4 | 6 | 1 | 0 | Ashley recounts the launch of GitLab Duo, explaining why they rejected reactionary point-feature messaging around code completion in favor of an end-to-end AI lifecycle narrative. | |
| Product-Marketing Collaboration Rituals and Decentralized Problem Solving | 4 | 6 | 0 | 0 | Brett asks about product-marketing alignment rituals. Ashley discusses decentralizing problem-solving by empowering product marketing VPs to collaborate directly with product VPs instead of bottlenecking at the executive level. | |
| Translating Open Source Lessons to Traditional Software Companies | 4 | 6 | 1 | 0 | Ashley reflects on lessons from GitLab applicable to closed-source software, highlighting transparent earnings communications from the CFO and generous freemium adoption over restrictive 15-day trials. | |
| Public Handbook Management and the SAFE Compliance Framework | 3 | 6 | 0 | 0 | Ashley discusses the mechanics of GitLab's public handbook, including external marketing handbook pages and how the SAFE framework separates public info from confidential financial and pipeline data. | |
| Operational Transparency: Open Meetings, Async Notes, and CEO Shadow Program | 3 | 6 | 0 | 0 | Ashley describes GitLab's open calendar policy, async meeting documentation, and the CEO shadow program where employees spend two weeks attending executive sessions with Sid Sijbrandij. | |
| Crisis Communication and Managing Transparency Risks | 3 | 5 | 1 | 0 | Brett asks about the downsides of radical transparency. Ashley explains crisis communication management and why leadership refuses to abandon transparency because of isolated leaks or bad actors. | |
| Non-Traditional Career Path: From Software Engineer to CMO/CSO | 4 | 6 | 0 | 0 | Brett asks about Ashley's career progression from software engineer and product manager to CMO/CSO. Ashley explains how developer empathy and being a former GitLab customer inform her dual strategy and marketing roles. | |
| Executive Customer Discovery Tours and Regional Differences | 3 | 5 | 0 | 0 | Ashley shares insights from executive listening tours, explaining how public sector and global regional differences require customized messaging. She wraps up with lessons on hiring for functional weaknesses. |
Statements from this episode (23)
Kramer: Open core model accelerates innovation via shared customer code contributions
“As customers are contributing code to our platform, we are able to share that as part of our platform with the entire world. So it sort of opens up all the contributors in the world. To be part of our team and part of our development and innovation and really …”
Early open-source startups do not need formal marketing teams or CMOs
“And so you don't necessarily need a CMO or anybody in marketing to really drive this when you start as that, as your root, as open source as your root, you open it up for the people that are contributing to the product that clearly believe in it because they'r…”
GitLab CMO Kramer: Developer relations and community team reports directly to CMO
“But we still have a group and it reports directly to me. That is developer relations and community. And so we run specific products through that, like our code contributor program, where we still do those exact same things. We still have hackathons where we br…”
Open core platforms should train enterprise customers to contribute code directly
“So you have a company that's using our platform really widely. They want a few more capabilities. Don't wait on us. We'll empower you and teach you how to have some code contributors in seat so you can move faster. And then of course we get the value from that…”
GitLab will always maintain a free open-core tier
“Do we put this in our free version, which we will always have as a good open source steward, or is this something that falls as part of our paid for package?”
GitLab governs its pricing model via 11 published community promises
“We have promises. So we have 11 promises listed out there on what we will follow to make sure that we're continuing to serve the community that helped us get where we are today, but also understanding that we're a commercial product now, and then help them dif…”
GitLab commits to always open-sourcing tests for open-source features
“Another one we have is that we'll always release an open source, the tests that we have for an open source feature. We'll share that with the world.”
Kramer: GitLab directly explains why features belong in paid tiers
“I'm a product manager in, in as my background, and often people would talk to you and say, I want this feature and you talk them in this giant circle that makes them feel really loved, but is also kind of telling them no, whether they get that or not. And so w…”
In-person field events are more effective than ever for enterprise pipeline growth
“And then the other thing that really, really works, particularly in upper mid market to enterprise field events. Field events have been back for about a year and they're almost even more popular now because for two years we all sat in our houses and stared at …”
GitLab CMO and CRO jointly own expansion pipeline and net ARR
“So Ciro and I jointly own expansion. So we're driving the pipeline for expansion. And of course he owns the overall number, which can be a mix of, is a mix of net new and growth.”
GitLab assigns single DRIs to lead marketing areas with multiple VP contributors
“And so at GitLab, we really believe on having a DRI for everything, a directly responsible individual. And then of course there's a ton of contributors. And so there will be several of my VPs that contribute To each of them.”
An open core model is a purchasing requirement for many government agencies
“Outside of some, you know, I visit with a lot of customers in PubSec, and that is actually for a lot of the agencies, a requirement.”
Gartner will adopt the 'DevSecOps platform' category within three years
“And so that's not something that happens overnight. That's something that will take about three years probably for Gartner to say, no, GitLab was right. It is a DevSecOps platform MQ that we're going to do.”
Kramer: GitLab positions AI across the entire software delivery lifecycle, not just code completion
“Instead, we stepped back and said, the value of AI on our platform is along every step in the software delivery life cycle. So that will be one piece of it. And customers absolutely need to know we have it and prospects, but we should be telling an end to end …”
GitLab pairs product marketers directly with product managers to prioritize features
“So we've built a product marketing team that is Getting deeper and deeper. They're matched with product managers, and they're getting deeper and deeper into how our product works and understanding the value of it to really want the product managers to come tog…”
GitLab's CFO shares roadshow investor sentiment with all employees via Slack
“This is the first company where I actually know everything after we do an earnings call and our windows open and our CFO goes on the roadshow. I understand what they're saying and not just me. He sends out a slack to the entire company of the sentiment, the ov…”
Kramer: All-hands meetings fade, but written handbooks maintain continuous alignment
“You know, I can say it in all hands, then it's a one and done. But as new people enter the company and onboard as people are trying to get up to speed on where we're going, they have one place to go.”
Kramer: Going public forced GitLab to restrict financial metrics via SAFE framework
“We became a public company, and so we had to introduce something our legal team noted as a safe framework. Please don't ask me what it stands for. You can Google it because I don't remember, but it's basically understanding if this is financial information, it…”
GitLab defaults to keeping all meeting agendas open to the entire company
“We never have a meeting without a meeting agenda and it's by default. We always make it open to the company if possible.”
Eligible GitLab employees can shadow CEO Sid Sijbrandij for two full weeks
“Anybody at the company, I think you have to be here for a certain amount of time can apply to shadow him for two weeks. And when you shadow Sid, you go to one-on-one. So he, they would come to a one-on-one with me. It's kind of funny. It's like me and him talk…”
GitLab bans slide presentations during meetings in favor of asynchronous pre-reads
“We don't really like to present, and so we really try to pre-send materials to make the most effective meetings, not sit there and present slide after slide in a meeting. We assume everybody is pre-read, then we can just jump into rich conversation.”
Kramer: Companies should not abandon transparency over isolated internal leaks
“And the thing we stand really true to is I never have wanted, and I know the team would agree with me, just One bad instance, one bad actor to spoil it for everybody else. So while we have had these things happen and every company has, it's not like we're like…”
Enterprise CTOs avoid CMOs but will gladly meet with Chief Strategy Officers
“Which, what CTO wants to talk to the CMO of DevSecOps? Like my platform, but they definitely want to talk to somebody that is working on understanding their needs. That was a former customer and that wants to come back with a team and understand, are we strate…”