How I AI - How Warp ships 2,000 PRs a month with AI factories | Zach Lloyd (CEO, Warp)

Episode Date: September 21, 2026

Zach Lloyd is the co-founder and CEO of Warp, an AI-powered terminal and software factory platform used by tens of thousands of engineers. Before Warp, he spent nearly a decade at Google, including time as a principal engineer on Google Sheets. He built Warp from the ground up as a modern, AI-native alternative to legacy terminals, and the team has since expanded into software factories: a full cloud-based system that takes an idea in Slack all the way through to a merged PR.In this episode:Why a software factory is more than a coding agentThe public Slack → Linear → GitHub → QA workflowHuman interactions per PR as a signal of automation and throughputWhy human review is still the bottleneckScoring agent runs, finding failure modes, and self-improving agent workflowsReplaying real tasks to choose model cost and quality tradeoffsCEO workflows with Figma MCP, Granola, and research agents—Brought to you by:DX—Engineering intelligence for the AI eraOpenArt—An all-in-one AI creation platform for images, videos, music, audio, and more—In this episode, we cover:(00:00) Intro(02:35) Warp’s AI software factory, Wilson(09:23) Automatic factory triggers(11:12) The engineering leader dashboard Zach wishes he’d had(15:18) How code review is changing in an AI factory(17:08) Tracking cost per PR across model configs(18:47) Using LLM-as-a-judge to score every agent run(20:02) Catching redundant tests(22:19) How the factory self-improves from failed runs(26:03) Quick recap(28:33) Building a cost-quality Pareto chart for model selection(31:35) How Zach uses AI for non-technical CEO work(32:10) Figma MCP demo(35:43) Granola MCP demo(36:41) GOG CLI demo(38:20) Thinking in parallel tasks instead of sequential ones(40:42) Zach’s prompting strategy for factory tasks(44:48) Where to find Zach—Tools referenced:• Warp (AI terminal and software factories): https://warp.dev• Warp Factories: https://warp.dev/factories• Linear (project and issue tracking): https://linear.app• GitHub (version control and PR management): https://github.com• Slack (team communication and factory input layer): https://slack.com• Sentry (crash reporting and automated issue triggers): https://sentry.io• Figma (design, used via Figma MCP): https://figma.com• Granola (AI meeting notes and MCP integration): https://granola.so• Grok Bot (fast inference, cost/quality trade-off): https://x.ai/bot/guides/grok-bot-101—Where to find Zach:X: https://x.com/ZachLloydTweets—Where to find Claire:ChatPRD: https://www.chatprd.ai/Website: https://clairevo.com/LinkedIn: https://www.linkedin.com/in/clairevo/X: https://x.com/clairevo—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email [e-mail].

Can I give you a hard time that humans really are the bottleneck? Because if you look at kickoff to PR time, it's 35 minutes. But if you look at PR to first human review, it's three and a half hours. And when you're doing, I think it was like over 2,000 PRs in the last month. Like, how do you keep things in the team from going, as I say, like chaos reigns? What is a software factory? For us, at least, it's an actual noun. It's like a product concept where it consists of a bunch of repos, a bunch of like MCP servers,

like a bunch of configuration and then a bunch of agents essentially so like a code review agent is not different agents different automations and it's all defined in code scoring happens across all runs but then there's a second loop popular thing on Twitter right now called self-improvement where you have like an observer agent and it can then create updates to your factory that will try to prevent the particular failure mode one of the things that's most helpful is like You could have these factory agents do computer use verification. So in this case, it made a video.

I'm just like talking to this thing that is doing this job that I've done for the last 20 years. And now it's like doing it kind of better than me. Spoiler alert, the humans are the problem. Welcome back to How I AI. I'm Claire Vow, product leader and AI obsessive here on a mission to help you build better with these new tools. Today I have Zach Lloyd, CEO of Warp. And he's going to show us exactly what he means. by the software factory. He's going to show us how you can kick off tasks in Slack, what it means to go beyond the software development life cycle, and how a technical CEO uses non-technical tools with AI. Let's get to it. This episode is brought to you by DX. In a recent study across more than 500 engineering organizations, DX found that spend on AI tools has grown 28X over the last year. The share of AI authored code is climbing, but overall

