Tag: product discovery

Master Modern Entrepreneurship: Build Lean, Start Young, and Obsess Over Customers

Modern entrepreneurship demands speed, clarity, and relentless customer focus. In my role leading product management and shipping category-defining features, I’ve learned that the fastest way to build enduring companies is to build lean, start young in our experiments, and study customers with scientific rigor. This is not about heroics; it’s about disciplined learning and making the market the ultimate arbiter of truth.

The foundational playbooks still guide my day-to-day: the Lean Startup approach and the timeless lessons from The Four Steps to the Epiphany and The Startup Owner’s Manual. Even in 2025, these ideas remain remarkably relevant because they center on one principle we can’t automate away—deep, direct customer understanding.

Why aren’t there more successful startups? Most teams conflate building with learning. They fall in love with solutions, optimize for output over outcomes, and skip the uncomfortable parts of customer discovery. Another pattern I see: teams ignore market type. The tactics for entering an existing market versus creating a new one are fundamentally different; using the wrong go-to-market playbook can erase months of runway.

Improving entrepreneurship in the USA starts with how we teach it. We should normalize hypothesis-driven product discovery in high schools and universities, pair students with real customers, and fund lightweight experiments instead of polished business plans. Programs modeled after The lean launchpad at Stanford demonstrate that when we combine mentorship, evidence, and speed, we create founders who learn faster than the market changes.

Lean Startup is also widely misunderstood. An MVP is not an excuse for low quality; it’s a vehicle for validated learning. The goal is to reduce uncertainty—not craftsmanship. The best teams run a cadence of testable hypotheses, instrument the product to capture evidence, and tie their roadmap to outcomes vs output OKRs so effort maps directly to measurable customer and business value.

Curiosity is the meta-skill. The founders who win are addicted to understanding “why” customers behave the way they do. Instincts matter, but instincts sharpen with reps. I treat instincts as hypotheses: hold them lightly, test them aggressively, and let the data upgrade your intuition.

Outlier founders often share similar traits: an early comfort with ambiguity, an almost irrational attachment to a future state, and a bias for action. That “irrational” conviction is a feature, not a bug—so long as it’s paired with a willingness to invalidate one’s own beliefs when the evidence contradicts them.

Becoming a great founder CEO requires a personal pivot from maker to multiplier. Early on, be the chief learner and chief seller. As traction builds, invest in systems—hiring bar, decision frameworks, and operating rhythms—that scale beyond your own heroics. I’ve found that clear product strategy, crisp decision rights, and outcomes vs output OKRs create the scaffolding for autonomy without chaos.

Why do some second-time founders fail? They overfit to their previous win, underestimate how much luck and timing played a role, or import a playbook that doesn’t match the new market type. The antidote is humility and fresh customer discovery—treat your new company like your first, and earn product-market fit again.

Building in existing versus new markets demands different muscles. In an existing market, your edge is focus, speed, and a sharp wedge that exploits a neglected segment or workflow. In a new market, your job is category education, sequencing use cases to reduce friction, and architecting distribution while the value narrative is still forming.

When I evaluate what makes a startup successful, I look for a learning velocity advantage: a team that runs more meaningful experiments per unit time than peers, converts insights into product changes quickly, and compounds those lessons into differentiation. Execution quality matters, but the compounding engine is the ability to discover truth faster.

On leadership, I often point to Satya Nadella’s transformation at Microsoft as a case study in rewriting culture through a growth mindset and customer-centric innovation. It’s a reminder that the “founder mentality” can be cultivated at scale when leaders change incentives, narratives, and mechanisms in concert.

The Four Steps to the Epiphany in 2023 (and beyond) still hold: Customer Discovery, Customer Validation, Customer Creation, and Company Building. I treat them as a continuous loop rather than a one-time sequence. Discovery never stops; validation is ongoing; creation evolves with channels and pricing; company building is the operating system that sustains the pace of learning.

If you’re building today, start smaller, learn faster, and get closer to the customer than your competition thinks is necessary. The compounding effect of disciplined product discovery, evidence-based roadmapping, and founder-led storytelling remains the closest thing we have to an unfair advantage.

October 20, 2025
From Zero to One: My Playbook for Building a World‑Class Sales Org (Lessons from Figma)

When I think about building a world-class sales organization from scratch, I look for playbooks forged in the hardest part of the journey: zero to one. Kyle Parrish, Figma’s first sales hire, built the company’s zero-to-one sales engine from scratch. Figma now has more than 3 million monthly users. Prior to Figma, Kyle spent 5 years at Dropbox in various sales roles. At Dropbox, Kyle successfully launched and scaled the Austin office to 100+ people, and then led the enterprise sales function in San Francisco and New York. Those facts anchor a set of timeless lessons I’ve applied in product management leadership and in partnering with sales to drive product-market fit and revenue.
The right time to build a sales function is when founder-led sales start to constrain learning speed and repeatability. Before hiring, I pressure-test three inputs: a clear ideal customer profile, a crisp value hypothesis supported by real usage, and a repeatable early sales motion that I can document. If I can’t capture the core narrative, top three proof points, and the qualification rubric on one page, I’m not ready to scale. That discipline protects runway and focuses product discovery on what truly moves the needle.
Who to hire first matters even more than when. I look for a builder-athlete—someone who thrives in ambiguity, writes their own talk tracks, and views every customer interaction as a product feedback loop. This person should be comfortable with founder-level context switching: discovery in the morning, enablement at lunch, and early pipeline surgery in the afternoon. I prioritize curiosity, writing clarity, and a history of winning in imperfect environments over shiny logos or rigid playbook adherence.
Integrating your first sales hire is as critical as selecting them. I embed them with product and support in the first 30 days, pair them with a designer or PM on weekly customer sessions, and give them a public Notion or doc to codify objections, narrative experiments, and qualification notes. The goal isn’t velocity at all costs—it’s precision learning at speed. That early collaboration helps us transition cleanly away from founder-led sales while preserving the product’s authentic voice.
Early sales motion should be simple, specific, and measurable. I start with a tight segment, insist on consistent discovery questions, and run weekly film reviews on calls to refine our narrative. If customers force me to constantly re-explain what we are, I treat that as a sign to evolve the story. It’s common to change the customer narrative as you learn which use cases actually land and expand. The best motions translate product magic into business outcomes without diluting what makes the product beloved.
On hiring and scaling, I favor a bar-raiser approach. The ideal experience sales candidates should have is less about title and more about evidence of building: writing the first playbook, proving repeatability, and showing that they can recruit talent better than themselves. Common traits of successful salespeople at this stage include intellectual humility, a builder’s bias, and an almost editorial standard for customer communication. I’ve seen unique hiring processes—live role plays with real customer objections, writing-based exercises, and cross-functional panels—consistently reveal signal that traditional interviews miss.
Outbound strategy should start narrow and be relentlessly measured. A small number of well-defined hypotheses, clean data, and tight messaging loops beat high-volume outreach every time. I’ve also seen segmented pricing and no discounts create the right incentives for clarity and value alignment. While discounting can appear to accelerate wins, it often erodes positioning and invites endless custom deals that break the product roadmap.
World-class sales culture is product-centric, rigorous, and kind. It prizes candor without ego, craftsmanship in discovery, and a respect for time—customers’ and teammates’. In practice, that looks like crisp deal reviews, transparent pipeline hygiene, and shared ownership of learning with product and engineering. Navigating the founder/Head of Sales relationship is easier when you align on definitions of a qualified opportunity, the ladder of proof for a narrative, and the weekly operating rhythm.
For ambitious salespeople, I offer straightforward advice: choose products you genuinely admire, ask better questions than everyone else, and write your learnings in public within the company. Your career compounds fastest when you become the teammate product and design proactively loop in. For early leaders, the most underrated skill is scaling yourself—documenting decisions, building systems that outlast you, and coaching your team to be better than you were at the same stage.
I’m often asked what differentiates exceptional founding leaders and early go-to-market operators. The secret to Dylan Field’s success is frequently framed around vision and product taste, but I also see a remarkable capacity to listen deeply and operationalize feedback without losing the soul of the product. Similarly, I’ve seen leaders like Oliver Jay model crisp execution and high-velocity learning—reminders that culture and cadence are strategic assets, not afterthoughts.
If you’re about to hire your first salesperson, simplify the brief: clarify who you serve, why you win, and what great looks like in the first 90 days. Start with a small, high-talent nucleus united by a passion for the product, then layer process only where it accelerates learning. Do a few important things exceptionally well, and let the results pull you toward scale rather than trying to push your way there prematurely.

