Amplitude, Inc. (AMPL) Earnings Call Transcript & Summary

August 5, 2026

NASDAQ US Information Technology Software earnings 63 min

Earnings Call Speaker Segments

John Lewis Streppa

executive
#1

I'm John Lewis Streppa, and I lead investor relations. With me on the call are Spenser Skates, our CEO and cofounder of Amplitude, plus Andrew Casey, who serves as chief financial officer. On this call, management will deliver forward-looking statements. That covers what we expect financially for the third quarter and the whole of 2026, how our products should perform, anticipated growth by quarter and over the long term, investments, and our broader future prospects. Such forward-looking statements rest on information, assumptions, and expectations as they stand now, and they carry risks and uncertainties, several of which we cannot control; actual results might therefore diverge materially from what those statements describe. More detail about the risks that might make actual results diverge appears in our filings with the Securities and Exchange Commission. We urge you not to lean excessively on these forward-looking statements, and aside from situations the law requires, we take on no duty to refresh them following today's call. A number of financial measures discussed on today's call are presented on a non GAAP basis. Internally, we rely on these non GAAP financial measures to make analysis of our financial and business trends easier and to serve internal planning and forecasting needs. Limitations apply to these non GAAP financial measures, and they should not be relied upon alone or treated as a replacement for financial information put together in accordance with GAAP. You can find further details about these non GAAP financial measures, along with a reconciliation between the GAAP and non GAAP financial measures, in our earnings press release and the supplemental financial information, both of which are available on our Investor Relations website. That's at investors.amplitude.com. Having said all that, I'll pass the call to Spenser.

Spenser Skates

executive
#2

Thank you, John, and good afternoon to all of you. It's a pleasure to welcome you to Amplitude's earnings call for the second quarter of 2026. I'll be addressing 3 topics today. To begin, the results we posted for Q2. Next, the way we reshaped Amplitude into an AI-focused business, and the reason virtually every organization I speak with is now eager to find out how they can follow the same path. And third, a review of what we offer on the product side, along with a closer look at some of our customers. Let's begin with the figures. Revenue for Q2 came in at $101 million. That represents 21% growth compared with the same period a year earlier. Our total ARR reached $410 million, which is 22% higher than a year ago and $36 million above where it stood at the end of the prior quarter; this figure breaks down into 2 components. The inorganic portion of ARR, which came from Statsig, contributed $17 million, while organic ARR added $19 million. Andrew is going to take you through the specifics. On a non GAAP basis, our operating loss amounted to $1.5 million. The count of customers generating over $100 thousand in ARR climbed to 824, which is a 30% jump versus a year ago. Growth is being propelled by both AI native businesses and big enterprises. Let me pull back for a moment and describe our transformation, and then explain how we're supporting customers as they move along their own AI paths. Our business is about helping companies create superior products. Every organization is eager to make the shift toward delivering software products in an AI native fashion; over the past 2 years we've completed that very shift here at Amplitude, and at this point our customers want to pick up what we've learned. The journey to becoming an AI company begins with how you organize the business. 2 years back, the first move we made was to overhaul our engineering team by recruiting AI engineers who had spent years building with the technology. After that, we expanded into neighboring areas such as product management, design, and the more technical side of go to market. We've also gained AI know-how via acquisitions, and founders along with other team members from those acquired companies have stepped into leadership positions throughout Amplitude. My own emphasis has been on recruiting executives who previously founded companies and who come from a technical background. Gabe, who serves as our chief product officer, launched several businesses, among them Loom Systems, which was acquired by ServiceNow in 2020. Beyond that, Nate, our chief commercial officer, holds a degree in math and physics and began his professional life as an engineer, writing code in c plus and Java and constructing databases. Most recently, we brought on Angela Ferranti to serve as SVP of marketing. Angela was the founder of Lovable, which participated in Y Combinator Summer 2021, was sold in 2025, and she is a technical marketing leader who creates apps using AI in her free time. On top of all that, we keep reeducating the entire Amplitude team through efforts such as AI Week, unlimited token spend, and a living token leaderboard. All of this has produced 3x the number of pull requests within 6 months. Our pull request cycle has been cut down from 5 hours to 44 minutes. Bug reports have fallen 55%. Designers and product managers, with no involvement from engineering, submit 5% of our pull requests; and by leveraging AI, we've shortened our closing process by a day. We created customer health dashboards, letting our salespeople and leadership monitor how customers are using the product while pulling in our own Amplitude information next to Salesforce records plus other data sources. Whenever I speak with customers, every one of them is zeroed in on how to remake their business so it becomes AI native the way we've already done here at Amplitude. The AI world is shifting fast, and they're eager to figure out how to keep up. AI adoption among our customers varies widely. What we need to do is engage them right where they stand, then teach them how to move forward. We partner with top AI firms to understand what the very forefront of product development looks like, and we pass that insight along to the broader market, even the biggest enterprises that are rolling things out at scale. Over 40 AI native businesses now pay us in excess of $100 thousand each year; among them are Harvey, Midjourney, Character AI, and 1 of the top foundational AI model companies. On the enterprise front, large organizations now represent more than 68% of our ARR. This quarter brought deals with Paramount, Jaguar Land Rover, and Domino's Pizza. Our pricing and packaging have gotten better. We simplified things down to a 1-meter so enterprises find it easier to bolt on more products. We also raised how much data comes with our free plan, making us the top choice for anyone just starting out. Whether you're a startup or a huge enterprise, Amplitude offers the best pricing. 1 of the most significant shifts that comes with becoming an AI native company, something we see at Amplitude and among our peers in private markets, involves the cost structure. Delivering AI native products demands a great deal of inference spending, which drives up what we spend on cost of goods sold. Conversely, growing a business at scale no longer requires piling on as much operating expense. We're accepting this cost structure shift as part of becoming an AI native company. For the time being, we anticipate gross margins holding in the low 70s. We'll counterbalance that through an equivalent cut in operating expenses. That keeps us on track to deliver the same operating income leverage we've budgeted for. Over the long haul, I'm still pushing Amplitude toward becoming a 20%+ operating margin business. We provide 3 products so we can serve customers no matter where they are in their AI journey. Amplitude delivers the most thorough insight into how people engage with your product. Our agents are handling more and more of that discovery on your behalf. Statsig handles feature flagging and experimentation, powered by the world's most sophisticated stats engine with an engineering first perspective; it also connects natively with data warehouses. Wade represents what's next in product development, self improving products that automatically suggest what to build from user signals. Though we're still early here, I'm genuinely thrilled to walk you through a demo today. Taken as a set, these 3 offerings complete the cycle of developing a product. Grasp what's going on, quantify what gets released, and release what counts. Building an AI native business happens through that very cycle. I'll go further into Amplitude now. Chat has grown into the main channel through which our customers engage with their product data across the globe. You pose a query using everyday words, and the analysis gets done for you, with no need to construct a dashboard. For plenty of companies, it has turned into the standard method of performing product analytics. Global Agent uncovers the underlying cause for 75% of the questions customers raise and delivers the answer directly. Each week brings 1.3 million global agent interactions, and rates of discovery from root cause are climbing by 1 percentage point monthly. Right now, more than 40% of all insights originate from AI agents rather than people, and we anticipate that share will keep expanding. For a demonstration today, I'd like to walk you through custom agents, Statsig, and Wade. Let's begin with custom agents. Custom agents function as teammates who take recurring workflows on your product data and automate them, then send that work out to other tools and systems. Here's our chat interface. A growing share of users engage with Amplitude chiefly via chat and agents. I'm going to pose a query. Which set of users has the greatest chance of making a purchase in the coming week?

