
Loading summary
A
Just this week I got asked to write a PRD about a new platform investment we wanted to make. After writing the doc 20 minutes, I was like, you know, this is boring. Like I want to build the thing.
B
ChatGPT's growth has become a global story. They crossed over 900 million weekly active users. It might be the fastest growing app ever to that number. It is a wild story and part of that story is their international growth story. Meet Abhi Muchal, a PM on international growth at OpenAI. In this episode he's going to show you how he uses Codex at work, how he has used it to help drive the growth and some of its latest features so that you can use it like a pro, not a beginner. I don't think there is a single piece of video on the Internet that actually shows how Open AI PMS work,
A
but with Codex there's now many examples where I have been able to take a feature to 70, 80% Most of humanity does not live in the US. Most of humanity does not live in the developed world. It lives in India, Latin America, Southeast Asia, and we care deeply about making sure that all the tools we build benefit those users.
B
If you stay till the end, you'll get to hear what his international growth PM role is actually like, as well as how being a PM at OpenAI is different from his prior roles. Foreign before we go any further, do me a favor and check that you are subscribed on YouTube and following on Apple and Spotify podcasts. And if you want to get access to amazing AI tools, check out my bundle where if you become an annual subscriber to my newsletter, you get a full year free of the paid plans of Mobin, Arise, Relay App, Dovetail, Linear Magic Patterns, Deep Sky, Reforge, Build, Descript, and Speechify. So be sure to check that out@buildle.akashg.com and now into today's episode. Today we're in for a treat. As you know, OpenAI is at the center of the AI revolution that has been affecting us all as PMs since they launched ChatGPT in 2023. What the team has done is pretty crazy and it's rare to get an AI inside look how an OpenAI PM actually works. In fact, I don't think there is a single piece of video anywhere on the Internet that actually shows how Open AI PMS work. Today we get the pleasure to sit down with ABHI Mutchal. He has been a PM at Meta. He has been a PM at Nubank. He has been a Head of product at Tenet as well. And now he is an international growth pm at OpenAI. He's going to open the covers like has never been done before, show his actual codec setup, show an actual app he built and uses inside OpenAI as a PM. So you're going to get to see how OpenAI PM's work, actual work products that they have, as well as learn about the PM job. If you stay till the end, you'll get to hear what his international growth PM role is actually like, how they've driven that international growth, as well as how being a PM at OpenAI is different from his prior roles. Abhi, welcome to the podcast.
A
Thanks for having me man. Followed your work for a long time. So super honored to be here.
B
Oh that means a lot. I really appreciate it. Sometimes as content creators we don't know how the work is landing with those at the frontier. And that's what I want to talk about today. In fact, where I want to start with is if anybody has been observing OpenAI at all, they have seen that in the last month or two, Sam has been talking about Codex, Codex, Codex, Codex. It seems like you guys have invested a lot of effort into Codex. Six months ago I told PMs Codex is the best way to use ChatGPT for their use cases. So what I want to understand is as someone inside OpenAI a PM inside OpenAI, what has Codex unlocked for your PM work?
A
Yeah, so I think taking a step back, when ChatGPT launched a few years ago, it started as a chatbot. Last year, as we added different tools to it, including connectors, it became a collaborator and with Codex it has truly become an agent. And what that means is I can give it parts of my job to do and it will do it end to end. And the meaningful differences for me there are I'm saving hours of my day, especially on repetitive tasks that I'm doing again and again. But also it is enabling me to do the things that I've never been able to do beforehand. So on the former, there is in a PM's life cycle, there's things that you have to do every week or every month, right? You have to maybe prepare for a review or write a weekly update or send a note to people on following up on things. All of that is automated by Codex. Now, in addition to that, I was never a great engineer myself. I studied computer science at Michigan, but haven't really been coding since then. And I always felt intimidated, especially with the caliber of engineers that are here, as to how I could Contribute. But with Codex, there's now many examples where I have been able to take a feature to 70, 80%. It's like, cool. I'm excited about this. Engineering does not have bandwidth. I'm just going to build it and I'm able to take it to 80% and then let the engineers take it from to the last final to the final mile. And that has been super empowering, both because I feel like I've turned from just a product manager to now also a builder. And I think it is inspiring to my team because it allows me to go from just writing docs to giving them functional prototypes about what we should be building.
B
What would you say is like the single highest leverage thing that Codex has enabled you to do? That wasn't possible before?
A
Absolutely. So I'd love to actually show you this, but before that, some context. So my job is at leading international growth involves thinking about how ChatGPT is growing around the world. We are many, many different countries. And as your audience would know, growth has many layers of the funnel. Right. We think about top of funnel acquisition, then activation, then engagement, then retention, then resurrection. We also think of competition. All of this information is in different dashboards at OpenAI. So me and my team would have to spend minutes and hours loading these different databricks dashboards, seven, eight different sources, trying to figure out how to synthesize this. It was crazy. I feel like we were just getting lost in the noise. A few weeks ago, as I was seeing other people starting to use codecs, I was like, you know what? What if I could build a dashboard that just one single web app that combines all these sources and then on top of that synthesizes what are the important elements? And voila. I was actually able to do it with Codux. So I want to show you a little bit. We can get a virtual drum roll. Let's see if this works. Okay, cool. Let's hope the demo gods are there. So what you're seeing on my screen is a version of this dashboard. Now, as much as I'd love to let you see the external data, the internal data, I've modified it a little bit so that you can see the structure without revealing any of the internal knowledge here. So what you see in this dashboard is basically the exact dashboard we use internally to think about international. Right? And at the top here, I've made up seven or eight countries that we can think through. Now, all of these are made up numbers, but you can see how these correspond to real life. So I can flip between different countries and see, okay, what is happening, what is like the top line metrics I care about, how are weekly actives doing, how is the penetration, how has it been growing from one thing to another? Then I can go one level deeper and Codex is categorized for me, what are the strengths and the risks. So here's the things that are going well and then relative to the rest of the world and other peer countries which Codex has figured out, what is the peer set for this country, what are the places we could be improving? And that gives me and my team a snapshot of here's the areas we should be focusing on or what is not trending well, we can go even deeper and do deep dives on, okay, here's how our market share is, here's how new user growth has been, here's how we're doing relative to other benchmarks and a little bit more detail. What is cool about this is that I can give someone an exact snapshot but then if they want to go deeper, they see all the relevant stats and how is comparing to competition and how it is comparing to our performance in other countries. And the final element that is awesome about this is that this is updated every single day through an automation at 9am every morning. So Codex runs it. I don't have to do anything. This has been a game changer for not only me, but for my entire team because now so many more people can look at this data in one place and are able to make better decisions about how we should be investing our time and what user problems we should be solving.
B
So I'll act as a skeptic here. This already lived in databricks. What is the unlock here? How should PMs be thinking about, okay, have some scattered dashboards. What's the generalized principle that people should be using codecs for?
A
Yeah, I think that the broader takeaway here is a lot of times, especially in working in growth, you're making decisions by looking at multiple different sources of information and there's a cognitive overload of trying to piece together how all these things fit together. So if it was just one databricks dashboard, I wouldn't have to do this. But because it's seven, eight different sources, all with different cadences and by the way, some of them are different tools. There's a tableau dashboard for two of these things. There's a databricks dash for six of these things. I was able to bring it together in one place and also provide the TLDR summary of what are the things that are important because that doesn't exist in a dashboard. So it's a combination of the synthesis and the takeaways that have really become a game changer for my work and my team's work.
B
Okay, so now I understand the value prop here. What we're doing is we're synthesizing data across multiple sources. We're leveraging LLMs and the connectors. If I wanted to build something like this myself, can you maybe just walk us through even if we can't see the end to end workflow, the steps, the prompts, what it would look like in Codex to end up with this type of a work product?
A
Yeah, absolutely. I'd love to show you. So I want to walk you through the journey that it took me to build it and hopefully this inspires others that you could do the same with codecs today.
B
Here's the dirty secret about prototyping. You spend two weeks building a prototype, you validate your assumptions, Engineering loves the direction, then what happens? You throw the whole thing away. Bolt changes this completely. When you prototype in Bolt, you're not building throwaway mock up, you're building real front end code that integrates with your existing design system. So when you hand it to engineering, they don't throw it away, they ship on top of what you've built. I use Bolt every single day. I host my land PM job cohort on it and honestly I'm up till 2am some days just vibing in the toll, having fun and building. That's when you know a product is good. When you're using it past midnight. Not because you need to, but because you want to. Check out Bold at Bold. New link in the show notes. I hope you're enjoying today's episode. Are you interested in becoming an AI product manager? Making hundreds of thousands of dollars more joining OpenAI and Anthropic, then you might want to do a course that I've taken myself. The AIPM certificate ran by OpenAI product leader McDad Jaffer. If you use my code and my link, you get a special discount on this course. It is a course that I highly recommend. We done a lot of collaborations together on things like AI product strategy, so check out our newsletter articles if you want to see the quality of the type of thinking you'll get. One of my frequent collaborators, Pavel Hearn is the Build Labs leader. So you're going to live build an AI product with Pavel's feedback if you take this AIPM certificate, so be sure to check that out. Be sure to use my code and my link in order to get a special discount. And now back into today's episode.
A
If you're able to see my screen here, I basically ask Codex, hey, I want to create a web app which shows how I monitor growth across key priority markets. With ChatGPT, the audience are internal stakeholders within OpenAI. Then I identified what I want the output to be. Here's the things that I care about. Let me switch between different tabs in different countries, as I showed you. Show me headline stats, highlight key strengths and weaknesses, and then have a red and green thing of what's going well and what's not. I'm a visual learner. I wanted to stand out. So that was the output. Then I said, here's the inputs. So I used a few different connectors and I was like, hey, the competition dashboard with Tableau, the exec dashboard in databricks and so on and so forth. And for this case, I just said, hey, since I want to demo to your audience, like, this is an external demo, so we're not using internal data. But I didn't do that when I was trying it out. But the key thing I want to highlight here was just to clarify to Codex, what are the inputs and what are the outputs? And then it sort of runs with it. So from that point forward, it went ahead and started building it. You can see that it was like thinking a bunch. It created a synthetic demo, added country tabs, added the views for the four sources of data. It had a few notes. And then the cool part is it ran a smoke test to validate that it was working itself without me even telling it or anything. So that's pretty cool. Then I was, okay, we've got something cooking here. How do I make sure that it's working well for me? So I said, run it on terminal locally and show it to me. So it spun it up on localhost, got a web free view. Great. Then I was like, all right, I opened it. But like, the background was like, not what I wanted. It was like too dark. I felt like it wasn't like on brand. So make the background like OpenAI.com let's stick to the brand that we have and test it with the fixes so it can. So I can see that it's working.
B
And so if people don't know playwright, it comes up a lot when you're AI coding. It basically is allowing Codex to see what it actually looks like to users. Right. It kind of takes like a screenshot almost of it so that it can see it.
A
Exactly, yeah. So Codex opens Up the web browser, it takes a screenshot, sends that information, or maybe it's a series of screenshots, sends that information back to Codex for it to self identify. What are the UI issues that have been there prior to being able to use tools like Playwright? I would have to go open the browser myself, be like, this net, this net, this net now it just made it much more seamless. But what's also cool is that since we've also now created a browser within codecs, so I can just see this preview right here. So I asked it to open the preview and I could see, okay, here's the things that are coming up. The brand colors look okay, the data looks okay. So without going anywhere else, I can just do an end to end workflow in Codex.
B
And I think this is a really important point for people because a lot of PMs, their sort of first entry point into AI tools was around February last year when they were told use bolt, use lovable. At this point, Codex is now able to build previews and show you previews directly in the app. So if you want, you can actually use Codex for prototyping. I'm curious, do you use codex for prototyping?
A
100%. Just this week I got asked to write a PRD about a new platform investment we wanted to make. After writing the doc for like 20 minutes, I was like, you know, this is boring. I just want to build like, I want to build the thing, right? So I built a prototype and then showed it to people. And that created a better discussion because I think everyone's a visual learner and wants to see what the end product looks like. And so I've moved away from writing PRDs to just creating prototypes.
B
Whoa, we gotta pause there. Because that's like the hottest topic in product management. You moved away from writing PRDs and just creating prototypes. I guess someone might say, hey, well the prd, you probably still need that to figure out what's your null hypothesis, what your success metrics and your guardrails are. Use it as a document for some stakeholder alignment and make sure that privacy and legal and compliance. And for you guys, probably the safety integrity Red team concept is all checked off on it. If you're just on prototype, how do you take over those key tasks of a prd?
A
Yeah, I think that maybe the key point I want to make is that the end output isn't the document, it's the product you're trying to build and that is conveyed with the prototype along with the prototype. What I would call I have, like a companion document that explains, here's what's happening. And it sort of plays a role of what you're talking about in a party. It's like a quick spec of here's the big. He's kind of like an faq. As you look at this prototype, you may have these 10 questions. Cool. And these are the 10 questions. And it sort of covers that. So, yes, I still have an accompanying document, but it is a companion. But the main show is the product itself, and that's what people are initially reacting to.
B
Okay, it makes a lot of sense. So you have been a PM in the pre AI era. So how would you compare and contrast? Like, let's rewind back to when you were at meta, for instance, versus now, what you're doing at OpenAI. Maybe you can walk us through the product development process and life cycle. Like, when does prototyping come in? What does it replace along the steps of product development?
A
Absolutely. So I think that pre AI era, the usual process was you started with a hypothesis, you collected some data, built some conviction, and then to convince everyone around you that this was worth doing, you wrote something like a SPAC or prd. Different companies have different names, which covered all the key elements of what needed to happen. After that, there was some internal alignment. Then you convinced the designer, hey, let's visualize this to people. Then you would work with a designer, do a few revs. Okay, this is what it looks like. Then you go talk to engineers, can we build this? Here's the things we iterate. And so I would say that a lot of the same thinking still needs to happen, but we're moving faster now because I, without needing to leverage valuable design or engineering time, able to start with, here's what I think this could look like. And obviously everyone knows I'm not a great engineer, I'm definitely not a good designer, so everyone takes it with a grain of salt. But here's I want you to react to something, and that shortcuts a lot of the steps that I was taking beforehand because I can show. Here's what I think this need can look like without having to waste designer engineering time. And then we're just talking about how we can build it or if this makes sense.
B
Got it. And at OpenAI, like you mentioned, you'd take the code to 80%. So would you be literally working off. Would your Codex instance be hooked up to the main GitHub and be working off the main code so it could use the real components and everything? And would you be shipping like a pull request or would you just kind of have like a local repo inside your local so that you could show them the 80% done. What are the mechanics of that?
A
Yeah, great question. So it depends on what the purpose is for what. I built this demo website that I just showed you all I was mostly using, working locally because it didn't need to integrate with the ChatGPT infra. It was something more for internal consumption. Right. But let's say there is like a new feature that I want to ship for users in India and I want to figure out how can I, in a very scrappy way, get people to understand what this might look like. In that case, I would actually use GitHub, pull from our broader repo with all the ChatGPT code base, then point it to. And this is the key part, point it to something similar that it should build upon. So the question I often ask my engineers is when I'm going down this rabbit hole of like, Avi's going to go build this thing, I'm like, hey, what's the most similar thing we have done to this? And they're like, oh yeah, this. Just look at this GitHub. So I take that, point that to Codex because then it knows here's the thing it needs to build on top of rather than spending a bunch of time navigating the code base. So I think that's the critical thing, is get a reference from an engineer of what is the most similar thing we've done. I do a few revs with codecs. I get to a point where I have a pull request out and then I go to engineers and be like, hey, help me understand if this is the best way to do this. Maybe there's something's failing in my merge. Can you help me out? And so it just accelerates that entire process.
B
Really helpful insight. Okay. Prototyping and dashboards, those seem like two major use cases for codecs. You talked about a couple of the other ones. Maybe you can just enumerate them for us into buckets. And what I'd also be interested in, as you enumerate that is what is it still not good at? Like, what are the honest limitations?
A
Yeah, so I'm going to start with talking a little bit about how I use codecs in work. But I also have some cool things. I could show how I use it in my personal life. That's interesting to your audience. So I would say in work, I put it into two buckets. There is the set of things I was Already doing but were repetitive tasks, updates, dashboard reviews, synthesis, preparing slides for a external or internal presentation, preparing slides for a deck for a presentation. I need to give all those things Codex is now doing end to end and the things of those that are repetitive. It is automating. All I do is point it to the right things and then there is like the net new stuff which I would call becoming a builder. And those are things I was not doing beforehand such as creating prototypes or creating dashboards. And Codex has sort of enabled me to do that. So that's on the work front. You want me to talk about the personal front as well?
B
So really quickly marinating on the work front for a little bit more because I want to open up a couple more layers there. What is like the operating system for a PM at OpenAI? Is it Slack or do you guys use a system like that? And does Codex help you with that?
A
Great question. So maybe I want to show you actually the great example that answers this. I want to show you a little bit of what are my automations every single day as you suggested. We live and breathe in Slack. We use Slack obsessively. I have not seen a company that is so addicted to Slack as we are. And it like all forms of communication including actually with some external partners. We brought them into Slack because we don't we just operate that way now every PM wakes up in the morning and especially with me. I work with people in different time zones and I'm just overwhelmed with like the amount of Slack notifications and pings and I inevitably miss something like that. I get like, you don't want to be the guy who's like gets a response, hey, I sent you that message three days ago. What happened? And like oh crap, I missed it like in all the Slack notice. So what I actually built is an automation which is my a daily Slack inbox triage for me. It looks at all the key channels I've told it. Here are the important people like hey, make sure if Akash sends me a message, tag that and tell me the things that I haven't read that I should read and tell me the things that I haven't responded to that I should respond. I get this once a day in the morning and that's how I start my day. So that's like a really cool automation that has saved my life. The other automation you see here is the dashboard that I showed you earlier. I've got this on an automation where every morning It's a daily 9:30am here's the automation that powers that dashboard, pulls all the data. And then finally I was talking about weekly updates, right? So we have to write a weekly update to our stakeholder group, talking about what's going well, what's not. How's that even this one pulls from a lot of data sources. A lot of it is in Slack, some in Google Drive, some in Notion, some from dashboards. So I've got an automation running that pulls all these things, puts it together, creates a weekly update and post it into Slack for me to review and send it out to everyone.
B
Wow, is there like an art? Because I've heard some people who connected to Slack and I think even sometimes I face this issue. Is there like an art to like giving it the right context to navigate Slack correctly? Like sometimes your decision to ship like a particular international growth feature might live inside the 38th message on a Slack thread where the legal team is like, yep, okay, now it's good to go. Is there any tips or tricks around the Codex Slack integration to make that really work?
A
Well, yeah, this is a good question. So like with anything when it comes to ChatGPT or Codex, context is king. And context does not only mean point it to these connectors, like use a Slack connector. It also doesn't only mean pointed to these Slack channels, it giving it information of what is the kinds of posts that it should index that are important. So anything, for example, I may say anything that talks about progress on evals or metrics is important. Anything that's like a net new learning, anything that's flagged as a blocker is an important thing. But connecting to a question you asked me earlier, I will be honest that I think this is one place where I don't think we're perfect yet. I still think that we struggle with the separation of signal to noise. And so this is why instead of asking Codex to just directly post the update to my stakeholders, I ask it to send a draft to me. And then oftentimes I'm like, okay, these three things totally made a ton of sense. This one thing, probably not that important, it missed this thing I should add. And then here's slightly different framing I'm going to change because I know that in a hallway conversation my boss asked me that she wanted me to cover this.
B
So that's one limitation. I'm curious, are there any other mistakes or things that you tried to do in Codex that maybe you're not doing any more that people could learn from? Just accelerate their learning curve with Codex?
A
I think another failure mode is regarding data sources so as you might imagine, pretty big product. We have a B2C business, we have a B2B business as well. And we have some data tables that look very similar but are very, very different. Right. You could talk about like weekly active users when it comes to consumer. You could talk about weekly active users when it comes to business and enterprise. And a failure mode is giving a very generic query to codec saying tell me about how weekly active user growth has changed. And that could be interpreted in many different ways which are all correct. And so I think that the thing that I've learned for now is that I need to be very precise with it about what is the kind of things I want and ideally point it to what dashboard. I still think that right now with an ambiguous prompt it won't be effective at getting the right data.
B
Awesome. And then final question on the work codec setup. Have you developed like Ryan Lopopolo wrote this amazing harness engineering piece that you guys had on your blog? For instance, what have you developed in your own personal PM harness for codecs? There's obviously this connectors component. Have you developed skills or a really deep agents MD file? What are those things within the harness that people should know about?
A
Yeah, great question. I think that one of the takeaways for me learning for me for the last three months is that for the longest time we as an industry talked all about the model. We also talked a little bit about the product and both of these continue to be important. But the big unlock has really been the Codex Harness because I think that is really what is powering a lot of what is being done today and is enabling me to pull from all these data sources to build these prototypes. I think the harness has truly been like a differentiator in terms of how I've used it. I'm going to give credit to some of my teammates because I think they've used it even better than I have. On any growth team you make decisions by running experiments and to make sure we're doing right by our users, we have a pretty rigorous experiment review process. Before you run an experiment, you write a quick doc explaining here's the hypothesis, here's the things you're trying to go for, Then you set it up on statsig, you run the experiment for a few days and then after that you need to write a postmortem of how it went, what do you recommend the decision to be and take it to a live meeting where we discuss the trade offs. Now what I describe here has a few different steps and a Few engineers on my team actually built a skill for growth engineers to do experiment reviews. So all you need to do is to point to the stat signal, it writes the hypothesis itself, it monitors how the experiment is going, updates it, and then whenever we feel like the engineer is ready to present an experiment review, provides a summary and comes up with recommendations and things that we should watch out for. So that's been an amazing skill that has really been a game changer for productivity for our team.
B
Awesome skill. And who is the right person to author that skill then? Is it like a product analytics expert that does like the owns that skill and creates it as a shared team resource?
A
I think the beautiful thing about Codex is that the person who cares the most is the one who makes the skill. It doesn't matter if it's an engineer, an analyst, or even a pm. I've made some skills as well. And so I think the person who feels like, hey, this would be a game changer in my workflow and this could help others, is the one who ships the skill.
B
Okay, so that's the work side of Codex. I'm really keen to hear how are you using Codex in your personal life and what are some mind blowing use cases we should be using it for?
A
Absolutely. So I gave you two examples. The first I want to show you, and the other one I can talk about. As you might expect, we're doing international growth. A lot of the people I'm talking To outside the US use WhatsApp, right? Day and night communications happens on WhatsApp, especially in countries like India and Brazil. And a lot of business communication and personal communication happens. So I have a large Indian family in a bunch of family WhatsApp groups. You wake up, you see like 1700 messages. You're not sure what's important, what's funny, whose birthday did I miss? Right? Just like I always get yelled at for not being good at those things. So recently with Codex, we came out with computer use. And the idea there was being able to enable Codex to see what else is happening on your computer, to give it the context to take actions. So I was like, you know what? I've got the WhatsApp desktop app on my computer and I'm going to show you this because this happened on my personal PC. Let me see if you can make sense of it for me. So as an example, I recently went to India, was bombarded by a bunch of messages. So Codex, I'm getting back from a day of travel. Catch me up on WhatsApp by looking at the desktop App and share. What are the most actionable things for me to take a look at? So it's taking the same mindset of what I do at work, but applying it to the personal life. In this example, it worked. It opened the app and then it realized that there's two actionable things. There's a client meeting, which is actually work related because I was doing that. But then there's a personal meeting. In this case, my friend Claire, who is in town and wants to meet but cannot do Saturday dinner. What are the times that would work? And that was awesome because, like, I would have probably missed these two things, right? So that's step one. But then I was like, hmm, could it even go further?
B
I used to think I had a retention problem. Turns out I had a messaging problem. I was sending the same onboarding emails to every new user, whether they activated on day one or never logged in again. I had no idea who was slipping or why. Customer IO changed that. Every message I send is now based on what users actually do in the product. Someone hits a key activation moment, they get nudged to the next. Someone goes quiet, they get a different path entirely. Their agent makes it fast. I describe the campaign I want and it builds the full journey. Form triggers, timing, copy, even branching logic. And when I want to know how something is performing, I just ask the agent directly and it tells me what to do next. They also have an MCP server, which means AI tools like Claude can see directly what's happening in your Customer IO workspace, Your segments, your customer data, your attribution, all of it. So instead of explaining your business context every time you need help, Claude already knows it. Notion. Use Customer IO to personalize their onboarding and hit nearly 50% open rate. Improved conversion by 6 to 7% with localized campaigns and pushed open rates up another 20% through AB testing. The idea is simple. Customer IO helps you deliver more impact from every message you send. If you're a PM or founder and your onboarding is still one size fits all, try Customer IO at Customer IO. I'm notoriously bad at my inboxes. I guess there's a version of that where I seem cool and unavailable, but the reality is I miss sponsor emails, guest pitches, and stuff that my team actually needs me for. So I got an AI assistant, the sponsor of today's episode, Ariso. Ariso connects to my email, calendar and Slack. Then I just chat with it over Slack and it helps me with everything. It builds workflows to respond to emails, resolve customer issues, prep me for meetings. It actually comes to my meetings, updates its own knowledge and remembers context from past conversations. So every time I talk to it, it already knows what I'm working on. I used to pay for Granola and Lindy separately. Ariso replaced both. One tool does more and it lives right in Slack where I already work. Check it out at Ariso. AI Akash that's a R I S O A I A A K a S H Today's episode is brought to you by Jira Product Discovery. If you're like most product managers, you're probably in Jira tracking tickets and managing the backlog. But what about everything that happens before delivery? Jira Product Discovery helps you move your discovery, prioritization and even roadmapping work out of spreadsheets and into a purpose built tool designed for product teams. Capture insights, prioritize what matters and create roadmaps you can easily tailor for any audience. And because it's built to work with Jira, everything stays connected from idea to delivery. Used by product teams at Canva, deliveroo and even the Economist. Check out why and try it for free today at atlassian.com product discovery that's a T L-A-S-S I-A N.com product discovery Jira product Discovery Build the Right things
A
Instead of just summarizing and reading things, could it take actions for me? And I was honestly not sure how this is going to work, but let's try it out. So in the first example, this client has said, hey, I want to meet up what days and times work best. So what's the normal process? You have to go look at the calendar, figure out what times work, figure out what the slots are. You have to read the message. Since it's a little formal, you got to respond in the right way. Acknowledging it that takes a lot time of of time. So I was like, why don't I throw Codex at this problem? I asked at the beginning. Codex computer use respond to the message from client A and WhatsApp desktop app by acknowledging what they sent. Then offer times available tomorrow afternoon by looking at Google Calendar. Then open the WhatsApp app and send the message. So here's a couple things that are happening right? It's ingesting the information from WhatsApp. Then it's looking at Google Calendar, which I've also synced with as a connector and this is my personal calendar to see what are the times available. Also my work calendar summarizing both then opening the WhatsApp app and sending a message. So I'm going to show you a little bit of how this happens. You can see it's looking at WhatsApp. You can see it's trying to understand what's going on. Then it's saying, I'll place the draft in the composer for you. So instead of sending it itself, it realizes that it might be something I want to vet to make sure I don't send something. That's crazy. It's typing the text, thanks for the Follow up. In WhatsApp, it tells me that the draft is ready, it opens it up for me to see it, and then all I have to do is press send. So that's like, honestly a game changer that I was able to do that. And it was able to do it in a way where it gave me enough control to understand where I might need to intervene, open up the app, and all I need to do is press send and edit. So that was really cool.
B
Wow. And I think that one of the things with AI is that we only decide keep pushing the latest models and latest feature toolkit to see what's possible. Many of us probably tried something like this six, seven months ago. The computer use was very lossy. It took like five, six minutes. I think the most mind blowing thing for me in that demo was that it just took a minute and eight seconds. Like, you guys have really sped up the computer use and so what's possible now is so much greater.
A
Yeah, absolutely. I agree. And I think that even for me working within OpenAI, it's hard for me to keep a track of everything that's launching. Like yesterday we launched the ability for you to use it seamlessly with Google Chrome. And so I think that a key thing for PMs who are probably inundated with all the AI news is to try to set aside maybe sometime in your week, maybe 30 minutes. And you can actually use Codex to help with this. Like, tell Codex, hey, like, what's going on in the world of AI that might be relevant to me. Tell me the two, three things I should try out and then try it again. And a lot of times you'll still see that it doesn't work. And that's okay. But what I've learned from this is that the things that are today almost work but don't are definitely getting solved soon. And so that's like the signal of where there is value coming in the future. Yeah.
B
One of my favorite prompts now that Codix can do this is say, analyze all my past chats, look up all the latest features. What new features should I be Using from how I use you. And it seems like it's able to incorporate all that knowledge now where it wasn't able to before.
A
Absolutely. I think this is something we've focused on with both codecs and stat. Chat is like model self knowledge. It's like helping the tool understand what it is capable of, which is a really interesting recursive problem. By doing that, it can help you onboard to the tool, you can come to it. And like I've never used Codex before. Here's what I do. Help me understand what I could be using, what are the skills that would be relevant. So I think that's super powerful and it's a great suggestion.
B
Is there anything else in people's personal lives that they should be using Codex for that they might not be using it for right now?
A
So I have a funny example for you. I'm not going to say I recommend it to others, but every year, like just a few weeks ago, you have to file taxes. Last year I switched jobs and I was like, you know, like I work with this accountant and I think the accountant is great. But what if I could just do it myself, right? Like, what if I could just like get it working end to end? And so if you go to ChatGPT today and you ask ChatGPT to file your taxes, it will give you advice, but it won't create the end to end output of a 1040. So I was like, you know what? I get why chat doesn't let you do that. Get it? It's like risky. But what if I could build a web app? So over the last few months I built a 1040 filing web app, which what it does is it takes as input all your tax documents and then spits out an output. Not just the analysis, but a full 1040 that you can submit to the IRS. All you need to do is sign it. I was so cautious though. I was like, you know, like this is still new technology. This is tax return. This is like Uncle Sam. I don't want to screw it up. So I did this and then I also had my accountant do my taxes and then I did like an a B test comparison. And I was like, huh? Like the accountant is saying my refund is much higher. This like doesn't make sense. So I sent it my accountant what Codex did and he's like oh crap, I forgot one income source. And I was like, oh my God. That was like a mind blowing moment that like this Codex agent which has no knowledge of accounting practices was able to spot out a mistake in my. What my accountant did. So I'm still planning on using my accountant for liability purposes, but the fact that I was able to do this was. Was insane. So I think anyone could do that.
B
Yes. I also used it to check my accountant's work in this latest tax cycle. So I highly recommend that for people. Everybody though what the kind of the red alarm going off when we tell them that is like, how do I do this safely? So how exactly do you feed sensitive information into an AI model while maintaining peace of mind?
A
Yeah. So I think there's two elements to safety that people think about. First is regarding data and the second is probably regarding control. My sense is that the data element there's known solves for like if you turn training off, you delete that chat, it won't be in your memory. If you use an enterprise account with us, it comes with a lot of other protections that enables you to securely use enterprise data. So I think those elements have existed and will continue to harden. But I think the other element is about control. I think in this open claw era, everyone's seen those threads on Twitter where it's like, oh my God, openclaw went and deleted something for me, right? I have a lot of respect in what the team has built here with Codex because you can ask, there's like different levels of permission. You can say, I want to review every action to completely. Like I want you to just run with it and find the right steps in between. And so that's pretty awesome. And what that enables is that every time it's connecting to a new data source, it's pulling something on your laptop, it can ask you for permission. Then in my prompts also I usually tell it, here's where I want to give feedback. I want you to get it to WhatsApp and before you send the message, give feedback. I think establishing that control relationship is really important and that's what helped me use it well.
B
So we just walked you guys through how an OpenAI PM uses Codex in his work and his personal life. Now I need to learn more ABHI about your PM job specifically because you've already given us a couple really interesting hints. It's on international growth and I've been on this personal agenda myself of kind of like getting rid of this term aipm. I feel like it's too umbrella. I feel like realistically there are many different types of AIPMs. So maybe can you help me understand your own personal taxonomy of AIPM and what type of AIPM you are within that?
A
To the Broader question, I think every PM needs to be an AI pm. That's what this new era is enabling. To be able to operate at the velocity that people do today. You need to use AI tools. And so I think that any product manager needs to be an AI product manager. And whether that means using it just to do parts of your job or using it to build things and push the frontier, that's kind of up to you. As far as my role, I'll start with like one click up. Like, our mission statement is to make sure that AGI benefits all of humanity. Most of humanity does not live in the us. Most of humanity does not live in the developed world. It lives in India, Latin America, Southeast Asia and all these other countries. And we care deeply about making sure that all the tools we build benefit those users. I think that the job I have is to figure out how we can be continuously providing value to users outside the world that are outside the Silicon Valley tech bubble. We have grown a ton since we've launched ChatGPT. A lot of that growth has come from places like India. Like India is one of our fastest growing and now our second largest market. And so my job is to think about three layers of the stack. One, how do we improve our models, how do we improve our product to surface relevant use cases and then top of funnel? How do we tell the story of what ChatGPT could be doing or Codex could be doing for you?
B
The traditional sort of growth and core split is that within core PMs will own specific application surface areas. I imagine at OpenAI there's also just the entire research model arm of product. So there's like research and then apps and then within apps is it like there's core teams that own specific features and growth sits kind of cross cutting and you specifically are focused on the international part of it or how is that structured?
A
Yeah, I think that generally we are still an extremely scrappy company and we have way more to do than we have people to do it. And it just comes down to like, what do you care about? And people are very willing for you to drive that end to end. And so I think that the org structure and boundaries are more loose and more of a suggestion than a hard boundary. That said, we do try to follow the similar structure where growth sort of is cutting across the work that is happening across the core app across different features and trying to figure out how we drive value. And my specific angle is what are the unique pieces of value that people around the world might have that we maybe we're not thinking about day to day. Right. And maybe our audience is not thinking about day to day that we can think about. And that is at the model layer, the product layer, as well as the top of funnel marketing and partnerships layer.
B
Makes sense. So if we broadly think about, okay, you guys did this mind blowing thing. You guys hit 900 million weekly active users probably faster than anybody else ever. There's going to be a lot of components that drove that growth, both from other PMs and yourself and those PMs in the growth org. Maybe can you walk us through what have been from like a product point of view, the most important things for that growth and what people really want to know is like what. Which were the ones that the growth team drove within that.
A
Yeah. So I'll start by saying that like most of the growth and the credit that I would give for what has happened is not because of me, it's not because of my only team, is because the amazing work that the rest of OpenAI is doing. And I would say my job is to sort of channel that and to help help ground the work that they're doing in real life. User problems that may be outside the US I think the narrative arc of ChatGPT is that a few years ago when it launched, it was really a chatbot tool. And I would say that it was used widely. But specifically we had sort of, I would call like early product market fit in two segments. One was knowledge workers. So people like you and I. And the other element was students. Right. Now what is interesting here as you think about it, and this is research done by ChatGPT. So quoting ChatGPT stats, when you think about a country like Germany, about 60% of adults that have Internet access are knowledge workers. If you think about a country like the US somewhere like 40 to 50%. So great in those places if we want to grow, like catering to students and knowledge workers covers a lot of what we want to do. But when I joined here, one of the things I looked at is like, okay, how does that differ for like India or Brazil? So In Brazil, only 10 to 20% of the working population are actually knowledge workers. In India it's lower than 10%. And so the thing I started thinking about is like these are all people that have jobs, they're adults, but they're not sitting day to day looking at a computer. Right. That's not what their work entails. Maybe they're trading goods, maybe they're running a small business. Maybe work is happening on WhatsApp. And so what are the use cases that can drive value to them. So in 2024, one step change for us was launching search. Right. I think beforehand, if you remember early ChatGPT, it was like an arbitrary knowledge cutoff where it was like, sorry, I don't remember things past this date, which made it hard to do simple queries about how do I get to work, what are the things I should be looking at? Right. These are the kinds of things that matter to a larger the world that are not just knowledge workers. So launching search was one step change and the other one was hands down image gen. When you think about how people interact with technology, a lot of people are not spending time typing and reading a lot of text. It's multimodal. They're talking, they're calling, they're viewing videos, they're viewing content. And image generation was our first breakthrough moment in that, in that vein where we provided the rest of the world that wasn't a knowledge worker, a obvious way to experience the benefits of AI without having to be steeped in reading three paragraphs of text. And it was so visually different than anything that had been done beforehand. And that's what led to like you know, a breakout moment for ChatGPT last year. And it's continued this year as we've launched Imagen to Images 2, which I can talk a little bit about as well.
B
Yeah, we've had this recurring theme throughout this pod about figuring out what are the latest and greatest capabilities of the latest models. And Image two is like the biggest elo jump of any model. Like if you look at 1 versus 2, you look at Gemini Nanobanana 2, Gemini Pro 3, whatever you want to call that model versus image 2 that you guys just released, it's like insane jump way bigger than the jumps between 2, 3 and 4. So can you show us what is just recently become possible with the Imagen model?
A
Yeah, absolutely. I'm going to show you a few examples so you can see like how amazing it is. But I just want to start by saying huge kudos to our research team that work day and night, like when I saw that El Amarina chart, I was also stunned. Like I've never seen such a step change improvement and I can viscerally feel it when I use the product because I use Imagen every day. Been using it for months and like it has been such a game changer. Why don't we do this? I'm going to share my screen, I'm going to show you like an example of something that what I tried doing Beforehand it would not work. And then while that's loading, we'll talk you a little bit through like what are the things that have we have focused on to make this model amazing? Here's an example of something that when I tried in the past did not work. So here I do a lot of user research to people in the field and this is a prompt that I learned from someone who was in Bangalore, wanted to open a bookstore and wanted to imagine what this bookstore would look like. And specifically they wanted to have an image of book titles in multiple different Indian languages. If you know anything about India, the language changes like every hundred kilometers there. And so you have to think about Hindi, Bengali, Marathi, et cetera and put these titles on books. Now the first image and model struggled with this character rendering, especially in different languages is very difficult. Plus we want to make it really realistic. We don't want to make it feel like AI. So why don't we give a stab at what this new model does. Okay, so it's going to take a few seconds to run in that time. I want to talk to you a little bit of like from our exact blog post, which I love. And it was like image forward, like what are the things we worked on? So first we've worked on providing greater precision and control. Every time you create an image, you probably don't single shot the final output. You want to edit and provide profine grain ideas of. Here's what I want you to change here. It's kind of what you might do on a figma file and with Imagen we've now allowed you to do that. Right. It's able to do these fine grain edits to take something that was fun to being workout. So that's pretty awesome. We've also allowed you to make multiple images at once and so that tells a story. And the thing that I spend a lot of time with the team working on and I care deeply about in Mission Align is working better at different languages. So this is one of my favorite examples. This is a Japanese manga comic and this example brings together some of the amazing things we've done here. So first, in prior versions of the model we would never get the character rendering right. It would either not be in the right characters or mixing up languages. And while I can't speak Japanese, I don't know if you can. It is able to get all the characters correct and it is able to point out what are the things, what is happening in the story one place and another in a random cool fashion. And you can see the level of detail here in the image outputs is so real and it's stitching together multiple images at once. So that's like an incredible example of how it is able to do this. Now let's switch back for a second and let's see if my prompt worked.
B
And I think you guys also got the character consistency a lot better now too. Like we saw in that manga that it was the same guy, like a different guy across the frames.
A
Exactly, exactly. Yeah, that's definitely something that would be the best. So what you see here, which is really cool, is that is imagine this bookstore actually in the book format itself and it's talked about like the stories across multiple different languages. Like you have all these different states of India that are represented here, so Kerala, Himachal Pradesh, Assam, all of the different languages. And the rendering for each of these, to my knowledge, looks pretty spectacular. But then if you zoom out, this looks like something that is actually in a high definition image that was taken of an actual book. Yet in the 30 seconds that I was showing you something else, ChatGPT just made that. So that's just been like mind blowing. And then for those who are, you know, pro image creators, what you can do is you can switch from instant to thinking. And that enables a model to like even up, up its game on top of a very high bar, have more realistic outputs, provide high definition images. So that's what my pro tip would be to all the image creators out there.
B
Okay, so at least one key tip is use thinking. And in my personal use of it, I feel like what it's doing is it's like taking my prompt, understanding what is my actual goal, and basically like writing like a better prompt. That's how I've interpreted it. What are the other things one needs to know if they're about to go heavy into Imagen? What are the limitations? Can I use this for charts in my upcoming product review or is it still getting axes wrong? What can't. Where should I be pushing the boundaries of usage for imagen?
A
Yeah, great question. So one pro tip, first of all, if you want to describe edits, you can click this edit button and that opens up different options. So you can say, hey, I want this ratio of an image, right? So that's pretty cool because a lot of times you got to edit it for a specific format. If you're uploading it to Instagram, you can also select different areas of the image. And let's say I just specifically don't like this part part, you can highlight it now and Say Imagen, everything else is good but this part of the image I'd like you to edit. So that's like a pretty, pretty cool example and why once again it's going from using this images for fun to actually using it for work. And then to your other question, what are the breakout use cases for Imagen? And we've seen this especially in countries like Japan has been infographics. What we noticed even prior to us building the model was a lot of people were trying to use Japan and East Asia creating infographics that would share on social media. So how is Japanese growth been like what is happening one place or another? And what Imagen does is it is able to provide create studio level outputs. So that's like an amazing thing. I still think that the place that I know that we'll continue improving is steerability. So allowing users to say I want you to change this specific thing but keep everything else the same. We've made a lot of improvements in that both in the product and the model. But it's something that is not still not perfect and I expect us to continue improving.
B
Okay, I cannot emphasize for you guys enough too if you haven't yet used the latest image model. I'm literally using it multiple times a day and my biggest use case is charts. Like it's, it's finally good at those. I feel like all the other AI tools that I'd been using like they would do random things like just use out of scale chart or something like that. So feels like it's really crossed over something. It almost feels like to me and I'm curious if you felt this way by the way, that like somewhere around December of last year the coding models and codecs got really good. And it feels like right now with image two, like in April we the
A
images got really good, 100% I think that it was truly a step change and the evals show this. But sometimes evals are maybe disconnected from reality. But this time I can see that every single use case that I was trying before has just gotten better. It becomes so much more realistic. The edits are so much more precise. The model is able to search in the web the real time and look at what's going on and bring that information into it rather than using a knowledge cutoff from the prior part. And so I think we've really made a step change improvement there. Whereas is why I encourage not only people who want to use images for fun, which is awesome, but also small businesses and creators, people who can't afford working with an entire agency or hiring someone full time to do this, that Imagen can get you like beforehand maybe 30% of the way today I think it can get you 90% of the way.
B
Yeah. And I can't afford creators and designers and sadly I've had to let some of them go. Because the difference between Imagen is that it can make a full change for you in two minutes. Right. And so your iteration speed gets really, really high versus when you worked with your designer. A lot of times you'd send that message to them, they have to prioritize that work, then they'd have to do it. So there's always going to be a couple hours of lag there. Imagen is like instant, which is just crazy.
A
What has been. I'm curious, but this is useful feedback to our team. What has been your favorite use case of Imagen so far?
B
So what I do is I tell it build a chart that looks like it could have been in the Economist or Bloomberg, a very high quality financial paper of this recent data and make sure that this data is up to date. And like you said, number one, it'll go find the updated version of the data. So like there's this very famous chart of how the price of goods has gone in America and TVs have gone down and university has gone up. It was able to go find the extension of that data for 2026 for me and I was able to make it look like beautiful journalist quality. So that has been the breakthrough for me.
A
Super cool. While we were talking, I tried another use case. I just want to show you very quickly. So I recently went to Tokyo for work and while all the business meters were happening, I tried to sneak out and maybe spend four or five hours just like absorbing the city and the culture and a lot about like the Meiji dynasty and how it was powerful to the history of Tokyo and Japan. So I asked Imagent as we were talking right now and he was thinking, tell me about Tokyo's relationship with the Meiji dynasty in the Japanese language infographic that's relevant to that audience. And what's really cool is it went and searched for this information as we were talking on the web, looked at the history of the Meiji dynasty and I didn't want to make it something that was like a tourist would be impressed with. I wanted to make it something a local would be impressed with. So it shows the history of the Meiji dynasty over the period of time. So this is just like mind blowing. And when I showed this to people in Japan, they were stunned. So that was like a big moment for me because I felt so proud of the work that we've done.
B
We've walked through Codex, we've walked through Imagen. In my mind, those are the two things you guys really need to be trying. Now I want to unpack for a little bit. PM@OpenAI. So you've been a PM@ Nubank, you've been head of product at Tennant, you were also a PM at Meta. What is fundamentally the difference working as a PM at a Frontier Lab?
A
Yeah, a couple of things. First, I would say that in some ways the model is the product, right? The core thing we're building is the model and we build the product on top of it. The crazy thing about the model is that it is so general product purpose. It can do so many different things. Also, the amazing thing is no one exactly knows what the next model is going to be. Even we don't. Right. We have a hypothesis of what's coming, but we're not sure. We have things we're trying to improve on. But there are always behaviors when we put it out to the world that people use that we didn't even expect. And we've seen this with not only image, but also text and our voice models as well. And so I think the key difference is that you operate in such an ambiguous environment where so many things could be changing and you have to be like your roadmap has to be extremely dynamic and flexible and receptive to what are the improvements that the research team is making. When we put something out there to the world and we give it to beta testers, what is Akash seeing? Maybe I should be highlighting that in the product. Right. And so I think that's like the big change is that it is extremely fluid, but in a good way because we want to adapt to where the research is going.
B
So if I am a PM at a regular company and I have it in my mind that I would love to break into OpenAI, what are the things that I need to be upskilling learning? There's just too much noise out there. AI news is a category we just talked about. You can use Codex to help you digest AI news, but there's also AI fundamentals. And some people are telling me I need to learn how to vibe engineer. Other people are telling me I need to understand rag and fine tuning. What is the truth? What do I actually need to know as a PM on AI topics? What are the AI topics I need to understand?
A
So I'll say that first as a comfort to Your audience. A lot of the core PM skills still matter at OpenAI, right? Structured thinking, analytical thinking, communication, telling, storytelling. That matters wherever you go. But I would say I'll add two things. First is I think it's important that you're living and breathing AI. You're using AI tools to do your work and even outside of your work, so you're understanding where what the frontier is today and where it's going. The second thing I would say is that the currency of progress, especially in a frontier lab, is evals. You've probably heard this term being used a ton. But anytime we think about a problem that we want to get our researchers excited to improve, the question they ask is, can we build an eval? And simply what an eval is is a way of rubric which helps us understand for a specific problem, how do we measure progress? What are the types of scenarios that we want to test? What are the expected output we want to have? And then we look at where we're today and we set a goal of where we want to be and we work with research to help climb on that. So I think speaking the language of evals is like another key skill for all PMs.
B
I can already see the pitchforks out because I have had enough comments to my evals articles and evals episodes. What is the actual level of depth that a PM needs to go on evals? What do they actually. Where is the line between okay, this is what the PM is doing and they speak the language versus this is the research team taking it over?
A
I would say that the roles are quite fluid and there's different PM archetypes here and different people who spike in different things. There are some PMs who are working very closely with researchers co embedded with them and they're going the entire way. They're coming with a hypothesis, they're writing the eval, they're running the eval, so end to end workflows, and then there's others who may be a little less involved and are basically helping research understand. Here's the problems we want to solve and working with them to figure out. How do we go from that to an eval that maybe research is driving? So it's a little flexible depending on where you're working on. I wouldn't say that you need to come in and be an end to end expert, not having run many of these, but I think you understand the value of it and what it's trying to achieve.
B
Can you tell us your story? I've been collecting you're now the fourth person I've had in OpenAI, I've been collecting the stories of how you all have broken. Because if when I ask my audience, hey, where do you guys Want to work? OpenAI always ranks first. So we always want to hear the actual personal stories of how you guys broke into this hottest company in the world.
A
Yeah, I consider myself lucky. Every day I pinch myself. Everyone here is like, definitely way smarter than me. So I think it's like astounding that I even got here. You know, thankful to those who took a bet on me. But if you take a step back, I think my the through line through my career is trying to figure out how we take technology to the next billion people. I grew up in India, spent a lot of my childhood there and I was always trying to figure out how we can build technology that helps people like that. After that, I started, you know, when I started working, worked at Meta and one of the things I did was actually work on the election Integrity team that was starting to stop misinformation around elections around the world. So Brazil, India, eu, Africa. And so that's like when I first started interacting with this at work and the bug kicked in and then I heard about this like crazy company in Sao Paulo, Brazil called nubank, which was then a growth state startup. And they reached out and were like, hey, would you like to come work here? And it was a wild thing in 2019 to consider that. But I packed up my bags and was ready to move to Brazil. I spent some of that time working remotely from the US because of COVID But then I went there, I learned Portuguese, I worked in our Brazil business, our Mexico business and our Columbia business just hopping around. And so this is like a through line through my career. And so when OpenAI was starting to think about this international role, I think that I had thought about these problems for a while and in fact was building a early prototype company around trying to solve real time language translation. At my previous job, some people spoke Portuguese, some spoke English, spoke Spanish, but no one spoke all of them. It was like a big chaos at work. So I was like, okay, let me just build a chrome extension on top of OpenAI APIs that would help solve this problem. And so I sort of got in touch with the team, was building and I think a combination of my experience and then the builder attitude is what led me to be here.
B
Okay, so the ingredients are really coming together now, which is obviously world class experience at two amazing companies, Meta and NuBink, training you on the fundamentals of PM and specifically international growth. So you have that extremely strong career base. Obviously you're going to be top of your field there. But then the other component, which I think probably some people are missing and now they hear validated from your story is you went out and you actually built a AI product.
A
Yeah, 100%. And I think that the latter is important not only from the perspective of a resume or an application, but for your own skill set and learning. When I started building, I started realizing what can work, what cannot work. I needed to create. I didn't even know this word then, but I need to create evals myself. Like the translation thing wasn't working, so we had to create like a rubric. And so as I got into the interview process, I was like, okay, a lot of the things that we're talking about now, I haven't done it to this standard, but I have understand operationally. And so that really helped.
B
I could talk to you for another hour, 2, 3, 4. But thank you so, so much for opening yourself up for this time, sharing so much information. I have not gotten these insights after talking to so many people. So thank you so much.
A
Yeah, thanks for having me, Akash. And the final note, like, I think I went to Michigan like you and when I was there like 10 years ago, there weren't that many people in the product management industry. So I remember when I started learning about it, I like looked at you on LinkedIn. So it's funny, like a decade later, full circle, being able to talk to you in this format. So thanks for all the help that you do for everyone who's interested in product and growth.
B
Oh, thank you. If people want to find you online, where should they find you online?
A
Yeah, LinkedIn is probably the best place. Not a big Twitter person yet, but LinkedIn and my name is the same as my handle.
B
All right, guys, if you guys are working on international AI products, you don't know the person who's responsible for international growth. Until the next episode. We'll see you later. I hope you enjoyed that episode. If you could take a moment to double check that you have followed on Apple and Spotify podcasts, subscribed on YouTube, left a rating or review on Apple or Spotify, and commented on YouTube. All these things will help the algorithm distribute the show to more and more people. As we distribute the show to more people, we can grow the show, improve the quality of the content and the production to get you better insights to stay ahead in your career. Finally, do check out my bundle@buildle.akashtri.com to get access to nine AI products for an entire year for free. This includes Dovetail, Mobin, Linear Reforge, Build, descript, and many other amazing tools that will help you as an AI product manager or builder succeed. I'll see you in the next episode.
Episode: How to Use Codex Like an OpenAI PM | Abhi Muchhal, PM OpenAI (ex-Meta and Nubank)
Host: Aakash Gupta
Date: June 3, 2026
Guest: Abhi Muchhal (Product Manager for International Growth @ OpenAI)
In this episode, Aakash Gupta sits down with Abhi Muchhal, a product manager at OpenAI leading international growth, to discuss how PMs can supercharge their workflow using Codex and stay at the frontier of AI product management. Abhi gives a deep dive into actual PM workflows inside OpenAI, showcases how he automates and builds with Codex, and shares actionable insights on both professional and personal use cases—including real demos and strategies for bridging global markets. If you want to move beyond mere "prompting" and start using Codex as an advanced collaborator and builder, this episode is packed with tactical advice, practical tips, and candid discussion of the strengths and current limitations of AI in product work.
Timestamps: 03:11 – 09:53
Evolution of ChatGPT for PMs:
“When ChatGPT launched… it started as a chatbot. Last year, as we added different tools… it became a collaborator. With Codex it has truly become an agent.” – Abhi (03:56)
Codex as a Synthesis Engine:
Workflow to Build a Codex Dashboard:
Timestamps: 14:52 – 17:02
Shift in PM Practice:
“Just this week I got asked to write a PRD… After 20 minutes, I was like, you know, this is boring. I just want to build the thing.” – Abhi (14:52)
Org Impact:
Timestamps: 18:17 – 20:24
Timestamps: 21:09 – 30:07
Work automations at OpenAI:
Best Practices for Automation:
Main limitations:
Personal automations:
Timestamps: 20:24 – 28:27
Categories of Use:
Codex Harness and Skills:
Timestamps: 47:17 – 57:46
Imagen’s Role in International Growth:
Pro tips:
Current limitations:
Timestamps: 58:09 – 65:27
Model-first Product Development:
How to Break Into AI PM Roles:
International Growth Mindset:
“With Codex, there’s now many examples where I’ve been able to take a feature to 70, 80%. It’s like, cool—engineering doesn’t have bandwidth, so I just build it.”
— Abhi (05:01)
“The end output isn’t the document, it’s the product you’re trying to build—and that is conveyed with the prototype.”
— Abhi (15:55)
"Context is king. Not just what connectors to use, but what types of messages or posts really matter to you."
— Abhi (23:43)
"One mind-blowing use case—Codex could spot a missing income source in my accountant’s tax filing!"
— Abhi (37:00)
"The big unlock has really been the Codex Harness—that's what's powering all these workflows and prototypes. I think the harness has truly been a differentiator."
— Abhi (26:24)
"Every PM needs to be an AI PM. That's what this new era is enabling."
— Abhi (40:57)
“Imagen can now get you 90% of the way to a finished asset—what once took hours with a designer is now done in two minutes.”
— Abhi (55:36)
Episode Timestamps Quick Reference
Summary prepared for listeners who want to work, build, and grow at the cutting-edge of AI product management. If you want to use Codex like an OpenAI PM—start building, iterate with AI, learn by doing, and share your workflows.