Airtable growth

Podcasts · Business, Startups · Source

Created by Rishabh Srivastava

This summary was largely done for my own note-taking, sharing it just in case it adds more value to other people.

I have no affiliation whatsoever with anyone in this note. This is a summary largely taken for my own reference, and may contain errors :)

Context

Source URL:

Airtable's path to product-market fit - co-founder Andrew Ofstad on building horizontal products - In Depth

Felt that they had product market fit when they were growing virally within companies, and went wall to wall

Also saw industries and functions where they were landing and expanding well and repeatedly

Snowballs happen in a lot of different s-curves. Started seeing expansion happen organically when people left their jobs and brought tool with them to new company

Growth really kicks in when you build more use cases and can really expand within companies

If someone built something in airtable (like a product roadmap tracker, or a marketing calendar), and they shared that with their team to do useful work — can get a ton of customer insights from these + has viral adoption

Target “golden datasets” -> things that companies really need to run and do their jobs

Help enterprises get these golden datasets and letting their teams build on top of them in a safe way

Product was very collaborative by nature

Pricing reflects positioning. They priced against Salesforce/servicenow instead of Dropbox or Evernote

Pricing transparency early on is very good for the customer, even if you don’t intend to charge them. Good pricing ensures that they don’t think you’ll sell your data etc

Series A driven more by customer love and metrics than revenue

Creating hundreds of templates really helped with product engagement

Becoming a common data platform for the enterprise, for companies that use air table to build mission critical processes

Navigating enterprise vs self-serve. Keep the product as simple to use as possible. Let people that are not in IT departments still build products and deploy them to their teams. Continue to empower end users, but do build tools for IT to do governance and access controls

Separate the surface area of the product into personas. If you’re the end user, you shouldn’t have to check out random access things

Vision is to empower line of business employees to build tools and not deal with a 100 different siloed applications for each department, none of which connect together