Spenser Skates

executive
#3

Chat is now capable of writing its own code to carry out this analysis. That means we can go far deeper and generate striking new charts and outputs—such as the diagrams shown here, which feature out-of-time decile lift, an ROC curve, and segment propensity. You can dig into it on your own by examining the code that was genuinely used, along with the analysis presented step by step; never before has this kind of depth been achievable in analytics tools. We're no longer held back by what a UI can do. We can also build automated agents that execute on a recurring basis behind the scenes. Here's what I tell it: run this analysis every Monday morning. Take the results and cross-check them against the marketing work in Confluence. Then send me whatever you find via a Slack DM. From there, Amplitude assembles the agent — the very one displayed here. What you're viewing is the full prompt, connectors to Atlassian included, and it will trigger on its own each Monday, delivering the output to me. Our aim is to build the leading analytics agent that covers all data sources. On the front of experimentation and feature management, Statsig sits at the top. With Statsig, experiments operate natively on your cloud data warehouse — Snowflake, BigQuery, Databricks, or Redshift, whichever you happen to use. Let's look at how that functions. What you're seeing is the results page for one of hundreds of tests an ecommerce customer is running. In this experiment, a larger product image is being compared against the standard one. A strong experiment requires a great deal of statistical rigor underneath, and yet the interface remains simple enough that an engineer can launch it. Up top, they can monitor exposure, which tells them whether the experiment is healthy. What we want to see is a 50 to 50 split. That signals things are on track. And here, as you can see, the check is returning healthy. Now we move to the scorecard that holds the results. The confidence interval is 95%. Methods like CUPID and sequential testing, both of which Statsig uses, allow engineers to arrive at a decision more quickly. Those are running, and via monitoring we're seeing specific occurrences that this experiment was designed to measure. So far the outcomes appear favorable. For the checkout event, there's a 27.4% gain, with a 2.3% margin of error. Cart conversion is up. Total purchase dollars are up, even though carts per session is down. As for rolling out this feature, we do it in phases. It starts with employees, moves to early access users, then early release, and lastly a planned rollout to everyone else—a process spanning some 2,500 individuals. Statsig provides numerous advanced experimentation features, including feature gating, dynamic configs, and automatic rollbacks. Together, these equip a team to ship a change gradually, tweak it live, and have it revert automatically when something goes wrong. Last, I want to introduce Wade, which shows where product development is headed. Thanks to Wade, products are able to enhance themselves—it proposes what ought to be developed next by leveraging signals that come from your users. Wade really is magical. It looks at each data source you have at your disposal. That covers analytics, experimentation, session replay, guides and surveys, feedback, and many more. It then pulls all of this together, turning it into a set of suggested product modifications, laying out a roadmap for those modifications, and assisting you in rolling out those updates inside your product. Let me take you through an actual case that WAVE proposed and constructed for Amplitude's documentation site. In looking at session replay as well as analytics data, Wade noticed a jump in failed searches on our docs site. At the core of the problem was that a search on our documentation page fired with every keystroke. When a person entered one letter to start a search, a blank "no results" screen showed up before they had finished typing, which created a bad experience. Wade explains how common this issue is. Every person who searches is impacted, and the expected outcome is an 80% decline in overall search failures. WAVE then created a visual depiction of the problem by itself, displayed below, so it's easy to understand. A full record of the supporting evidence is provided too; as for the plan, WAVE sketches out a wireframe displaying the proposed change. Setting a minimum of 3 characters and a debounce of 200 milliseconds before the search fires. Wade can also drive execution forward. It generated the pull request on its own, and cursor wrote the code. Mark, our technical writer, merged that pull request and shipped it. No engineer, designer, or product manager took part. Finally, Wade monitors what the change delivered. There is a huge decline in overall search failures. Absolutely amazing; let's now talk about a few of our customers. Our results this quarter were strong in both new lands and expansions. We either deepened or established relationships with organizations such as Paramount Global, Jaguar Land Rover, Teladoc Health, Chime, Disney ad platforms, F5 Networks, Coursera, Grammarly, Kraken, and Crunch Fitness, among others. I want to go through 3 examples demonstrating how these customers are using our platform. Number one is Coca Cola FEMSA. Its customers number in the hundreds of thousands of small shops across Latin America—2,500 of them. Every shop is different, but for years the company had no choice except to push a single broad campaign to all of them, because customizing messaging manually for that many retailers just couldn't be done. AI changed all of that. Each retailer began receiving a weekly suggestion of its own, generated by AI. Doubt ran through their internal teams. The idea of a unique message going out to every shop every week felt dangerous to them, and no one was willing to predict it would work. To get an answer, they brought in amplitude. Their AI campaigns ended up producing a click-through rate of 11%, which is 4x what the earlier approach managed to achieve. Our cohort analysis then demonstrated that this gain was sustained. After a retailer got involved, its revenue remained elevated across the weeks that followed; that proof converted doubters at FEMSA, and they scaled from a pilot of 2,500 stores — yes, 2,500 — to 690 thousand retailers. Number two is Replit. Replit is an AI app-builder that enables people without technical backgrounds to turn an idea into an app using AI. Replit has a large global community of committed builders who provide feedback. To understand how customers engage with its agents, Replit depends on AI feedback from Amplitude. Reviews from the Zendesk App Store, along with Twitter and Reddit, have all been connected to that AI feedback, allowing them to identify and prioritize the issues that must be resolved to improve retention and engagement. What previously required weeks of manual work on their end turned into a single simple click with AMP. Amplitude. This is what product development's next generation looks like when put into practice. Third is The Economist. The Economist is a print publication that is currently transitioning toward digital distribution and subscriptions. An AI assistant named Lens was built by a research unit of theirs, and it responds to questions from analysts and strategists by drawing on The Economist's content. Their usual analytics might show what users were up to, but determining whether the AI's answers were genuinely good was beyond them. Staff members were reviewing sessions by hand, but the sheer volume made it impossible to keep pace. There's a 96.9% task success rate, and weekly failures have dropped 84%. That's the loop functioning as intended. Build with AI, assess whether it's good, and repair whatever isn't. To wrap up, the companies operating at the bleeding edge are selecting Amplitude. Thanks to a shift we've undertaken, Amplitude is now an AI-first company, and our foundation for what comes next depends on the possibilities that analytics holds. With Wade, products that improve by themselves are closer than ever before.