October 20, 2025
From Vertical Focus to Power Users: My Playbook for Product-Market Fit and Founder Mindset

I’ve learned that the fastest route to product-market fit blends ruthless focus, a tight-knit community of power users, and a clear-eyed understanding of founder psychology. As a VP of Product, I’ve seen how aligning strategy and self-awareness creates compounding advantages—especially when you commit to a vertical, build with your most advanced users, and make decisions faster than your market shifts.

Start narrow. Building for a specific customer forces clarity: one ICP, one core job to be done, one measurable outcome. That single-threaded focus removes ambiguity from product discovery, sharpens prioritization, and accelerates iteration. Only after unmistakable pull—retention, compounding usage, and customer-led expansion—do I widen the aperture to a broader customer base.

Clay is a lead-generation software that uses AI to scrape 50+ databases and help companies scale their outbound campaigns. When I evaluate products like this, I look for a crisp vertical wedge (for example, outbound sales teams or growth marketers), a clear “time-to-first-value” path, and strong affordances for advanced workflows. Winning a vertical creates a reliable beachhead for expansion without diluting the core value proposition.

Power users are the engine of product evolution. I actively identify and convene them—by analyzing power-law usage patterns, high-complexity workflows, and frequent integration touches—then invite them into hands-on feedback loops. I’ve found small, recurring sessions where we co-design in Figma and document patterns in Notion to be especially effective. These users don’t just validate; they reveal emergent use cases, inspire templates, and shape the roadmap. The result is a community that evangelizes organically and sets a high bar for everyone else.

Speed is a strategy. I front-load decisions with clear success criteria, kill-switch thresholds, and a cadence of two-to-four-week sprints. The discipline isn’t just “moving fast”—it’s committing to bounded bets, reducing work-in-progress, and measuring outcomes over output. Focus is often misunderstood as doing less; in practice, it’s doing the essential few things completely and letting the data make the hard calls. This mindset unlocks faster iteration cycles and cleaner OKRs that reflect real customer value.

My principles for product-market fit are simple but demanding: undeniable engagement (habitual use without prompts), concentrated love from a specific customer archetype, willingness to endure friction for core value, expansion motions that begin with usage not discounts, and a backlog shaped by customer pull rather than internal aspiration. When these signals converge, you don’t ask, “Do we have PMF?”—you ask, “How do we scale responsibly?”

Founder psychology shapes the product more than most admit. A company is the reflection of its founder’s personality, from appetite for risk to tolerance for ambiguity. I align my own psychology with the business through honest self-inventory, explicit constraints, and a cadence of reflection. I’ve found the life spiral framework helpful to contextualize growth phases, and techniques from Internal Family Systems to reduce reactive decision-making. The outcome is a calmer operating system that scales with the company rather than against it.

Translating this into a customer journey, I design for a sharp “aha” moment within minutes, a guided path to first successful workflow, and a clear unlock that turns a single task into a repeatable motion. From there, I build leverage: templates, automations, and integrations that accelerate outcomes for advanced users while remaining accessible to newcomers. This is how individual success becomes team adoption—and team adoption becomes the basis for expansion.

To ground strategy in practice, I often pair discovery and build cycles with tools that meet teams where they already work: Airtable: https://www.airtable.com/, Clay: https://www.clay.com/, Figma: https://www.figma.com/, Internal Family Systems: https://ifs-institute.com/, NetSuite: https://www.netsuite.com/, Notion: https://www.notion.com, Sailthru: https://www.sailthru.com/. The stack matters less than the behaviors it enables: rapid prototyping, transparent collaboration, and decision trails that survive scale.

If you’re moving from first-time to second-time founder (or leading product through that evolution), the mindset shift is profound: less attachment to ideas, more attachment to evidence; fewer bets, bigger conviction; and a deeper respect for focus as an accelerant. Lean into vertical excellence, invest in your power users, and do the inner work. That’s how you achieve product-market fit—and keep it.

October 20, 2025
The Human Side of Engineering Leadership: Practical Plays to Build Creative, High-Performing Teams

Engineering leadership is a human sport first and a technical sport second. The longer I lead product and engineering teams, the more convinced I am that world-class execution comes from clarity, trust, and an environment designed for deep work — not just clever architectures or more process. In my role leading product, I see the biggest unlocks happen when we combine operational excellence with empathy and purpose.

My “utopia” — where engineers have time to create and invent — starts with sacred focus time. I protect no-meeting blocks, design sprints that include exploration, and carve out recurring capacity for prototypes and technical debt. When builders know they have sanctioned space to think, we get more product discovery, better ideas, and fewer last-minute heroics.

Shipping software at scale is difficult, and it’s harder to ship today than ever before. Complexity from microservices, compliance, security, platform fragmentation, and AI-driven surface area expands every quarter. The counter is operational hygiene: clear ownership, ruthless scope, a predictable release cadence, excellent tooling, and a culture that values outcomes over activity.

What makes a startup operationally sound is surprisingly simple to describe and hard to do consistently. Define decision rights, keep teams small and mission-aligned, instrument everything, and ship on a reliable train. Feature flags, dark launches, automated testing, and crisp rollbacks turn risk into routine. Most importantly, we write things down — intents, constraints, and success metrics — so execution scales beyond any single leader.

Product managers can dramatically improve engineering culture. The fastest way is through precision: sharp problem statements, explicit success metrics, clear acceptance criteria, and honest trade-offs. I hold our team to “outcomes vs output OKRs,” framing goals by customer and business value rather than task volume. PMs should also shield makers from thrash, resolve ambiguity quickly, and bring real users into the room early and often.

From an engineer’s perspective, good product management sounds like respect for the craft. We acknowledge performance budgets, technical constraints, and the hidden cost of complexity. We ask for estimates responsibly, show our work in decision docs, and make room for forward deployed engineers to close the loop with customers. When PMs consistently do these things, trust grows — so does velocity.

The role of product compared to design and engineering is easy to state and easy to forget: product owns the why and what, design owns how it feels, engineering owns how it works, and all three own the outcome. I treat the PM job as system optimization across functions — removing friction, sequencing bets, and maximizing learning per unit of time. When incentives are aligned to shared outcomes, handoffs turn into collaboration.