innovation has remained flat. As teams generate code faster, new friction in code review and validation is offsetting those early velocity gains. DX tracks speed, quality, and cost together across the software development lifecycle, giving engineering leaders clear visibility into how AI impacts delivery and whether those investments are translating into real value. Download the full report at get dx.com slash how I-A-I. That's G-E-T-D-X.com slash how-I-A-I. Zach, thanks for joining how I-A-I. Thanks for having me.

Excited to be here. There are a lot of trends on the timeline right now, but one that I think is going to be big for 2026 or seems to be big for 2026 is the factory. The factory, this like fantastical idea that we have. that we're going to, you know, input tokens and output enterprise value, something like that. At least we'll output code. So I, you know, I'm excited for you to show us as CEO, as engineer, as builder.

You know, what to you is the factory and how it looks inside warp? The factory is definitely trending. I actually don't love the term factory, but it is the sort of thing everyone is standardized on. It feels a little bit sort of like dehumanizing to me. But yeah, the idea is exactly what you said. It's like how do you, in a world where we have these sort of magical agents kind of harness their power in a more organized way to have them, you know, basically build software for you from your ideas. And so, yeah, excited to show you how I use factories and like what it means to me. I was at Lenny's Summit recently.

and I think Marty Kagan also said he hated the word factory. I wonder if it's more like Santa's workshop, right? Like we have magical elves that craft wonderful things that spark joy and are delivered gift wrapped for us. So I'm going to say the AI, the AI magical workshop. No, show us, you know, what does this look like for you? Yeah, you did say, you know, you put in your ideas, you output product. Is that real?

How does that really work? Yeah, so it kind of works like that. The way that I think of factories is like there's there's basically two types of personas who are using them. So there's, I'll show you like basically how we do this in Warp. There's like the builder persona. So the builder persona is someone who is contributing ideas, wants to build stuff. And from that persona, it doesn't look like, at least the way that we have it said, it doesn't look that different from like how one of the things.

these engineers or designers or product people on our team might build with a local coding agent. The big difference you can see here, so this is like, this is our Slack, is that most work is starting in a public place. And so the way we think of factories is like you, you basically can say in a public Slack channel, you can tag, we named our factory Wilson, you can tag Wilson and be like, okay, I want you to build something for us. And when you do that, what Wilson will do is like, essentially do not just like the direct build, which is what you might get if you're using like Claude Code or Codex, but we'll also like do a few other steps.

So what it will do is it'll kind of go through all the steps of like, first it will triage whatever this is. So it'll treat it as like an input to the factory, not just like the direct thing to build. Meaning it will, you know, for this one, Harry's saying he wants to change the way this feature looks. He gives like pretty detailed instructions. He, you know, attaches an image. He says use computer use. And this kicks off a flow where the first thing that the factory does is actually kind of open an issue.

So you can see over here it's like we use linear in addition to using. so that everything gets tracked. So the factory integrates not just with Slack. It opens an issue. Then it does the actual implementation. For this one, it's like it was simple enough and ambiguous enough that we could actually implement it. Then it does, it will create the PR.

So it integrates also with like GitHub. Then it does the QA, which I think is like really important these days. Like if you want to not spend all your time doing code review, one of the things that's most helpful is like you could have these factory agents do like computer use verification so in this case it like made a video of the completed feature so it's like showing the thing showing all the keystrokes and so what you get here is is not just like and then it gets merged right is not just like the single step of build build the thing like if you were doing this with like the coding agent and like the prefactual. world, what you would typically do is like pull up your local coding agent, do the change there, test it locally, and then like push it up to GitHub. But you get the whole thing of like the ticket, the code review, PR, the video, all all done together. And then the other like really

kind of magical thing is that it's all done in public. So if you are, you know, someone else wanted to come in and look at this and see how the task was done or even contribute to it. And so we all have multiple people on these Slack threads. You get to a world where as like a builder, you're no longer sort of working in this local silo. Instead, you're working in a public space where everyone can see what you're doing. And so that's like from the builder's point of view, how they like use the factory. Does that make sense so far? Yeah.

And you know, I think what I'm reflecting for folks who are maybe still trying to grapple with, okay, like, what's a coding agent? What's a factory? What's the difference? I think what I'm from you is the factory, quote unquote, is comprehensively designed to reflect your version of what the software development lifecycle should be. And so it's not just like idea to code to PR to push. It is, okay, an idea needs to go through several steps.