Spenser Skates

executive
#4

The speed at which we're innovating keeps picking up, and the way we're building allows it to scale with leverage — I couldn't be more thrilled about what lies ahead. So with that, I'll pass things to Andrew, who will take you through the financials.

Andrew Casey

executive
#5

Thank you, Spenser. We delivered a solid quarter and took a meaningful step ahead in how we execute. We're moving closer to the future we envision, where products get built and refined in new ways. Quarterly revenue passed the $100 million mark, ARR hit $410 million, up more than 22%, including the ARR we picked up from Statsig, and free cash flow set a quarterly record at $23.7 million. Alongside that, we gave back $69 million of capital this quarter through our buyback program. All of this came while we folded in Statsig and its customers, navigated our own shift to being AI native, and rolled out our updated pricing and packaging approach. AI is reshaping the way customers engage with Amplitude. The more of their billing that runs on AI, the greater their measurement needs become. When customers put our AI into their workflows, they perform almost 10x as many analyses as those doing things by hand. That raises the value they get from the data flowing into the platform and makes it more probable that they'll bring in bigger volumes of data and add more products, and that's what drives our growth. The new pricing and packaging is delivering results; it backs our market consolidation play by giving customers a lower total cost when they bring their applications together on our platform. It also gives customers more predictability on cost and makes quoting simpler for our sellers. During the second quarter, 70% of the ARR we closed came on the new model. That's up from 25% in the first quarter. Today, 28% of our overall ARR sits on the new pricing and packaging. The effect is that average ARR is rising, multiproduct attach is higher, contract duration is longer. All of which make our revenue more durable. Our margins represent a decision. The investments we're making are meant to fuel future growth while profitability keeps improving. Gross margin fell more than 1 point from Q1 because of the STAT SIG integration; we're working on optimizing the new hosting environment and cloud structure, though improvement will take time to move from the low 50s gross margin toward the 70 plus we expect for the Statsig business. On top of that, we're seeing stronger customer uptake of AI capabilities and more data ingestion into our platform. Together, those have pushed up our costs and pulled our gross margins down another 2 points from Q1. We've said for a long time that we'll grow with leverage. This cost-of-revenue investment puts more weight on keeping our operating expenses at a lower level so we can achieve that leverage; in Q2, we brought sales and marketing down to under 40% of revenue, and G&A into the low teens. That's helping lift operating margins. Over time, we'll keep managing both areas down as a percentage of revenue while continuing to put money into R&D to fuel innovation. We're instrumenting the business to speed up growth. Take share, and demonstrate leverage. One metric we keep a close eye on is how much data customers actually use versus what they're entitled to, since that's a core driver of monetization. Right now, that figure sits at its highest point ever. This reflects improved pricing and packaging, plus greater usage coming from our AI capabilities. We've strengthened the durability of the business through RPO growth and reworked our internal processes to harness the scalability AI provides. We're pursuing the AI opportunity and gaining share along the way. Now to our second quarter results. Just a reminder — every financial figure I'll mention, apart from revenue, is non GAAP. Our GAAP results, plus a reconciliation of GAAP to non GAAP, are available in the earnings press release and supplemental financials posted on the Investor Relations section of our site. Revenue for the second quarter came in at $100.9 million, up 21% versus a year ago and 8% quarter over quarter. At the close of Q2, total ARR reached $410 million, up 22% from a year earlier and $36 million higher than the prior quarter. Within that number is $17 million in added ARR contributed by Statsig, compared with the $16 million we had expected to contribute when we shared first quarter results. Total remaining performance obligations grew 35% year over year to $483 million. Current RPO increased 30% year over year, and long term RPO was 47% higher year over year. Now for additional detail on what drove the quarter. Enterprise new business and expansion deals both had a strong quarter, and once again platform sales were especially robust. Almost half our client base, 48%, has bought more than one offering from us, and that group accounts for 80% of annual recurring revenue. Customers holding at least five products contribute over 26% of ARR — double what it was in Q2 of last year. On a pro forma basis, net dollar retention hit 105% for the period, powered by cross-sell expansion throughout our customer base. That pro forma figure takes in both Statsig and Amplitude customers. In Q2, our gross margin landed at 71%. That represents a decline of about four percentage points versus the same quarter a year ago, and a sequential drop of four points as well. The reasons were rising inference expenses tied to faster customer uptake of our AI offerings, plus bringing Statsig and its hosting infrastructure into the fold. Sales and marketing accounted for 39% of revenue, which is lower than the 44% recorded in last year's second quarter. G and a represented 13% of revenue, a decrease of one point compared with Q2 of last year. R and D made up 21% of revenue, an increase of roughly three points year over year, driven by spending to expand the Statsig opportunity and provide support to its customers. Operating costs overall came to 73 million, which works out to 72% of revenue. We posted an operating loss of $1.5 million, equal to 1.4% of revenue. On a per-share basis, net loss was -$0.01, calculated using 129.4 million basic shares, versus $0.01 during the same stretch last year. Free cash flow for the quarter reached $23.7 million — 24% of revenue — compared with $18.2 million, or 22% of revenue, in the year-ago comparable period. As the quarter ended, our cash and investments totaled $162 million. Our confidence in this platform's long-term value remains strong, and we have drawn — and will continue drawing — on our cash reserves to soften the impact of dilution. Our balance sheet remains in a solid position, giving us room to pursue a bolder M&A approach so we can speed up our R&D road map when it makes sense. Now let's move to our outlook. As a reminder, we frame how we set guidance around execution. We're happy with the progress we've made overall in consolidating point solutions onto our core platform and in the uptake of our various AI technologies; we've instrumented both our business and our selling so that using more of our platform becomes easier. We think we're positioned well to keep accelerating growth profitably. For Q3 of 26, revenue should land somewhere between $105.6 million and $108 million, which works out to a 21% annual growth rate at the midpoint; non-GAAP operating income should come in somewhere between $2.5 million and $4.5 million. Non-GAAP net income per share should fall somewhere between $0.02 and $0.03, assuming weighted average shares outstanding of roughly 133 million on a fully diluted basis. For the full year 2026, given how the second quarter performed, we're lifting our revenue expectation to somewhere between $407.2 million and $411.2 million, a 19% annual growth rate at the midpoint. We're also raising our outlook for non-GAAP operating income for the entire year, driven by how we performed in the second quarter along with actions we took during the first half, to a range of $6.3 million to $9.3 million. For non-GAAP net income per share, the expected figure falls between $0.06 and $0.08, based on an assumption of approximately 137.1 million weighted average shares outstanding on a fully diluted basis. To close, we're accelerating the rate at which we innovate, and we're growing the value customers receive from us. We have confidence in our ability to scale a durable, growing business while also delivering agentic analytics to the world. With that said, I'll hand it over for Q&A. John, the floor is yours.

