Tag: product creator

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.

I’ve spent years building and scaling marketplaces and leading product teams through zero to one and one to many. Along the way, I’ve learned that winning marketplaces aren’t accidents—they’re engineered. In this first-person playbook, I break down what matters most, from the earliest choices that shape network effects to the growth loops that compound over time.

When I start working on a new marketplace, I focus on a few non-negotiables: the atomic unit of value (what gets exchanged and why), the liquidity threshold (how much density is enough to trigger repeat use), and the trust model (policies, payments, and reputation that prevent disintermediation). Marketplaces rise or fall on liquidity, selection quality, price transparency, and reliability—get those right early and everything else scales more predictably.

Marketplaces are different because they’re two-sided systems. They require careful sequencing of supply and demand, tight geographic or category focus to achieve density, and an operating model that remembers “the product is supply, not software.” I design the software to shape incentives and reduce friction, but I obsess over supply quality, responsiveness, and retention—because that’s what demand truly experiences.

Finding product market fit is about measurable liquidity, not anecdotes. I track time to first transaction, percentage of new users who transact within their first session or week, repeat purchase rates by cohort, and supplier utilization. I use the “setup, aha, and habit” framework to design activation: great onboarding (setup), a fast, undeniable first success (aha), and a path to reliable repetition (habit). When those three lock in, network effects start to work for you.

Scaling requires deliberate growth loops, not one-off channels. My go-to loops marry supply acquisition to demand creation: content/SEO loops (inventory generates pages that attract demand, which attracts more inventory), referral loops (happy suppliers bring peers, happy buyers bring friends), and performance loops (paid channels that are unit-economically profitable due to high LTV and rebuy rates). The goal is compounding, not dependency.

There are 2 ways to acquire supply and demand in the early days: do things that don’t scale (hands-on supply curation, concierge onboarding, localized seeding) and build scalable systems (self-serve onboarding, programmatic SEO, performance marketing). I typically start manual to ensure quality and learning speed, then translate those learnings into self-serve flows and automation.

What’s unique about building a marketplace is knowing when to shift focus between sides. I bias toward building great, retained supply first in narrow slices—one city, one category, one use case—then I layer demand once time-to-transaction is reliably short and fulfillment quality is high. As density rises, I rebalance: unlock more demand when supply is underutilized; throttle acquisition or expand geography/category when suppliers are at capacity.

Hiring is another inflection point. Early on, I want scrappy generalists who can own a slice of the funnel end-to-end—supply ops, trust & safety, and growth-minded product managers. As we scale, I formalize teams around supply acquisition, supply success, demand growth, matching/relevance, and marketplace quality, with strong data science embedded throughout.

Finding sticky customers depends on frequency and habit formation. In high-frequency categories, I relentlessly remove friction and drive reactivation. In low-frequency categories, I stay top of mind with utility features, content, and lifecycle nudges—because even “the best low-frequency marketplace” wins by owning the moments that matter before, during, and after the transaction.

Category strategy requires patience. I generally prefer single-category focus until I’ve achieved strong liquidity and repeatability, then I consider adjacent expansion. I ask: does expansion improve marketplace health for existing users, or does it dilute density? “Single versus multi-category marketplaces” and “When to expand” aren’t philosophical questions; they’re math about liquidity, cross-sell, and operational complexity.

Competitive strategy is instructive. “Uber versus Lyft” demonstrates how operational scale, category breadth, and geographic density compound advantages. “What Grubhub should’ve done” underscores the cost of missing durable loops and quality control. I also challenge provocative claims like “No value in car-sharing” by modeling unit economics, asset utilization, and multi-tenant demand patterns—use the data to decide what to believe.

Looking ahead, I’m excited about “Emerging marketplaces in 2024,” especially vertical B2B, services with verified credentials, and embedded marketplaces inside workflow tools. As I scale any marketplace, I continually focus on “Improving supply and demand over time,” tightening SLAs, raising fulfillment quality, and reducing time-to-liquidity. I keep a running list of “Avoid these marketplace mistakes,” from subsidizing both sides for too long to expanding before density, and I revisit “One thing all marketplace founders should know”: compound advantages come from loops, not hacks.

For inspiration and pattern-matching, I regularly study leaders in the space. Referenced: Airbnb: https://airbnb.com/

Bill Gurley: https://www.linkedin.com/in/billgurley/

Blue Apron: https://www.blueapron.com/

Booking.com: https://www.booking.com/

DoorDash: https://www.doordash.com/

eBay: https://ebay.com/

Eventbrite: https://www.eventbrite.com/

Expedia: https://www.expedia.com/

Faire: https://www.faire.com/

Fermat Commerce: https://www.fermatcommerce.com/

Grubhub: https://www.grubhub.com/

Lyft: https://www.lyft.com/

Pinterest: https://www.pinterest.com/