It needs to go down the conveyor belt of product and into like the funnel of issues. tracking and then we need to code it and then we need to QA it and then we need to have these very specific verification loops where we can take our sticker and say quality controlled by you know number one two three and so to you and the way you're describing it where it goes beyond a coding agent or a co-pilot is that it is actually designed to take take the very specific end end product steps not just the engineering kind of like input output that's that's That's definitely part of it, for sure. It's like it does more of the software lifecycle.

So it does more of those steps. There's a whole other bigger part of it to me, which is. So I showed you this from like the perspective of the individual builder. If you were to go into our Slack, you would see like this is happening over and over like all day long. The people in our team are building in this way. And sometimes, by the way, it's not just like the engineers who were kicking off work like this. It could be work that's being kicked off automatically. So for instance, we have, I don't know if you know, Century, but it's like a crash reporting system.

And so we have signals when there are crash reports coming from like our terminal app that we try to automatically fix those. And those go into the factory too. So it could either be human initiated. It can be initiated by like an external. system and it can be initiated actually in any of these tools so it's like you can initiate it like we could have started this whole thing in linear we could have started this whole thing in GitHub and so it's it's integrated into all the tools but the bigger piece of the factory approach in my opinion is not like it's not so much how it uh the individual builders work because it's not all that different from

individual builders who might be using like like might be going into the terminal for instance and using a coding agent to do something it's different it's in public but what's really different in the factory approach is that everything is like centralized in the cloud and there's a whole other aspect to it which is for not the builders but for the people who are like the managers who are like trying to scale software development on their team finally something for the manage what everyone's been wanting right too much attention on the builders no but in all seriousness if you're like like my concern uh is someone who's running a company is like i want i want soft like it's a super duper competitive market i want to see how quickly we're moving i want confidence

that um the way that we're building software is actually improving over time i want to make sure that we're not like wasting too much money. And in the world of like all of like every builder has their own individual local setup, that's very, very hard to get. And so this is like an engineering manager's dream. It's like a, it's like a CTO's dream. Like not that this is the coolest thing in the world, but it's like now I have the ability to sort of centralize and see what everyone's doing.

So for instance, on this screen here, it's like, These are, this is actual data from our team in terms of like how we're using the factory. It's like there's a sort of sense of like how automated is the factory. What's our velocity? How long does it take us to like ship stuff? And so there's just all these measurements. Can we pause real quick on your productivity? Because I actually haven't seen this measure before.

And we've seen a lot of measures, which is human interactions per PR. Just talk us through why that. Because honestly, I haven't heard that one before. and I like it. You know, this sort of instinct underlying this is that we are going to be, not to put this the wrong way, but it's like humans are a little bit of the bottleneck in terms of production itself. They're also the creative force.

But in general, what companies want and we're trying to build for companies at warp largely is like, how do you automate more? how do you make things that can truly just be done agentically be done in an almost fully automated way? And so, you know, the general instinct is like the more times you have to prompt, the more times you have to steer or like cajole your agent, that's like that's going to be a limiter on throughput. So this is where you start to get into like factory world. Like this is like imagine you're running like a Tesla plant or something. It's like how many times do you have to stop the line? And so, you know, we're trying to give engineering leaders a view of like, okay, how are you, are you able to sort of make things more efficient over time?

And quick question. Are those just because my mind, I mean, I, you know, as a one-time CTO, I'm like, yeah, this is exactly what I want. Are these interactions, do you think of these interactions as like the prompts, the sort of like upfront steering? Are you thinking about like how many comments on PRs, how many loops? like how inclusive is this like interaction per PR score? It's it's all of those. So because the and again, I think this can definitely be refined over time. And bear in mind we're like trying to figure out so what is the right set of metrics. But this actual metric because the factory is like integrated into all of your knowledge work tools, it includes all those things.

Like how many repromps in Slack? How many comments on linear? How many times did you have to create? correct the thing in code review. And so it's like a kind of like, yeah, it's a proxy for how much work did you have to do in order to, you know, get the thing to do the job. Okay. Wait, I want to give you a hard time one more thing.

