Transcript
0:00 If you're not using cloth code this year, no matter what your role is, you're probably underperforming compared to others on the company. PMs often pride themselves on like the spec, the perfect spec. They have to understand that it's actually AI that's reading the spec now versus engineers. 50% of Ramp's code is built by AI. That's 50% up from 30% in December. It'll probably be 80% by March. And this is not just like a front-end prototype, right? This is the real product, back-end, front-end, and I have a PR and I can just submit it to the engineering team. PMs are shipping tons using the spec. And so are designers, so are operators, so are like the account managers and sales people are also getting activated. My job is to automate my job. And our all our jobs is to automate our jobs.
0:40 >> All right, everyone. My guest today is Jeff, CPO of Ramp. And Ramp is one of the fastest growing companies ever and probably the most AI-native company that I know outside of the big labs. So, last year Jeff and team shipped over 500 features and hit over a billion dollars in revenue, all with around 25 PMs. So, yeah, really excited to talk to Jeff today and welcome, Jeff. >> Super excited to be here. Thanks for having me, Peter.
1:05 >> Awesome, man. So, you know, I've worked at a lot of big tech companies, but like can you give us a quick overview of how Ramp ships features like from idea to launch? >> Yeah, I'll I'll skip I'll skip the basics and and just jump into the fact that it's a crazy time right now and the way that we are building has always been around velocity and and the way that you move fast is by leveraging tools and AI is just an incredible accelerant to everything that we do. And you know, I hope during this call that, you know, I'll be able to share a few of the ways that we've we've leveraged AI to accelerate, to inspire folks and and and help amplify then the learnings. I also expect that a lot of the things that we're going to talk about today are going to be outdated, you know, even by the time that that you even share this this this recording. So, excited for it. But yeah, I mean, the product development process you know, hasn't dramatically changed in terms of root principles, right? It's about understanding customer pain point, about identifying the right solution, about building the solution, and then testing and iterating. And and I think AI just lowered the cost of each of these sections dramatically. You know, the cost of code is basically down to almost zero apart from the tokens. And so, PMs just need to be actually writing the specs for the agents rather than engineers themselves, and I think that's a It's a complete shift in terms of of how we go about it.
2:29 >> Yeah, so so basically the PMs will make the will make the product first pretty much by themselves, right? Or make the prototype at least, and like get some validation before doing anything else. >> Yeah, I mean we we, you know, PMs often pride themselves on like the spec, the perfect spec, and they have to understand that it's actually AI that's reading the spec now versus engineers. And so, the spec itself is is is basically the output of a prompt. And then the output of the spec is the product. So, at the end of the day it's just prompt to product, back to prompt, back to product. and yeah, we are essentially collaborating on an actual product itself in a prototype.
3:07 I wouldn't even call it a prototype. It's actually a working product rather than the actual spec itself. >> Yeah, I always suspect that engineers don't really read my specs carefully. So, like I always I always try to keep my specs to like less than two pages to begin with cuz, you know, no one wants to read this But like, yeah, the AI agent will actually thoroughly read read it. So, that's So, that's a good thing. Okay, so before we even get to the spec though, like first you have to like like you said, you have to understand customer, understand problem, and and like how how do you How do you guys work with AI to figure out what what to build or what the customer pain point is?
3:37 >> Yeah, so the advantage that we have is that, you know, we have we have 50,000 plus customers on Ramp and growing super super fast. We have over a million end users. And so, that gives us a ton of signal. We also have a ton of people on on sales, on support, on account management. And so, those are all touch points that we can leverage to understand kind of what the problems are and what opportunities are and and what we should be focusing on. The the The question is around like how do you actually sift through all this noise? And that's where like a large language model is fantastic. So, the first thing we invested in is, what we call voice of the customer. And typically it was a, you know, it was it was a person that we hired that that tried to, you know, do all this work, themselves.
4:15 Now it's basically an agent. And and that agent is essentially able to sift through all our Gong recordings, all our Salesforce notes, all in-app surveys, all support tickets, all in-app chats, any email that is being sent to, to account managers. And essentially gather all that context as well as our Snowflake database and our analytics and help answer any question that that product managers have around their persona, their pain points, their their workflows, and the gaps of their products.
4:42 so happy to jump into that, but that's that's a huge thing that we've invested in. Yeah, do you do you want to do you want to are you able to give a live demo of of that or like show us how that works? >> Let me share one version of that. So, yeah. This is our voice of the customer tool. And, and and you as you can see, you know, you can ask any question for on this on this on this bot and this bot will literally go through any type of question. So, you know, for this demo I asked, you know, what's feedback that we people have on our procurement product, right? And, you can you can see that the sources. So, do you want me to look through support tickets, chat logs, sales research, feature requests, etc. I just said, "Okay, let's just go through support ticket and chat logs." It literally went through 90 days of support tickets and chat logs and identified the actual key, topics that we need to focus on as well as links to the underlying, assets for me to double click into.
5:30 So, you know, purchase order management approval flow routing, chat, you know, chat understanding with Ramp Assist, exports, currency constraints. I mean, this is like this was done in, you know, from 38 to 40 so, about 8 minutes. and something that would have taken 8 days for a human to actually do across the entire volume. >> Yeah, I mean this is basically like kind of prioritizes your road map for you or it it like has number of support tickets and and everything.
5:57 >> It at least helps you identify with a ton of context that the problems that your your customers are facing with and enables you to go deeper. So then you can, you know, it's it's essentially a conversation, right? Imagine you have this like full-blown analyst. How do you continue prompting the analyst to go deeper? So now it's like, "Okay, I want to go super deep on this specific problem case. Bring customer quotes. Bring me some like log rocket sessions.
6:15 Bring me you know, customer IDs that I can go and research to. Create a email that I can go to that I can use. Draft that in my Gmail account for me to actually automatically send to set customer to book meetings on my behalf." All of these things are basically prompts and and this agent actually has all the connectivity to be able to do these things. >> And I love how the user interface is just like a Slack channel or or like I guess you can DM the agent, too, if if you want.
6:41 >> Yeah, 100%. We've seen like Slack being a a great place to actually host these things because that's essentially what you would do with a human, right? You would you would Slack your your product operator or Slack a team channel being like, "Go do these things." So it's a very natural way of of of of doing work and personalizing these these agents as essentially your coworkers. >> Oh, wow. Okay. Okay. >> This episode is brought to you by Grainola. If you're in back-to-back meetings, you know how much work it is to take notes live and clean them up afterwards. That's why I love Grainola, the best AI meeting notes app in the market. Here's how I use it. Grainola automatically takes notes during a meeting and I can add my own notes, too.
7:17 After the meeting ends, I use a Grainola recipe to extract clear takeaways and next steps in the exact format that I want. Then I can just share our notes directly in Slack with my colleagues or even get Grainola to share the notes automatically. Honestly, of all the AI apps that I use, Grainola is the one that saves me the most time. Try it now at grainola.ai/peter and use the code Peter to sign up and get three months free. That's granolas.ai/peter.
7:45 Now, back to our episode. >> So, that's that's the quality of the piece that you showed me. What about the the metrics and the data piece? Like, how do you Like, do you just give people access to like pull data themselves or how how do you do Yeah. >> Yeah. So, so there's you know, the space is moving very very quickly. So, six months ago, you know, we we we launched our own bot for for data analysis. I'll I'll give a quick a quick >> quick view of this.
8:11 >> And this is now outdated. and I'll tell you why. So, we launched what we call Ramp Research. So, it's funny like before you would you would ask a data analyst or you would try to do it yourself with, you know, Looker. Hex is getting pretty good at like creating your own prompts, etc. But, it was still, you know, fairly fairly a lot of work to like get an answer to a question, right? And now it's like hey, I have a question. Give me the answer.
8:37 so, now we have Ramp Research that essentially I mean, it it it it the use cases are insane. And actually, by making it easier for people to ask questions about data, you actually you actually increase the number of people who actually ask questions about data. And you actually become more data-centric as a company. So, you know, what's an example? you know, let's say that you have a automated email campaign and you want to understand the performance.
8:58 What's the open rate of automated emails a customer sent? Boom. You know, Ramp Research understands our entire database, and understands all the schemas, and understands what you're trying to do, and automatically like generates the the actual interpretation of of said results. And this is, you know, this is used, you know, so much. And this was this was in 2 minutes, right? by by literally everyone. So, sales people trying to find, you know, what are our customers in Milwaukee?
9:21 support people trying to figure out like the the common use cases of XYZ product. marketers trying to figure out the performances of their campaigns, etc. But, I I shared that this was outdated in the sense that we now basically have moved to Snowflake CLI plus Claude plus skills. So essentially we we we've now moved to to using, you know, Claude code. We we have our own database of of skills that we've developed. So we have a data analyst skill that essentially fully understands our database and understands how we go about approaching a data analytics problem and the best practices of that. And then we essentially can now prompt Claude to say, "Hey, you know, you know, build me a full report of the performance of, you know, our procurement product and identify, you know, the top reasons why people opt in, the top the top blockers in our funnel, and, you know, draft with me, you know, 10 different growth ideas that we could be running." And and and Claude will actually generate, you know, a full HTML report fully baked into our data that is directly actionable.
10:27 >> Yeah, okay. So it's not just a Q&A anymore. It's actually doing work for you, right? That's why it's better than the thing. >> Yeah, I mean, at the end of the day, like, it's funny like you you you know, you ask a question, but you have a goal, right? So sometimes you ask the question and you get the result, but you should just tell AI what your goal is. And you'll actually be surprised at the questions that the AI can actually ask themselves to get to the goal.
10:49 >> And and have have you given the entire company access to Claude Claude coders or like just engineers or everybody can use use it? >> Anyone can use it, right? And in fact, like, you know, we'll get into this around like how you actually become more AI driven as a company, but if you're not using Claude code this year, no matter what your role is, you're probably underperforming compared to others on the company. And so it's certainly not a product for for engineers. It is absolutely a product for builders. And you know, we talk a lot about Claude code right now, like, you know, Opus 4546, like, big launches and a big big movement in the last like 3 months. I mean, you just saw the Anthropic $30 billion raise. But I I I expect the the tools to continue evolving. Like, I you know, by the time we we meet next, you know, in the next 90 days, it might actually be completely different, right? and so, it's less about like forcing people to use one tool, it's about giving people full access to any tool they want to share openly what work people are using, and then get people to adopt to get to the aha moments, and then but yeah, we don't want to be dogmatic, but we want to like radically empower, and and also have like full visibility on what people are doing.
11:59 >> Yeah, let's talk about later, cuz I I I think so many companies still don't get this. They're like, "Oh, you know, like, what's the cost of this? What's the ROI of this? Why should I give some sales person this thing?" They just don't get it, man. We'll talk about We'll talk about that later. Yeah. So, let's let's keep going. Let's keep going down the product development process. So, now you have all this crazy feedback coming, and the quant I mean, people talk about product sense like it's some mythical thing, but I think it's just like like how much product feedback are you getting like how how much are you like embedded in like the the feedback loops and like the the data every single day, and then you kind of just develop that as a second nature kind of thing, you know?
12:33 So, but so but after you have that, like how do you actually you know, you mentioned that you don't actually respect anymore. Like, how how how do you define the solution? You just make the make the product right off the bat, or >> Yeah, so so there's the there is the problem identification, then there's like the actual like writing of requirements. and we have, you know, our own Claude skills for that, right? So, so, you know, Claude has has full access to our Notion. Notion has the full context and all all our personas, and all the research we've done. It's all automatically transcribed and aggregated. And then we have skills in in in Claude that is like your your product spec skill. and we prompt We've designed it so that it's a conversation-based approach. So, just like you have maybe like a a manager or a peer reviewer on your spec, Claude will actually like interact with you and ask you for clarifying questions. So, for example, you know, what's the main goal here? What are the main Here are the Here are the trade-offs. Like, should we trade off this or that? Like, have you thought about this? Like, what is the intersection with that? It has all the context about what we're trying to do because it has all the other projects that we're building, and all of that is is is a notion. And so, it it it helps you you basically refine and and and get to an end state.
13:44 But, yes, we don't really talk about the spec itself. That's just a a step in the process. We talk about the actual product. And so, happy to happy to share a little bit of like how how fast we move in terms of prototypes and and and show you kind of what we're talking about here. >> Yeah, yeah. Please show us the skill and and you know, everything else. Yeah. >> Yeah, so let's let's go through like, you know, an example of this skill.
14:05 And then we'll talk we'll talk about the actual how we build. So, this is an example of of like, you know, cloud skill. Like, you know, folks should be pretty well versed in this in this in this world. Yeah, so, you know, product shaping defining like the role where I push for simplicity, surface trade-offs, surface questions. you know, key key to definition of the problem, you know, like looking up like you know, all the data that we have access to, do the actual research, look at different competitors, customer evidences. It has links to all these different things.
14:39 synthesize the the completion. Help me shape this question. So, you know, you know, present the the synthesis. Ask plenty questions around, you know, the forcing decisions, all the different principles that we have, and then like related skills. So, like, this is like a skill that you that that we we load up. And this is This was actually just built by by one of my PMs. other PMs actually have their own skills. We're trying to figure out like how we actually get to like one strong skill as part of like the the the the evaluation process, but this is one of the examples.
15:07 >> I want to share something. >> just have to So, you basically just like, "Hey, I want to build like some expense tracking feature." And then this thing actually drives a conversation, right? You actually drive the conversation with with you. Yeah. >> Exactly. >> Okay. >> And then let's go into like the build. So, so, so, you know, 50% of Ramp code is is built by AI and and that's 50% up from 30% in December. It'll probably be 80% by March and you know, it's it's not inconceivable for it to be like 90 to 100%.
15:37 >> Yeah. >> We've hit we've hit coding escape velocity and and and it's a brave new world out there. We the the question becomes like how do you make it easy for a non builder to engage with, you know, code cuz it's it's obviously pretty intimidating. So we invested a lot in in building our own visual on top of you know, any any large language model and to radically accelerate like how builders can build and how even like the PMs can build. I mean if you if you if you have like infinite coders at your disposal, you know, you are actually the bottleneck and you actually need to like start moving faster. So I'll give I'll give you an example. Let's say that you actually want to you have a lot of feedback from customers saying, "Hey, I need more visibility on what needs my attention and I need to understand kind of what's overdue, what's on track and like what's upcoming? So I need to understand like my accounts payable cash flow, okay?"
16:38 >> Yep. Yep. >> So all I need to do is I will go in and say, "Okay, please build me a report on top of this table that has four metrics. My overdue paint my overdue bills, my upcoming bills, 0 to 30 days, 30 to 90 days and the total amount outstanding that we'll need to pay. Okay? So this is obviously a shitty spec. This is just for demo purposes. But the but Inspect will go and it will actually implement this product.
17:13 And it will understand the task it needs to do. it'll actually plan, it'll understand the code base. you've already directed it exactly to where you actually need. and it also has access to our design component library, right? So, I don't need to teach it to design, you know, what a metric should look like, what a module should look like, what a click should look like. It it has all these components baked in. And so, it's actually able to just reuse a lot of our existing code to build this thing. And I actually did this yesterday for this demo purposes. So, yeah. You know, here here's here's like where where it gets to.
17:47 See if this is working. Boom. Wow. So, now now you have on top of the bills table your entire your entire metrics. what's past due, what's coming up, and the total to pay. And and this took 5 minutes. >> And and this is not just like a front-end prototype, right? This is like the real product? Or >> This is This is the real product. Back-end, front-end. and I mean, a lot of this is front-end code though, because I I didn't need to create more end points. Like like we already have all these end points. But, Inspect is able to do both front-end and back-end.
18:21 >> Dude, that's cuz I I've been using like, you know, Google AI Studio and stuff just to make prototypes, but that that's like pure front-end code. It's it's not you you can't actually push to prod. But, it sounds like >> and and it doesn't have context on your code base. It doesn't have You need to You need It doesn't look the same as your product. no, I mean, here I can I can literally now I can I I can go in and, you know, I have a PR and I can just submit it to the engineering team.
18:47 And we have an automatic PR review processes where, you know, a double-digit percentage of our PRs are automatically approved. So, PMs are shipping tons using Inspect. And so are designers, so are operators, so are like, you know, some some extent like account managers and and and sales people are also getting activated on on this on this piece. So, it's it's just a massive accelerant. And and the number one users are also engineers. engineers using Inspect. And and and here's the other crazy thing about about this technology that I want to share.
19:20 >> Yeah. >> So, you know, often times you you you have feedback. So, we we we we love feedback. We obsess over like customer feedback. We have you know, tons of Slack channels where people are just constantly posting things, right? >> Mhm. >> It's very overwhelming once you have, you know, the number of customers that we have. you know, this is an example of of a a UX channel. and you know, basic thing, right? Hey, like Treasury's a product should probably be case sensitive, right?
19:46 >> Yeah. >> at Inspect in the web repo side nav, change the following sentence. PR merged. Like like like this is just one and this is a very easy thing. >> Yeah. >> But like anything any question that you have, say you're an engineer, you say, "Where where do I get started?" There's an escalation, a problem. Like anytime there's an escalation on ramp, you know, AI takes the first step. It understands exactly what happened. It understands where in the code base. It creates the actual PR. And often times it ships it. Same thing with with support tickets. Anytime there's a support ticket that comes in where someone is confused, we have Inspect basically run through that and and and recommend changes and have the PR up and ready for like the PM or the product operator or even the engineer to review and ship it. Like the the speed at which we can move with these some of these things is like radical. And this is >> of have an AI to get the first first pass.
20:39 >> Yeah, yeah. >> First pass everything. >> Yep. >> Let me push back on that a little bit. If everyone in the company is shipping these PRs all day, how are you going to keep the product co-co-cohesive or like keep the quality bar high? >> A lot of the the PRs themselves are like quality of life improvements. >> >> we also, you know, within Inspect we have an understanding of like complexity and so we we do have a process by which we review things based on like the sheer amount of complexity that it has. and it does route to the right person based on, you know, whether this is like a big change on the product side or on the engineering side, etc. but we haven't we haven't yet gone to a a big problem. We also have a a pretty robust release process. So, once the PR is merged, like we will like slowly roll it out. And before any like major changes happen on the product that goes to the rest of our customers, we have an automated process by which, you know, I get involved or the directors of product get involved as well.
21:30 >> Okay, so so you have the typical like first like everyone in the company plays with it, and then, you know, if not if nothing breaks, you could beta users to play with it, and then you roll to all users? >> Yeah, exactly. So, we so we have we have dog fooding, alpha is like your your your customers that that are you know, as part of your research group. Beta is anyone that opted into the beta tier. We have about, you know, 10% of our customer base that's in the in the beta tier. So, you can launch very very quickly to beta, and then you track you track analytics on that. And then to go to from from beta to to GA, we basically you know, require it's for for large large announcements like not not really like this, you know, naming convention or anything like that.
22:07 >> Yeah. >> For any large feature that is material to to the customer, we basically have a review process that's fully automated. So, so because everything is, you know, you know, in in our databases, we have another bot, you know, ramp releases that creates a ramp release report. It it it it it pulls all the information of the context. It pulls you know, a preview of the actual product that we can use. it pulls from our our snowflake databases the impact this feature has had. it pulls from you know, any Slack channel the summary of all the work that was done.
22:39 and it it basically like, you know, synthesizes all the things that it also can create it can do work. So, to do release, you basically need, you know, help center article. Well, that it gets written automatically. You probably need like internal enablement of like what this feature is, how do you use it, why did we build it? It writes that automatically. You can also post in Slack. so yeah, that's a a bit of like how we how we speed up the process.
23:02 >> And when you review these like larger features, are you reviewing the actual product or you're reviewing cuz you know, like a lot of companies is just like the the PM writes some sort of document, right? And then it goes through like multiple rounds of reviews. And then And and and then you approve it and then and then they finally go build product. But like I don't know I don't think that's how it works at Ramp, right?
23:20 >> Yeah, I mean the the the the question is like what is what is my role in all of this now, right? And and and and I think you know, in the past my role was, well, you know, I'm the best at like the craft or I'm the best at like understanding what customers want or I'm the best at, you know, understanding the data. And that's no longer true. Like you have a super intelligent like platform that you can leverage. So yes, like I I I will try my best to look at the all the all the customer feedback, make sure that this is actually meeting the customer feedback.
23:49 I will look at the metrics and call on like this is not good enough or this is not big enough. That's something that is fairly subjective. I will like go into the product and test it out and play with it and like really just hone in on on on like what's working, what's not working. But I think the higher-level job for leaders now is based on your feedback, what broke down in the in the process? >> Mhm.
24:10 >> Right? So if if you caught a a poor user experience, >> Mhm. >> what broke down? What prompt failed? What skill failed? What design system failed? Because giving feedback to the person and so that they can just fix it, that's that's that's that's a >> Yeah. >> That's a one-time bandit. Right? The what you want to do is you want to figure out within the process what broke down and fix that process so the next time you never have that feedback again.
24:35 Like a classic example for me is like I've asked I've told the team 10 times the the call to action needs to be above the fold. >> Yeah. >> That's like you want to you want to you want to just you know, for 6 years of of of of AB testing, you want to increase conversion? It's a big button that's above the fold. That's it. And and and I've I've said that like 10 times or maybe 100 times.
24:59 But now it's part of our design create process, which is a fully automated a process in of itself. And so before before it gets to me, you know, within within our Figma prototypes, tho- those those those core concepts are actually fully integrated. >> Okay, got it. So okay, so you don't have to Yeah, you don't have to say the same thing over again. You can provide me with like high-level feedback or something. Yeah. >> My job is to automate my job.
25:21 That's and our all our jobs is to automate our jobs. >> Yeah. >> we can talk about what happens next, but yeah. >> And and how about the how about the cuz another thing that sucks up a lot of time is like this annual planning process of like oh I spend like a month to figure out what we're going to build for the year or like for the next three three years, right? Like how how how how do you guys manage that process? Or is there even like a like how far do you go how far are do you guys look on this stuff?
25:45 >> honestly, 3 months. >> Okay. >> We we we can only predict within 3 months now. And and by the way, like within 3 months you can do what you can do in 3 years now. So like 3 months is actually a really long time. >> Yeah. >> you know, planning planning for me is I think there's actually like three main objectives to to planning. One is actually aligning on strategy, which is much much more important. Like what problems are you focused on?
26:13 What are problems are you not focused on? And which customer segments are you going after? And and how are you thinking that we're going to win long-term? Like what is the the end state for this thing? So it's about trade-offs. And I think like the conversation should really be about trade-offs. The second thing that that is planning is good for is just having some level of commitment from the teams, right? some level of accountability. And the third is to have some baseline for sales to know what's coming.
26:41 for them when they when they when they when they talk to a customer and the customer asks, "Okay, like this is great, but you know, I I I I have a lot more needs when it comes to our international exposure. And the sales team needs some basic assets. And so that's that's that's that's the third kind of pillar. And that also is like fairly automated. So once the team kind of does, you know, their their backlog and their and their plan in Notion, we have an automatic like process that creates, you know, one-pagers and then it creates slides and content for the sales organization within our own branding guidelines. and then the sales team can essentially just like look at higher-level view of our road map to be able to sell effectively against it.
27:21 >> Wow, okay. And then you have all these like vision and like, you know, how we're going to win stuff. Obviously, AI can read read it and if something changes, you can just ask AI to update it. Is that Is that how it works? >> I mean, what what I ask AI to do is is to synthesize information. Like a lot of a lot of leadership time is about helicoptering between the nitty-gritty problems and then the higher-level like strategy and road map. And and and making sure that every level of the organization understands information at the bottom and information at the top.
27:53 Like how you communicate to the CEO and the board is very different than how you communicate to the director, is very different than how you communicate with the teams. And that LLMs are incredibly good at because So like the translation layer, right? When I'm in an all-hands meeting versus when I'm in a team meeting versus when I'm in a board room. Very very different. And so I I waste a lot less time on those things. >> Got it. Got it. Okay, great. Let's get to the key question then. I mean, you just mentioned that your job is to automate your job. I'm sure all your PMs feel the same way. And so So what's going to happen to the PM function? Do you do you do you think Do you think it's game over or like yeah, what's going on?
28:28 >> You know, it it it's it's funny like I was I was surprised by like what once you automate code, like the a lot of people concluded that PMs are it's like over for PMs. And and I and I was I thought to myself, it's it's over for the engineer. For most engineers. So maybe it's like a lot of engineers who are like, "I'm going to be a PM now." because the engineering function is is is has changed a lot. Now that obviously there's a there's a there's a ton of value for engineers because I think an engineer now is managing hundreds of thousands of agents and they can actually scale their impact.
29:01 but let's go back to the PM the PM role. Like a lot of what a lot there's a lot of bad PMs out there or badly trained PMs. I think that the way we've trained PMs in the past has been really really bad. And it we've trained them on stakeholder management. We've trained them on prioritization. We've trained them on communication. We've trained them on frameworks. And those are all outdated because code is free. And so like all that matters now is are we going in the right direction?
29:28 How fast can we go? And how do we remove bottlenecks? And how do we build a system by which like we can accelerate? And and and to do that I think PMs need to really rethink their skills. So like a lot of PMs join product management because it's a safe job. You know, they might not be good enough at the engineering task. They might not be good enough at the design task. But like they're really good at, you know, the the the consultanty I'm an ex-consultant. Like that's why I joined the the function. Like I understand the the customer. I can communicate to engineers. And I can like I can I can really I can I can I can somewhat facilitate decision-making. The the downside is that if you're a risk-averse PM, you're not going to change your ways. So I still see, you know, very high-performing PMs who are who don't get it. Who haven't yet adopted these these core skills. Who haven't changed the way that they're working. Because it's worked for them so so far in their career. They've been successful because of it. That is the biggest dangers that I'm seeing. And so I I think that the the role of the PM is going to shift. And I think it's going to shift in two directions.
30:26 PMs are going to become much more builders, right? Because code is free. So just like I showed like a a product, right? That I that I that I basically built in in in 5 minutes. it's going to require then like the iteration from the product very very quickly. And so I think I think the craft and the building is going to be like really really essential versus the spec. Like, you no longer have to write the spec anymore. You need to actually like be in the product itself.
30:52 >> Mhm. >> Now, an engineer a great product engineer can do that, and a great product designer can do that. The other path for product is is the business side. So, you know, what what engineers are and and designers often lack is an understanding of the context in which the business operates and what actually matters. And and how we're going to win long term. So, they're really really good at Maybe they're really good at building really good products. And so, give them that. And then the product team should be focused on like, "Okay, but now that we have this really good product, like how are we competing? How are we positioning? How are we distributing?
31:27 How are we monetizing? How are we actually using this to win and drive enterprise value?" And and and I think that, you know, even looking at OpenAI and Anthropic, like the the the it's a it's a it's a it's a decision of strategy. >> Yeah. >> they have different strategies. And and that's actually where where the PM should be should be really really focused is is the underlying way that we're going to win and play and playing that GM mindset. because because they're going to You're going to have a ton of builders that can that can build great products, that can iterate on customer feedback, that have all the context. You've built that system. So, now focus on like what actually no one can do, which is to make sure that the product you're building is going to have insane amount of value in the market and insane amount of value for your business.
32:07 >> And like a lot of PMs are just like stuck like I think I mentioned they are stuck in like cross-functional alignment meetings all day like back-to-back. So, like And I I I think it's like a company culture kind of thing, too, right? Like, do do you have do you make sure your PMs actually have time to build or is it sort of like do they have to get alignment from 10 people to ship anything? No, it doesn't seem like it doesn't seem like that that's the case.
32:25 >> Yeah. >> No, I mean, we've we've we've designed the organization so that we we do not have committees and we do not have sign-offs. You just need to prove that you've added value, and then you can go go for the raises. I I will say that like it's it's it's actually really really important for PMs to carve out time to build. And I say this not just PMs, but like managers. I I think that it's it's a really tough time to be a manager right now because you're managing a team whose skill set needs to change, and and you might not actually have that skill set. So, I I I I think that right now like going back to IC mode is is paramount. and and I've done this for myself where I say like, "Hey guys, like I'm going to be way less meetings. I'm going to be way less in one-on-ones, and I'm going to be like I'm just going to be adopting AI tools.
33:09 I'm going to be building and vibe coding and understanding what's working, what's not working so that I can be become a more educated because it's it's just this is just the beginning. I mean I mean the sheer amount of of changes that happen over the even the last like 3 months is is is profound, and I think if you're stuck in meetings, you're not going to you're not going to you're not going to be effective. So, definitely creating space for for work.
33:30 And and honestly, you know, that's also where nights and weekends come in, which is like this is the year that like you need to you need to really prioritize learning and growth because no one's going to do that for you. so yeah, it's it's going to be a wild ride. >> And and if if it's doing it the old way, like it comes going to die basically, right? If it's doing it the old the waterfall and all all this kind of stuff, it's not going to survive. Yeah.
33:53 Let's skip to talking about companies that are watching this, they want to become AI native like Ramp, like how you guys operate. Like how how do they go about like doing like, you know, building systems and that kind of stuff? Yeah. >> So, there isn't like one right way, but I'll I'll I'll share kind of what what we've done. and we've kind of like built built a framework around this. So, so we think about like being being AI proficient in like multiple levels, okay? The bottom level is like people who sometimes use ChatGPT, right? We'll call them like the L0, okay? The the level one is like people who build their custom GPTs, maybe they built a Notion agent, maybe they've built they've used like Claude code to like do some of these things, etc. Level Level two is people who are actually like fairly proficient. They they are they have been able to build an app that that automates part of their job.
34:44 They have been able to commit code or feedback to other people's work. And then level three is like the fundamental like systems builders, okay? And our job is to get everyone in the organization up the ladder. And the way we do that is as follows. The people who are still in L0, they they will most likely not be at the company because the fact is like you can you can you can tell them as much as possible. If you're not a self-starter and you don't have that growth mindset, like it's going to be very very hard to train to train you out. So so that's L0. The the L1s into L2s, L2s into L3s, and L3s like basically like influence and and the rest of the organization. And the way we do that is we have a lot of public channels around people sharing what they built. We've made it really really easy for anyone to adopt these things. So we've removed any constraints around access, around tokens, around budgets. We've we have like the setup of those tools are are extremely well done.
35:40 So you have access to all the different MCPs. You have access to all the different skills. We even have like an internal repository of skills that people are deploying to. You can pull from those. And then we have, you know, a lot of culture around, you know, in all hands around like showcasing non-builders doing things. You know, our finance team building their own treasury management system. Our legal team, you know, doing contract reviews. Our marketing teams automating like website creation.
36:06 To get people inspired. And then we have office hours that that people can join to to ask any questions to get set up. We have designated experts that people can just ping and like their entire job is to get to evangelize to get you set up to get you comfortable to get you going. those are like some of the the principles there. And then we we And then the other piece is just like, you know, hiring and performance management.
36:28 So, on the hiring front, we we now have an absolute requirement for anyone who joins the company to be somewhat proficient for these tools. There's just absolutely no excuses. And in the interview process, we'll have basically a dedicated session for this, where like they will either I mean for the product team, I literally have a session where you're going to build you're going to build a product. Like you're going to show me a product that you've built. And you're going to tell me exactly how why you built it and how you built it and how it works. Like it is a full-blown prototype. and then we also track usage of AI across the company. So, you know, we have we vibe coded this this this product even within the team where we can see everyone in the company and their full usage of tokens across Notion AI, ChatGPT, Cloud Code, Cloud Coworker, our inspect tools, our any of the internal apps. And we can see kind of like who is actually pushing the bar to amplify and who's not and who we need to intervene on.
37:22 >> Do you worry about like the cost of running out of control or like the ROI so clear that there's no it's just just give everyone access? Let them do it. Yeah. >> I mean I I I haven't done the ROI around like if you let's say you have a person who's who's has a hundred thousand dollars salary, how many how many tokens should this person use? And there's debates right now around, you know, you know, productivity versus just like noise and you don't actually need these things. I think right now we need to invest the budget for people to discover. And if we are not as efficient in that spend, that's okay. That's our competitive advantage. That's why we raised money.
37:59 That's why we have a pretty good war chest. >> Yeah. >> But I can safely say that, you know, we pay employees a lot of money and it and the the token consumption per employee is not even close to double digits. And I and I think it's I think it's not unreasonable to think that it should be higher than your salary. Because like if if you have agents that that are able to do 10 times more work than you, then why would you not pay them twice as much as you?
38:27 And so I I I think that's like the way that we should be really framing it. but but yeah, I would say like we're not really worried about costs. we're worried we're mainly worried around we have like the next X months or X years where AI has not yet fully one shot at a ramp platform. and and and we need to use that to our competitive advantage to to move as fast as possible. >> Yeah, and I feel like a lot of the internal tools that you showed me are also really good for ramp customers, right? You can just like, you know, pick that available for ramp customers.
38:58 >> 100%. >> Okay, last last last question, man. So so if I'm a you know, PM or builder, how should I think about my career these these these days? you know, like the old climb the ladder to VP or whatever, like is that still going to work or how should I think about being employable still? >> I would say I think that the where you should be optimizing is not management. It is being the best builder in the world. I would say that management is probably dead.
39:29 there's always going to be value in someone giving you feedback and coaching and and and and being your advocate and and being a team leader, but now is not the time to build that skill set. Now is the time to like be very very proficient in this new technology and to radically improve the the the way that you use it. and so I would say for for for all the PMs out there, you know, get really embedded in these tools. And that's why engineers are so good at at at, you know, understanding what AI is capable of cuz they live and breathe it. Like they they that's the first knowledge work that has been, you know, mostly automated with with with coding agents. But it's coming for everyone else. I mean, it's going to come for PMs, it's going to come for designers, it's going to come from for any any white collar job. And so I would say just get very very proficient in using these tools and ultimately like the the your career is about impact and right now the impact that you can have is to to you know, ship great products faster and move more metrics for for customers into the business. And so you know, create a lot of space to learn these things and and have the beginner's mindset, the humility to understand that the way you're doing things is not the best way.
40:42 And I think my job as a leader is is just to get people to to get to that aha moment. And even even my brightest PMs, I I had to sit down with them and say like we're going to go through this workflow together. What what what have you done today? And I will show you a new way of doing it. And once once you get that aha moment, that like red pill, there's no coming back. Like you like you you're like I oh I get it now. And it'll also make you a better builder because you're the software you're building, if you're in B2B and even in B2C, it is going to look radically different than than what exists today. I mean, fundamentally software is dead. It's all going to be like co-workers and if you haven't used co-workers in your own job, you don't understand how it like that actually might look like your product a lot more than you think, right?
41:25 >> Yeah, you don't have to process it. >> That's exactly right. Like they they the ramp itself is going to look much more like a finest co-worker than it does, you know, tables and charts and workflows. >> Yeah, I feel like it's it's all like you know, I've been using open client thing. It's all like CLIs and like you know, there's like no one wants to touch buttons anymore. It's just like Let me let me talk to my co-worker and let let you know, get him to do stuff for me.
41:47 So that's basically it. Yeah. Cool. >> And and and and how do you build one of those great co-workers? Domain level expertise is another one. Like I think that in the past it was like I'm going to talk to customers, I'm going to kind of understand the requirements and kind of build a product for them to do their job, right? >> Mhm. >> But if you're doing the job of your customers so that they can do other things, you need to you need to actually be an expert or you need to build a system by which you can ingest that expertise, right? So accounting, like you can build an accounting workflow where they have to go and code things, but if you're actually going to code on behalf of the accountant, you need to you need to deeply understand that the philosophy or be able to extract that knowledge. Like, how do you download, you know, CPA and all the best practices and actually bake that into your product? So, it's a very different way of thinking where fundamentally, like a login in your product in the future, I think it's going to be a failure, right? And I think that's also how we think about it. We we track the amount of time you spend in Ramp and how we can actually reduce that time as much as possible, which is, by the way, the opposite of how a many PMs are trained.
42:45 The the the Facebook and Netflix, right? The the FAANGs of the world that are that are mainly advertising businesses, like it is the opposite. And I think there's going to be a reckoning, for sure. But also a very exciting time. I mean, you know, I think it's very very scary and then a lot of people are alarmist and everyone should be paranoid. Yeah. But man, it's an amazing time to be building right now, and especially a product manager where you have taste and vision. The time it takes to go from your taste and vision to a product is shorter than ever, and I think it's really really really exciting time to be a builder here.
43:16 >> Yeah, and I think another thing you mentioned is just like setting up systems to delegate all the work to AI, right? So, you can focus on stuff that you actually enjoy doing. I think that's a key part of it. So, yeah. All right, Jeff. Well, I mean, thanks for being an inspiration, man. Like I I I I think hopefully well, ho- hopefully every company can learn how to operate like Ramp Ramp. Yeah. >> We're just getting started. There's also a lot of things that you know, we're not doing well that other companies are doing super super well. I think, you know, part of me going on this this talk is not to to share that we've that we have that we have all of it figured out.
43:48 Most of the things that you saw here are things that we built in the last months. so, excited to keep the conversation going, excited to continue learning, and you know, really really a privilege to to to be here today. Thanks a lot for for having me. >> Yeah, hi Jeff.