Tag: startup compensation strategy

  • Old-School Selling Beats PLG in the AI Era: My GTM Playbook for 8‑Day Enterprise Deals

    Old-school, in-person selling is having a renaissance in the AI era, and I’ve seen why up close. From leading product and go-to-market teams through hypergrowth, I keep returning to one lesson: enterprise buyers still reward the teams who show up, orchestrate change management, and own outcomes end-to-end. The tech has changed; the human dynamics haven’t.

    Has the sales playbook changed in the AI era? The tools are faster and the surface area is bigger, but the core motion remains the same: “showing up” beats letting the marketplace decide. That’s why in-person enterprise rollouts still beat product-led motions, especially when the stakes include security, governance, and cross-functional adoption. You win by reducing organizational risk, not by assuming free trials will do the heavy lifting.

    Great enterprise sellers collapse silos. They sell to engineers and executives in one motion, pairing deeply technical validation with crisp business narratives. In my org, that means every high-velocity pilot has a dual thread: hands-on, eval-driven proof for the builders and a value architecture for the budget owners. When those motions run in parallel, time-to-value plummets and procurement friction fades.

    Selling to AI-native buyers who grew up on ChatGPT changes tempo, not fundamentals. The same seller, different tempo: 8 weeks vs. 8 business days. These buyers evaluate fast, expect clear ROI, and push for automation-first workflows. How AI-native buyers handle build vs. buy decisions comes down to build for differentiation and buy for acceleration. If you make procurement feel like product—frictionless, instrumented, and transparent—you’ll meet their bar.

    Process matters, but humanity wins. Building a robust sales process that still leaves room for unscripted moments is where trust is formed. I’ll never forget the story of the rep who taught a champion’s son guitar over Zoom—an unscripted moment that cemented a partnership. The lesson: raise the floor without capping the ceiling. Equip every rep with repeatable plays, then celebrate the creative instincts that make champions out of customers.

    In early GTM, why the three highest-leverage early sales hires aren’t sellers at all resonates with my experience. I prioritize a solutions engineer who can de-risk integration, a forward-deployed operator who can run the first rollout like a product manager, and a customer success lead who designs adoption paths from day zero. Together, they compress the value journey from proof to production.

    Compensation design shapes your talent market. The case for outsized commission accelerators for star sellers — and the kind of person they attract is real: magnets for competitors who close complex, multi-threaded deals and thrive with ownership. But beware: why too much process narrows the kind of seller you attract. Over-script it and you filter out the very people who can navigate ambiguity with customers.

    Under the hood, instrumenting the funnel from stage zero to close keeps the system honest. I track intent signals before pipeline, conversion by persona and use case, proof milestones, and time-to-value in production. The three pillars of GTM excellence for me are repeatable discovery, referenceable outcomes, and relentless enablement. And inside the leadership team, building peers who are 80% aligned, not 100% preserves healthy tension while keeping execution fast.

    AI is expanding the definition of enablement—whether AI is changing what good enablement looks like isn’t a theoretical question anymore. I see world-class teams arming reps with retrieval-first knowledge bases, sandbox environments, and objection libraries that evolve weekly. Meanwhile, selling against direct and implied competitors at once is the norm: your battlecard must cover “do nothing,” internal tools, adjacent categories, and new AI entrants—while you still remember why in-person enterprise rollouts still beat product-led motions for durable adoption.

    Planning horizons tighten in AI markets. How far out should a GTM leader be planning? I work a dual cadence: a rolling 6-week operating plan that’s ruthlessly tactical and a 2–3 quarter roadmap for coverage, enablement, and category storytelling. What a normal week looks like in hypergrowth blends customer time, pipeline triage, onboarding and enablement, deal engineering, and process tuning—always with one or two high-conviction bets that could bend the curve.

    References: Ahead: https://www.ahead.com; Amazon: https://www.amazon.com; Anthropic: https://www.anthropic.com; Attio: https://www.attio.com; Augment Code: https://www.augmentcode.com/; Cognition: https://cognition.ai; Cursor: https://cursor.com; Dani McCabe: https://www.linkedin.com/in/danielle-mccabe/; Datadog: https://www.datadoghq.com; GitHub Copilot: https://github.com/features/copilot; HubSpot: https://www.hubspot.com; Jeremy Powers: https://www.linkedin.com/in/jeremypowers/; JPMorgan: https://www.jpmorgan.com; Matt McClernan: https://www.linkedin.com/in/mattmcclernan/; MongoDB: https://www.mongodb.com; Nicole Rettinger: https://www.linkedin.com/in/nicole-rettinger-23b20465/; Notion: https://www.notion.com; OpenAI: https://openai.com; Parag Agrawal: https://www.linkedin.com/in/paragagr/; Parallel: https://parallel.ai; Snowflake: https://www.snowflake.com; University of Chicago: https://www.uchicago.edu; Windsurf: https://windsurf.com

    If you’re scaling an AI product today, pair a disciplined sales-led growth engine with the best of product-led growth: fast paths to proof, hands-on validation for builders, executive-level value mapping, and human moments that turn customers into advocates. That’s how you compress an eight-week cycle into five business days—and keep the expansion flywheel spinning.


    Book a consult png image
  • Stop Being the ‘CEO of Culture’: Build Scalable People Systems Like a Product Manager

    Stop Being the ‘CEO of Culture’: Build Scalable People Systems Like a Product Manager

    I keep seeing the same pattern: when people leaders try to be the “CEO of culture,” they stall. When they act like product managers, culture scales. In a recent deep-dive with Colleen McCreary, the Chief People Officer at Credit Karma, I explored exactly how to operationalize that mindset to drive durable results and employee retention at startups.

    With more than 20 years of experience in HR, operations, recruiting and M&A, Colleen has headed up the people function at companies such as Vevo, The Climate Corporation, and Zynga. She’s also seen the early-stages and scaled through multiple IPOs and acquisitions, which means she has a great perspective on the people problems founders tend to run into as their businesses grow.

    What stood out immediately is her operating system: she designs for the 80% and focuses on clarity, context, and consistency when building people organizations and crafting culture. As a product management leader, this resonates deeply with how we approach product roadmapping and sprint planning, as well as outcomes vs output OKRs — optimize for the majority use cases, make intent unambiguous, and deliver predictably.

    She walks us through some really tactical examples of that work, including how her team approaches compensation at Credit Karma and the reason they do promotions quarterly. In my experience, this cadence functions like a product release train for your startup compensation strategy — reducing ad-hoc exceptions, creating transparent expectations, and reinforcing fairness. The result is higher trust and healthier decision velocity when headcount scales.

    Equally powerful is her reframing of the role itself: she views the Chief People Officer not as the CEO of culture, but rather the product manager of the systems and tools that run the company. That shift unlocks rigorous thinking — requirements, trade-offs, user research, and iterative launches — for everything from onboarding and performance to recognition programs. Treating culture as a portfolio of interdependent systems turns soft notions into measurable, improvable products.

    We also examined how rewards and recognition were incredibly different at Zynga and Credit Karma, and why career growth isn’t just about a promotion. I’ve seen teams accelerate growth by expanding scope, deepening skills, and enabling lateral moves — especially during the IC to manager transition — instead of over-indexing on title changes. When you define multiple growth paths, you give top performers more ways to win without distorting your org design.

    Finally, we discussed whether to double down on strengths or focus on correcting weaknesses when it comes to performance. My playbook mirrors hers: set outcomes, coach to amplify superpowers, and shore up only the critical deficits that block those outcomes. This keeps the conversation anchored in impact rather than activity and aligns incentives across managers and teams.

    If you’re a first-time founder or an early people leader, the takeaway is clear: stop looking for a cultural silver bullet. Build an operating system for people the same way you’d build a great product — define the problems, prioritize, ship incrementally, and measure what matters. When you do, culture stops being a slogan and starts becoming your most reliable growth engine.


    Inspired by this post on First Round.


    Book a consult png image
  • Moments That Changed Us: Teresa Torres & Petra Wille on Leadership, Loyalty, and Product Discovery

    Moments That Changed Us: Teresa Torres & Petra Wille on Leadership, Loyalty, and Product Discovery

    Some conversations stay with you because they surface the hard-earned truths that quietly shape our judgment as product leaders. This episode of All Things Product with Teresa Torres and Petra Wille is one of those. As I listened, I found myself revisiting my own inflection points—times when prioritization became survival, when loyalty met reality, and when user research humbled my assumptions. What follows are the moments and mindsets I believe every product creator and product management leader can learn from.

    Listen to this episode on: Spotify | Apple Podcasts

    In this episode, Teresa and Petra swap the stories that shaped their careers. From navigating the fallout of the 2008 recession as a startup CEO, to realizing the company won’t love you back no matter how loyal you are, to the first user interviews that cracked open a new way of seeing product work—these are the pivotal (and sometimes funny) moments that changed everything. As I reflected, I connected these stories to practical patterns we all face: capacity limits that force clarity, leadership under uncertainty, and the discipline of product discovery.

    At [02:30], Teresa’s crash course as a startup CEO during the 2008 recession reminded me that there are seasons in product where perfect information doesn’t exist—only direction and conviction. I’ve been there. In those moments, we earn trust by making the next best decision, communicating trade-offs clearly, and moving. That’s leadership when the stakes are real.

    By [11:20], the conversation reframed prioritization as survival, not just a backlog exercise. I’ve learned the same lesson: hitting the limits of your own capacity reshapes how you prioritize. It’s not about doing more—it’s about deciding what not to do. In practice, that means aligning roadmaps to outcomes, not output, and letting OKRs focus the team on the few bets that matter now.

    At [18:45], Teresa shares the insight that unlocked her agency as a leader: “No one knows the answer.” That line is liberating. When we stop searching for the mythical right answer, we create space for informed bets, time-boxed experiments, and evolving product strategy. I’ve seen teams accelerate the moment they internalize this.

    At [29:10], Petra’s story—why the company doesn’t love you back—hits close to home. Loyalty is admirable, but without boundaries it becomes burnout. As leaders, we protect both people and outcomes by setting explicit expectations, designing sustainable on-call and delivery cadences, and recognizing impact early—long before a too-late pay raise tries to fix a deeper problem.

    The [42:05] moment about the pay raise that came too late is a textbook example of how retention is a lagging indicator. Compensation, growth paths, and recognition must be proactive. If you wait for exit interviews to learn, you’ve already lost institutional knowledge and momentum.

    At [50:15], Marty Cagan and Petra’s first user interviews at Starbucks show how humble, early customer conversations transform practice. Product discovery is not a ceremony; it’s a habit. Even scrappy interviews, when paired with a clear research objective and rapid synthesis, can change a roadmap. I encourage teams to start with simple, recurring conversations and make insights visible in sprint planning.

    By [01:02:00], the funny research fail—“close the window” taken literally—delivers the humbling reminder that you are not your user. Language is loaded. Tasks must be unambiguous. And when in doubt, ask one more clarifying question. Every usability study I’ve run has revealed at least one assumption I didn’t know I was making.

    Here’s what I took away as a leader and operator: capacity constraints are a gift if we let them focus us; uncertainty is the job, not a blocker; boundaries prevent burnout and build better products; and early, continuous user interviews keep us honest about outcomes over output. If your roadmap isn’t informed by real user context every week, it’s time to change your operating rhythm.

    Follow Teresa Torres: https://ProductTalk.org

    Follow Petra Wille: https://Petra-Wille.com

    Mentioned in this episode: The True Story of Struggles and Success Of A Startup CEO with Teresa Torres by Barry O’Reilly: https://barryoreilly.com/explore/podcast/the-true-story-of-struggles-and-success-of-a-startup-ceo-with-teresa-torres/?ref=producttalk.org

    Mentioned in this episode: Petra’s work on coaching product leaders: https://www.petra-wille.com/?ref=producttalk.org

    Mentioned in this episode: Marty Cagan: https://www.svpg.com/team/marty-cagan/?ref=producttalk.org

    Mentioned in this episode: iPAQ: https://en.wikipedia.org/wiki/IPAQ?ref=producttalk.org

    Have thoughts on this episode? I’d love to hear which moment resonated most with you and how it’s shaping your product practice. Share your perspective and let’s learn from each other.


    Inspired by this post on Product Talk.


    Book a consult png image
  • What I Learned from Molly Graham: Hard-Won Management Lessons from Google, Facebook & Quip

    What I Learned from Molly Graham: Hard-Won Management Lessons from Google, Facebook & Quip

    I sat down with Molly Graham, a seasoned exec and builder who particularly excels at helping startups to go not from 0 to 1, but from 1 to 2. She helped build and scale Facebook, Quip, The Chan Zuckerberg Initiative in their early days, and is now the COO of Lambda School. Every time I revisit her playbook, I find fresh, practical insights that resonate with my day-to-day leading product and scaling teams.

    Today, I zero in on management. In my role leading product management at HighLevel, I’ve seen — just as Molly has — how so many startup mistakes come down to general management issues. We unpack the traps that are easy to fall into, how to avoid reactionary leadership, and why deliberate operating mechanisms matter when the team and roadmap are growing fast.

    One counterintuitive practice I double down on: spend more time with your highest — not your lowest — performers. Your top talent sets the quality bar, accelerates product discovery, and protects employee retention at startups; investing in them compounds. I share how I structure 1:1s, goal-setting, and outcomes vs output OKRs so high performers stay aligned, unblocked, and energized.

    We also talk about managers who shaped our philosophies, the messy IC to manager transition, and the cadence that keeps teams focused without stifling autonomy. Expect concrete tactics you can use tomorrow, whether you’re a first-time manager or a seasoned leader scaling from dozens to hundreds.

    Two themes I return to often: codify your culture early, and ‘give away your Legos’. As scope expands, leaders who consciously hand off ownership create more opportunity, reduce bottlenecks, and build a resilient organization. On compensation, I outline a startup compensation strategy and the principles for setting up your first comp system so it’s fair, explainable, and scalable.

    If you’re building from 1 to 2, this conversation is a management field guide: clear mental models, practical rituals, and candid lessons learned from scaling product, people, and culture.


    Inspired by this post on First Round.


    Book a consult png image
  • Treat Operational Debt Like Tech Debt: Inside Elastic’s Distributed Work Playbook

    Treat Operational Debt Like Tech Debt: Inside Elastic’s Distributed Work Playbook

    I recently connected with Leah Sutton, SVP of Global HR at Elastic, to unpack how a truly distributed company operates at scale. Elastic’s fully-distributed employee base, which includes over 2,000 spread across 40 countries and 48 states, presents the kind of complex, real-world constraints that product leaders like me think about every day—signal-to-noise in communication, decision speed, and the compounding effects of process design.

    What stood out immediately was Elastic’s “distributed by design” company DNA. Leah’s remit spans HR operations, recruiting, and employee engagement, and the way these systems interlock felt remarkably product-like: clear ownership, explicit interfaces, and intentional defaults that remove ambiguity. As I listened, I kept mapping her operating principles to the way we instrument product teams for clarity and velocity.

    One of the most practical threads we explored was hiring and leveling for remote leadership—specifically, how to interview for leaders that can manage well remotely. In my experience, the best signals mirror the competencies we prize in product management leadership: written-first communication, outcomes over activity, latency-tolerant decision-making, and the ability to architect rituals (standups, docs, async reviews) that scale across time zones. I’m a fan of structured behavioral interviews that surface these capabilities with work samples and scenario-based prompts rather than abstract hypotheticals.

    We also dove into the operational realities of payroll and compensation across regions. The mechanics matter: consistent leveling, location-aware bands, and transparent principles for how currency, cost of labor, and market movement flow into offers and merit cycles. From a startup compensation strategy perspective, I’ve found that publishing your compensation “spec” (philosophy, exceptions policy, refresh cadence) dramatically reduces friction and improves trust—especially when paired with automation for eligibility, approvals, and audit trails.

    Elastic has also invested in tactics to mitigate the language and cultural barriers that often trip up global leadership teams. I’ve seen meaningful gains from a few simple, repeatable patterns: default-to-written with concise summaries in plain language, rotating facilitation to balance voices, timezone-inclusive scheduling with recorded context, and cultural onboarding that teaches teams how decisions actually get made. These are small, compounding design choices that preserve speed without sacrificing inclusion.

    Zooming out, Leah describes Elastic’s source code as not so much a traditional list of values but more the things that make Elastic, Elastic. That framing resonates with me—values as operating constraints, not wall art. When teams treat culture as an executable spec rather than a slogan, you get fewer surprises, fewer forks, and far more consistent decision quality across the organization.

    The concept that most energized me, though, was the push to treat operational debt like technical debt. In product organizations, we maintain backlogs, SLAs, and roadmaps for tech debt because we know it silently taxes every future sprint. Operational debt—fractured tooling, ad hoc onboarding, unclear decision rights, fuzzy compensation rules—creates the same drag. My playbook is to surface operational debt explicitly, size it with impact metrics (time-to-decision, cycle time, error rates, employee retention), assign ownership, and pay it down on a cadence—just like we do with code quality and reliability.

    If you’re leading HR, product, or a cross-functional team in a distributed environment, there’s a durable blueprint here: design for async by default, hire for written clarity and systems thinking, codify compensation principles, and manage operational debt with the same rigor you apply to technical debt. Learn more about Elastic’s source code here: https://www.elastic.co/about/our-source-code. You can follow Leah on Twitter at @leahesutton.


    Inspired by this post on First Round.


    Book a consult png image
  • Master Startup Compensation: Proven Tactics for Offers, Equity, and Retention at Every Stage

    Master Startup Compensation: Proven Tactics for Offers, Equity, and Retention at Every Stage

    Compensation is one of the most emotionally charged and strategically consequential decisions a startup makes. I recently dug deep into this topic with Kaitlyn Knopp, founder and CEO of Pequity, which automates HR workflows to make compensation more equitable and scalable. Her perspective resonated with my own experiences leading product teams, where pay clarity, fairness, and speed can make or break hiring and retention.

    Prior to starting Pequity, Kaitlyn built compensation programs and teams at companies like Instacart, Cruise, and Google — bringing a deep well of experience to this often complicated topic. That breadth matters: startup compensation strategy must evolve as you move from zero to one, to scale, and then to sustained growth.

    For founders making their first hires, I emphasize the same traps Kaitlyn flagged: ad hoc offers, one-off exceptions, and over-indexing on negotiation. Instead, I recommend a lightweight framework anchored in broad levels and an initial comp philosophy. This early scaffolding doesn’t need to be heavy or bureaucratic; it simply needs to be explicit enough to guide consistent decisions and communicate how salary, equity, and performance will work for the next 12–18 months.

    On offers, I take a balanced view of negotiating. There are pros and cons to negotiating offers, and over-negotiation can quietly erode internal equity and manager confidence. Rather than endlessly debating base salary, I lean on creative approaches outside of salary — such as the exercise window — to tailor offers within guardrails. And because many candidates (especially those who’ve never worked at a startup before) struggle to value equity, I always include a simple equity one-pager: how vesting works, potential outcomes, and what risk actually means in practice.

    As the company grows quickly, new challenges appear. Retaining existing employees requires intent, not improvisation. Equity refreshes are a powerful tool when tied to impact and market realities. I also pay close attention to the psychology of bonuses — they can motivate or misfire depending on timing, frequency, and clarity. During periods of inflation and salary adjustments, I favor a transparent narrative that connects the market, our compensation philosophy, and the choices we’re making this cycle.

    There’s a tempting trend toward highly individualized packages. While flexibility has its place, I’ve found that too much customization introduces hidden inequities and ongoing operational drag. The antidote is education. I invest in helping employees fully understand their comp — not just the headline numbers. That means straightforward walk-throughs of dilution and tax considerations, so folks see the real value and trade-offs over time.

    Here’s how I operationalize this playbook with my team: we publish a clear compensation philosophy; define broad levels and salary bands; standardize equity grant guidelines with built-in refresh logic; and formalize an offer review process to prevent one-off exceptions. We also equip hiring managers with candidate-facing materials to explain equity, stock options, the exercise window, vesting schedules, and potential scenarios. This reduces confusion, accelerates decision-making, and builds trust.

    For ongoing discipline, I treat compensation like any other critical product system: we set review cadences, define decision rights, audit for pay equity, and proactively monitor market signals. When we do run compensation changes (promotions, adjustments, bonuses), we pair them with simple, empathetic communication so employees understand the why behind the change — not just the what.

    No matter your stage, the goal is consistent and comprehensible startup compensation: an initial comp philosophy you can defend, offers that reflect both market and mission, and retention mechanisms that honor impact. Do these well, and you’ll ship faster, hire better, and keep your highest performers engaged for the long haul.


    Inspired by this post on First Round.


    Book a consult png image