Micromanagement kills creativity. Declarative versus prescriptive leadership is the antidote: set the intent, define the constraints, agree on the measures of success — then get out of the way. I replace step-by-step tickets with a one-page brief and a weekly demo cadence. Guardrails create safety; autonomy creates ownership; together they create better software.

I foster a debate culture by making disagreement safe and productive. We write RFCs, invite dissent, time-box decisions, and “disagree and commit” when the window closes. Good debates chew on assumptions, not people. The payoff is compounding judgment and a team that can argue well without leaving scars.

Three leadership ideas I practice every week: first, default to clarity — ambiguity is the silent killer of execution. Second, manage energy, not just time — sustain the team’s battery with realistic pacing and visible wins. Third, train judgment — distinguish one-way doors from two-way doors and match decision speed to reversibility.

Understanding employee motivation is a superpower. People move for different reasons — mastery, autonomy, purpose, progression, compensation, recognition. I map motivations explicitly in 1:1s and shape work accordingly. When someone’s day-to-day aligns with what they value most, performance and retention both rise.

My advice on discovering what motivates people is straightforward: ask better questions and observe the work. I love asking, “What feels like play to you but looks like work to others?” I rotate responsibilities to run small experiments, then codify what sticks in growth plans. Motivation is dynamic; treat it like a product you’re constantly rediscovering.

On org design, I review team topology every six months. Strategy changes and customer needs evolve; our organization should, too. I favor lightweight reorgs — adjusting missions and interfaces rather than wholesale reshuffles — and I use rotations to refresh learning without destabilizing roadmaps. The aim is responsiveness without chaos.

One habit I see in successful leaders is relentless focus on outcomes. We inspect impact, not activity, using transparent scorecards, weekly business reviews, and OKR hygiene that spotlights real progress. When outcomes are the north star, prioritization becomes sane and teams feel meaning in their work.

Sound judgment is crucial for decision-making. I separate reversible from irreversible choices, run pre-mortems, and keep a decision log so we can learn at the portfolio level. Informed speed beats perfect slow, and fast follow-ups are a feature, not a bug.

Crystallized lessons from large-scale software environments keep proving true: cadence beats heroics, observability pays for itself, and investment in developer experience is the highest-ROI platform bet you can make. Also, write it down — clear artifacts are how complex systems learn together.

I stay wary of becoming irrelevant. The antidote is shipping, curiosity, and deliberate learning — talking to customers weekly, pairing with engineers, and letting junior talent teach me new tools and patterns. Relevance is earned every quarter.

If I had to pick one leadership lesson, it’s this: people remember how you made them feel. Trust, candor, and consistency create the conditions for excellence. The best strategy in the world won’t move if people don’t feel seen, safe, and challenged.

I’ve changed my mind on a few big things: more documentation beats more meetings, hybrid can outperform in-office with the right rituals, and smaller, more frequent reorganizations are better than large, rare ones. I used to think speed and quality were a trade-off; now I think clarity gives you both.

My growth has been shaped by thoughtful operators, designers, and engineers who taught me to balance ambition with stewardship. Their fingerprints are on these practices, and my teams’ results are better for it. The human side of engineering leadership isn’t soft — it’s the hard edge that makes everything else work.

October 20, 2025
Customer Success Masterclass: How I Design, Build, and Scale a World‑Class CS Org

Customer success is not a department I bolt on after product-market fit — it’s a strategic engine I design in parallel with product, sales, and support. In my role as VP of Product Management at HighLevel, I’ve learned that the fastest way to accelerate growth is to operationalize value delivery, from onboarding to renewal. In this masterclass-style breakdown, I share how I formalize customer success in early-stage companies, the hiring and compensation tactics that actually work, and the metrics and rituals that keep teams focused on outcomes.

When I formalize customer success at a startup, I start small and intentional. The goal of v1 isn’t scale — it’s clarity. I define the core moments that matter (onboarding, time-to-first-value, activation, expansion), codify the handoffs with sales and product, and set outcomes vs output OKRs so the team is measured on customer impact, not activity. Only once I can consistently predict value delivery do I introduce more specialization and automation.

Early hiring order matters. I typically hire ICs before building out a full CSM layer. Think implementation managers, solutions consultants, and forward-deployed problem solvers who can translate ambiguous customer needs into product-anchored outcomes. These folks create the playbooks and close the “last mile” between product capabilities and customer workflows — a prerequisite to scaling a durable CS org.

My tactics for hiring standout talent are simple and disciplined. I source for learning athletes who show a bias for action and executive presence, not just a customer-facing resume. I run structured interviews and working sessions that simulate real problems. Three questions anchor my evaluation: 1) Tell me about a customer who was at risk — how did you quantify the risk and what did you do? 2) Describe a time when you influenced product direction using customer evidence — what changed? 3) Walk me through a renewal or expansion you orchestrated — what was your strategy, and how did you align incentives across sales, product, and CS?

Fail-case patterns are consistent across stages. The most common are: reactive firefighting instead of proactive planning, weak business acumen (can’t tie product usage to business value), and poor cross-functional muscle (inability to influence product, marketing, and sales). I avoid these by probing for data fluency, systems thinking, and evidence of repeatable playbooks — not one-off heroics.

I actively consider candidates with non-traditional backgrounds. Teachers, analysts, management consultants, and product-adjacent operators often outperform because they are structured thinkers, exceptional communicators, and relentless about outcomes. I assess them through scenario work and mentorship plans that accelerate domain onboarding.

I index hard toward a bias for action. In interviews and trial projects, I look for people who quickly form hypotheses, validate with customers, and ship iterative solutions. The best CS operators don’t wait for perfect data — they create momentum while instrumenting the learning loops that improve precision over time.

Here’s what v1 of customer success looks like in my playbook: a crisp onboarding journey with defined exit criteria, a success plan that ties product capabilities to business goals, a lightweight QBR rhythm focused on outcomes, and a clear escalation path for risk. I keep the tooling lean and favor a living playbook over ornate process — speed and clarity beat bureaucracy.

Key early-stage customer success metrics include adoption and depth of feature usage, time-to-first-value, product-qualified accounts, renewal intent, gross and net revenue retention, and engagement signals from executives and power users. I complement the numbers with disciplined rituals: weekly risk reviews, a win/loss “value realization” debrief, and a Voice of Customer readout that feeds directly into product discovery.

Should customer success or sales own renewals? My answer: align ownership to your business model. If your product is value-expansive with complex deployments, CS should co-own or own renewals to manage risk and value realization. If your motion is highly transactional or heavily quota-driven, sales can own the paper while CS owns the health and expansion signals. What matters most is a single, unambiguous source of truth for renewal accountability.

Where customer success fits into the org depends on stage and strategy. Early on, I advocate for a direct line of sight to the executive team and tight integration with product and sales. As the company scales, I ensure comp plans, OKRs, and planning cadences keep incentives aligned across functions. Misalignment between CS and sales (especially on expansion vs retention) is one of the fastest ways to erode customer trust.

To distinguish a product problem from a customer success one, I ask: is the failure one-to-many and reproducible (product), or one-to-few and context-specific (CS and onboarding)? If multiple segments show the same friction, I escalate to product with evidence: cohort analysis, user journeys, and a prioritized hypothesis backlog. If the issue is account-specific, I focus on enablement, configuration, and stakeholder alignment.

