I recently dove deep with Andrew Ofstad, co-founder of Airtable, to unpack Airtable’s path to product-market fit and the realities of building a truly horizontal product. As a product leader, I’m always looking for patterns that translate across teams and stages — and this conversation offered a wealth of practical insights for founders and product managers alike.
We started with first principles: how the founders came together, their vision for the product, and what the initial prototypes looked like. That early narrative matters — it anchors positioning, keeps scope disciplined, and ensures your earliest builds reflect the core value proposition rather than a laundry list of features.
From there, we stepped through Airtable’s alpha, beta, and launch timelines, as well as their early traction. I pay close attention to these milestones because they reveal the learning cadence: how quickly teams validated hypotheses, which signals they treated as leading indicators, and how they balanced qualitative pull with quantitative adoption during product discovery.
We also explored the challenges of creating a horizontal product that can do many things, including identifying initial use cases and figuring out how to describe what they were building. In my experience, the key is to land a small set of canonical use cases, articulate crisp jobs-to-be-done, and build narrative clarity around the “why now.” Without this, even great products struggle to convert curiosity into active usage.
On commercialization, we dug into how to approach pricing and competition, as well as their early go-to-market strategy. For products with broad applicability, I’ve found that founder-led GTM is essential early on — it shortens the learning loop and informs SaaS pricing and packaging. Start with simple, customer-aligned tiers, validate willingness to pay against clear outcomes, and keep positioning focused on value, not feature parity.
We then looked ahead to what the next 3 years will look like for Airtable, and how they’ve navigated scaling while staying true to their vision. Scaling a horizontal product requires tight product roadmapping and sprint planning, strong messaging discipline, and an unwavering commitment to the core value — all while layering ecosystem leverage, templates, and community to accelerate adoption without diluting the product’s identity.
Whether you’re a founder validating your own idea, or a product leader looking for growth advice, there are tons of tactics here that go much deeper than the typical founding stories you hear. My takeaway: great horizontal products find product-market fit by starting narrow in use case, obsessing over teachability, and letting customer outcomes pull the roadmap forward.
Inspired by this post on First Round.
Leave a Reply