Yes. Because before we started recording, you said like, how technical. And I was like, okay, well, we're going to put on the CTO, at least the CTO right now. Can I give you a hard time that humans really are the bottleneck? Because if you look at kickoff to PR time, it's 35 minutes. But if you look at PR to first human review, it's three and a half hour. Three and a half hours. And so it's like so funny that still cycle time, man, like it's the thing.

You really have to focus on. It's that number. Yeah. There's still the bottleneck. And we're, I mean, we're still doing human code review. Do you do all, all your PRs get human code review? Currently, all of our PRs get human code review. Wow.

And so, now this is like, I think, a team choice, an organizational choice. Yeah. We have, the one thing that we have changed around this is not, like, we used to require, like the workflow used to be like person A on our team would build something with an agent, and then person B would review the agent's code. We no longer require that. Like, the person who prompts the agent can also review its code. Okay.

Yeah. You're making me feel better. So that's a better thing, but it's still like we, you know, we don't have yet complete trust. I think the way this will evolve is like some percentage of stuff will eventually will feel confident enough that we can skip that. Yeah, I did an episode recently. I built an Eve agent called Merge Mommy. And this is the flow that I often see in even mature engineering organizations. is what you do is you basically like risk score every PR automatically.

So go through your risk score it. And then anything that is low or extra low risk gets a stamped approval from merge mommy and then a human's allowed to just smash the button and merge. Anything that's like medium high or whatever or has some like outlier on risk requires human review. And that just like lets you get that bottom tranche of the queue out. also just so you have good capacity for high quality human review on the things that really matter. 100%.

I think code review becomes an exercise in risk management. I think that's right. I want to show you some other stuff in the factory just to show you how this is different than just standard interactive agent. So you get, cost is on everyone's mind right now. And so you get like, this is Asian cause. It doesn't factor in that sort of cost. of the people at the moment, but it's like, you know, you can see like we, we were really expensive a few weeks ago. We made some changes to our model configuration and we've driven this cost down

and we want to continue to drive it down. But just like having the centralized view for this across your whole team, super valuable. Can I ask you a question of cost? Quick question on cost. So, I mean, this is a pretty, you can see the drop here. I see this a lot when I'm talking engineering organizations, they often see like a rise in cost of PR as their per PR as they're adopting AI, which you all already have. And then we see this drop as you're doing optimization. Do you feel like the biggest lever here is model right now? It's like that, is that the lever? Yeah, it's, it's model. I think model is the biggest, I think, like, context, like the way.

Context management. context management matters as a secondary thing. I would say model is the biggest. Yeah. And the way to really figure this out actually is to test, which is something I want to show as well. But basically, I think model is the biggest one. Any other questions on the just like the spend view?

No, that's great. So the other thing, like this is where. really gets kind of factory oriented is like the the way that we're changing development and this is I think this is most relevant for folks who are watching we're trying to manage like these teams and scale coding agents is like we now we're like measuring everything and so this last thing in here which we call scoring basically gives you a view um across all your agent runs of like how they're doing on different dimensions. And so we basically, because the factory is like a closed,

kind of like closed loop system, like every time an agent does a task in the factory, that task gets recorded. And what that opens is the possibility for you to go and like, like go back retroactively and look at how well the task was done. And so you could do this as a person. You could literally just go back and look at tasks. But the other thing that you can do is you can have agents do this, which is what we do.

And so, for instance, let me see if I can find an interesting one. Like here's an interesting one, like redundant tests. So if you're working with, you know what I'm talking about here, it's like, oh, I know what you're talking about? Every PR I push is like, I have run and set up 135 tests here. It's not. It's like, it's like in the reason it does this is because, you know, they're writing tests not to like prevent regressions necessarily, but also just to like test behavior along the way. And so you end up with a bunch of tests that you don't need. And so we, you know, if you take the factory approach, you kind of know this might be a failure mode.

And what you can do is you can write essentially a score that uses LLM as a judge to be like, okay. okay, I want to go and look at, you know, all of the agent runs. And I want to see how often we're, you know, an agent thinks, a different agent than the one that did the task, thinks that there's redundant tests. This makes sense? Yeah, totally. And so you basically are like, okay, I want, I'll pick a judge model. This is like a kind of medium smart judge model.

