I’m endlessly fascinated by how modern platforms turn open source momentum into durable, enterprise-grade businesses. Ashley Kramer is the CMO and CSO at GitLab, a publicly listed DevSecOps platform. She started out in software engineering before becoming a product leader, and eventually, a marketer. Most recently, Ashley was the CPO and CMO at Sisense, a data analytics company last valued at over $1b. That multifaceted path mirrors the intersection I live in daily—where product management leadership, developer evangelism, and go-to-market strategy converge to drive sustainable growth.
What stood out to me most was the precision with which GitLab layered a commercial model on top of open source roots. The nuance matters: the difference between open core and open source isn’t just semantic; it determines packaging, pricing, and how you balance a vibrant community with enterprise-grade requirements. The tensions of being a commercial, open source company are real—especially when you’re serving many different customer segments with distinct needs. From my seat, this is the essence of open source monetization: protect developer trust while building clear value for enterprises that justifies “consumption SaaS pricing,” security, and support.
Transparency plays a starring role. GitLab’s culture shows the power—and the trade-offs—of working in the open. I’ve seen firsthand how openness accelerates alignment, speeds up product discovery, and reinforces outcomes vs output OKRs. But you must be deliberate. Examples, benefits, and downsides of a transparent company culture are on full display in their handbooks and public processes, which I frequently reference for my own teams. Why GitLab is transparent about their marketing and the 2 examples of GitLab’s uniquely transparent culture provide a blueprint for building trust at scale—while the downsides of being a transparent company remind us to design guardrails.
On the marketing front, the role of marketing at GitLab underscores a systems mindset: define the customer problems, align with the product roadmap, and ensure tight collaboration with sales and community. GitLab’s main marketing metrics, combined with a clear model for how marketing collaborates with product, make the strategy both measurable and adaptable. I’ve applied a similar approach by anchoring campaigns in user outcomes, then instrumenting every touch—from content to conversion—to close the loop with product usage and retention.
Structure supports strategy. The thinking behind GitLab’s org structure, in and around marketing, is a reminder that ownership beats approval chains. GitLab’s planning process and GitLab’s meeting structure and cadence reflect a discipline that’s hard to achieve without cultural scaffolding. In my experience, explicit planning rhythms and written decision logs are force multipliers for cross-functional execution and faster product-market fit lessons.
Selling to enterprise as an open core company demands clarity on what’s free, what’s paid, and why. That’s where serving many different customer segments becomes both an art and a science. Developer love and enterprise readiness can coexist when you design the offer thoughtfully—feature gating that respects the open source ethos, security and compliance that satisfy a “CISO,” and pricing models that feel fair. For teams driving developer evangelism, the north star remains unchanged: remove friction, amplify community contributions, and provide a clear, upgrade-worthy path for enterprises.
When it comes to campaigns, I took away a simple, durable lesson from an example of a recent marketing campaign: anchor the narrative in customer pain, tie it to measurable outcomes, and connect the dots—from awareness to activation to expansion—across product and marketing. An example of GitLab’s marketing in practice reinforces that even in highly technical domains like “DevSecOps,” the most effective storytelling is still about clarity and credibility.
I also appreciate how Ashley’s background informs execution. Benefits of having an engineering and product background as CMO include crisper problem definitions, better partnership with product leaders, and the ability to translate complexity into value propositions that resonate with both developers and executives. It’s a competitive advantage I’ve leaned on throughout my own career as we scale platforms and craft founder-led GTM motions into repeatable engines.
For leaders building in the open, a few resources are worth bookmarking—and I keep returning to them when refining strategy, process, and messaging.
DevSecOps: https://about.gitlab.com/topics/devsecops/
GitLab’s open core business model: https://handbook.gitlab.com/handbook/company/stewardship/
GitLab’s open source employee handbook: https://handbook.gitlab.com/handbook/people-group/
GitLab’s open source marketing handbook: https://about.gitlab.com/handbook/marketing/
GitLab’s open source remote handbook: https://handbook.gitlab.com/handbook/company/culture/all-remote/guide/
GitLab legal team’s SAFE framework: https://about.gitlab.com/handbook/legal/safe-framework/
GitLab: https://gitlab.com
E-Group: https://about.gitlab.com/company/team/e-group/
CISO: https://www.cisco.com/c/en/us/products/security/what-is-ciso.html
Sid Sijbrandij, CEO of GitLab: https://www.linkedin.com/in/sijbrandij/
Tableau: https://www.tableau.com/
Pulling it all together, here’s the playbook I see: make the open core boundary unmistakably clear, invest deeply in your developer community, operationalize transparency with documented processes, and build revenue with enterprise-grade features that map to real-world risk and scale. Do that well, and you earn the right to price for value—while staying true to the community that made the product possible.
Leave a Reply