John Lewis Streppa

executive
#6

Thanks, Andrew. Now we'll move into the Q&A portion. To make the most of our time, we'd ask that you keep it to one question plus one follow-up.

Analyst

analyst
#7

Thank you, John. Right. If I may begin with Spenser. What I actually wanted to ask about was Wade. I understand it's still in limited beta. My sense is that internally you've had it in use for a number of months at this point. Yes. So I suppose my question is, with Wade, do you anticipate that it might drive a shift — a company moving away from employing bespoke agents tailored to particular use cases and instead going toward a wider AI native product development platform, based on what you're observing? And if that's the case, in what ways might that alter your buyer, perhaps the budgets you're seeing, and the addressable market as time goes on?

Spenser Skates

executive
#8

By bespoke, what exactly do you mean? Could you elaborate? As in, rather than relying on specific agents to handle one particular task underneath, because you've got, say, many agents operating below doing various things for what — alright, I follow what you're getting at. I understand. Okay. Let me break apart a few separate items. What exists on the amplitude side, and I demonstrated with custom agents, is that you've got these agents capable of scanning your data and uncovering insights for you, getting to the root cause of questions, doing so on a routine basis; and sort of distributing it. Regarding what Wade does specifically, as you mentioned, it's sort of — it's examining all your data constantly and then saying, hey. These are friction points. Here's something not functioning the way it ought to. Here's a feature I believe you should give more emphasis. Here's something I consider a best practice that you aren't currently doing. And so it functions at a sort of elevated level; when it comes to the persona, what I think we're observing is a merging of engineers, product managers, and designers into this AI builder persona. It isn't really, like, you've got engineers thinking about what to build, and you've got product managers who are likewise just shipping code; and so the best, you know, if you look at where the AI native teams that everybody wants to become, these roles are blending together; so it remains the same problem we're solving, which is how do we help you build a better product, but we're simply automating a greater portion of it because we're saying, hey. We're going to examine all the data constantly and then offer recommendations. That, like, I have been — we have been discussing self improving products here at Amplitude for roughly 9 years. And so I've actually been blown away by what's achievable with today's technology, where it's just — it's the ideal problem for AI in many respects. The datasets are enormous and complicated; so you can't get any human to review them. And then the synthesis of okay. Here's what I believe could be improved and best practices is actually, like, remarkably impressive. So what that boils down to is that merely through somebody utilizing your software, it improves, since it's simply converting suggestions. There's no longer a need for a person to head into amplitude or any data system and say, hey, this is how I read these outcomes; therefore I believe, you know, when it comes to budget and persona, I believe, once more, that means rather than having those separate roles, you get engineering, product management, and design blending together. You're still engaged in digital product development, and that continues to report up to a certain leader, that same executive, as previously; but yes, how you go about it appears different. Did I—did I address what you were asking about?

Analyst

analyst
#9

Yes, certainly. I appreciate it. Let me ask Andrew a quick follow-up. Assuming my calculations are right, the full-year guidance was increased by over twice the amount of the revenue and operating income beat. So could you walk through the main factors behind the higher growth expectations, and why there seemed to be some pressure on pro forma expansion during the quarter? Then, what are your thoughts on margin leverage — the levers available while you deal with COGS pressure and increasing token spend internally? Thanks.

Andrew Casey

executive
#10

Yes, of course. A few points. First, regarding our capacity to produce revenue in upcoming quarters, we begin with the healthy balances we're booking that appear in our RPO. When you hold commitments from customers over a longer duration, your ability to predict future revenue keeps improving. That's the first point, and it's one reason we stress it so heavily. Second, we examine how strongly our customers are reacting to certain initiatives we're launching. That shows up through our new product capabilities, our new pricing, new packaging, and areas where our sales team is running new promotions and activities. Each of those strengthens our ability to see an increasingly robust pipeline, and that pipeline moves more quickly through its stages, giving us growing confidence that we'll keep adding more in net new ARR. From a revenue standpoint, as you're aware, the bulk of our business comes from our subscription revenue. So those key factors — understanding what the baseline is, what you can see in your pipeline, and what you expect it can convert — are what I'd call our ability to go execute against the plans ahead of us. The sales team has done a really good job driving consolidation in the market, and that by itself, together with our products, is driving great conversions. So that's the first point. On the margin side, I'd say, look. In the case of the Google environment we acquired for Statsig, we'll be focused on driving optimizations there over a period of time. It's definitely lower. It's — we said in the low 50s. From a gross margin perspective. That stems from us taking on an entirely new environment. As you know, most of Amplitude — all of it, in fact — is on AWS. So we took on a whole new cloud and hosting environment, and you have to go through the paces of really optimizing how you run those environments for customers. Initially, our goal was to bring everything together while guaranteeing that service remained uninterrupted. At this point, we're shifting rapidly toward figuring out ways to get the most out of those environments. That represents one significant lever affecting gross margin. Beyond that, we're always examining where we can put money to work so it generates bigger efficiencies throughout every one of our operating expense categories.

John Lewis Streppa

executive
#11

Brent. Thank you, Mark.

Jackson Ader

analyst
#12

Hello. Thanks, everybody. It's wonderful to have you all here. Andrew, I believe this question is directed at you — I'll stay with you, and instead of concentrating on the cloud segment, I'd like to examine operating expenses; we've seen really significant acceleration in organic ARR. That's coming from the business, you know, but you know, taking a slightly longer-term view, even on a non-GAAP basis, we're still approximately at breakeven. Is that right? And so I am wondering as you consider, like, generating additional leverage and additional incremental margin that you mentioned earlier on the income statement, what sort of effect should we anticipate that having on the organic growth figure, if any?

