How I Find—and Keep—Product-Market Fit: Lessons on Conviction, Distribution, and Mergers

Futuristic metallic infinity loop glowing at the center of a dashboard UI, ringed by connected icons for cloud, analytics, gears, and chat, symbolizing AI-driven DevOps, data integration, and automation.

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.


Book a consult png image

What is The 4 Levels of PMF and how does it help you test product-market fit?

The 4 Levels of PMF is a framework for calibrating evidence to identify the constraint that will break the PMF model, such as data availability, switching costs, procurement friction, or a distribution bottleneck. It helps teams understand where to focus experiments and improvements to move PMF forward.

Why are platform shifts like Amazon Redshift important for PMF?

Platform shifts test timing and ecosystem dependencies that can bend a product’s trajectory. The author maintains a watchlist of platform moves to anticipate changes and would cannibalize their own roadmap if a new platform absorbs the value.

How can you design distribution into a product?

Design collaboration surfaces, data assets, and partner workflows that make every new customer a channel. Crossbeam’s model shows how overlap mapping and partner ecosystems can turn integration nodes into growth nodes, complemented by proactive outbound motions and the ‘joint jam’ sales tactic.

What is the 'joint jam' sales tactic?

Co-creating a live, high-signal artifact with the prospect that proves value with their data, not slides. This approach helps demonstrate value using the customer’s data early in the process.

Why are mergers like Crossbeam/Reveal used for durability?

Mergers can reduce fragmentation, standardize workflows, and accelerate network effects. Success depends on strategic fit and cultural compatibility, with integration framed by a 100-day plan.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Signup for Weekly Digest Emails

Categories

Archieve