You don't want it to be too expensive. Otherwise, you end up spending a lot of money on scoring. You have it classified in terms of like for this task. like, how did it look? You pick like a sort of sampling rate in terms of how you want to do this. And then you get over time a set of runs where you can see that like sometimes this agent thinks that there were some like surplus tests. And so this is what I mean by like the real measurement.

Then what you can do is like you can go and you can actually, you know, as a human, you can go and kind of look at what's happening here. but I'll show you there's also a better way to do this in the factory world where it's like you can actually use agents to sort of identify what's gone wrong in these runs and try to improve the factory. Does this make sense? Yeah, I'm curious, do you do this on a per run basis or on an aggregate basis across a set of PRs? Aggregate, great question. So yeah, so what we do is like the scoring, and this will I call like this.

thing we call this like the score the scoring happens across all runs but then there's a second loop uh which is another like popular thing on twitter right now called self-improvement where you take an agent and you basically say okay for all of the failed runs and you need like you need like a real sample like maybe 20 25 failed runs you need some significant sample size otherwise it starts to over correct based on single uh based on single things you have it look, you have like an observer agent look and it can then create updates to your factory that will try to prevent the particular failure mode. And so let's see if I can find one that's like, I don't know this. I'm just literally picking a random one here. But this is finding some, some

issue with our skills that are driving the factory. It's presenting evidence and it's saying, okay, we should change the definition of one of our factory agents in a particular way. And if you go under the hood and look at this, it's like it's changing this like step 10 of what our factory agents should do. Does it make sense? Yep. And so this is, to me, this is really exciting. Like the way, the thing that's like enabling this whole thing to work is that you define the factory in code.

code. Yep. And so, you know, what I mean by that is like if, if you were to look at the sort of definition, you would say, okay, the factory, what, like, what is a software factory? It's like, it's like for us, at least it's an actual noun. It's like a product concept where it consists of a bunch of repos, a bunch of like MCP servers, like a bunch of configuration and then a bunch of like agents, essentially. so like a code review agent design like different agents different automations um and it's all defined

in code and the the value of doing it that way with like in warp factories is that you get the ability to actually um you can like test different configurations and know like you're basically freezing the state of the factory at a given point so you can be like okay if we were to to change the factory definition and then like run all these status again, we could see if things were better. It also makes it so that like an agent can actually, because these are all, it's all code. Like coding agents can actually update the factory to make it better. Does this make sense? Yeah.

This episode is brought to you by Open Art Arena, the global leaderboard for creative intelligence. Every week, new AI models launch and everyone claims to be the best. but best at what? Open art arena is built to answer the question that actually matters. Which model is best for your specific job? Instead of one overall winner, Open Art Arena ranks models across real creative tasks, from advertising and film to animation, product, graphic design, editing, and lip sync, covering both image and video.

And these rankings aren't based on hype. They're judged by professionals, industry leaders, and working creators through blind evaluations, so judges never know which model produced which output. That means you can see how models actually perform when it comes to the creative work you're doing. So stop guessing which model to use. Explore rankings based on real creative work

and find the right model for your project and save time and cost. See the rankings at Open Art Arena. Yeah, I just want to like, you know, kind of sum up where we are so far because I think there's so much rich stuff in here, especially for engineering leaders and builders. And then I know we're going to get to some workflows that are not engineering focused, which I'm excited about. But a couple trends themes that I've seen as you talk through this.

One, work happens in public. So I'm seeing, you know, this move towards instead of work being assigned in tickets and then tickets being worked on laptops, work is happening in public, whether it's Slack or some other channel. And then executed in the cloud. So sort of anybody can interact with that. the factory does have this software development lifecycle kind of like definition to it. But on top of that, it has this aggregate meta analysis that you're doing across all the behaviors,

which is giving, you know, as we said, giving the people, the managers, what they want, which is, are we getting more efficient over time? Is this factory actually effective? How many humans? How many agents? What's the inner balance between the two? Spoiler alert, the humans are the problem right now. And then what you're doing is you're also doing these evals against key behaviors in your factory that you want to correct. And this is something that when I talk to engineering organizations, I tell them all the time, which is such a challenge when you're using something locally like, for example, Cloud Code, is I say you need session level telemetry because you need to be able to aggregate up the failures within sessions across your engineering team. And so some teams do this truly by like sucking up every local coding session to S3 and running their evals kind of like on their own and their own platform. But I do believe that if you do not have session, tool call, MCP call, test failure, computer use level observability into every single coding session, you're missing a lot of opportunity to optimize efficiency, cost, model just like how your team uses the tools. And so I think it's super important that people do this. And then