Andrew Casey

executive
#13

Well, what I would say is that, 1, we are still — we continue to expect from an organic standpoint, we possess a fantastic set of products, Spenser just described several of them that are brand new to the market. We believe they have a massive total addressable market that we can pursue. So revenue growth would be the predominant area where we will see rising operating income. On the question of leverage measured against operating income, my expectation is that, as time goes on, we'll get more and more efficient with the gross cost tied to start revenue, which should let gross margins widen gradually. Getting there just isn't quick, especially with customer demand inflecting the way it is and data lines expanding. As I said earlier, the volume of data ingestion on the platform relative to entitlements has never been higher. Back when I came on board, that figure sat in the low 60s. When you look at how much customers have actually consumed relative to what they're entitled to, we're now solidly past the 80% mark. That points to more expansion through upsell, and historically that's an area where we struggled quite a bit — overselling, and figuring out how to get contracts sized correctly. This is the first time we've moved beyond those issues, and we're beginning to see genuinely strong upsell activity, with growth being fueled not only by cross sell. So the main way we're driving better profitability is through revenue growth. On the leverage side, my expectation is that gross margins will head higher down the road; it's simply going to take some time. We've got a lot of ground still to cover when it comes to sales and marketing, specifically bringing that down as a share of revenue. There's room in G and A, I believe, and my sense is that as the R&D group picks up more and more abilities to turn out products more quickly, we'll keep seeing bigger and bigger efficiency gains there over time.

Jackson Ader

analyst
#14

All right, and I've got one more quick question as a follow-up. Could you remind us whether, given that we're now operating under a different sort of pricing and packaging approach — one that's a bit more variable, I suppose — there ought to be any shift when it comes to the seasonality of how your revenue ramps or gets recognized as we go forward with this new packaging?

Andrew Casey

executive
#15

Regarding revenue, what I'd say is that you see a reasonably predictable pattern by which revenue gets recognized. That's because, as mentioned, the bulk of our revenue in upcoming periods is set by our RPO — those committed contracts. ARR, though, is going to track a very standard seasonal shape. My expectation leans somewhat toward the enterprise selling side of things. Q1 is going to remain our softest period in terms of net new ARR additions, since that's when we're bringing on new territories, hiring new reps, and rolling out new strategic initiatives; this year especially, we're busy teaching the sales teams about both the new pricing and packaging and a great many of the new products we've launched. So annually, that pattern shows up, meaning a sluggish beginning followed by an uptick. In 2 this year, just as a reminder to everyone, we likewise experienced significant shifts in our sales and marketing leadership, and that's largely what's now working its way through, along with a cost advantage stemming from a reduced sales and marketing figure as a share of revenue. And that comes from the efficiencies we're generating.

John Lewis Streppa

executive
#16

Brent. Thanks, Jackson.

Scott Berg

analyst
#17

Hey, Spenser and Andrew. Great quarter. Appreciate you fielding my questions. I'd like to build on the sales enablement topic Andrew brought up earlier. We ran a few separate customer checks during the quarter, and the one takeaway that kept coming back is that I don't believe your current customers fully realize all the various modules and new features you've launched this year. Yeah. Absolutely. I can see Spenser grinning. I realize that's partly just a matter of time, clearly, and one customer wasn't even aware you'd bought Statsig. So I suppose, where would you say you are in that process? Where are you — at what point does it become properly ramped? I mean, the quarterly sales numbers were solid as they stand, but clearly, stronger, stronger awareness there could help even more.

Spenser Skates

executive
#18

Yeah. To your point, I think plenty of folks still categorize us as an analytics firm, and that makes me absolutely nuts. Honestly, I'm just out there saying, hey, we've got Statsig now, and this is cutting-edge feature experimentation. And you can use it as well, and this is the very same infrastructure OpenAI runs in-house. Like, incredible. Plenty of customers aren't even aware of that. Right? And then the same goes for Wade. Right? I think it's just beginning to grasp Wade and then the same goes for our remaining products. I think if you recall from the prepared remarks, like, you do see ramping; so, you know, we're shifting customers from 1 to 2 to 3 to 4 to 5 to more products, but it happens much more slowly, and that makes me nuts. I think it's, you know, there's no replacement for the effort of, hey. We created something incredible. We need to educate, you know, the hundreds of folks we have in our field. And then they need to educate the thousands of customers in market. Like, that's simply work. that's simply the entire thing. Something I'm devoting a lot of time with Nate, our chief commercial officer, along with the rest of the executive team on regarding how we get that and do that more efficiently; we just had to kick off a few weeks ago where we showed off a lot of what you saw today with Statsig and Wade and custom agents. But, you know, that's not even to mention the other products we have, like session replay and guides and surveys and AI feedback that can displace point solutions. Anyway, that's I think last year, said the year of the plat — it was the year of the platform. I think we still have a ways to go on educating people on it. What I'd say is that the positive side of this is that what most customers want is evidence that we're operating right at the forefront of where this space is headed. So in my opinion, analytics along with the entire data and behavioral data ecosystem is going to experience the same kind of transformation that coding went through over the past 2 years. That's still going to take place. And because of that, they want to — you know, we observe it in plenty of things we've been showing in demos and, you know, our customers are seeing it as well; so what they want to know is, hey, am I dealing with a company that's at the bleeding edge on this? And so even if they aren't quite ready to bring in a WAVE or perhaps even a Statsig, I understand that, okay. You can at minimum assist me in taking that initial step toward using some of the fundamental capabilities here, and afterward I'm able to layer on more, you know, even if it might be too much for me at the very beginning or I'm not prepared as a company; so in any case, what all of this means is that we still have plenty of work ahead to ensure our field is properly equipped. You know, there are certainly areas doing this really well, but there are also areas where we need to improve. So I appreciate you bringing that up.

Scott Berg

analyst
#19

Appreciate that, Spenser. My next question concerns how things are going with bringing Statsig into the fold. Obviously, you set a fairly ambitious target for absorbing that asset into your teams. Where do things stand right now? The other clients we talked to were really enthusiastic about it. A few of them, as you know, are already SaaS customers and so on. So I just want to get a sense — have all the objectives on that front been met? And are you now at the stage where you can focus purely on product and sales rather than still needing to fold the organization in?

Spenser Skates

executive
#20