There’s a simple way to reduce churn: make value realization explicit and measurable from day one. Define what “success” means with the customer, instrument usage and outcomes, review progress in standing rituals, and intervene early when leading indicators fall. A proactive executive sponsor program — including direct outreach from product leadership on at-risk accounts — can be a force multiplier.

To get honest feedback, I decouple discovery from renewal cycles, use third-party or product-led surveys, and create safe, structured avenues for critique (e.g., advisory councils with clear rules of engagement). I also return the favor: close the loop on what we learned, what we shipped, and what we’re shelving — customers reward transparency with candor.

When customer success and product teams collaborate well, the whole system accelerates. Product discovery gets sharper, roadmaps reflect real-world value drivers, and launch readiness improves because CS has co-authored the enablement and rollout plan. I treat CS as a core input to product discovery, not just a downstream implementer.

Structuring an early CS team is about coverage and clarity. I start with a player-coach leader and a few high-caliber ICs, define segmentation and ratios (e.g., enterprise vs scaled), and standardize handoffs with sales and support. As signals stabilize, I layer in specialization: implementations, technical success, renewals management, and scaled programs for long-tail accounts.

For compensation packages, I align variable pay to controllable, outcome-centric metrics: gross retention for core CSMs, net retention for expansion-focused roles, implementation milestones for onboarding teams, and shared targets with sales when collaboration is essential. I avoid activity-based comp and use tiered accelerators to reward durable, high-quality results.

Aligning customer success with the business model is non-negotiable. In a low-touch, product-led motion, I invest in scaled programs, education, and in-product guidance. In complex B2B software, I prioritize executive alignment, value engineering, and strategic QBRs that map product adoption to business outcomes. The throughline is the same: prove ROI, relentlessly.

In B2B software, the role of customer success is to operationalize value realization. That means orchestrating people, product, and process so customers achieve their outcomes faster, renew with confidence, and expand because the value is undeniable. When done right, CS transforms from “post-sales support” into a revenue-creating, product-sharpening discipline.

Common customer success mistakes I see repeatedly include spinning up process before purpose, underinvesting in onboarding, confusing relationship management with executive influence, burying CS under misaligned incentives, and measuring output instead of outcomes. Avoid these, and you’ll build a world-class customer success org that scales with conviction.

Referenced: Aaron Levie: https://www.linkedin.com/in/boxaaron/, Box: https://www.box.com/, David Love: https://www.linkedin.com/in/david-s-love/, Gainsight: https://www.gainsight.com/, Jon Herstein: https://www.linkedin.com/in/jonherstein/, Jonathan Lister: https://www.linkedin.com/in/jonathanlister/, Ken Fine: https://www.linkedin.com/in/kmfine/, Medallia: https://www.medallia.com/, Nick Mehta: https://www.linkedin.com/in/nickmehta/, Opower: https://www.oracle.com/utilities/opower-energy-efficiency/

October 20, 2025
How to Find Your Product Wedge: Battle‑Tested SMB SaaS Lessons from Square, Gusto, and My Playbook

Every enduring platform I admire started with a sharp product wedge—an unmistakably form‑fitting solution to a painful, persistent problem. In my own work leading product teams, I’ve seen how a great wedge unlocks momentum, trust, and distribution long before you earn the right to build horizontally. In this piece, I break down what I’ve learned from studying companies like Square and Gusto, and share the practical playbooks I use to find wedges, scale them, and turn them into platforms.

SMBs require unique software solutions because their constraints are different: time is scarce, tasks are juggled by a small team, and workflows span both the front of house and the back office. What wins is software that collapses steps, automates compliance, and delivers clear ROI in hours—not quarters. If you can’t demonstrate immediate utility and reduce cognitive load, you won’t earn a second week of usage, let alone loyalty.

The level of specificity required when building for SMBs is higher than many expect. “Form‑fitting” isn’t just a metaphor—it’s the difference between adoption and abandonment. In practice, that means obsessing over the exact moments of friction: where data gets retyped, where the cash drawer doesn’t reconcile, where payroll rules create anxiety. The fastest way to a wedge is to remove a choke point so completely that your product becomes the default way of working.

Building vertical versus horizontal SaaS is a strategic fork in the road. Verticals can win by encoding industry nuance (menus, wage rules, inventory, tip pooling), which drives faster adoption but narrows TAM and increases service intensity. Horizontal suites maximize TAM but risk feeling generic until they’ve earned trust. The play is often sequential: tight wedge first, then carefully adjacent expansions that preserve the original fit while compounding value.

Inside strong product orgs, decision‑making frameworks make that sequencing explicit. I lean on outcomes vs output OKRs to clarify what must improve for customers, not just what we plan to ship. I pair that with crisp guardrails—who we are building for, what problems we solve end‑to‑end, and what we intentionally ignore—for speed and focus. When everyone knows the game we’re playing, we can move faster with fewer meetings.

How to build horizontally from a wedge product: start by mapping the “jobs” that cluster around your wedge and identify which are triggered before, during, or after your core workflow. Expand into the nearest job that either (1) eliminates a costly handoff, (2) compounds your data advantage, or (3) increases switching costs without increasing complexity. Sequence matters; stitch together two workflows perfectly before you add a third.

I use The Three Horizons Model to balance the portfolio. Horizon 1 protects and grows the wedge with relentless quality and speed. Horizon 2 extends into adjacencies that deepen customer value and LTV. Horizon 3 explores new bets with asymmetric upside. The discipline is to time‑box and stage‑gate Horizon 3, so you develop options without starving the core or confusing the narrative.

Crafting a compelling vision for products means painting a clear picture of the world customers want—and the shortest believable path to get there. The vision should connect the wedge to a future platform, but every waypoint must feel pragmatic. When assessing Horizon 3 bets, I look for early signs of inevitability (regulatory tailwinds, data scale effects, platform shifts) and a credible edge we uniquely possess.

To give product teams the freedom to try things, I design for speed with safety: small, API‑first modules, toggled rollouts, and success metrics agreed upon upfront. Creating a risk‑taking culture isn’t about celebrating risk; it’s about celebrating validated learning. Make it cheap to run thoughtful experiments and easy to kill what doesn’t work.

Developing good product sense and intuition takes deliberate practice. I treat it like athletic ability: you can’t outsource reps. The fastest builders I know run weekly customer conversations, share raw call notes, and practice “storyboarding” real workflows until they can spot friction on sight. Five signs of great product sense: you predict failure modes before launch, you simplify scope without losing the magic, you can articulate the must‑have moment, you measure what matters, and you know when to say “not yet.”

Shipping faster without increasing headcount comes from better constraints, not heroics. I favor fewer, larger bets; pre‑wired cross‑functional pods; ruthless de‑scoping to the must‑have moment; and a zero‑tolerance policy for work that doesn’t move a core metric. Shorten the distance from insight to production, and speed shows up everywhere.

Generative AI is reshaping product discovery and prototyping. Tools like Copilot are accelerating content generation, scaffolding, and testable flows, which lets teams validate value propositions earlier and with more fidelity. I use gen AI for product prototyping to pressure‑test onboarding copy, simulate edge cases, and explore variations that would have taken weeks to mock by hand.

If you’re building for SMBs today, choose a wedge you can dominate, prove undeniable value fast, and then expand deliberately—one adjacent workflow at a time. The companies we admire didn’t skip steps; they sequenced them with conviction.

References and resources worth exploring:

Alyssa Henry: https://www.linkedin.com/in/alyssa-henry-0905692/