what you've added is this extra layer of, great, then take those insights and make the factory better, however you define better. This is a great summary. Great. I did it. Professional podcast. There's there's what I just thinking of a sense of how you can continue to like, you can go even further once you have this data. I think your summary was awesome. The other thing that you can do and like I think and orgs are going to do this because this is how like there's going to be

nothing more important than optimizing the way that you like build and ship software in the future and so one other thing that is really powerful if you set up everything you just said where it's like you have the you have the tracking you have the e-vals there's one further way that you can make it

even more powerful which is adding the ability to basically take your own data and replay those sessions with different configurations to actually measure, like to your question earlier, like, well, how would it have done from a cost perspective or a quality perspective if you had done like different models?

And so, for instance, again, this is what we have built into warp factories, but there's lots of ways you could do this. Like the idea is you can, just like there are these public benchmarks like sweep bench and terminal bench, that are on like generic data, you can recreate on your own data, like from real past factory tasks, how would things have gone had you used a different model configuration, for instance?

So this is like a kind of Pareto chart, which again, these things are on Twitter all the time, but it's like what's cool here is like if you take the factory approach and are like really scientific around, okay I want to know like I want to let's say you want to curate a bunch of front end tasks and then see like can I be using JLM 53 on those instead of using you know opus yes definitely

should I be using Gemini 37 flash you're going to take a quality hit and so like you get to choose your own sort of tradeoffs here and then you can feed this back into a model routing strategy where you actually have evidence that, okay, on your own tasks for these types of, like, the best model configuration for costing quality is, is like whatever you find. Are you comparing that to what actually shipped?

Like, how are you evaluating quality? You know, there's like seven ways to skin a CSS. Like, how do you actually decide, you know, this is better quality or not on front end tasks, for example? Yeah, awesome question. And so the way that we do it in more factories, and you can probably do different things here, is we use the exact same like scoring infrastructure that I showed you earlier.

So for instance, you know, over here, we have all these different scoring dimensions. So you can, if you have confidence in this scoring infrastructure, basically you're replaying past tasks and trying to see if there was like how it affected these scores. So it's primarily LLM as a job. judge, but you can also, it's like you could do this with human judges. You could do it algorithmically, but the thing that we have built is out while I'm as a judge. Got it. Super interesting.

Okay. So you've given me so many ideas on how to take the factory idea further. I'm curious, just like take off our builder hat, our CTO hat. Let's let's put on, I, you know, I was talking to you, again, before we came on, I was like, people love to see how non-technical people can do technical things and how technical people can do non-technical things. So show us some of your other like AI use cases that are maybe less about evils and benchmarks and MCPs and more about, you know, being a CEO. Yeah. So we'll get like I think like zooming out. This is cool with all these charts. I still have a hard time making changes to Figma. And like I I don't know if you're the same way, but when I go to try and change like a like a like a fake.

Figma thing, I'm like, it's like I have three thumbs or something. Like I just, I cannot figure out how to use it. But I do know that it's like if you, like, this is how we like do our slide decks. For instance, it's like we, we are using Figma slides. You can make things that look very nice. So one thing that I do now is like, if I need to change a slide deck, I do it through the Figma MCP and the coding agent. And so like just to kind of show what that looks like, we have this kind of. semi-boring

like slide here on cloud execution. So I'll show you how I would do this just so you get a sense. So I'm going to do this I use this in Warp. I use Warp as a coding agent. This would also work in CloudCode or Codex.

I need a figma MCP. And so I'll just paste this in and then I'm going to talk to it, which is another thing. I assume people are on the voice train at this point. Are you on the voice chain? Yeah, we We give all credit to Hillary Gridley. She calls it the Yappers API.

Highest big width way to talk to an LLM. Yeah. So I'm going to say like, I'd like to make a new version of this slide, use the Figma MCP to get the context, duplicate the existing slide rather than making changes directly to it. Let's have it be so that the host box contains. the runtime box. Let's, let me see what else. I got a switch back here. So we're going to have host

contain, sorry, host should contain sandbox. I'll go back and edit this. Let's make the context system something that's like, kind of like, you know, cloud around these things that feeds into them.