Yeah. As you can picture, Statsig has existed for 5 years, and a great deal of effort goes into taking it from, well, an entire set of individuals who had never laid eyes on the codebase, never sold it, or anything like that. I believe we have more or less made it through — there's always something — but we have made it through every one of the pressing emergencies. In operating and shipping Statsig. So that's excellent. Customers are quite enthusiastic about how it's being received. We want to be sure to give you the reality that this is our primary focus, whereas at OpenAI, it was somewhat more of a secondary matter for them. It has all been met with a positive response. That's good. At this point we're beginning to consider, alright, what comes after this for Statsig. So if you go to, say, statsig.com/updates, we're putting out releases. We've been putting out releases for the past few months; we keep building along the road map. We keep tying it into Amplitude far more closely, so that if you use both, which many of our clients do, you gain the advantage of drawing on data from 1 and the other; and I think another thing we're noticing with Statsig is that there's substantial demand coming especially from AI natives. So 1 of the reasons we're so thrilled to team up with Statsig is that they — well, a great deal of how future product development gets carried out — people are picking Statsig for that. So it's engineering-first teams that tend to be far more technical; they're constructing entire software development harnesses. They want to control how things get deployed within that harness. And Statsig is built really, really well to scale. As I said, OpenAI operates a version of that infrastructure in-house for itself; and so, as you know, they've put that to the test in all sorts of ways over there, and, as you know, we're doing the very same thing, with everybody outside of OpenAI. There's a great deal on our plate when it comes to figuring out the way to make Statsig a central piece of the software development harness for every one of these bleeding edge AI customers, and that's the direction everybody ultimately wants to move in. So that's where our attention is.

Scott Berg

analyst
#21

Great, I appreciate you fielding these.

John Lewis Streppa

executive
#22

Absolutely, Scott. This is Brent. Thanks, Scott.

Billy Fitzsimmons

analyst
#23

Hey, everyone. It's great to see the results and the guidance. One thing I find exciting about Statsig is the potential for cross-selling. I realize a few things need to happen first, but the last time I looked, I believe 80 out of the 400 Statsig customers are already on Amplitude, so there's a large group that isn't. Could you help put this in context for us — how should we think about the potential cross-sell opportunity from Amplitude into Statsig, or possibly the other direction, and how should we think about that through the model over the long term?

Spenser Skates

executive
#24

I'd say the far bigger opportunity is probably bringing Statsig to Amplitude customers. As I mentioned earlier, Statsig customers tend to be much more bleeding edge when it comes to AI innovation. That's where everyone is trying to get their organizations over the long term. It's a very — Amplitude has historically been more focused on product management, whereas Statsig is much more tailored toward engineers. It has tons of customization out of the box. It has all the statistical testing; now, as I said, those 2 personas are merging, but, you know, it's still early days on that. So I think the opportunity is that as more of our traditional Amplitude customers look to build like AI natives, introduce AI into their software development process, try to build out a harness, and eventually try to get to self-improving products, all of those are chances for us to bring in Statsig. We definitely do see places where Statsig customers are also very interested in Amplitude. But, you know, there's a lot more, both from a number and ARR basis, that are Amplitude.

Billy Fitzsimmons

analyst
#25

Great. So for my follow-up, could you give some context on how your staffing requirements might have shifted since the start of the year, or on where you're finding the greatest returns from efficiencies powered by AI inside Amplitude?

Spenser Skates

executive
#26

Oh, there's a tremendous amount. Regarding recruitment, a handful of distinct points. First, it's been — my focus has been squarely on reshaping our whole workforce, bringing leaders, bringing engineers, bringing folks in other departments into an AI-native mindset, both through recruiting such talent, bringing it in, you know, bringing on executives who possess that experience. And beyond that, upskilling and further educating the staff we already have here. Like, everybody's eager to pick it up. It's like, yeah. You know, folks recognize, like, hey. The better I get at working with AI, the more valuable my abilities become both here at Amplitude and elsewhere down the road; so everyone's, like, getting on board with it, which is wonderful. A handful of particular areas, I think on yeah, so that's, like, something that never stops. Like, I just — we recently brought on Angela, which we shared today, in marketing. You know, we constantly examine companies and other spots to bring in talent. That's another fantastic source of extremely high-leverage talent. One amusing thing I'll share with you all during, you know, slumps or whatnot, plenty of businesses reduce campus recruiting; yet since it's, like, the simplest item to trim; yet if you've got the conviction to judge who's excellent from that candidate pool, you can land some outstanding people straight out of college, which is terrific; so we've made that a major priority here at Amplitude. So that's, like, the main item. And then the one particular area is Statsig. You know, as you'd expect, this is a massive, you know, intricate product plus code base and architecture. And so our we've taken our current experimentation team, and they're now operating Statsig, which is terrific; yet they also require far more support, so we're bringing in, you know, many different positions and recruiting for that data science leads, or deployed engineers. You know, additional engineers who are simply acquainted with that architecture; we've actually brought on one individual who previously worked at Statsig, prior to the acquisition opening, and we're carrying on further there. So there's a great deal we must accomplish there. We've sort of I kinda seized the opportunity, which is nice, but now we've got to, like, go get the most out of it.

Billy Fitzsimmons

analyst
#27

Billy, take it away for a question. Appreciate it, everyone.

John Lewis Streppa

executive
#28

Sounds good. Thanks a lot, Billy.

Clark Wright

analyst
#29

Thanks. It was really encouraging to see that 30% rise compared with the prior year among accounts exceeding 100 ks in ARR, and that appears to be the biggest figure for 2021. Would you be able to separate out the additions coming from Statsig? And what other factors are driving the new logo momentum you're currently observing?

Andrew Casey

executive
#30

Absolutely. Roughly 40 customers originated from the Statsig side of the business that we brought on. If you work through the arithmetic quickly, that still leaves you comfortably in, at almost 23, 24% growth for customers within that cohort above $100 thousand, so that group continues to expand rather well and adds to ARR as well as revenue growth. That was genuinely strong; and like Spenser said before, what we observe when we engage with customers, particularly the ones we've just been introduced to for the first time, whether they're completely new to Amplitude or previously with Statsig, is that they tend to be, 1, highly appreciative that Amplitude is guiding and advancing the road map, demonstrating confidence in our capacity to genuinely deliver a future in which self improving products become a reality; they accomplish this by embracing an experimentation mindset, and afterward they feel very confident moving ahead with Amplitude across other areas; therefore that cross sell expansion possibility is genuine. I believe we discussed this back then. There was a multi-hundred-million-dollar opportunity awaiting us simply within the install base. So that has us quite enthusiastic.

Clark Wright

analyst
#31

Understood. And in the prior quarter, you mentioned that event volume growth was 21%. On a year-over-year basis. Where does that stand at present, when you discuss the momentum you're observing at all-time highs? And what should we expect regarding how that ramps moving forward, considering agentic workflows and how many events they're able to handle?

