Category: Product Management

I’ve long believed the most resilient software companies master two hard things at once: they move decisively from mid-market to enterprise, and they ship multiple “best-of-breed” products without losing focus. The operating model that makes this possible — running 16 “startups within a startup” — resonates with how I build product organizations. In this piece, I’m unpacking the frameworks I use to make that model work at scale, from “product-market-sales fit” to capacity-driven go-to-market.

Why do companies get stuck in the mid-market? In my experience, it’s rarely just sales execution. It’s usually a product readiness gap hiding inside a distribution story. Enterprise customers expect battle-tested architecture, deep security and compliance, robust RBAC, data governance, audit trails, and predictable SLAs. They also expect a clear value proposition, strong references, and a crisp “who do we beat and why” articulation. If any one of those is fuzzy, your deals elongate or disappear. The fix starts by designing intentionally for enterprise and mid-market from day one: plan for scale, extensibility, change management, and procurement complexity — then validate with lighthouse customers, not just friendly pilots.

Sometimes the hardest enterprise move is saying no. I’ve advised teams to walk away from a marquee logo like Netflix when the requirements force unnatural acts that derail your roadmap. It feels counterintuitive — especially when the logo is irresistible — but your ideal customer profile must govern priorities. Your long-term velocity compounds when you align deeply with the customers who value your native strengths.

I differentiate between “product-market-fit” and “product-market-sales fit.” The former tells me a product delivers undeniable value; the latter tells me my distribution system can reproduce that value at scale. I watch for signals beyond anecdotes: win rates by segment, cycle time, ramp time to first deal, multi-threading depth, net revenue retention, and the percentage of customers who expand within two quarters. When these lag, I diagnose whether I have a product problem (insufficient value or clear “must-have” outcomes) or a distribution problem (positioning, enablement, or segmentation). The diagnosis determines whether I ship features, sharpen messaging, or rewire the motion.

On go-to-market, I build a capacity-driven machine instead of chasing deals. That means matching pipeline health to quota capacity, calibrating territories to intent density, and instrumenting enablement so new reps reach productivity with consistent talk tracks and crisp objection handling. I prefer simple, repeatable plays that compound: a precise ICP, strong proof packages, and a pricing model that meets customers where they are. When those are humming, founder-led GTM transitions smoothly to a scalable sales engine without losing the product’s original edge.

Hiring your first head of sales is a leverage point. I look for four things: pattern recognition in my specific segment, a builder’s mindset (process and playbooks without bureaucracy), rigorous pipeline hygiene, and the ability to partner with product on “where we win and why.” In the interview, I run scenario loops: how they’d disqualify non-ICP deals, how they’d recover a late-stage stall, how they’d deliver the first 90 days plan, and how they’d coach to a consistent message. Early founders absolutely need to learn sales — not to become the forever closer, but to encode customer truth into the product and the motion.

Strategic timing matters, too. There’s a well-known case of selling three days pre-IPO; whether or not you’d make the same call, the lesson stands: market timing, certainty of outcome, and board alignment are strategic variables, not afterthoughts. A healthy board brings independent thinking, timely guidance on capital and risk, and a unified narrative — especially when the market is volatile.

On competition, I pressure-test our narrative around points of parity and a “binary differentiator.” In crowded markets, incremental advantages don’t move the needle. You need one thing customers can’t ignore — faster time-to-value, a step-function in accuracy, or a cost curve that resets the category. I ask every team to prove a binary outcome: if we’re in the eval, there’s a clear, testable reason we win.

Launching multiple products simultaneously demands ruthless clarity. I structure the org as “startups within a startup,” each with its own GM, product roadmap, and GTM targets, but anchored to a shared platform for identity, data, and extensibility. Product managers operate as mini-entrepreneurs — owning P&L-like metrics, customer outcomes, and crisp product positioning — while a central platform team ensures consistency and speed. The rallying cry across these teams is simple: “We need to be best of breed.” If a product can’t credibly win on its merits, we either sharpen it until it does or we stop investing.

Execution lives in the details. I emphasize outcomes vs output OKRs, product trios for tight alignment, and continuous improvement powered by CI/CD so we can learn faster. We track DORA metrics like deployment frequency to ensure our cadence supports enterprise reliability. Weekly operating reviews focus on value delivered: have we solved the customer’s core job, and can our sales and success teams prove it with repeatable stories? When the answer is yes, expansion follows naturally.

Bringing it all together: moving upmarket, building “product-market-sales fit,” and running 16 product lines under one roof is achievable with the right structure and discipline. Design for enterprise from the start, let your ICP guide every trade-off, anchor GTM in capacity and repeatability, hire sales leaders who build with you, enforce a “binary differentiator,” and empower product managers as owners. Do that, and the “startups within a startup” model becomes a force multiplier — not just a slogan.