Copilot: https://copilot.microsoft.com/

Gokul Rajaram: https://www.linkedin.com/in/gokulrajaram1/

Gusto: https://gusto.com/

High Output Management: https://amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884

Marty Cagan: https://www.linkedin.com/in/cagan/

Opendoor: https://www.opendoor.com/

Silicon Valley Product Group: https://www.svpg.com/

Square: https://squareup.com/

The Three Horizons Model: https://www.mckinsey.com/enduring-ideas-the-three-horizons-of-growth

Toast: https://pos.toasttab.com/

October 20, 2025
Scaling Enterprise AI That Sells: Battle-Tested Playbooks for PMF, Champions, and Agentic AI

Enterprise AI is exhilarating and unforgiving. I’ve seen gorgeous demos fall apart under real-world constraints and seemingly modest pilots unlock outsized value at scale. In this reflection, I share the playbooks I rely on to build, scale, and sell generative AI in the enterprise—what actually moves deals, secures product-market fit, and sustains trust with the C-suite and the front line.

Why is it so difficult to scale AI products for enterprise? Because the bar is higher on every dimension: data governance, security, extensibility, integration depth, reliability, and measurable ROI. An enterprise-grade, full-stack generative AI platform isn’t just a model; it’s the surrounding system—observability, evals, policy, workflow, and human-in-the-loop—that makes outcomes predictable, auditable, and safe. The fastest path to adoption is simple: deliver on-brand, on-policy content and decisions using a customer’s first-party data, and prove that quality holds up under load.

My north star is dependability over demo magic. The number one challenge is making model output dependable across messy, high-variance enterprise inputs. I build an evaluation harness early, with gold datasets, task-specific metrics, and human adjudication. Every change ships behind guardrails and is measured against cost, latency, and quality SLOs. When governance, change management, and procurement show up (they always do), I treat them like first-class product requirements, not hurdles.

Champions are the secret to winning complex accounts. I map the org, find operators who feel the pain daily, and quantify that pain in dollars and hours. Then I define success criteria upfront—time-to-value in under 30 days, measurable uplift (e.g., deflection, conversion, cycle time), and a plan for scale. I deploy forward deployed engineers alongside the business to co-design workflows, refine prompts and evaluators, and document before/after outcomes. Champions don’t just approve pilots; they co-author the business case and defend it.

To win the enterprise, trust architecture matters as much as model architecture. I lead with clear answers on data residency, encryption, SSO, RBAC, DLP, and retention policies; I address whether customer data trains models, default behaviors, and opt-in controls. I offer flexible deployment (VPC or private networking when needed), transparent pricing, and SLAs with real teeth. I also integrate where work already happens—CRM, help desk, knowledge bases—so value shows up in the flow of work.

Signs of healthy product-market fit are unmistakable: pull from lookalike buyers, multi-threaded expansions, champions who present results internally without me in the room, and usage that moves from experimentation to business-critical. I watch for weekly active usage above pilot thresholds, POCs converting to multi-year deals, and adjacent teams (Support, Marketing, Legal, RevOps) asking to onboard with minimal push. PMF feels less like persuasion and more like coordination.

Scaling large language models for specific use cases requires ruthless focus. I constrain scope to tightly defined workflows, pair retrieval with structured knowledge, and mix model strategies (base models, fine-tunes, tools, and function calling) based on cost and latency budgets. I codify policy-as-code and deploy guardrails at the orchestration layer, not just the model layer. Continuous evaluation—both automatic and human—is the heartbeat of quality.

My advice to AI founders in 2024 is pragmatic. Start with outcomes, not demos. Establish outcomes vs output OKRs that tie directly to revenue, cost, risk, or customer experience. Use gen AI for product prototyping to shorten discovery cycles, but graduate quickly to instrumented workflows in production. Align early with InfoSec and Legal; your speed will be gated by trust, not code. And when in doubt, ship smaller, safer increments faster.

Healthy co-founder relationships look the same across winning companies: clear domains, fast escalation, and a shared appetite for “disagree and commit.” I keep a decision log, time-box debates, and make moments-of-truth visible to the team and board. You’ll know it’s working when you have more energy after hard conversations than before.

The future of agentic AI is deeply enterprise: multi-agent workflows that plan, act, and verify with human oversight where it matters. The winners will combine reasoning, tool use, retrieval, and policy with audit trails that satisfy compliance while keeping velocity high. Think of it as re-engineering business processes around AI-native steps, not sprinkling AI on top of legacy workflows.

Culture turns strategy into reality. I anchor my teams on “connect, challenge, and own.” Connect means obsess over the customer problem and internal alignment. Challenge means we red-team our ideas, run experiments, and measure impact. Own means we accept outcomes, not just output, and we iterate until the business moves. This is how a customer support ai strategy becomes a durable moat, not a slide.

If you’re a product creator or product management leader, the above playbooks are meant to be lifted and adapted. Start where the pain is loudest, quantify the win, and let champions carry the story. The compound interest of disciplined product discovery, strong governance, and relentless evaluation is a generative AI business that sells itself—and scales.

October 20, 2025
DevTools at Scale: Hard-Won Lessons on PMF, AI, and Culture from Apple, AWS, Microsoft

Building and scaling DevTools has taught me that world-class culture and relentless product focus are non-negotiable. Drawing on experiences across Amazon, Apple, and Microsoft—and hard-won lessons from startups like Unblocked and Buddybuild—I’m sharing the principles I rely on to ship great developer products at scale.

Why building for developers is different: developers are discerning, allergic to friction, and quick to churn if the DX isn’t exceptional. That means fast setup, clear docs, ergonomic APIs, sane defaults, and deep integrations with GitHub, GitLab, Bitbucket, Confluence, AWS, and Microsoft Azure.

I benchmark teams against gold-standard platforms like Stripe, Twilio, and Looker—tools that reward mastery, never bury the lede, and make success observable in minutes, not days.

From the early days of Buddybuild, the signal was unmistakable: remove toil from CI/CD, shorten feedback loops, and teams will expand usage without a sales nudge. The pattern holds across DevTools: when time-to-value approaches zero, the product sells itself.

Early signs of product market fit: organic team-to-team adoption, repeatable setup success, contribution from power users, and inbound demand you cannot keep up with. When these show up, “Why great product is everything” stops sounding like a platitude and starts reading like a P&L.

Monetizing product market fit is straightforward if you align value and pricing units. Seat-based maps to collaboration; usage-based maps to compute, API calls, or storage; hybrid models reduce edge-case friction. Keep the packaging simple and double down on “The power of positioning.”

AI is complicating product market fit. Gen AI accelerates gen ai for product prototyping, but it also introduces instability: model drift, hallucinations, and evaluation blind spots. I build an evaluation harness, human-in-the-loop review for risky flows, and a clear customer support ai strategy before scaling.

Being customer-obsessed is the moat. I embed forward deployed engineers with key customers to translate real workflows into product decisions, close the empathy gap, and validate behavior in production environments.

On decision-making, I blend product discovery with crisp documents and measurable bets: PRFAQs or design docs to clarify intent, guardrails in analytics, and outcomes vs output OKRs to keep teams aligned to impact.

Unblocked, a developer tool that lets you talk to your codebase, points toward a future where code search, context, and refactoring converge into conversational workflows. I’m bullish on the pattern, but I stay sober about failure modes and cost-to-serve.