Andrew Casey

executive
#32

Yes; it is certainly expanding more quickly than both ARR and revenue, and it is among those things where, for us, it feels as though we've been through a great many quarters of attempting to raise it and get the entitlements appropriately sized and all the rest. It is certainly a leading indicator for us that, you know, 1, we won't experience the same kinds of churn problems as previously. 2, sales has embraced that value-based orientation sale where they aren't attempting to get everything up front; they're attempting to get our customers to value quickly and demonstrate to them the value of an expansion; and as I mentioned, it is a signal that we'll see upsells make a larger, meaningful contribution to growth. In contrast to before, when it was a detractor and the bulk of our growth came with cross sell. We simply won't encounter those identical situations if we have customers who are pushing against their entitlements. And obtaining value from the investment they've made.

Clark Wright

analyst
#33

Understood. Thanks.

John Lewis Streppa

executive
#34

Brent, and thanks to you, Clark.

Koji Ikeda

analyst
#35

Yeah, thanks. Thanks a lot, everyone. I'd like to ask something about Wade. The demo was great, and I really like the long-term vision. It sounds like it's going to be fantastic for identifying issues, discovering fixes, writing code, and tracking results. It really seems like the complete package. So my real question is this: if Wade accomplishes everything I believe it can, what would be the reason to still use Amplitude's other offerings, such as Statsig and product analytics?

Analyst

analyst
#36

It feels like you could handle everything from there.

Spenser Skates

executive
#37

Yeah, absolutely. Absolutely. All right, so this is something I touched on briefly when talking about the architecture. Wade pulls information in from a wide variety of sources. It gathers analytics information from Amplitude, and experiment information from Statsig. Down the road, our plan is to make it agnostic, so that over the long term it's able to pull from any analytics tool — whether that's Google Analytics, Adobe, or another option. That doesn't matter; then it turns those insights into something useful. So you still need somewhere to source that information from. It isn't capable of simply examining a product and determining what users are doing with it. It genuinely has to receive that information from somewhere. And that makes for a good build where, hey — go with Amplitude. Go with Statsig. When you feed additional sources of information into this system, the results improve. That's what you're noticing. One major takeaway from the surge in AI is that having an enormous amount of information at your disposal simply produces superior, more precise, and deeper findings. It's essentially a direct—you know, it's something you can observe. The scaling laws suggest you're able to expand that virtually without limit. So Amplitude Analytics, along with the experimentation capabilities and all our other offerings, serves a truly vital role as the hubs where that information gets gathered. To reiterate, our aim is to stay agnostic, so we can connect with any system—whether that's a data warehouse, something internal to you, or other tools, including third-party ones—and let you build on top of it. Another point, I think, is that having this data enables us to gain far deeper insight into what should be developed. Imagine you're a startup just getting going and you lack the enormous dataset—multiple petabytes, as we have. Then it's like, okay, how can you possibly tell whether what you're suggesting is a best practice or will produce a good outcome? Since we hold this dataset, we end up with plenty of feedback loops. We can say, alright, this is the shape of an excellent ecommerce app. This is the shape of an excellent social media app. So imagine what a fintech application should look like. Imagine which sign-up flows actually work well. Imagine how personalization in messaging should work, and so on. And given that only a few companies operate in this area, there aren't any public datasets you could compare against. So having it means we can build a much better, higher-quality version of Wade than practically anyone else out there. Then, the other positive aspect is that it isn't, well, it's an alpha, meaning customers are actually using it; it isn't being used by us in-house. There are several startups involved. A handful of enterprises are making use of it too. So it's generating genuine outcomes that, honestly, when you examine this, you're simply thinking, wow. How on earth did AI produce this? This is unbelievable. I'm certain that whoever takes this space will have a multibillion dollar enterprise, possibly even beyond that. Thus, our approach is essentially, let's charge ahead with that as quickly as we possibly can. I believe we're nicely situated for this chance since we lead in analytics along with a few other domains. Right. And, well, let's proceed, let's go construct that enterprise as rapidly as possible.

Koji Ikeda

analyst
#38

Understood. I appreciate it, Spenser. That's everything on my end.

John Lewis Streppa

executive
#39

Many thanks to you. Certainly, Koji. I appreciate it, Koji.

Nick Altmann

analyst
#40

Hi there, and thanks, everybody. Building on Koji's earlier question, I'd like to ask Wade something from the other direction: it seems like there's a more compelling case for adopting the broader platform alongside Wade. Exactly. I know it's still very early, but what does that conversation look like with customers right now? For example, are you noticing more people buying multiple products or the platform as a whole, as they weigh Wade and the notion of a product that keeps improving itself? And then my second question: how should we view Wade's monetization trajectory in the nearer term? Is the monetization kind of indirect—meaning it gives people a stronger incentive to adopt the broader platform and that's the way you plan to make money from it—or does it function as a separate SKU?

Spenser Skates

executive
#41

Right, so your read on this is spot on: the more sources of data you bring into it, the stronger it performs. Because of that, I've personally already watched several customers come aboard through session replay. Plus there was one that specifically purchased AI feedback for the reason that, hey, what the wave delivers makes that much of a difference. And you've got it exactly right in that it fuels the entire platform strategy, or it's like, okay. So you've got all these separate point solutions, and really they're just additional places to pull data from. Session replay stands out as especially strong. As you can picture, being able to look at exactly what the UI state was and where someone clicked carries a lot of value for figuring out how to improve things. So watching that has been fantastic. And again, it's still early — there are a handful of customers using it. But as we expand it, I believe that'll bring in more adoption. And I don't think — going back to what I told Koji — our aim is to stay agnostic here. Our goal is to create the most advanced solution possible. So bringing in additional sources would only improve things. Regarding making money, we will definitely charge for this. There's no question we'll charge. Consider the value it delivers. Previously, with analytics or data tools, you'd have to go in yourself, gather an event, or pose a specific question, receive an answer, and then figure out how to use that in your business. But now, you have an entire process handling that automatically. Hey, I've noticed this user is already experiencing friction right there. Take my docs example: it basically says, look, we notice the majority of searches aren't succeeding. What's causing that? So, what you're dealing with here is single characters, correct? And we don't wait for someone to finish entering a whole word. That means the error shows up before they've even completed typing it, which feels terrible. And honestly, it's the sort of thing where you think, well, that's obvious. Sure. Yeah, you should address that and make it better. And that's not the only instance — it's closer to that same pattern times hundreds of problems across each area of your offering. One takeaway is this: behavioral data plus the areas where a product shows up are so vast that no team could possibly keep track of all of it. So the reality that this system is constantly searching for ways it could improve — that alone is just magical. I mean, what it’s able to do is wild. So my view is whichever business ends up winning in that space is going to reach several billion dollars in revenue, maybe even beyond, and we want to move hard. And yes, buyers will pay for that. Now, once again, it’s still early — we’re in alpha — so we haven’t nailed down precisely what our monetization approach will be, but we will definitely charge for that functionality. That’s one of the big things, you know, people keep asking, hey, so much money is flowing into AI — where does it actually show up? This is one where you can trace the connection very clearly. It’s like, look — the customer experience improves. They spend more. Revenue rises. There’s less friction. Less downtime. The entire thing simply gets better. That’s a fantastic use case from an application perspective.