True CEO. Put a cloud on the slide. You're going to see some bad design here. Let's make the launch pad have a sort of like rocket type theme. This is not what my sales team wants, by the way. And let's make tracking. I don't know. Why don't you come up with some ideas for how to make tracking better?

The overall idea here is to make this slide more visually appealing than the simple, you know, five boxes. and semantically show the relation of the boxes to each other. So I'll do this. Do you know what word I say to Figma? I say semantically. No, what? To Figma MCP all the time. Oh, my God, all the time.

Semantic color, semantic. It is my orthogonal. That's really funny. Yeah, I mean, we'll see. So I'm using I'm using GROC a lot recently Same I don't know what your model of choice is

I think rock is pretty good From like the cost and speed and quality Tradeoff I could show you I could do some other Yeah why don't while that's loading Why don't you show us something else Yeah I'll show you another one So I'm a big granola user

As well And so Again if I were really trying to improve this sales deck. Another thing that I would want to make sure is that the sales deck is speaking to the things that customers are actually talking about. So I'm going to start a second task here using the Grinola MCP where I'm like, can you use the Grinola MCP to look back over my last four weeks of sales meetings and try to build up a list of the top 10 frequently most asked questions in these meetings as they pertain to

warp software factories don't list any specific customer info in the summary, anonymize it because I'm doing a podcast. So we'll get this one cooking as well. I can do one more if you want.

Yeah, let's, I mean, let's cue them up. Again, I love to see a AI-pilled CEO just open tab, after tab, after tab, and kick stuff off. I mean, this is stuff that, this is stuff, these are all, by the way, real things that I am constantly using AI for. So the last one is like,

a task that I use AI for is trying to rediscover potentially like cold leads that I might have talked to in the last like, you know, six months or so. You know, our product has changed a crazy amount. I might want to reproach them. And so the thing that I, I use for this, or had in the past been using this,

I actually just started using instinct. Do you use instinct? Oh, no, I had a bad experience with instinct. You had a bad experience with instinct. So the normal way I would do everything is still through my, is still through a coding agent, but I would, let's, I'll do one more prompt here. Can you use the GOG, CLI to look for

emails and calendar events I've had in the past, six months with potential enterprise leads who might be useful for another outreach for warp factories you can learn about warp factories at warp.dev slash factories and make me a Google sheet with the info on them and share the sheet link but don't print out any specific customer email or name in this thread. What I like about this at the meta level is like, is this how your brain works where you're just like, I need to do the slide, kick off the slide.

I need to like update some of our sales position kick that off. I need to like follow up with cold leads. Like is this. Yeah. Is this a reflection of your CEO brain? Because it's certainly a reflection of my brain. Yeah. I mean, if I were if I were in like sales mode, go to market mode, and like I am in in that

mode quite a bit now unfortunately more more so than like straight up builder mode or edge manager mode although I do all these different things I'm constantly trying to find like what is the right positioning are we are we communicating in these meetings in a way that lands and like it's so amazing to have a disability like for me who can't design or draw at all or like to have this now superpower and we can go let's let's see how this figma is doing over here has it started to do it yet oh it's starting oh it's got some work with you but it will it will do better but yeah if i was in sales mode like i'm trying to figure out are we positioning it right what are people asking about um yeah and this is this is right like this is

from our actual sales calls and like this is that what i would say is the number one thing for the factory like the product category we're in is like by versus build and it's backed up by evidence and it makes sense to me. Security comes up a lot. What's the workflow? What's the measurement? How do we manage costs? It's so cool. And so it's like what I would do is like, you know, I want to then go make sure that our sales deck, our website, all this stuff is speaking to the questions people have. I might turn this into like a literal FAQ. Like I think we we have, you know, probably ability to improve that or we just try and work this and do our positioning, but

I'm constantly doing this and trying to understand if what we're building is the right thing and we're positioning it the right way. Oh, you got a rocket ship. Sorry, we're back at Fig. For those that are not watching, we got a rocket ship. We got a cloud of some sort. It's trying. It's not very good yet. It will get better. The rocket ship's not terrible. That's not bad.