Here’s my cautious take on AI: latency, privacy, and provenance matter as much as model quality. The best teams treat prompts as product, training data as liability, and evaluation as a first-class release gate.

Hiring is where many teams stumble. Don’t over-index on competency when hiring. I optimize for learning velocity, ownership, and kindness under pressure. Competency scales output; character scales organizations.

As a second-time founder and operator, I treat mental health like uptime. I schedule recovery, define non-negotiables, and surround myself with peers who normalize the hard days. Burnout is a systems failure, not an individual weakness.

I don’t do demos. I prefer self-serve trials with instrumented onboarding, sample projects, and guardrails that let the product do the talking. If a prospect can’t succeed in 15 minutes, we fix the product, not the deck.

On customer feedback, I separate noise from signal with cohorts and context. I prioritize requests that reduce time-to-value, unblock integrations, or meaningfully expand the surface area of successful use cases. That’s how to deal with customer feedback without losing strategic focus.

To build and scale DevTools, keep the bar high and the loop tight: ship small, watch usage, learn fast. Invest in platform reliability, rock-solid SDKs and CLIs, and a developer experience that earns trust release after release.

Resources and touchstones I revisit often:

Apple’s acquisition of Buddybuild: https://www.cnbc.com/2018/01/02/apple-agrees-to-buy-buddybuild.html

AWS: https://aws.amazon.com

Bitbucket: https://bitbucket.org

Confluence: https://www.atlassian.com/software/confluence

GitHub: https://github.com

GitLab: https://gitlab.com

Looker: https://looker.com

Microsoft Azure: https://azure.microsoft.com

Stewart Butterfield: https://www.linkedin.com/in/butterfield/

Stripe: https://stripe.com

Twilio: https://twilio.com

Unblocked: https://getunblocked.com/

If you’re building for developers, stay ruthless about simplicity, respectful of their time, and obsessed with proof in production. That’s how durable product-market fit is earned—and monetized.

October 20, 2025
A Masterclass in Founder Conviction: Gong’s $100m ARR, PMF Breakthroughs, and AI Sales

I’ve long believed that true product leadership is measured by conviction you can defend with data. That’s why the story of Gong resonates so deeply with me. Eilon Reshef is the co-founder and CPO at Gong, an AI-powered platform that tracks, records, and analyzes sales calls to drive revenue growth. In 2021, Gong raised $250M at a $7.25B valuation. Gong was one of the fastest SaaS companies to hit $100m ARR, and now has over 4000 customers. Before Gong, Eilon sold his previous e-commerce startup, Webcollage. Why does this matter to product creators like us? Because betting on recording sales calls wasn’t a popular opinion at the time—it was a bold thesis about conversation data as the primary system of record for revenue. The insight was simple and powerful: conversations are the most unstructured and under-utilized signal in B2B sales. Capture them end-to-end, analyze them with AI, and you unlock repeatable sales execution at scale. I was bullish on this category early for the same reason: recording sales calls converts ephemeral “tribal knowledge” into searchable, coachable truth. That enables better product discovery, sharper positioning, and tighter feedback loops between go-to-market and product—even more so as gen ai capabilities matured. Early product-market fit signals were unmistakable: persistent usage by frontline reps, managers organically building coaching rituals around insights, and executives tying outcomes to pipeline velocity and win rates. The emergence of “raving fans” wasn’t a vanity metric—it was the leading indicator that the product was changing behavior and embedding into daily workflows. Keeping the beta lean was crucial. Instead of building a feature buffet, the focus stayed on a few, high-utility workflows that consistently delivered value in the wild. In my own teams, we mirror this with forward deployed engineers and a tight set of design partners who are willing to co-develop, tolerate rough edges, and trade early access for tangible impact. Design partners, when chosen well, become your reality check and your accelerant. Their hardest problems guide prioritization; their workflows reveal where friction truly lives. This is where outcomes vs output OKRs matter—measuring behavior change and revenue outcomes, not just shipped features. The initial demo reactions often sounded like a referendum on change management: legal concerns about recording, rep discomfort, or doubts about AI accuracy. Strong founder conviction met these with data and empathy—clear consent frameworks, rapid improvements in transcription and modeling, and, most importantly, undeniable win stories that reframed risk as opportunity. Monetization followed the value. Pricing and packaging worked best when buyers could connect usage directly to measurable outcomes: faster ramp, better forecast accuracy, higher conversion rates, and more consistent deal execution. With a land-and-expand motion, teams saw success at the manager pod level before scaling across the org. I appreciated the disciplined approach to the roadmap. A unique product roadmap framework anchored on durable customer outcomes created internal clarity: which insights change coaching, which recommendations change behavior, and which automations remove repetitive work. This is classic product management leadership—create alignment with narrative, evidence, and a few high-conviction bets. The journey to multi-product was a natural extension of product-market fit. Start with conversation intelligence; expand to adjacent revenue workflows where the same data asset offers compounding value—forecasting, deal risk, enablement, and coaching. The throughline: one trusted data layer, many value surfaces. Having built AI products since 2015, I’ve learned to prioritize data quality, model reliability, and tight human-in-the-loop design. The best gen ai experiences pair high-recall analysis with opinionated UX that guides managers and reps to take the next best action. That’s how you turn insights into habits. Looking ahead, the future of AI in B2B sales efficiency is practical autonomy: assistants that summarize calls, draft follow-ups, update CRM fields, flag risks, and trigger playbooks—without adding workflow friction. The winners will combine precision models, secure data handling, and workflow-native delivery. Measuring success goes beyond dashboard vanity. What matters: adoption depth across roles, coaching frequency, deal cycle time, conversion lift, forecast accuracy, and the creation of “raving fans” who advocate internally and externally. When the product becomes the backbone of pipeline conversations, you’ve crossed the line from tool to system. I also see enduring relevance in foundational thinking like Crossing the Chasm. It explains why design partner fit precedes market fit, why early majority buyers demand social proof, and why operational excellence matters as much as product insight during hypergrowth. If you want to explore the broader ecosystem and resources mentioned, here are the references exactly as noted: Act-On Software: https://act-on.com/ Amit Bendov: https://www.linkedin.com/in/amitbendov/ BlueJeans: https://www.bluejeans.com/ Crossing the Chasm: https://www.amazon.com/Crossing-Chasm-3rd-Geoffrey-Moore/dp/0062292986 Gong: https://www.gong.io/ Mistral: https://mistral.ai/ OpenAI: https://openai.com/ Salesforce: https://salesforce.com/ Webcollage: https://www.crunchbase.com/organization/webcollage Webex: https://www.webex.com/ Zoom: https://zoom.us/ Where to find Eilon Reshef: LinkedIn: https://www.linkedin.com/in/eilonreshef/ For product leaders, the takeaways are clear: anchor on customer outcomes, cultivate design partners who become co-authors of your roadmap, use gen ai for product prototyping to accelerate discovery, and measure conviction not by opinions but by repeatable revenue impact. That is the essence of durable, product-market fit lessons you can operationalize today.

October 20, 2025
Build Platforms, Not Apps: My Playbook to Delight Customers and Scale Product Strategy