Nick Altmann

analyst
#42

Nicholas Altmann here with a question for Brent. Thanks a lot.

John Lewis Streppa

executive
#43

Absolutely. I appreciate it, Nick.

Yitchuin Wong

analyst
#44

Hey there. Evening, everyone. Appreciate you letting me ask something. Spenser, along with the rest of the crew, it's honestly exciting to watch this AI platform grow so quickly each quarter. I'd like to dig into agent analytics, which is now something you can actually measure. I'm a fan. Think about the agents themselves, correct? What I mean is, the space we're looking at already has a bunch of players attempting to track prompts, track latency, hallucinations, and everything else you could name. So which customer pain points does agent analytics address that today's observability tools are unable to? And after that, how do you think about the size of the opportunity? For that particular problem?

Spenser Skates

executive
#45

Yeah. Well, I'd say, first of all, if this ends up taking the place of the majority of conventional interfaces, well then the size of the opportunity becomes just as big, maybe bigger, than what happens with conventional user interfaces involving session replay plus analytics; regarding what makes our positioning distinct, the thing we provide, which I touched on briefly in that customer story about The Economist, is the ability to link whatever is happening on an individual basis inside a session to the lasting effect on your company; so you're able to say, alright. Hey. The bot gave you a good answer. Did that cause you to spend more, or register, or renew your subscription? On the flip side, if you hit an issue and ended up annoyed, did that produce some unfavorable long-term result? That feedback loop matters enormously. Most of the engineering-focused observability offerings we've come across in this area tend to sit on their own. It's like, alright. All they do is display the traces, and that's about all. Meanwhile you're completely in the dark about whether it eventually produces different outcomes later on. That's the reason we're seeing both conventional sorts of enterprises that are reworking how they operate, such as The Economist, and also plenty of AI-first companies. You know, I brought up 1 of the biggest foundation model businesses. They're also examining, as you'd expect, they've got plenty of tools in place, yet they want to understand, alright. Does this eventually push somebody toward becoming an upsell, that whole set of things over the longer term? So having the ability to link that journey from start to finish is the thing only we provide.

Yitchuin Wong

analyst
#46

Sounds like another chance to grow TAM there. Oh, for sure. For sure. Yeah. Today I didn't go into it that much. We showed it off more during the Q1 earnings call; but, yeah, it truly is one of those items that my chief commercial office and I feel a lot of enthusiasm about. Yeah. Certainly eager to hear additional details, Wade included. I've got a brief follow-up for Andrew too regarding the guidance. Like, amplitude growth had clearly been speeding up over the last year or longer, correct? Even when we adjust for the static business this quarter, I believe it's still speeding up; but the implied guide I'm seeking for Q4 indicates roughly a 2- to 3-point decel. Could we perhaps dig into the biggest step down in the Q4 guide — is it mostly just seasonality or added conservatism?

Andrew Casey

executive
#47

What I'd say is that whenever we put our guidance together, we constantly examine what we think has, you know, a really high probability of happening. And earlier I brought up certain factors regarding pipeline, how effectively that pipeline has grown, you know, where we're noticing solid demand from our customers. Typically, Q4 ranks as our best quarter when it comes to net new ARR, and that's due to how we designed our comp plans. That's how enterprise selling cycles tend to unfold in a company operating on a calendar basis. I'd simply say our guidance rests on what we know exists out there in terms of our pipelines, our RPO, and it's what we feel at ease with. Understood.

Yitchuin Wong

analyst
#48

Congrats, guys.

Andrew Casey

executive
#49

Thank you.

John Lewis Streppa

executive
#50

Thanks, YC.

Willow Miller

analyst
#51

Hi, everyone. Appreciate you letting us ask. Could you share what you're now thinking about that goal of more than 20% revenue growth, especially after such a solid quarter and a strong guide for the third quarter? With Statsig and now Wade in the picture, I'd love to know how you're viewing it.

Spenser Skates

executive
#52

Oh, yes. To me, Statsig speeds up what we've planned for the long run, and that's a big reason Vijay and I felt Amplitude was the right place for Statsig over time. As I see it, we delivered $19 million of organic growth in the last quarter, Q2; so we're basically right at that 20% mark. The annual figure sits at 410. Divide that, and you get, well, annualizing the quarterly figures leaves us just under that 20% growth target. For me, like I've consistently said, 20% is really the floor. We all want to keep reaching and beating that 20%. Over the long term, we're setting our sights much higher. We want to reach 30 and then go past that as the business keeps expanding. Clearly, there's a lot to do to get from here to there, but that's what we're deeply committed to.

Willow Miller

analyst
#53

Great, that’s good to hear. Thanks.

John Lewis Streppa

executive
#54

Thanks, Willow. That brings our second quarter earnings call to a close. We appreciate the time and interest you’ve given us. We hope to see you during this quarter while we’re on the road at conferences put on by KeyBanc, Citi, and Piper Sandler. Thanks. Thanks, everyone. Thanks.

Read the full transcript via the API

You're viewing the first half of this call. Get the complete Amplitude, Inc. transcript — plus 131,000+ transcripts from 7,000+ companies, speaker segments, AI summaries and full-text search — through the EarningsCalls.dev API.

Get the API View API docs →

This call discussed

For developers and AI pipelines

Programmatic access to Amplitude, Inc. earnings transcripts and 131,000+ others is available through the EarningsCalls.dev REST API. Plans from $39.99/month — full transcripts, speaker segments, full-text search, and the recently-added /api/v1/transcripts/recent polling endpoint for ETL pipelines.

More tools for stock research

OptionsBell: an unusual options activity scanner that tracks options flow across all US stocks and emails you when large trades appear in Amplitude, Inc. or any ticker on your watchlist.

StockMarketScan: a stock screener with alerts: 24 pre-built screens refreshed every 5 minutes, watchlists and email notifications. Both offer API and MCP access and fair monthly pricing.