Introduction
Spenser Skates is the co-founder and CEO of Amplitude, one of the defining companies in the modern product analytics and product-led growth movement. For founders, product leaders, and investors, his journey offers a clear case study in how deep technical skill, rigorous experimentation, and relentless focus on user behavior can compound into a market-leading company.
Amplitude did not start as a polished category leader. It emerged from the ashes of a different startup, built originally as an internal tool, and then scaled into a public company that helps thousands of teams understand how users engage with their products. Skates’ path—MIT engineer, failed startup founder, second-time founder who helped create a new category—captures many of the hard lessons and high-leverage decisions that define successful tech companies.
Early Life and Education
Formed by Engineering and Competition
Skates studied Electrical Engineering and Computer Science at MIT, an environment that rewards both intellectual rigor and serious competition. He participated in programming contests and quantitative competitions, honing a mindset that treats problems as systems to be understood and optimized rather than as vague challenges.
This early focus on systems thinking shows up repeatedly in his later career: the way he uses data to reason about product-market fit, the way Amplitude is structured as a “system of record” for product behavior, and the way he built processes to turn product analytics into a repeatable growth engine.
Equally important, MIT exposed him to a community where starting a company felt normal. Many of his peers were exploring startups, research projects, and side businesses. That normalized the idea that building something from scratch was not only possible, but expected for ambitious engineers.
Startup Journey
First Attempt: Sonalight
Before Amplitude, Skates co-founded Sonalight, a voice-recognition startup famous for a Y Combinator demo where he put his phone in his pocket and sent texts hands-free. The product worked, but the underlying reality was tougher:
- The technology was impressive but hard to productize for mass-market behavior.
- User retention and engagement data revealed that initial novelty did not translate into long-term habit.
- The team spent increasing effort building internal tools to understand user behavior, rather than purely focusing on voice features.
Crucially, Skates and his co-founder Curtis Liu built their own in-house analytics system to understand how people actually used Sonalight. That system let them see what most startups at the time could not: how users moved through the product, where they dropped off, what features drove retention, and which cohorts of users stuck around.
The painful conclusion from the data was clear: the analytics tool they had built internally was more valuable—and had more potential—than the voice product itself.
Pivoting to Product Analytics: Founding Amplitude
Out of that realization came Amplitude, founded in 2012. Instead of trying to build another consumer app, Skates and Liu focused on solving the analytics problem that they and many other founders were struggling with:
- How do you understand user behavior at the event level, not just at the pageview level?
- How do you track cohorts and retention over time, rather than just vanity metrics?
- How do you give product teams—not only data scientists—tools to answer their own questions?
They initially served other startups and mobile-first companies, positioning Amplitude as a product analytics platform rather than a generic web analytics tool. This framing would become foundational to the company’s later category leadership.
Key Decisions
Amplitude’s rise was not inevitable. Several key strategic decisions made by Skates and his team shaped the company’s trajectory.
1. Betting on Product Teams, Not Just Marketers
In the early 2010s, many analytics tools focused on marketers—campaign performance, funnels, attribution. Skates chose a different path: Amplitude would be built for product teams.
This meant prioritizing features like cohort analysis, retention curves, behavioral segmentation, and paths analysis—tools that help answer questions like “What behaviors correlate with long-term retention?” or “What features do power users adopt early?” This decision both differentiated Amplitude and aligned it with the shift toward product-led growth.
2. Depth Over Dashboard Flash
Analytics products can easily devolve into pretty dashboards that do little to drive decisions. Skates intentionally pushed Amplitude toward depth of analysis—complex queries, behavior-based insights, and the ability to explore data interactively.
That focus attracted sophisticated product teams and data-driven companies that needed more than surface-level metrics. While it made the product more challenging to build, it also elevated Amplitude above lightweight analytics tools that were easy to adopt but limited in impact.
3. Building a Category: “Product Analytics” and “Product Intelligence”
Rather than positioning Amplitude as “another analytics tool,” Skates invested in category creation. Amplitude’s content, events, and customer education consistently reinforced concepts like:
- Product analytics as the system of record for digital products.
- The importance of a North Star Metric to align teams around product value.
- Product as a primary growth driver, not just a feature of the business.
This category narrative made it easier for buyers—and investors—to understand why Amplitude mattered and how it differed from traditional marketing or web analytics tools.
4. Leaning into Product-Led Growth and Sales, Not One or the Other
Skates avoided a false dichotomy that traps many B2B founders: choosing either pure self-serve or pure enterprise sales. Amplitude did both:
- Self-serve and bottoms-up adoption among product managers, growth teams, and data analysts.
- A structured sales motion to turn successful teams into larger, multi-year enterprise deployments.
This hybrid motion required operational complexity—pricing models, onboarding, account expansion—but it allowed Amplitude to grow quickly within companies once the product proved its value.
Growth of the Company
From YC Roots to Category Leader
Amplitude’s early traction came from the YC and startup ecosystem, where teams were hungry for better product insights. Those early adopters gave Amplitude:
- Rapid feedback loops for iterating on features.
- Case studies demonstrating how analytics improved retention and activation.
- Credibility among other high-growth companies.
Funding and Investor Support
As Amplitude’s traction grew, it attracted top-tier venture capital firms. Investors were drawn to:
- Strong product-market fit with digital-first businesses.
- High retention and expansion within customer accounts.
- A clear category story around product analytics and product intelligence.
Multiple funding rounds over the years allowed Amplitude to scale engineering, expand internationally, and build out go-to-market capabilities while continuing to invest heavily in the core analytics platform.
Scaling the Product and Market
Growth for Amplitude meant tackling several hard scaling challenges:
- Data infrastructure: Handling billions of events per month while keeping queries fast and reliable.
- Security and governance: Meeting the needs of enterprise customers with strict compliance requirements.
- Customer education: Teaching teams not just how to use the tool, but how to make data-driven product decisions.
- Global expansion: Supporting customers across regions and industries, each with different product analytics maturity.
Going Public
In 2021, Amplitude went public on the Nasdaq, a milestone that validated both the company and the category it helped define. For Skates, the public listing was less a finish line and more confirmation that product analytics had become core infrastructure for modern digital businesses.
Leadership Style
Skates’ leadership style reflects his engineering background and his conviction that systems and culture matter as much as product.
Data-Driven, But Not Data-Blind
He is known for pushing for rigorous, data-informed decision-making: instrument everything, define clear metrics, and let user behavior guide priorities. But he also emphasizes that data should inform, not replace, product intuition. This balance helps avoid both “data theater” and purely opinion-driven roadmaps.
High Standards and Clarity
At Amplitude, expectations are set clearly: ship quality, think critically, and connect work to customer outcomes. Skates’ communication style tends to be direct and analytical, focusing on:
- Clear goals and metrics.
- Transparent tradeoffs.
- Honest postmortems when things go wrong.
Customer-Obsessed Product Culture
Skates pushes for a culture where everyone understands the customer’s journey. Product managers, engineers, and go-to-market teams are expected to use Amplitude’s own product to analyze behavior, identify friction, and test hypotheses. This “build what we ourselves rely on” approach reinforces both product quality and cultural alignment.
Lessons for Founders
For founders and builders, Skates’ journey offers several actionable lessons:
- Your internal tools may be your real product. Sonalight’s voice app struggled, but its internal analytics system became Amplitude. Pay attention to what you are uniquely good at—even if it was not part of the original plan.
- Retention is truth. Amplitude’s core insight is that retention and behavior over time matter more than top-of-funnel spikes. Founders who instrument and understand retention early have a structural advantage.
- Define and own your category. By committing to “product analytics” and later “product intelligence,” Amplitude avoided being lumped in with generic analytics tools and instead framed the market on its own terms.
- Serve the people actually making decisions. Skates targeted product teams rather than only executives or marketers. Building for the practitioners who feel the pain daily creates pull from the bottom up.
- Combine product-led growth with sales, not instead of sales. Self-serve adoption can seed accounts, but structured sales and customer success help capture the full value in larger organizations.
- Be willing to pivot hard when the data says so. Walking away from Sonalight was difficult, but essential. The discipline to pivot based on evidence—not ego—often separates enduring companies from forgotten ones.
Quotes or Philosophy
Across interviews, talks, and writing, several core ideas define Skates’ philosophy on building products and companies:
- Retention over acquisition: He consistently emphasizes that most companies do not have an acquisition problem—they have a retention problem. If users do not stick, more marketing spend will not fix the core issue.
- Product as the growth engine: In his view, growth is increasingly product-driven. Features, onboarding, and user journeys are as critical as sales and marketing in driving revenue.
- North Star Metric: He advocates for each product team to define a single metric that captures delivered customer value, and then align the organization around improving that metric.
- Instrumentation as a mindset: Skates promotes the idea that teams should instrument everything meaningful in the product. You cannot improve what you cannot measure, and you cannot measure what you do not track.
- Compounding advantage through insight: He sees product analytics as a compounding asset: the more you experiment and learn from behavior data, the faster your product evolves relative to competitors.
Key Takeaways
- Spenser Skates turned a failing startup into a category-defining company by recognizing the value of his internal tools and having the courage to pivot.
- Amplitude’s success is rooted in deep focus on product analytics, serving product teams, and elevating retention and behavior analysis as central to growth.
- Key strategic choices—owning a new category, prioritizing depth of analysis, and blending product-led adoption with enterprise sales—created durable differentiation.
- Skates’ leadership style combines engineering rigor, data-driven decision-making, and a strong product culture centered on understanding real user behavior.
- For founders, his journey underlines the importance of listening to your data, being willing to reinvent your company, and building systems that turn insight into continuous product improvement.