I’ve been reflecting on the product lessons behind a career arc that has reshaped multiple industries. Adam Nash is the co-founder and CEO at Daffy, a platform that makes it easier to donate to charities and non-profits. Before Daffy, Adam was the President and CEO at Wealthfront, where he scaled the company’s assets under management from $100M to over $4B. Adam has also held leadership and technical roles at Dropbox, LinkedIn, eBay, and Apple. As a VP of Product Management, I see enduring patterns in these experiences that every product creator can apply. Over the last decade, many teams have felt that the world is less disruptive than expected. In my view, this “slowness” is less about a lack of innovation and more about the compounding dominance of distribution and platform effects. When platforms harden, apps struggle to break through. That’s why I coach my teams to design for platform leverage from day one—assume the game is about ecosystems, not just features—and to build product discovery loops that create new access, not just new interfaces. We’ve also tended to think about luck incorrectly. What looks like luck is often preparation meeting a catalyzing platform moment. The most resilient companies build the capacity to take advantage of inflection points when they arrive—technically, organizationally, and with a clear point of view on where customer value is migrating. This is product management leadership in practice: orchestrating readiness for the inevitable change while staying grounded in outcomes vs output OKRs. Consider how eBay survived the dot com bubble. The lesson I carry forward is simple but powerful: when your core product creates real network utility and trust, shocks can prune the market and strengthen your position. Liquidity, clear incentives, and disciplined execution make a marketplace anti-fragile. I’ve applied this mindset by prioritizing durability over novelty, especially in critical user flows where reliability trumps speed of iteration. Founders should build platforms, not apps. Platforms create compounding advantages: data network effects, extensibility, and a value surface that invites others to build with you. Apps often cap out at feature parity; platforms unlock a persistent widening of the moat. My test: if your roadmap doesn’t include APIs, a partner strategy, and a value-creation flywheel that improves with every user and contributor, you’re likely shipping an app. If it does, you’re on a platform path. What made LinkedIn successful offers a crisp strategy lesson: good company strategy = good product strategy. When the company’s mission, business model, and product bets align around a clear customer job-to-be-done, execution accelerates. Setting strategy isn’t a document; it’s a cascade of decisions that translates into what we ship, how we measure, and which trade-offs we make. In 2009, that meant focusing on the highest-leverage network use cases and aligning metrics with durable member and ecosystem value. Not every great idea finds its market on the first try. Why KaChing didn’t work and pivoting to Wealthfront underscores core product-market fit lessons: you can’t will a market into existence, but you can iterate into it if you listen to customer behavior, not just customer requests. One universal lesson on customer acquisition I’ve seen repeatedly: the most efficient growth happens when the product itself reduces anxiety and increases clarity at the precise moment of decision. That’s why I treat growth like a product problem—friction maps, value timing, and onboarding narratives are as strategic as any feature release. Leadership transitions are inevitable in growing companies. My advice on successful leadership transitions is to plan them early, be explicit about decision rights, and make “how we decide” a visible artifact across the org. How to delegate moral authority is just as critical as delegating operational authority; teams move faster when they understand not only what to do, but why it is the right thing to do for customers and the company. There’s a real problem with metrics and customer requests when they become the only signals that matter. Metrics are rear-view mirrors and customer requests are often local optima. The craft is to synthesize signals into convictions—and then to earn trust by shipping the right things. Apple’s approach to “delighting” customers is a reminder that delight is not random whimsy; it’s a disciplined practice of removing cognitive load and amplifying emotion at key moments. I use the 70/20/10 rule you’ve never heard about to balance roadmaps: 70% on core commitments, 20% on accelerants, 10% on bold, “delight” experiments. How Daffy ships “delight features” shows how even financial and charitable products can surprise and delight without sacrificing clarity or compliance. Here’s the playbook I carry forward: build platforms, not apps; align company strategy with product strategy; treat growth as a product problem; make leadership transitions a strength, not a risk; and systematize delight so it shows up predictably, not accidentally. Above all, keep your OKRs centered on outcomes, not outputs, and let product discovery be the engine that finds truth faster. Referenced resources I keep handy for deeper study: Andy Rachleff: https://www.linkedin.com/in/rachleff/ Bill Gates: https://www.linkedin.com/in/williamhgates/ Daffy: https://www.daffy.org/ Daffy’s 2023 Year in Review: https://www.daffy.org/resources/year-in-review-2023 eBay: https://www.ebay.com/ Jeff Weiner: https://www.linkedin.com/in/jeffweiner08/ Reid Hoffman: https://www.linkedin.com/in/reidhoffman/ Robinhood: https://robinhood.com/ Ryan Roslansky: https://www.linkedin.com/in/ryanroslansky/ The Innovator’s Dilemma: https://www.amazon.com/Innovators-Dilemma-Clayton-M-Christensen/dp/0062060244 Tim Cook: https://www.apple.com/leadership/tim-cook/ Wealthfront: https://www.wealthfront.com/

October 20, 2025
Build Enduring Software: Minimum Remarkable Products, Customer-First Culture, and Org Design Lessons