Postmates: https://postmates.com/

Shopify: https://www.shopify.com/

Simon Rothman: https://www.linkedin.com/in/simonrothman/

Square: https://squareup.com/

Tony Xu: https://www.linkedin.com/in/xutony/

Turo: https://turo.com/

Uber: https://www.uber.com/

Zillow: https://www.zillow.com/

If you’re building a marketplace right now, pressure-test your model against these principles: define your atomic unit, get to liquidity fast, treat supply as the product, design growth loops that compound, and sequence expansion only after you’ve earned dense, repeatable usage. Do this well and you won’t just grow—you’ll build a marketplace with defensible moats and real staying power.

Product-market fit isn’t a finish line; it’s a dynamic state that needs to be earned repeatedly. In my work leading product strategy, I’ve learned that the most resilient companies combine ruthless intellectual honesty with repeatable discovery habits, movement-first distribution, and a bias toward decisive action when markets shift under their feet.

One case study I return to often: Bob Moore is the co-founder and CEO at Crossbeam, a “LinkedIn for data” platform that helps companies find overlapping opportunities with their partners. Crossbeam has raised US$117M to date and recently acquired Reveal in 2024. Bob previously cofounded RJMetrics (now part of Adobe Commerce Cloud) and Stitch Data (acquired by Talend). He is also the author of Ecosystem-Led Growth. The arc of these companies offers a clear lens into finding founder-market fit, falling in and out of product-market fit, and rebuilding with conviction.

When I evaluate ideas, I start with founder-market fit and falsification. I look for a lived pain, an unusual insight, and unfair access—then I try to disprove my thesis fast. I’ll line up dozens of target users and adjacent stakeholders, pressure-test the problem, and map evidence to The 4 Levels of PMF. The goal isn’t to “win” early interviews; it’s to surface the constraint that will eventually break the model: data availability, switching costs, procurement friction, or a distribution bottleneck.

Market shifts can invalidate a great product overnight. The analytics stack reconfiguration around Amazon Redshift is a perfect reminder that timing, platform shifts, and ecosystem dependencies will bend your trajectory. I actively maintain a “watchlist” of platform moves (cloud data platforms, changes in ad networks, privacy policy shifts, AI infrastructure) and connect them to my product’s core assumptions. If a new platform absorbs the value we created, I’d rather be first to cannibalize our own roadmap than last to react.

On distribution, I engineer sharing, reciprocity, and compounding usage directly into the product. That means designing collaboration surfaces, data assets, or partner workflows that make every new customer a new channel. Crossbeam’s model highlights how overlap mapping and partner ecosystems can turn integration nodes into growth nodes—an ethos that aligns with Ecosystem-Led Growth. Internally, I complement this with proactive outbound motions and the “joint jam” sales tactic: co-creating a live, high-signal artifact with the prospect that proves value with their data, not my slides.

Falling out of PMF is a feature of reality, not a failure of leadership—provided you move with clarity. The RJMetrics journey illustrates how you can find market fit, then lose it as the stack modernizes. My safeguard is a portfolio of leading indicators: retention by job-to-be-done, time-to-first-value, expansion drivers, sales-assist ratio, and the support “tax” on core workflows. When those turn, I default to intellectual honesty: narrow the ICP, rebuild the wedge, or sunset the thing that’s stealing oxygen from the core.

Building with conviction versus consensus is a critical cultural muscle. Consensus can smooth relationships, but it often averages out the insight. I anchor decisions in clear principles, write tight pre-mortems, and set owner-driven DRIs. We invite dissent early (red-team reviews, structured decision docs), then “disagree and commit” with a time-boxed checkpoint tied to specific, falsifiable milestones. This lets us move fast without romanticizing our own ideas.

Creating scalable and durable startups requires architecture, not just ambition. I push for composability across data models, feature flags for safe exploration, and an experimentation fabric that lets us test distribution hypotheses at low cost. We sequence multi-product bets only when we see strong, repeated pull from the market—ideally where network effects are latent. Unlocking network effects in software isn’t magic; it’s the disciplined design of interactions where each participant makes the system more valuable for the next.

Mergers are another lever for durability when executed with rigor. The Crossbeam/Reveal merger is a timely example of using consolidation to reduce fragmentation, standardize workflows, and accelerate network effects. Getting mergers right starts with strategic fit and cultural compatibility, but the real game is integration: aligning product architectures, pricing, packaging, and go-to-market motion within a 100-day plan that customers can feel in the product, not just read in a press release.

If you’re pressure-testing your own path to product-market fit, here’s what I’ve found most reliable: obsess over founder-market fit first, use The 4 Levels of PMF to calibrate evidence, design distribution into the product from day one, watch platform shifts like a hawk, and choose conviction over consensus—with mechanisms that keep you honest. Do that consistently, and you won’t just find PMF—you’ll keep it.