Zach, this is so fun. I want to go to quick lightning round questions and then we'll get you back to back on the factory floor. All right. First lightning round question. Everybody wants the factory. Everybody wants the go-to-market intern that will happily go through your call transcripts and the design in turn that will happily make your ugly cloud slides as a CEO. But when you have the factory humming and when you're doing, I think it was like over 2,000 PRs in the last month. Like how do you keep things in the team from going, as I say, like chaos reigns? Like, how do you keep your arms around all that activity, all that work, all that context, all those tasks? And know at the highest

level you're doing the things that matter. It's a great question. Like, the kind of boring answer is like a lot of the stuff that we've always done as software engineers still applies, which is like, you know, we're dog fooding. So we're just like huge, constant users. of the thing that we're building and making sure that like the quality of the thing still works well. There's like cool knowledge transfer that's happening where it's, I don't know if you've seen this too, but like the, there's like a kind of power law for like how these tools are used in terms of like we have some people on our team are super duper power users and other people are like kind of more at the average. And so there's this, when you, when you're working in this, what seems like a very chaotic, way in public with everyone slacking these factories all day, you do get a chance to sort of see

how like the really expert people are using it. And that kind of up levels other people on the team. And then like I said earlier, we're still doing, you know, it's not just like chaos, like everyone like, you know, slop stuff into the machine all the time. It's like we still have a product development process that, you know, is somewhat traditional in a bunch of ways. So it's like we do a whole bunch of user interviews. We watch people use the product. We do design jams before we start building to not so much like figure out exactly like how the UI should look, but just to make sure that we're tackling the right user stories. Like, because at the end of the day, like, it doesn't matter how fast you build software. It's like it still has to solve some user problem and

solve it in a good way. And so we're trying to figure out how to like not lose the key parts of like the human input here, but also, you know, use the fact that there's this like magic technology to, that can make you just go much faster. I love it. Amen. I could not say it better. Okay. Last question. And then we will get you out of here when your AI is not doing what you want. And also, I'm curious if this question is if you answer this question differently when you're working with say I privately versus working it in within Slack with it's not doing what you want.

What's your prompting strategy? Do you yell? I am lately, I will admit this to the audience. I am doing a lot of like, why are you like this? Why? Why? A lot of questioning. That's funny.

I'm like a pretty level guy. I think if you ask the people on my team, I don't know. I've never really yelling out my style. I get like passive aggressive is kind of what I would say. I get I get like I rolly like really like this is what we're doing now like you built this whole thing that no one asked you to build. So I'll get like annoyed like in like subtle undertones but I'm not a I'm not a yellow and so

I don't know and I also try to just keep the perspective that this is just like a bonkers thing that I'm just like talking to this talking to this thing that is doing this job that I've done for the last 20 years and now it's like doing it kind of better than me and so I don't know I'm still like I'm in like a little bit of like

a wonder phase with it I don't know if you've ever seen that Louis CK skit where he he talks about how when internet like Wi-Fi first got onto airplanes stop me if you know this

but it's like he's like he's It's a skid. He's like he's riding on an airplane. It's like, it's like 20 years ago and there's Wi-Fi for the first time. And he's just like, this is incredible. Everyone, like, this is like amazing and nobody's happy. And he tells a story about how like the guy next to him is like trying to watch a YouTube video and like throwing his hands up like, screw this. Like I can't get any signal. And Louis C.K. is like, like, this is bonkers.

Like we're on an airplane. This thing is like going up to space. Give it a second. And so I think it's, it's so easy. to lose perspective of like how wild this technology is. Like I'm I'm I'm generally like pretty probably like kind of more patient with it than most I would say. I love it. That's such a great perspective. Well, Zach, this has been super fun. Where can we find you and how can we be helpful to you? So you can find me personally like I'm on I'm on Twitter. I have Zach Lloyd tweets is my

is my Twitter. You should obviously come check out Warp at warp.dev if you want to build software factories. You know, I hardly even talked about it, but we have an extremely popular agentic terminal that's open source that you should also come check out and use. It's a great place to work with interactive coding agents. But yeah, this was awesome. I really appreciate you having me on. Yeah, thanks for joining Hawaii AI. Thanks so much for watching. If you enjoyed this show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts. Spotify or your favorite podcast app.

Please consider leaving us a rating and review, which will help others find the show. You can see all our episodes and learn more about the show at how IAIIPod.com. See you next time.