Some software companies endure and compound while others flash and fade. As a product leader, I’m constantly studying why, and I keep returning to a set of timeless principles that bridge strategy, culture, and execution. In this personal reflection, I synthesize lessons that help teams build software companies that last—and products customers love—while sharing how I apply them day to day. Alyssa Henry is the former CEO of Square, a financial services company providing products and services used by over 4 million merchants. Formerly at Amazon, Alyssa led the development and growth of Simple Storage Service (S3) at AWS. Alyssa now serves as an Independent Director at Intel and Confluent. Here’s the lens I use to unpack durable product leadership: Lessons from Amazon, Microsoft, and Square; “Minimum Remarkable Products” versus Minimum Viable Products; Navigating different work cultures in big tech; Insider reactions to the disruptive launch of AWS; “Pioneer” versus “fast-follower” companies. Across companies and stages, I’ve found “Noticeable consistencies in the human condition” that matter far more than we admit: people seek meaning, clarity, and momentum. “Differences in culture at Amazon, Microsoft and Square” are real, but the constants are trust, ownership, and a shared definition of excellence. When those are explicit, performance scales; when they’re implicit, friction compounds. One lesson that’s both provocative and practical is why “customers come first,” even above employees and community. In my teams, this doesn’t license burnout or disregard for stakeholders; it creates a north star that aligns trade-offs. We use customer impact as the tie-breaker, and we protect teams with smart scoping, pacing, and support. It’s also why “Why fast-followers can be less customer-focused” resonates—if your compass is your competitor, you’ll under-index on original customer insight. On product craft, I favor “Minimum Remarkable Products” versus Minimum Viable Products. Viable ships; remarkable endures. “Building Minimal Remarkable Products at Square” highlights the bar: a crisp, opinionated slice that is usable, lovable, and unmistakably on-brand. To get there, we obsess over the first-use moment, default choices, and the shortest path to value. Then we “How to scale an aesthetic” without creating a design monoculture—by codifying principles, not just patterns. Companies that last operationalize culture. “The importance of effective communication systems” can’t be overstated: single sources of truth, clear decision records, and explicit ownership reduce entropy. Next, “How to operationalize company values” means translating beliefs into behaviors (interview rubrics, launch checklists, escalation paths). Finally, “Why shared beliefs are crucial for good company culture” reminds me to ask: do our rituals reward the behaviors we claim to value? Org design is strategy in slow motion. From “Org design lessons from Square,” I’ve learned to align structure to the customer journey and the business model, not to personalities. “How to align different teams behind business priorities” requires ruthless clarity on outcomes, not tasks—this is where outcomes vs output OKRs keep us honest. When incentives, metrics, and roadmaps point at the same target, coordination costs fall and velocity rises. Competition is the crucible for focus. “Lessons learned from fierce competition” taught me to pick our battles and compound strengths. The “fast follower” vs “pioneer” playbook isn’t binary; it’s a portfolio. Pioneer when you have a unique insight or distribution advantage; fast-follow when the category is proven but customer dissatisfaction remains high. Either way, anchor to the customer’s job-to-be-done. I’m also inspired by platform thinking at scale. “The original thinking behind AWS” and “The unlikely origin of Amazon CloudFront and other products” illustrate how small, well-defined primitives become ecosystems when coupled with relentless customer feedback. “How Jeff Bezos influenced Alyssa” underscores the power of mechanisms over slogans—leaders who institutionalize their bar raise everyone’s game. When joining a new company, I start with “Joining Square and “building a picture” of the org.” I map decision flows, interfaces, and dependencies before proposing changes. Then “Knowing what to replicate from past companies” and “Questioning norms in new companies” become complementary moves: borrow proven mechanisms, but stress-test assumptions against the current context. That’s how you avoid cargo culting and create fit-for-purpose systems. Timestamps: (00:00) Introduction; (02:20) Lessons from Microsoft and Amazon; (08:29) Noticeable consistencies in the human condition; (10:50) Differences in culture at Amazon, Microsoft and Square; (13:27) Why “customers come first,” even above employees and community; (14:01) Why fast-followers can be less customer-focused; (15:50) The challenge of commercializing research projects; (18:58) Joining Square and “building a picture” of the org; (24:55) Knowing what to replicate from past companies; (27:45) Questioning norms in new companies; (28:41) The importance of effective communication systems; (31:31) How to operationalize company values; (33:38) Why shared beliefs are crucial for good company culture; (37:05) Building Minimal Remarkable Products at Square; (38:13) How to scale an aesthetic; (42:46) Org design lessons from Square; (50:06) How to align different teams behind business priorities; (52:57) Lessons learned from fierce competition; (57:39) The “fast follower” vs “pioneer” playbook; (61:05) The original thinking behind AWS; (66:08) The unlikely origin of Amazon CloudFront and other products; (73:47) How Jeff Bezos influenced Alyssa. Referenced: Amazon: https://www.amazon.com; Amazon Web Services: https://aws.amazon.com; Bill Gates: https://www.linkedin.com/in/williamhgates; Block, Inc: https://block.xyz; Cash App: https://cash.app; Fast Company – Back To Square One: https://www.fastcompany.com/3033412/back-to-square-one; Gokul Rajaram: https://www.linkedin.com/in/gokulrajaram1; Jack Dorsey: https://twitter.com/Jack; James Hamilton: https://www.linkedin.com/in/jameshamilton4; Jeff Bezos: https://twitter.com/jeffbezos; Microsoft: https://www.microsoft.com; Oracle Corporation: https://www.oracle.com; Sarah Friar: https://www.linkedin.com/in/sarah-friar; Square: https://squareup.com; Tom Szkutak: https://www.linkedin.com/in/tom-szkutak-4b59817; WSJ – Mobile-Payments Startup Square Discusses Possible Sale: https://www.wsj.com/articles/SB10001424052702303825604579513882989476424. If you lead product or aspire to, my challenge is simple: pick one mechanism to strengthen this week—tighten your communication system, raise your MRP bar, or sharpen your outcome metrics. Enduring companies are built the same way enduring products are: one remarkable, customer-centric decision at a time.

October 20, 2025
How Sentry Scaled DevTools to $100M ARR: My Playbook for PMF, B2D, and Packaging

I’m endlessly curious about how category-defining DevTools scale, cross chasms, and find product-market fit more than once. Few stories crystallize that arc better than Sentry’s recent momentum. The journey hits at the heart of what matters in product management leadership: developer obsession, disciplined packaging, and the courage to evolve your model as you scale. Milin Desai is the CEO at Sentry, an application monitoring tool for developers. Sentry has recently passed two key milestones: 100K customers and over $100M in ARR. Before Sentry, Milin was a GM at VMware and scaled their cloud networking into a billion-dollar business. Prior to stepping into leadership roles, Milin was a PM at Riverbed and a software engineer at Veritas. When I look at Sentry’s trajectory, I see two themes that separate enduring DevTools from the pack: Sentry’s developer-centric approach and the discipline to become the need, not the want. In practice, that means solving a daily, high-frequency pain with a crisp path to initial value, and then earning the right to expand by reducing toil, surfacing root cause faster, and integrating seamlessly into the developer workflow. This is also where “Sentry’s B2D model” shines. Developers don’t want to be sold to—they want tools that work with minimal friction, clear docs, and a pricing model that respects their usage patterns. The mantra to “Build for the many, not the few” pairs naturally with Building for the “Fortune 500,000”: design defaults and guardrails for the long tail, then let usage graduate into team and enterprise value. I’ve applied the same mindset in my own teams to unlock self-serve adoption without sacrificing governance or scale. From a go-to-market standpoint, the biggest unlock for me—and a lesson reinforced by VMware—is to Focus on packaging, not pricing. Lessons on pricing, packaging, and product from VMware translate directly to modern DevTools: segment by outcomes (workflow, team size, compliance) rather than by features alone; make upgrades obvious through natural usage thresholds; and tell a simple story that maps to how customers buy. Price becomes the byproduct of a clear packaging narrative. Leadership transitions matter, especially in founder-led companies. Joining Sentry as an external CEO can work brilliantly when the roles are explicit and the operating cadence is healthy. The CEO/founder relationship is strongest when there’s deep respect for the original product intuition and an equally strong mandate to scale what works. I’ve found that Forging successful relationships with founders starts with mutual clarity: who owns vision, who owns velocity, and how decisions get made when data is ambiguous. On product strategy, I resonated with the pragmatic stance on Open versus closed source product. What matters is trust, velocity, and fit with your distribution model. If open source accelerates awareness and credibility with developers, use it. If closed source is faster to iterate and aligns with customer security needs, do that. Either way, the bar is to keep Becoming the need, not the want by removing critical friction in the developer’s day. Scaling Sentry underscores a familiar pattern I coach teams on: instrument everything, shorten the feedback loop, and keep the “Hello, World!” moment under five minutes. The key ingredients to Sentry’s success translate broadly—tight product telemetry, opinionated defaults, and a packaging ladder that meets users where they are. These mechanics compound when supported by a crisp narrative that developers can explain to colleagues in one sentence. As products mature, The second product mindset becomes essential. After initial PMF, the next S-curve rarely arrives by piling on adjacent features. It comes from reframing the job-to-be-done for the broader team: moving from error monitoring to issues ownership, from signal to workflow, from tool to platform. That shift creates room for a Contrarian take on building for enterprise: earn enterprise by nailing the many. Enterprise credibility is the outcome of reliability, scale, and admin controls—not a separate product line too early. Here’s how I operationalize these lessons with my teams: start with developer-first onboarding; anchor packaging to outcomes and usage; harden governance and collaboration as natural upgrade paths; keep docs, SDKs, and integrations as product, not collateral; and measure time-to-value relentlessly. When we do that well, adoption expands organically, sales cycles compress, and customer love shows up in the metrics. In short, Sentry’s arc is a masterclass in disciplined, developer-led growth. For product leaders, the playbook is clear: build undeniable daily value, package it simply, and evolve your model as your users evolve. The rest is execution at every layer—product, pricing, platform, and people.

October 20, 2025