Merci Grace on PLG, hiring, storytelling, and building diverse teams at Slack

Executive overview

Most companies treat product-led growth as a tactic to bolt on later. At Slack, it was baked in from the first day of onboarding design — rooted in game design thinking, not growth frameworks.

The core levers: make value immediate, target connectors over average users, and treat the team-building problem as a product problem.

If a single person at any seniority level can pick up your product and get value without a conversation, you have a product-led product.

Storytelling and the founder edge

• Great pitches open in the middle of the action — skip the market slide, lead with the unique insight
• VCs back founders, not fundamentals; deals fail due to interpersonal dynamics more than business logic
• Start every narrative (pitch, blog, conference talk) with an outline and a clear arc
• Writing is the discipline that sharpens the story before you're in the room

How Slack built product-led growth

• The first growth role was called "new user experience," not growth — framing matters
• Core philosophy: "No one has built Slack before" — don't assume prior playbooks apply
• Aha metric: 3 real people + 50 real messages in a team; at 3 people, coordination breaks, making Slack's value obvious
• Push notifications to get users into their team simultaneously drove outsized retention gains
• Copying visible product decisions from competitors is dangerous — you can't see what's not working
• Social connectors in a user base are disproportionately valuable; make invites early, optional, and persistent throughout the product
• Trials: each additional free week converts incrementally more users — user buying timing has nothing to do with your revenue schedule

Product-led vs. sales-led: how to decide

• If adoption requires buy-in from a department head or integration with locked systems (PII, HR), it's sales-led by definition
• DevTools are the most underrated PLG success stories — any engineer can pick one up
• Day zero value is a prerequisite: if the pitch is "you'll appreciate this in six months," it won't sustain PLG
• PLG lowers the barrier in both directions — easy to enter, easy to leave; retention must be earned by the product itself
• Enterprise companies increasingly use PLG frameworks for expansion within accounts, not just initial adoption
• Bottom-up is a subset of PLG: the product must be adoptable by anyone at any level, not just a specific function

When to hire salespeople and a growth team

• Founders are always the first salesperson; hire a dedicated one only when demand outpaces founder bandwidth
• A second signal: customers begin expecting a salesperson — some enterprise buyers cannot purchase without one
• Start a growth team when white-glove onboarding converts well — that proves the value exists; growth makes it self-serve
• The first growth hire should have deep customer empathy and high internal trust, not just funnel expertise
• Don't wait for perfect instrumentation; growth work is largely product-specific and must be invented for your customer

Onboarding principles

• Design onboarding from day one of product design — it shouldn't be the last thing built
• The best onboarding uses the product itself to teach the product (e.g., a to-do list that asks you to check off a task)
• Carousels only work when swiping is the core product modality — otherwise users dismiss them immediately
• Plug-and-play onboarding frameworks won't feel native and often replicate features that didn't even work at the source company
• Schedule regular usability sessions — watching real humans sign up is embarrassing and essential
• Test alternatives with prototypes before arguing with stakeholders; a bake-off proves the point without conflict

Hiring for product roles

• Hiring is a two-way evaluation: find people positioned to thrive at this specific company, not just qualified in the abstract
• Assign a real take-home problem — offer 3 options and let the candidate choose; the choice itself reveals how they think
• Red flags: technically implausible solutions, weak narrative structure, inability to pick one direction for good reasons
• Slack was narrative-driven; the story always won over the number — screen for candidates who can structure a compelling case
• Great candidates demonstrate: sound technical judgment, creative but grounded solutions, clear measurement instincts

Building diverse teams

• Passive inbound and referrals will underrepresent women and people of color by default — actively go find candidates
• Women convert at lower rates on riskier opportunities; compensate by broadening the top of the funnel, not accepting "pipeline" as an excuse
• Early diversity creates a flywheel: two women on a team changes tone more than one; each hire makes the next one easier
• Avoid assuming any one hire fixes the problem — not every woman actively supports other women in the pipeline
• A more diverse team raises baseline standards of respect and behavior for everyone, not just underrepresented groups