I recently sat down with Kate Taylor, who recently joined Notion as their Head of Customer Experience. Previously, Kate spent 8 years at Dropbox, leading their SMB revenue and scaled sales operation before leaving in 2020. Prior to that, she started her career as a sales rep at Salesforce. That trajectory alone offers a rare, end-to-end vantage point across product-led growth, scaled sales, and customer experience — precisely the intersection where modern SaaS wins or loses.
In our conversation, Kate shared a wealth of advice for building out product-led growth and self-serve motions. She shared tons of nuances around going up market, competing with sales and product planning, offering up tactical advice that any founder, product or go-to-market leader can learn from. As someone who has built PLG and hybrid motions, I found her guidance both pragmatic and immediately applicable — especially for teams balancing self-serve efficiency with enterprise demands.
We went deep on product prioritization. At Notion, their system of 700 tags enables a rigorous, multi-dimensional view of customer needs and product work. Hearing specific examples of tradeoffs they’ve had to navigate reminded me how essential it is to pair qualitative signal with quantitative usage data — and to operationalize that insight in product roadmapping and sprint planning. My takeaway: a well-structured tagging and feedback taxonomy is a force multiplier for product discovery and product-market fit lessons.
We also explored pricing and packaging — from specific experiments at Dropbox to why interestingly Notion’s trial isn’t time based. That philosophy reframes trials around value realization and activation, not arbitrary timelines. In my experience shaping SaaS pricing, this approach improves conversion and long-term retention when you align paywalls to “aha” moments and clear outcomes. It’s a call to design pricing alongside onboarding, not after it.
Customer experience was another rich vein. We discussed how to handle a wide range of use cases while building the “front door” customer experience her team envisions. From why customer service shouldn’t be focused on getting customers off the phone faster, to the questions she asks to find more signal in their product feedback, Kate’s perspective elevates support from a cost center to a strategic insight engine. I’ve seen the same: the best CX loops feed product planning, reduce churn, and strengthen go-to-market alignment.
We closed on leadership. Kate unpacked why she hires for curiosity, how she teaches teams to ride the ups and downs of startup life, and how working for three very different CEOs — Marc Benioff, Drew Houston and Ivan Zhao — has impacted her own leadership style. The throughline is deliberate learning: create environments where product managers and operators can test, reflect, and iterate quickly — the same principles that make PLG work at scale.
If you’re building or refining a product-led, self-serve motion — or moving upmarket without breaking what already works — these insights on prioritization, pricing, and customer experience provide a clear blueprint. My advice: operationalize feedback, pressure-test your packaging against value moments, and treat support as your highest-signal discovery channel. That’s how you turn strategy into compounding growth.
I’ve been revisiting the hard-won lessons behind durable product companies, and Eric Berg’s journey is a masterclass. Eric Berg is the CEO of Fauna, which is an adaptive operational database platform. In joining Fauna as its CEO in the summer of 2020, he brought a wealth of experience as a product leader. Most recently, he was the Chief Product Officer at Okta, scaling the company from 10 employees and zero customers to its eventual IPO in 2017. He started his career in product at Intel, working under the legendary Andy Grove, as well as a five-year stint as a product leader at Microsoft.
From a product management leadership lens, the earliest chapters at Okta are a blueprint for zero to one B2B marketing and founder-led GTM. I break down his early go-to-market lessons and the keys to honing in on an ICP to get Okta off the ground, highlighting how tight product discovery, crisp problem statements, and ruthless prioritization turn ambiguity into product-market fit.
What stands out is the often-maligned “messy middle” — the stretch when traction exists but entropy expands. Eric’s moves on “moving upmarket” and evolving a “pricing and packaging model” are reminders that, when done well, takes a company to new heights. For SaaS pricing, I lean on value metrics tied to critical jobs-to-be-done, clear guardrails for discounting, and a win–loss feedback loop owned jointly by product and sales.
We then switch gears to team building and company building. The cultural patterns that stick with me: hire “folks up and down the org chart with the right ego to talent ratio” and operationalize a “disagree and commit” value so it’s not just a long-forgotten team motto. Practically, that means defining decision types (one-way vs. two-way doors), naming a DRI and approver for every call, time-boxing debate, and documenting the rationale so execution never stalls.
On execution mechanics, I’ve found that outcomes vs output OKRs paired with QBRs vs OKRs alignment creates a healthy cadence from strategy to delivery. When you layer in forward deployed engineers and structured customer advisory boards, feedback cycles compress without sacrificing focus — a powerful pattern in both product roadmapping and sprint planning.
Finally, the perspective shifts “as he approaches one year of sitting in the CEO seat” underscore the difference between building products and building a business. Capital strategy, talent density, and narrative become first-class product surfaces. As a product creator, I translate this into designing org APIs, setting explicit burn-to-learn budgets, and treating pricing, packaging, and GTM as core parts of the product.
If you’re navigating product-market fit lessons, wrestling with “moving upmarket,” or recalibrating SaaS pricing, this playbook maps the trade-offs from 0 customers through the “messy middle” and beyond. It’s a grounded field guide for product folks and operators who want to scale with clarity, strengthen culture, and accelerate learning without losing the thread.
I recently sat down with Sam Taylor, VP of Sales and Success at Loom. Previously, Sam was Dropbox’s first enterprise sales rep, and also served as Quip’s first sales leader. As a product leader, I’m always looking for the connective tissue between sales insights and product strategy, and Sam’s journey offers a rich playbook for product-led growth, enterprise sales, and go-to-market execution.
We started with his earliest experience at Dropbox, and I was struck by his aha moment that sales is an insight driver. That framing resonates deeply with how I run discovery and roadmap governance: when sales becomes a structured listening post, it sharpens pricing and packaging decisions and helps prioritize the feature roadmap as Dropbox moved up market. In practice, that means operationalizing feedback loops, pairing usage telemetry with win–loss analysis, and iterating packaging to match how customers actually buy and expand.
Reflecting on his time at Quip, Sam shared what sticks with him from working closely with its CEO Bret Taylor and COO Molly Graham. He also walked through tested tactics for selling in a competitive market where you’re going up against plenty of established players, like Google and Microsoft. My takeaway for product teams: differentiation must be engineered, not just messaged. Equip champions with crisp value proof, remove switching friction in the product, and align your roadmap to moments that neutralize incumbent advantages. In other words, design the product to win the deal before the demo even starts.
Turning to his current role at Loom, Sam is threading all of those experiences together. He emphasized his partnership with Loom’s product leaders, and how they’re teaming up to achieve what he jokingly calls “total Loom domination.” I loved the practicality here: a tight sales–product cadence, shared metrics for activation and expansion, and packaging that scales from self-serve to enterprise without creating friction. “Everyone wants a silver bullet,” but the real edge comes from compounding small, well-orchestrated decisions across pricing, roadmap, and enablement.
If you’re in sales, Sam’s path reinforces how to translate field signals into product change that moves pipeline and retention. And if you work in a product-led growth company, you’ll come away with a clearer understanding of how sales fits in: establish a reliable voice-of-customer loop, treat SaaS pricing and packaging as a product, and use product roadmapping to align with the most material customer problems. That’s how you turn insights into impact—and how product and sales win together in competitive markets.
I recently sat down with Jane Davis, the Director of UX Research and UX Writing at Zoom. She previously led UX Research and Content Design at Zapier, and managed the growth research team at Dropbox. I set out to distill a practical playbook any product team can apply — even if you don’t have a formal UX research function.
Jane tackles the thorniest customer development questions and walks through an end-to-end research process that works in the real world: clarifying your goals, asking the right questions, selecting participants, and synthesizing insights. I translate these steps into repeatable product discovery rituals that drive better decisions and faster product-market fit.
We start by applying her playbook in the early-stage startup context — when you’re shipping the first version of your product and don’t yet have the resources to invest in a full research team. I share how I scope lean studies, use founder-led GTM interviews to deeply understand the problem we’re solving, and shape hypotheses for competitive versus greenfield markets, including how to size demand and figure out willingness to pay for SaaS pricing.
We also dig into best practices for prototyping and iterating. I show how I pair lightweight prototypes with clear research questions, time-box sprints, and convert insights into product roadmapping and sprint planning that truly move the needle.
Later, we confront common roadblocks: building for multiple users, aligning personas, and what to do when people aren’t excited about your product or using it frequently. I outline tactics to diagnose the gap — value proposition, onboarding, activation, and retention — then adjust the solution, messaging, or usage triggers to rebuild momentum.
Whether you’re talking to potential customers before you start a company or looking to get better feedback from your current users, this conversation is packed with field-tested practices for founders, product-builders, and design folks alike. Use it as your starting point to run credible UX research, de-risk decisions, and accelerate product-market fit without a dedicated team.
I’ve long admired Giancarlo ‘GC’ Lionetti, the former CMO of Confluent and VP of Self-Serve Growth at Dropbox. (GC also previously spent 6 years at Atlassian, as a sales engineer and product marketing manager for developer tools.) He describes his career as more of a maze than a ladder, and that functional breadth across standout B2B companies resonates with my own approach to product management leadership.
In this deep-dive, I make the case for a hybrid go-to-market strategy that brings together more traditional selling with modern product-led growth. I’ve seen this blend unlock efficient, scalable growth without sacrificing enterprise-grade rigor — especially when you’re balancing self-serve and sales-assisted motions before and after product-market fit.
I start by mining lessons from GC’s time at Atlassian and Dropbox, comparing their business models and translating what it takes to make a multi-product go-to-market motion work. For me, the critical levers include crisp segmentation, clear packaging, intentional cross-sell paths, and an obsessive focus on the end-to-end customer journey.
From there, I share my advice for a hybrid approach, including my litmus tests for picking the right metrics and the structure of my weekly meetings. I distinguish inputs from outcomes, leading indicators from lagging indicators, and align each metric to a specific stage of the funnel with a single accountable owner. My weekly operating cadence ties product-led growth health (acquisition, activation, conversion, monetization) to sales pipeline, forecast accuracy, and deal health so both motions reinforce one another.
I also sink tons of time into understanding the customer journey, mapping out the delta between reality and the ideal vision. That means pairing qualitative insights with product analytics, instrumenting key aha moments, and documenting friction so the team can remove blockers in priority order. The result is a shared, visual narrative that turns strategy into execution.
On pricing, packaging, and activation, I lean on a few battle-tested principles: anchor pricing to customer value, keep the pricing metric intuitive, right-size tiers for clear upgrade paths, and design first-session experiences to reduce time-to-value. In SaaS pricing, even small tweaks to entitlements, limits, and paywalls can meaningfully shift activation and expansion, so I validate with experiments before rolling changes broadly.
To holistically evaluate any go-to-market strategy, I apply a simple diagnostic framework that scores acquisition, activation, monetization, expansion, and retention, then layers in organizational alignment and operating cadence. This clarity exposes whether issues are strategy, execution, or enablement problems — and where a hybrid model can create compounding gains.
Finally, I focus on team building for a hybrid go-to-market strategy — from hiring profiles to team structure. I look for product builders who can speak revenue, growth leaders who respect product quality, and sales partners who embrace product-led signals. A shared dashboard, a single planning calendar, and joint post-mortems keep incentives aligned.
If you’re a founder, or part of the broader community of founders, product and go-to-market leaders, you’ll find this playbook packed with examples of specific impactful experiments I’ve run, metrics that did or didn’t work out, and common traps that I see teams falling into. The goal is simple: create a durable growth engine that compounds by uniting product-led growth and enterprise selling.
I recently sat down with Jeanne DeWitt Grosser, Head of Americas Revenue and Growth for Stripe, where she’s responsible for all sales functions and leads the company’s enterprise strategy. She joined Stripe after a career in sales at Google and also serving as Dialpad’s Chief Revenue Officer. Reflecting on our discussion, I was struck by how deliberately she treats pricing as a growth lever.
We went deep on pricing strategy. I contrasted usage-based pricing with traditional SaaS pricing, and Jeanne outlined the trade-offs clearly: usage-based pricing brings your economics closer to customer value, while subscription simplicity can reduce volatility and improve forecasting. For product leaders and founders, the choice isn’t binary—it’s about aligning monetization with your value metric and customer workflows.
We also unpacked hybrid and tiered pricing—approaches Stripe has implemented at scale. I shared how I evaluate when to layer a base platform fee with consumption pricing or when to use tiered pricing to segment by feature depth, compliance, and support. Her guidance reinforced my belief that hybrid pricing can de-risk adoption while preserving upside as customers grow.
One concept resonated deeply: treat pricing like a product. In practice, this means clear ownership, an experimentation roadmap, instrumentation, and tight feedback loops across product, finance, sales, and RevOps. She described how this shows up in Stripe’s org design, and I mapped that to my own operating model: a cross-functional pricing council, standardized experiment briefs, and monthly pricing reviews.
We compared notes on pricing experiments with outsized impact—reframing value metrics, simplifying SKUs, right-sizing tiers, and re-bundling add-ons. I emphasized a principle I rely on: reduce cognitive load to increase conversion. Small shifts—like renaming tiers to reflect outcomes rather than features—consistently improve trials, win rates, and expansion.
A steady drumbeat of customer feedback is the backbone of great pricing. We discussed tactics that work: structured win/loss, in-product pricing prompts, targeted customer advisory boards, and lightweight conjoint or price-sensitivity surveys. I also use sales call listening tours and cohort-level NRR analysis to validate whether a pricing change improved time-to-value without spiking support burden.
For founders, pricing is both art and science. The science is your data model, market benchmarks, and experimental rigor. The art is timing, narrative, and how pricing supports your go-to-market motion. Whether you’re a small startup or a larger company, start with a clear hypothesis, ship iteratively, and build the organizational muscle to revisit pricing quarterly—not once a year.
Throughout our conversation, the examples from Stripe brought the playbook to life, from usage-based mechanics to tiered packaging that scales with enterprise needs. If you’re in sales or just starting to think about pricing your product, these insights will help you align monetization with value, accelerate adoption, and expand more predictably.
I recently dove deep with Andrew Ofstad, co-founder of Airtable, to unpack Airtable’s path to product-market fit and the realities of building a truly horizontal product. As a product leader, I’m always looking for patterns that translate across teams and stages — and this conversation offered a wealth of practical insights for founders and product managers alike.
We started with first principles: how the founders came together, their vision for the product, and what the initial prototypes looked like. That early narrative matters — it anchors positioning, keeps scope disciplined, and ensures your earliest builds reflect the core value proposition rather than a laundry list of features.
From there, we stepped through Airtable’s alpha, beta, and launch timelines, as well as their early traction. I pay close attention to these milestones because they reveal the learning cadence: how quickly teams validated hypotheses, which signals they treated as leading indicators, and how they balanced qualitative pull with quantitative adoption during product discovery.
We also explored the challenges of creating a horizontal product that can do many things, including identifying initial use cases and figuring out how to describe what they were building. In my experience, the key is to land a small set of canonical use cases, articulate crisp jobs-to-be-done, and build narrative clarity around the “why now.” Without this, even great products struggle to convert curiosity into active usage.
On commercialization, we dug into how to approach pricing and competition, as well as their early go-to-market strategy. For products with broad applicability, I’ve found that founder-led GTM is essential early on — it shortens the learning loop and informs SaaS pricing and packaging. Start with simple, customer-aligned tiers, validate willingness to pay against clear outcomes, and keep positioning focused on value, not feature parity.
We then looked ahead to what the next 3 years will look like for Airtable, and how they’ve navigated scaling while staying true to their vision. Scaling a horizontal product requires tight product roadmapping and sprint planning, strong messaging discipline, and an unwavering commitment to the core value — all while layering ecosystem leverage, templates, and community to accelerate adoption without diluting the product’s identity.
Whether you’re a founder validating your own idea, or a product leader looking for growth advice, there are tons of tactics here that go much deeper than the typical founding stories you hear. My takeaway: great horizontal products find product-market fit by starting narrow in use case, obsessing over teachability, and letting customer outcomes pull the roadmap forward.
When I study companies that turn product-market fit into durable, compounding momentum, Figma stands out. In this breakdown, I walk through Figma’s five phases of community-led growth and share how I’d apply each step to build an organic growth engine. My lens is product management leadership paired with pragmatic GTM thinking, so the emphasis is on what to do, when to do it, and why it works.
Phase 1 centers on the lessons from years in stealth mode — specifically, how to start planting the seeds for a community when you don’t have a fully-formed product. I focus on the inflection point to emerge from stealth, what signals matter, and how to use early feedback loops for product discovery without over-rotating on feature requests. Quietly building is necessary; quietly engaging is essential.
In this early phase, my playbook prioritizes rigorous product discovery, crisp problem narratives, and a cadence that makes learning visible. I invest in relationship-building with credible early adopters, share prototypes thoughtfully, and shape outcomes over output through disciplined product roadmapping and sprint planning. The goal is to design a community that feels invited into the creative process while preserving the integrity of your vision.
Phase 2 is all about the launch playbook — from taking over design Twitter, to marketing to folks who tend to bristle at traditional SaaS marketing. Here, founder-led GTM matters. I pair zero to one B2B marketing with specific audience rituals, leaning into channels where the product can be experienced, not just described. The message avoids enterprise jargon and instead showcases feel, speed, and collaboration, so the community can instantly “get it.”
Phase 3 shifts the focus to activation via community gravity. The goal is to get folks to try the product, even if they weren’t going to switch over right away to designing in Figma full-time. This is where I formalize an evangelist strategy — spotlighting workflows, templates, and stories that reduce the cost of the first session. I think about developer evangelism patterns applied to designers: celebrate makers, distribute small wins widely, and build momentum with authentic, peer-to-peer proof.
The final two phases connect passionate individual users to an enterprise strategy. They didn’t layer in a sales team until four years after the product launched, and didn’t add a paid product tier until another two years after that. Those choices underscore a disciplined sequencing of PLG with a sales overlay — land with love, expand with proof, monetize with timing.
In practice, this means evolving from bottoms-up adoption to clear value narratives for team and enterprise tiers, while tuning SaaS pricing and packaging to customer maturity. I optimize the handoff from product-led signals to sales motions, align success metrics to outcomes (not just usage), and enable procurement-friendly paths without dulling what made the product magical. That’s the GTM trade-off: protect the community engine while scaling into enterprise.
If you’re building your own community-led growth engine, these phases offer a durable blueprint: learn in stealth, launch where your audience lives, activate with authentic evangelism, and scale with a thoughtful enterprise bridge. Done well, this approach compounds — it strengthens product-market fit, accelerates zero to one B2B marketing, and sets the stage for sustainable growth without overreliance on paid channels.
I approach go-to-market like an engineer: define the system, design the interfaces, and be willing to refactor. Reflecting on lessons from Rich Rao affirmed that a rigorous, architecture-first mindset can turn messy GTM motions into a scalable operating system for product-led growth and B2B marketing.
Rich Rao is the VP of the Small Business Group at Meta, where he manages the global revenue and operations for properties including Facebook, Instagram and WhatsApp. He also spent 10 years at Google, where he held a bunch of different go-to-market roles at the company, eventually becoming the GM for the Devices and Education verticals.
In our discussion, he explains how his engineering background influences his approach to GTM — from an architecture method to the concept of refactoring. That frame resonates deeply with how I run product management leadership at scale: start with the blueprint, then iterate deliberately instead of stacking one-off tactics.
We also wind back the clock to his earliest days at Google on the team that was building and selling Gmail for your domain. That story captures the zero to one B2B marketing muscle: when constraints are high, the “system design” of GTM matters more than any single channel.
There are a ton of early startup mental models that Rich shares from this period in the company’s history, including why they ended up ditching free trials and his biggest pricing lessons. I’ve seen the same pattern: open-ended free trials often attract the wrong segments, inflate support load, and mask weak activation. Time-boxed or usage-capped trials tied to a clear value metric perform better, reduce churn, and sharpen SaaS pricing strategy.
Here’s how I operationalize an engineering lens in GTM. First, I create an “architecture method” for distribution: define system boundaries (ICP, jobs-to-be-done), interfaces (hand-offs between marketing, sales, and product), and SLAs (lead response, onboarding, success). Second, I instrument everything to observe bottlenecks — then “refactor” GTM like code: remove dead channels, simplify packaging, and standardize the path to value. Third, I treat pricing as part of the design, not a late-stage patch: align paywalls with activation moments, use value-based metrics, and avoid feature sprawl that confuses buyers.
When we need step changes, I run scheduled refactoring sprints: prune legacy offers, consolidate SKUs, and clarify messaging to reduce cognitive load. Just as technical debt slows product delivery, GTM debt (too many plans, inconsistent positioning, orphaned channels) drags conversion and expansion. A quarterly cadence to pay down this debt keeps the system healthy.
The outcome is a repeatable motion: an engineered go-to-market system that compounds learning, supports product-market fit lessons, and scales across segments without breaking. If you lead product or growth, think like an architect, measure like an engineer, and refactor before your funnel stalls — your team, customers, and P&L will feel the difference.
Change is the job. I build and sell products to reshape behaviors and markets, yet I’m constantly reminded that change is hard. Going back to chemistry, catalysts don’t just create change by pushing harder or exerting more energy — they remove or lower the barriers to change. That framing has reshaped how I approach product strategy, go-to-market, and adoption.
One lens I return to is “The Catalyst: How to Change Anyone’s Mind.” It underscores a simple truth: the obstacle isn’t always the idea; it’s the friction around it. The book outlines 5 specific barriers to change, called REDUCE — which stands for reactance, endowment, distance, uncertainty, and corroborating evidence. I’ve found that when we diagnose which barrier is in the way, our product and GTM decisions get sharper, faster, and far more effective.
Do you really need a 10X better product? Sometimes yes—but not always. In practice, the biggest competitor I face isn’t another vendor; it’s inertia. Prospects cling to the status quo because switching feels risky, expensive, or cognitively heavy. My job is to make staying put feel riskier than moving forward. That means de-risking the decision, shrinking the perceived switching cost, and removing “homeostasis hooks” like entrenched workflows and sunk costs. When I design onboarding, migration tooling, and progressive rollouts, adoption climbs—even when the product advantage is 2–3X, not 10X.
Urgency matters, but pressure backfires. I aim for urgency that respects autonomy. Instead of “buy now or else,” I show windows of compounding value—why acting this quarter creates momentum, unlocks ROI, or secures outcomes that are harder to capture later. Time-bound pilots, seasonal use cases, or milestone-based pricing can motivate action without triggering reactance. The goal is momentum, not manipulation.
Freemium isn’t just for software. I apply the same principle—reduce uncertainty and upfront commitment—to physical products and services through pilots, limited-scope deployments, try-before-you-buy programs, refundable deposits, warranties, and modular packaging. The point is to let customers experience value with minimal friction. If it lowers uncertainty and builds confidence, it belongs in your arsenal.
On pricing and negotiation, I default to clarity, not concessions. I anchor on measurable outcomes, map tiers to value ladders, and use give-get rules so price changes are tied to scope or risk, not arbitrary discounts. This avoids signaling lower quality and keeps identity intact—buyers want to feel like smart stewards, not bargain hunters. Framing around business impact (“Here’s the cost of staying put versus the ROI of switching”) consistently outperforms feature recitations.
Identity and category creation are powerful accelerants. When a prospect feels an offer threatens who they are—or what team norms demand—adoption stalls. I reframe the story so the decision aligns with their identity (“modern operator,” “data-driven leader”) and, when needed, I redefine the category to reduce comparison shopping. If you’re a new category, you’re not asking buyers to replace an incumbent—you’re inviting them to adopt a better lens. That shift diffuses reactance and opens the door to new budgets and metrics.
Corroborating evidence matters most when stakes are high. I equip champions with proof that speaks to their peers: credible case studies, ROI models, third-party benchmarks, and pragmatic references. Multiple independent signals—especially from customers “like them”—shorten the distance between interest and commitment. I’ve seen adoption jump when we pair a hands-on pilot with peer validation at each gate.
Here’s the throughline I use with teams: don’t push harder—remove friction. Diagnose which barrier in REDUCE is at play, then pick a targeted tactic: restore agency to counter reactance, offset endowment with easy reversibility and migration, bridge distance with progressive steps, shrink uncertainty with trials and proof, and stack corroborating evidence at the right moments. When we build products and GTM motions around lowering these barriers, we don’t just sell better—we make change feel inevitable.
I sat down with Douglas Hanna, Chief Operating Officer at Grafana Labs. Grafana Labs is an observability stack built around Grafana, a leading open-source technology for dashboards and visualization.
Douglas is a seasoned revenue leader, previously leading operations and GTM strategy at Zendesk. At Grafana Labs, Douglas has been instrumental in scaling GTM at the open-source company — building up both team headcount and its revenue model.
In our conversation today, Douglas dives deep into the process of bringing products to market at an open-source company. That focus on disciplined go-to-market execution resonates with my own experience building product-led motions that respect the community while establishing clear, sustainable paths to revenue.
We explore the different facets of building and scaling a revenue model at an open-source company. Douglas opens up the GTM playbook at Grafana Labs sharing: I found these principles especially actionable for open source monetization, SaaS pricing, and zero to one B2B marketing.
“When to commercialize a feature vs. switch to a hosted version of a product” — In practice, I look for telltale signals: features that impose heavy operational burden (security, scale, multi-tenant reliability), generate significant infrastructure or support costs, or require advanced governance. That’s when a hosted version can deliver outsized value. For individual features inside the core, I favor commercialization only when the value metric is unambiguous and the user experience remains seamless for the community. The key is a clear migration path from self-managed to hosted, with pricing aligned to usage or outcomes.
“Tried and tested frameworks for pricing and packaging” — I anchor on a few staples: value metrics that correlate with customer outcomes, willingness-to-pay testing, and the 3C lens (customer, competition, company). For packaging, a tiered “good/better/best” model helps segment needs, while usage-based or consumption pricing can unlock elasticity for developer-led adoption. I’ve seen price fences (SSO, RBAC, advanced analytics, scale limits) work well when they map to enterprise readiness rather than core functionality.
“How Grafana Labs thinks about what to put behind a paywall” — I share the same philosophy: keep community-loved, foundational capabilities open to preserve trust and growth, and place enterprise-grade scale, compliance, and governance behind the paywall. This often includes SSO/SAML, audit logs, granular access controls, advanced alerting, longer retention, and premium SLAs. The litmus test is whether the paywalled capability primarily serves larger teams’ risk, reliability, and control requirements.
“How the GTM team was built over time” — The sequencing matters. Early on, lean into product-led growth with strong developer evangelism, documentation, and onboarding. As adoption accelerates, add sales-assist, solutions engineering, and forward deployed engineers to convert complex use cases. Over time, layer in customer success, pricing operations, and ecosystem partnerships. Hiring profiles evolve from generalists to specialists, but the connective tissue remains a tight loop between product, community, and revenue.
Throughout our discussion, I appreciated the rigor in tying pricing and packaging decisions to measurable value, while safeguarding the open-core experience. That balance is the difference between short-term monetization and durable category leadership in observability.
You can follow Douglas on Twitter at @douglashanna.
If you’re building or scaling an open-source business, these GTM patterns provide a pragmatic blueprint: lead with community, monetize enterprise needs, and align pricing to real-world usage. It’s a playbook that rewards trust, clarity, and iteration — and it’s one I’ve seen drive repeatable growth when executed with discipline.
I get asked constantly how I decide when to trust my gut, when to lean on data, and when to take a big swing versus iterate. As a product leader, my answer has been shaped by hard-won lessons building B2B SaaS, product-led funnels, and enterprise features. Recently, I revisited Slack’s approach to decision-making, product reviews, and balancing product-led vs sales-led growth—and distilled a set of practices I use with my teams today.
Noah Desai Weiss is the Chief Product Officer of Slack, and has an accomplished track record inside and outside of the company. He started Slack’s Search, Learning, and Intelligence division, led the Self-Service (SMB) Business, and led the Expansion and Virtual HQ product areas (responsible for Huddles, Clips, and more). Before joining Slack, Noah was the SVP of Product Management at Foursquare (raised over $390m), and was a Product Manager at Google.
The throughline for me starts with a simple truth: not all decisions should be data-driven. Early in a product’s life—or when exploring a novel experience—data is often either unavailable or misleading. That’s where intuition, taste, and judgment come in. I treat intuition as a hypothesis generator and momentum maker, then instrument quickly to validate direction. This blend of “When to use intuition vs data to drive decisions” has saved me from overfitting to small datasets and from analysis paralysis when speed was the real advantage.
I’ve learned that “Taste and judgment are learnable.” You can coach it. Review artifacts together. Run side-by-side comparisons of design explorations. Write down what “good” looks like and why. My teams keep a living gallery of exemplary UX patterns and empty-state copy that exemplifies our bar. Over time, this scales the craft of intuition across a larger org—just as “How Slack scales intuition across their product org” suggests.
Of course, there are “Challenges of intuition-led product building.” The biggest are founder or leader overreach and survivorship bias. I mitigate this with timeboxed discovery: we commit to a clear decision date, capture our priors in writing, and express our confidence as a range rather than a point estimate. This sets up a healthy dynamic for “Managing pace vs accuracy in decision-making.” We move fast when reversibility is high, we move slower when the blast radius is large.
Matching people to the work matters too. Some product problems are inherently ambiguous and benefit from researchers, designers, and PMs who derive energy from the unknown. Others are best led by optimization-oriented builders who light up when the metric moves. I’m explicit about “Matching people to data vs intuition-driven work,” and I rotate folks so they can build both muscles.
In remote and hybrid environments, I’ve found the most underrated traits are proactive context-sharing, crisp written communication, and the ability to create signal in Slack and docs. “Underrated qualities for remote workers” aren’t just stylistic preferences—they are execution speed ups. I look for people who make everyone around them smarter asynchronously.
On product process, I’m inspired by “How Slack runs product reviews.” My rubric: one problem statement, a tight narrative memo, the bet framing (assumptions, risks, kill criteria), and outcomes tied to “outcomes vs output OKRs.” We align on the decision owner, consent vs consensus, and the next irreversible checkpoint. This keeps reviews from becoming theater and pushes decisions to the right altitude.
Culture shows up in small moments. “The importance of a team’s ‘vibe’” is tangible: Do we demo early? Do we celebrate learned negatives as much as wins? Do engineers, designers, and PMs feel joint ownership of the experience, not just their function’s slice? When the vibe is right, latency from idea to insight collapses—and that compounding is everything in product discovery.
Portfolio balance matters. I aim for a mix that lets us keep shipping customer-visible improvements while reserving room for breakthroughs. “Balancing “big swings” with incremental improvements” requires explicit ring-fencing: 70/20/10 works well for many orgs. Big swings get stage gates and PR/FAQ-like artifacts; incremental bets get weekly ship cadence and tight measurement. When we miss, we run pre-mortems and decision journals, reinforcing “Rituals for good decision-making.”
Go-to-market is where strategy meets friction. My guidance on “Advice on product-led vs sales-led growth” is to design the handshake up front. Let product-led growth do the land—self-serve activation, collaborative aha, bottoms-up virality—and let sales-led growth do the expand—security, compliance, procurement, multi-workspace governance. Instrument the handoffs, define eligibility heuristics, and ensure pricing doesn’t punish adoption. This is also where “Which products should focus on end-users versus executives” gets real; optimize early journeys for end-user success while giving executives the portfolio-level control and analytics they require.
I’m continually impressed by “What Slack learns from Salesforce.” Enterprise trust, admin controls, and scalable GTM motions can coexist with consumer-grade product craft. That hybrid DNA is powerful. I’ve adopted similar patterns: build for end-user joy, layer enterprise-grade controls, and price to match value realization, not procurement theatrics.
Speaking of pricing, “Pricing lessons from Salesforce and Marc Andreessen” pushed me to keep pricing simple enough for PLG while being flexible enough for enterprise. Seat-based pricing remains intuitive for collaboration products, but usage and “SaaS pricing” add-ons can map value to heavy features without overcrowding your price page. The key is to test willingness to pay early, avoid grandfathering yourself into a corner, and treat packaging changes like product changes—with discovery, rollout plans, and success metrics.
Humility isn’t fluffy—it’s an execution advantage. “Slack’s humility and why it matters” resonates with how I try to lead: ruthlessly honest about what we don’t know, eager to learn from customers quickly, and unafraid to reverse course when the evidence changes. That humility turns into speed because we stop defending past decisions and start iterating toward truth.
When working with a strong product voice at the top, “How to build product with a product-focussed founder” comes down to mutually agreed principles. Capture the founder’s taste in explicit heuristics, define the moments where their judgment should overrule the process, and codify how dissent and disagree-and-commit work in practice. This protects clarity without stifling creativity.
Here are the topics I unpacked and continue to apply across teams: “When to use intuition vs data to drive decisions,” “The most underrated traits in a remote work environment,” “How Slack runs product reviews,” “The importance of a team’s ‘vibe’,” “Managing pace vs accuracy in decision-making,” “Balancing “big swings” with incremental improvements,” and “Advice on product-led vs sales-led growth.” Each one is a lever that compounds when used together.
Curious to learn more about Slack? You can try Slack Pro and get 50% off using this link.
