← Return to Index Archived March 18, 2026
The Lead — Mar 18
AI AND I · DAN SHIPPER

How Every Builds a Writing Team in the Age of AI

Every editor-in-chief Kate Lee traces her path from literary agencies and Stripe Press to building a small, AI-literate newsroom. She explains how style guides, agent browsers, and shared editorial systems can raise the floor without surrendering judgment or taste.

56m / March 18, 2026 /aicreativitybusiness / Transcript sourced from rss
All episodes from AI and I →·Listen on Apple Podcasts →

Overview

Dan Shipper talks with Every editor-in-chief Kate Lee about her path from literary agent to roles at Medium, WeWork, Stripe Press, and Every. The conversation centers on how an experienced editor has gradually adopted AI, not as a replacement for editorial judgment, but as a system for raising quality, reducing operational drag, and helping a small media team publish at a higher level.

Kate argues that the useful version of AI is trained on a team's own standards, examples, and feedback. The goal is to give writers and editors a reliable first pass, while keeping humans responsible for taste, judgment, and the final call.

Key Takeaways

  • Kate's career choices were often reactions to what came before: she left slow-moving book publishing for the speed of Medium, sought stability after early-stage media by joining WeWork, moved to Stripe for operational excellence, then returned to a small team at Every because she preferred working directly on the company's core product.

  • Every's editorial operation had a consistency problem. Freelance editors were talented, but drafts arrived at different quality levels because each editor applied standards differently. Kate responded by turning a large internal style guide, initially around 400 rules, into an AI-assisted editorial review process.

  • AI works best here as a "floor raiser." Before drafts reach Kate, writers and editors run them through an internal editor trained on Every's style guide and past feedback. That does not guarantee a finished piece, but it reduces repeated mechanical fixes and lets senior editors spend more time on argument, structure, and fit.

  • The hard part is not merely writing a style guide. Teams need to translate editorial standards into instructions AI can follow, test those instructions, revise them, and make sure people actually use the tools. A document written for humans may need a different structure when it is used as model guidance.

  • Kate's recent shift in AI use came through operations rather than prose. Agentic tools helped her set up hiring workflows in Notion, post roles, organize applicants, and create a first-pass screening system. She still reviewed every application herself, but began from a more useful shortlist and evaluation framework.

  • AI has also changed what a small editorial team can produce under deadline. For Every's model "vibe checks," the team can gather testing notes in Discord, summarize them into a living document, build interactive web pages, and prepare coverage for multiple releases in a short window.

  • Human judgment remains the limit case. Kate distinguishes between consistent copyediting and the broader job of reading a piece for quality, audience fit, voice, and whether it belongs in Every at all. Those tasks often happen together, which makes full automation harder.

Practical Steps

  • Turn recurring editorial feedback into a shared AI project. Collect style rules, examples of strong work, common mistakes, and approved revisions. Ask writers to run drafts through it before submitting to an editor.

  • Review published work as a team. Examine the headline, subject line, deck, opening paragraph, and reader response. Record what worked and what did not, then add that feedback to the editorial system.

  • Use AI for first-pass operations before handing work to humans. For hiring, define the criteria you care about, ask the tool to identify relevant evidence, and then personally review the candidates rather than accepting rankings blindly.

  • Treat AI suggestions as editorial input, not instructions. Writers should explain to themselves why they accept or reject a suggestion. That preserves judgment while making the process more disciplined.

  • Start with the work that causes friction: unfamiliar admin panels, spreadsheets, research organization, scheduling, or repetitive formatting. The first useful AI workflow may not be the most obvious part of your job.

Notable Quotes

  • "It's not about accepting what AI says blindly at all. But it's not generic and it's not random. It's trained on our stuff and it's trained on what's worked." - Kate Lee

  • "Your job as a writer or editor is to consider it." - Kate Lee

  • "I like to work on the thing that is the thing." - Kate Lee

It’s not about accepting what AI says blindly at all, but it’s not generic and it’s not random; it’s trained on our stuff and what’s worked. — From the episode

Full Transcript

Source: rss 56m runtime

When I was the only editor working with our writers, I really used AI as a way to try to enforce our editorial standards. What I was finding is the work just came back at a different level from each of them. We basically created a project where every draft before it came to me, if it was an internal writer, they would need to just like run it through our editor. We have a style guide. When I came here, it was just like 400 rules. Hopefully by the time it gets to me, the sort of floor has been It's not about accepting what AI says blindly at all, but it's not generic and it's not random. It's trained on our stuff and it's trained on what's worked. And so your job as a writer or editor is to consider it. Kate, welcome to the show. Thank you. Thanks for having me. I'm so excited to have you. One, because we've worked together for so long. You've been part of Every for so long. We've been working together on Every for like three and a half years. For people who don't know, Kate is our editor-in-chief. She does everything involving the newsletter and has been doing that for like a really, really long time. And the business surrounding it to like sponsorships and events and courses and stuff like that. Oh, man, you joined us at like quite an interesting time because it was like the I think your first day was the day that Lex launched. And so it was like, well, everything was like it was Lex is an AI app that we incubated, like maybe, I guess, three and a half years ago or three years ago, something like that. And it went super viral. Yeah. And at the time, we were really just known for being a newsletter. And so we have this viral software app. And then we spun that out. And so we went back to being a newsletter. And we had to kind of like look at each other and be like, what are we doing here and what do we want to be? Um, and so I want to talk about, I want to talk about you. I think, I think your career is incredibly interesting. I want to talk about how things have progressed, uh, for you and, and how you've seen every and what that journey has been. Cause we've honestly never talked about that. I was just curious about it. And then I think the, the last like interesting thing on my mind is, um, I feel like you have had this really interesting transition, which you just said, I think you framed it really well. I'm sort of like an early adopter at child stuff, and you're sort of like a knowledge worker who's excited about this, but is not just going to use it because it's cool. And I feel like you've had this major transition in your workflow over the last month or two that even though we've been working on this for three and a half years together, it's and you have obviously adopted AI in your workflow, like it's something has like shifted for you. So I really want to talk about that. For sure. We've had a really interesting career that I think... I think the kind of career path you have is the kind of career path that a lot of people at every habits. It's the best. It's like you've done so many things. Thank you. Yeah. I, so my career is in media and technology. And I think there's the version of like the how immediately did I get to every which you know, you can kind of there's one version and then like how did my career maybe set me up for that. But my background is actually in book publishing. So initially as a literary agent way back when. Kate was like a star agent. Like there's literally a New Yorker article from the front of the New Yorker being like, Kate Lee is a star. Very kind. I was the subject of a talk of the town piece. Yeah. when I was just starting out in publishing and it really jump-started my career. It was extremely overwhelming at the time and I will just never forget it. I'll read it. 27? That's right. 27? Something like that. Wow. I still have not been to talk about this. Yeah. I mean, I guess I would recommend it. I don't know. But really wanted to ultimately, after 10 years as a literary agent working among... my colleagues were the best of the best of agents representing the best of, uh, journalists, novelists, literary fiction, big commercial nonfiction politicians, businessmen, et cetera, Nobel prize winners, Pulitzer prize winners, um, felt like, um, ultimately having done it for 10 years, like I wanted to see what else was out there. It wasn't something that I necessarily wanted to do for the next 30 years. and really wanted to move into tech. And my network at the time was just, you know, people who were founding things in New York, which was a much sort of smaller ecosystem than it is now. And I just knew I wanted to be a part of that. I didn't, not that I wanted to found a company, founding a company is the hardest thing anyone can do. Um, kids harder. fair. I can say that too. I just seen it. Appreciate it. You have a good insight into that. But anyway, I wanted to move into that world and through just a whole series of conversations and networking and meetings. Actually, one of them with ultimately ended up being your Josh and her. So one of your very good friends, but from the browser company. Yeah. This was a very long time ago. Ended up meeting at Williams when he had left Twitter and was founding medium. And so I jumped to medium and, and was there for four and a half years. And you led all their, I led, I was their first person in New York and their first like sort of content head. And it was, Just like the, I just felt like such a sort of seamlessness product market fit, so to speak with the job, because it was everything I loved about working with writers in just like a new way, a faster way, much faster feedback. And, and of course it was the first time I had worked with any real technology people. I mean, the technology people I'd always worked with was an ID department. This was, you know, product managers, things like that. Um, and then, um, medium went through a number of changes as, as, as most companies have and most media businesses have. Um, and from there, I actually went to WeWork. Very nice way of saying it. I don't know. Do you want me to go into more of it? I'm happy to like, to share what happened. I think we all know what happened in 2016, um, in terms of to the, to the sort of larger environment. Um, but I actually very explicitly in my next move was like... I'm really exhausted from media. I've just like, I've been in it for a really long time and I was just in a really early stage company. And I don't like, I just need to go somewhere less crazy. So I'll go to wait. That's literally, you know, one can question my judgment, but, um, the company had just raised the, I don't know, however many billions from soft bank. And it was just, they were just in a huge expansion mode. And I went there to lead their, um, global editorial program. And I ended up staying there for almost two years. And it was like true madness. You know, grew from 4,000 to 14,000 people, just like crazy, crazy, like three different people doing the same job because we were being hired so fast. So that was, that was a really, you know, different experience. And like, I worked with amazing people. Of course, all these companies have such talented people. Yeah. Um, but ultimately knew that like, that was just not a place I was going to stay. Um, and then I saw a job opening, a job opportunity, which was to be the publisher of Stripe Press, which is Stripe's, um, publishing arm. And I just was like, this is such an incredible opportunity. And so I applied for the job and talked to a bunch of people there and then started there actually about six weeks before the pandemic hit. So, um, it was a really, Stripe is an incredible company and it was, um, again, just, just such talented people. I think any, any job in general that you're going to start right before pandemic is just like, that's just hard. And I think they, um, absolutely did, uh, you know, everything you could want from, from any company in that regard. So I was a publisher of Stripe press, which had launched sometime before. So I was, I was taking over an existing list and then building a new list. And then I also ended up becoming, um, overseeing increment, which was their, um, magazine for developers. How did you know that? You didn't know that? Increment run by a woman named Sid Orlando. Fantastic magazine. Print. Also print and online publication devoted to developers, which was Stripe's really early and core audience. And I learned so much at Stripe. And just one of them being like, you know, Stripe is a payments and financial infrastructure company. And so people would be like, why publishing? You know, why have a publisher? And first of all, I would say if I have had many people and founders or VCs or other companies being like, can we do a book publishing career on Mike Stripe? And I'm like, no. And I shouldn't sound that categorical, but I think what the among the unique ingredients for success at Stripe are founders who are genuinely, genuinely voraciously, you know, excited about ideas and books and that that being set from the very top really sets that up for success in a different way than if it was an initiative that came out of a different team. And I think it was like a pure marketing. Correct. It wasn't like, you know, coming up in a marketing brainstorm. This was like this was a genuine desire to both read great books, to rediscover books that have been potentially lost to history, to discover new ideas and to really help. entrepreneurs. The, the mission of Stripe Press is to, is called Ideas for Progress. And it really connects to Stripe's largest mission, which is enabling more global entrepreneurship. And, and again, that is done through various ways, through various products, but like that is that overall mission. And so that was, that was certainly, that was a fantastic experience. And I should say Stripe, is probably anyone who's worked with me knows that I'm like, can be really, I don't know, like particular about certain things and never would have. copy and commas and all things like that. And Stripe is a place where the attention to detail was absolutely incredible and was, what they're sort of known for. And it was almost a little bit counterintuitive because if you think about it, of like it's a financial infrastructure company, it's a payments company, why do they need to have a beautiful gradient on their homepage? But they do. And they invest a ton in making sure it is just right. And so even if it's not meant to be a household name necessarily or wasn't at that moment in time, it didn't matter because the people who love them loved them. And that that relationship was really important. That's really interesting. So, yeah. And then while I was at Stripe, I met you. I basically was like, I got to find writers. I got to find people to write some books. And every had just started. This was when I guess it was 2020. It was like early pandemic. Everyone was starting newsletters. And I had met your co-founder, Nathan, a number of years ago when I was at Medium. I believe I had met him probably with Evan. And actually, I think when I met him, he came in with Hamish. That's so funny. Hamish is one of the co-founders of Substack. Yeah. Yeah. And so I just reached out to Nathan and I was like, I'm at Stripe now and would love to talk. And he connected us and we had an initial phone call and just stayed in touch. And then I ultimately decided after two years to leave Stripe and go independent and get back to working with really early stage companies. And so I reached out to I guess I reached out to both of you again and I was like, do you need any help? I mean, yes. And we were like, boy, there was like this running joke for. Basically, from 2020 until when you join. So like three, three years or two years of every year or whatever. That was like editor in chief at every is like defense against the dark arts at Hot Works. Like no one lasted very long. God, I didn't know that beforehand. I really am. I said Tony. I know, but that exact framing. I definitely knew there had been a number of people. You tried different configurations of that role. It was just really hard. It was and it was not necessarily the fault of any of the people that we hired. It just was like. We do a very particular kind of writing. And I think early on, I was like, well, if you have editing experience at a big company like New York Times, you must be able to do the kind of stuff that we do. I didn't realize different editors are just made differently and have different jobs. And editor is a very wide ranging title that's the same thing as founder. You know, it's like, what kind of founder? Do you have a barbershop or do you have like a venture-backed company? They're very different. And finding someone who has the writing taste for technical stuff or stuff in and around technology is very hard. I think that you're either like really into tech. or you're really into writing and you're, it's not always, but a lot of times you're like a little skeptical of tech and you're like, and you're coming at it from that perspective, which a lot of more mainstream media outlets come at it from, which is an important perspective, but it's very different from our like kind of coming from the builders place. And so like, I'm pretty sure the minute, like the, the first time we met, like the first meeting, I was like, do you want to come on full time? If I didn't say it, I was thinking it. And I spent like a lot of time trying to get you to come full time. And then you did. Yeah. That's been really, really, really amazing. Yeah, it was the right time. I mean, I basically, I think I immediately started like, you know, just sort of advising, you know, you and the company and the team. And then ultimately started doing some freelance editing because you needed editing help. And so I started doing that. And then I took on... the, um, the guest contributors. Right. Um, and I was also really aware, I basically had like three main clients at the time and I really loved having kind of like the ability to pick the projects I was working on, the people I was working on, set my own schedule, um, And I just was very aware that like, I always liked working with this team the most. And so then after, after I was spending time on, you know, guest pieces and making those great, I, you know, sort of the last thing to touch was like you, Nathan, Evan. So the, the, the main writers, the sort of full-time writers at the time who you all had a very, seemed to have a very symbiotic like process of giving each other feedback and writing together. But I was basically like, look, we're going to do, put all this work into these. Yeah. We're also going to do a little bit more work. And that was sort of the last frontier of just like what I was actually editing. And then with, as Dan alluded to, or as you alluded to with this, um, spinoff of Lex, um, there was just a moment to, you know, not, not only just an editor in chief, which you definitely needed, but like, what are we doing in this company? There was an opportunity to come in and be like, let's figure out what this is. Um, which is when I came in full time. Yeah. And I've always wondered this because I have never actually worked at a great company. I have worked at companies, and I'm not casting aspersion on those companies. But by great, I mean a really high performing startup or a company that used to be a really high performing startup. I've only just kind of dinked around on my own stuff, more or less, or worked at an acquiring company or whatever. But you've had a lot of experiences with some of the big name companies of the last like 10 or 15 years like EDM and WeWork and Stripe and every And I feel honored to be, you know, that that's you've added that to your resume after all those. But I'm curious how your experience here compares or like what you've taken from all those different things that and how that relates to every. Yeah, I think in some to some degree. Yeah. My own career experience has been like every every job or every every experience has been a sort of reaction to what has come before. And so, you know, when I left book publishing, I was like, I want something fast and, you know, nimble and and just immediate feedback just because that's the you know, the book business just works on much longer timelines. And I was really, you know, eager for that. Um, and then, you know, I basically was like, oh, I need a much more established company when we were, and then leaving we work, which was a disaster as a company for many reasons. Stripe is an incredible company and operationally is incredible and, um, also grew enormously while I was there. Um, that was, that was a fantastic experience. And then also set the scene for me wanting to come do a startup again. Everything has been a reaction. And, you know, one of the things that I really knew that I wanted to get back to in in. Well, first of all, I should say. After I left, you know, when I left Stripe and I was doing projects of my own and I was like, I love the sort of like control. And I was like, I'm never joining another startup and I'm never joining another media company ever again. Oops. Never the never. Yeah. you know, famous last words. But I really felt that at the time that that's like, I wanted to, you know, that's how I wanted to do my career. And I think ultimately what I find, I get the most satisfaction out of is like, I personally just like working in small teams better or just find that more personally satisfying. And I also really like working as I like to say, it sort of sounds, doesn't sound like much, but like, I like to work on the thing that is the thing. Mm-hmm. which basically means like, I want to work on the thing that is the main thrust of the company. And even if, for instance, media is not the most remunerative, let's say, or, you know, as let's say as a software product or something, it's the thing that is the driving heart of the company. And so what I am doing is what is contributing directly or not contributing to the success of the company in a way that feels for me much more direct and satisfying than... doing marketing, even very good content marketing in some other capacity for, you know, for a much bigger company. I want to get into this moment that I feel you've had, because I think of you, I think that you can be a real, maybe ambassador is the word for... particularly people out there who maybe have some resonance in their career trajectories to you, or they're like, I'm in book publishing, or I was in book publishing, or I'm an editor, or I'm a writer, or a lot of the... a lot of the strands of experience that you have that are incredibly important at every, but if you're from not from our world or not working at every, you might look at a lot of what we do or a lot of the AI stuff. It's like, Holy shit. This is like crazy. I don't know if I like this and I don't know how this might, how I can really, incorporate this into my work or whatever. So I just, I kind of, I'm curious about, I mean, we can talk about the breakthrough that you had recently, but also maybe more generally how it has, why you went in to do this at all and how that has changed over the last couple of years for you, like incorporating AI into your work and then where that is now for you. Yeah. So it's interesting. So when, you know, three, three and a half years ago, whenever it was, when I joined the company full time, I think I was the fourth, fourth or fifth full time employee. Yeah, it was like, I mean, I mean, at the time that you joined full time, there was like three people full time, including me. Yeah. Now there's 20. Yeah. And it will be probably 23 or something soon. So, yeah, it's got a lot bigger. It's grown a lot. Certainly percentage wise, we have grown an enormous amount. And I think when I so when I was just starting here and thinking about, you know, what I wanted my career to be. Yeah. It's kind of maybe a little counterintuitive that I was like, oh, like joining this small startup. I sort of like I there was a there was an aspect of it that I was like, this is a world I really know. And also can sort of really it will really work with my life, which at the time I just had a second kid and needed startups known for work by balance. I was like, I'll turn startup now. A little bit, a little bit strange timing, potentially. But I was like, hey, whatever you want to do. I don't care what. For sure, a tremendous amount of flexibility, which I am always grateful for. But I think I knew coming in, I was like, I know, I really know what my zone of expertise is. And I really know that, again, there were only three other people at the time. the company. So it wasn't like, Oh, there's 50 other people. I was like, no one else can do what I'm doing. I just knew it. And so I felt like I had just a really clear sense of like, I'm going to come in and I know what it takes to get my work done every day. And it was very much going back to being an, I see an individual contributor. I, you know, I had managed large teams. I was like, Nope, I'm just going to come in and do it all myself. And like, I can control what I can do. And I think you wanted that. You really wanted that. Yeah. Yeah. Yeah, I was like very happy to be like, this is what I'm doing every day. Which I think most people who have that they've like managed large, managed large teams. It's like a little bit of an ego hit to like go back to being an IC rather than being like, this is a refreshing, like way to just like get back into the basics of what I do. You know, it's really interesting. Yeah, it felt really satisfying. And I think because I'd had, you know, I ended up, I think I was sort of consulting for about a year and a half before I came here full time. I basically threw other clients as well, was like, well, I guess it's just me to do the work. Like I have to figure it out. So I feel like I was really able to get inculcated that way. But, you know, when coming into every at the time and again, having started full time, right, literally when we were launching Lex, like it's... It was both clear that there is a new technology happening, but also not at all clear what that was going to mean for us, which was, you know, we were going back to being a news, a newsletter company and really having to figure out, like, what did that mean and what what made us different and differentiated us. And I think there's always been, you know, the focus on Hickolity writing has always been at like the beating heart of the company and was from the very beginning. And that's been really, really important. But it's been really interesting from the AI perspective to be here because, you know, again, I don't know that anyone planned it. It's just I know that when GPT-3 came out, you were just really excited about it. I was like, Kate, I can automate your job. Yeah. Yeah. Well, we can talk about how you've been trying to automate my job for the past three years, and I don't. Yeah. But no, you just really wanted to write about it, right? You were like, I just really want to like, I'm just going to spend the next three months writing about Chachi Buti. Only Chachi Buti. Okay. And that was like that fall. And you did. And that's when we ended up launching the podcast. And it just was so clear that there was like such a richness there of things to talk about. uh it was on my mind yeah definitely it was on my mind and like i have you know an email to our investors like around the around the time when when lex happened like being like this is the we're gonna do more of this this is the plan right um but also the practicalities of we're running a business we have to publish every day i'm writing a lot like it's moving super fast it took a little bit for that to actually like play out. One of the things that I think is I love about this business is I was just like, I'm pretty happy doing that. Like, that's actually great for me. I love writing, you know? So I wasn't like upset to be in the news, in the, in the, just deep in the writing newsletter stage, you know what I mean? Yeah. Right. And I think one of the really important lessons of Lex was like, yes, technology wise, the ability for two people to build this product that who, you know, weren't necessarily hardcore engineers was, was, was really meaningful. And the fact that we were able to distribute it to a list and get, that was a huge deal. And sort of having that like distribution built in, which has just obviously, or not obviously, but like has distribution is so, so, so important. And so really maintaining, like we have to sort of cultivate this list. Yeah. But I think, you know, I can say when I started full time, we I we had very lofty goals and I remember those goals and like metrics. And and then let's see what happened. Elon Musk took over Twitter. Oh, my God. That was big. That was bad. Traffic cratered. And it was like, oh, wow, we have to figure out what this is going to be. Are you remembering that moment? It's all going back to me. I'm like sweating a little bit. That was so many crises ago. It was so many crises ago. I remember being like, what's going on here? This isn't the trend that we were seeing before. Yeah, the link sharing. Just like they did deprioritize links and it was like, oh, that's our whole business. It was really, really tough. So do you remember what our strategy was? It was emphasize bottom of funnel. Yes. And that we started doing a lot of more courses. So it's like, if we're not going to grow Top of Funnel as much, we're going to emphasize the relationships we have with our best subscribers. We started doing courses and that was also a big impetus to start doing more software. Cause it was like, we can monetize, even if we have a smaller number of people, we can monetize them better with software and consult it. Right. Yeah. Right. No, it directly led, I mean, that is what directly led to the, you know, the way that IREA is now, along with, of course, the changes in technology, such that like now you can, we can run, you know, four or five products with one jam each, which just like would not have been possible a couple of years ago. It's been real. So, so in terms of like your question about like how I've felt being both a part of this journey and AI, et cetera. I mean, I always like, I always have felt like media and technology has been like the real nexus of my career. You know, I, AI is certainly. It has felt like a huge sea change in a way that probably people who were in early mobile experienced it as well. But what did you feel the first time you saw the words come out of GPT-3? What was your reaction? I think I was, I don't, I'm trying to remember where it was if I can. And I don't know if I remember the actual first time. You remember when I was trying to force you to make a spreadsheet of every copy edit change? Yes. You made it so we could make a prompt that would do your copy edits like three years ago. Why did you feel that? So, so Dan has been trying to automate my job for, for like three plus years and you're getting closer. It's slowly but surely. You have, you have really been like, there is, you know, because what an aspect of what I do of editing is like repeated patterns, things I'm sort of catching all the time, a certain standard we want to hit and rules to follow that is like very well suited to editing. I can't tell you how many times you've deleted the word very from my drafts. And like, I'm just trying to save you. I'm just trying to save your brain. That works. Correct. And so I think like initially, I don't know that I felt, I don't think I felt the sense of wonder that you felt. I think it was more like a, wow, this is really interesting. And I think in general, the way that I have watched it has been like, I feel like I get to have a front row seat to everything that's happening. And I'm so grateful for that. I am riding along with it and, you know, trying to, I basically feel like I get to learn every day from you and from colleagues about what's happening because the attitude very much is, you know, as you said, it's not like you have to try these tools. It's you get to try these tools. Like you work whenever you get to try these things. Mm-hmm. by the same token, I think, you know, to what you said earlier, we sort of represent the two sides of our audience where like you're the early adopter very much on the edge pushing forward to the nth degree of what these tools can do. And I'm really that like knowledge worker who works in tech or is savvy about tech who wants to use AI, knows I need to use AI but like I also have been doing a job a certain way that has not been reliant on AI and so yeah, it's really been interesting with each time these new models come out and, you know, you have built, um, uh, you know, ever smarter versions of a copy editor. It's been like, well, I don't still fully don't have to use this cause it's not, nothing is as perfect as what I have been able to do myself. Um, and is just going to, in the short term, at least, is just going to create more work. And then in the past couple of months, again, I'm not about to say that you modified my job, but in the past couple of months, you, I have seen and I have been able to use AI to do aspects of my job that, again, maybe aren't fully yet along the editing side, but are in, you know, absolutely administrative, operational research reports, anything like that. And like, it has completely saved me as, as you know, like spending hours in Notion or hours in a spreadsheet. And it has felt like a real aha moment of like, oh my God, I don't have to, I don't have to go into the settings and figure this out myself. I can just tell an agent to do it. And that, you know, time is precious. And I try to accomplish a lot every day. And I don't want to be spending time wrestling with software. Can you say one or two specific concrete big light bulbs for you? So I think one of the light bulbs was around Notion and hiring. I had opened two or three headcount positions earlier this year. And, you know, we don't have an HR department. We're doing all the hiring ourselves. And so I needed an efficient way to just... manage the, manage the whole process. We use Notion for our, not just the job descriptions, but for the applications. And then how do we filter them and how do we post them and how do we, how do we do all these things? And I was really dreading it. I really was like, this is just going to be such a manual process. And, and, It was just going to be hours of sifting and going through things. And what we did was, I think it was Atlas was the first, was OpenAI's browser. Basically, you were like, just have it tell Notion to like, A, first of all, post the job. Because Notion is not my friend. Maybe I shouldn't say that, actually. You're allowed. Notion is our friend. Be honest. Notion is our friend, but not your friend. Notion... First of all, I mean, maybe at some point in this conversation, like Google Docs is just the thing that I have lived in for years. And as for, you know, there's a reason that Google Docs is still has the privacy that it has. It is so easy and so good. But really found that, like, if I was going to be having to spend an afternoon figuring out how to replicate a Notion page and get it up and get it in our database, like this was just going to be. a huge waste of time. And you were like, just tell Atlas to do it. And I was like, what do you mean? And I like, and I am that person who needs to sit next to you and you're like, open the computer, type it in. And then, and you're like, just type that. And you're very good. You don't do it for me. You, you're saying like, type in this. And then I'll, I know what I'm doing. Yeah. you you leave me you leave me to water and um and I did and it was like it like I mean you know I watched it think and I watched it like it needed access to a few things but you were just like it you know and then if it doesn't work I sort of assume that if something isn't working that it's my fault always like oh I did something wrong with technology and you're like oh no just ask it again or say you did it wrong do it again and I was like oh could talk to us and just be like, you were wrong. Try again. Um, and it really, it made that process so much more seamless, both like just getting the jobs up, which again, probably sounds super easy and mechanical, but like was, was just taking me a little bit of time. And then, you know, the very grateful to have hundreds of applicants. And I, you know, needed some ways to start to filter and understand, you know, what, what I, what I wanted to be looking for. I will say I did end up going through almost all of, I did actually end up looking through all the applications myself, but it was very different being able to be like, okay, these are sort of 10 flags of things I should look for. Not just like, okay, I have to go through a hundred and, and I'm, I'm really, I'm going to spend time on each of them. It just gave me a first pass. And then it gave me a way to sort of evaluate, like, here is everyone I'm looking at and I can evaluate it against this. Um, and it, it, you know, made it possible to hire people while at the same time doing my job. And I think that's, that is a pain point for startups, um, Um, where we all hire our own people, but you have hiring is so important and you never really have the time to spend on it that you wish you did. They should show you something about like the way my brain works and how much experience or lack thereof I've had at big companies. Like I really had not thought about the fact that HR is the one that recruits people. Mm hmm. And like I worked at a big enough company and hired a team with a big enough company that I probably I must have done that in the past. But I didn't really think I didn't just didn't think about that. Yeah. And yeah, there's always that thing where you're like, I can either do the job or hire the person to do the job, which is there's a very similar AI thing. Yeah. Where it's like I can either do it the way I know how or I can like potentially waste time trying to figure out how to get some someone or something else to do it. And yeah, it's been really interesting seeing that light bulb for you. Because I actually have a very similar light bulb with agent browsers in particular around just like settings panels. I'm just like not good at those. And I'm get asked all the time for like, can you have me to this role or can you do this thing? And I'm just like, really, I'm going to spend like 15 minutes of my day, like transitioning from whatever else I was thinking about to like the this console dashboard thing. And it's like not intuitive. And it's like, Alex just doesn't. I'm like, great. This is fun. Yeah. And it's very actually freeing for me to see that like, you're like, I'm not gonna, I don't know what the settings thing does. I'm just asking that and I'm like, Oh, that's like, I am someone who I clearly I know myself, I obviously learned by by doing and I also learned by like modeling. So like, it's important for me to I'm not necessarily going to be like, I can think of the five use cases by myself right here, but I will be able to be like, oh, we're using for editing and we're using it. How's the company using it? We're using for operations and we're using it for this. How do you use it for writing and editing currently? Great question. So I should say that as a team, we have ways of using it. And then my usage has shifted as... I have actually been able to have more of a team. So when it was, um, when I was the only editor, um, and working with our writers and, and maybe freelance editors, um, I really used AI as a way to try to enforce our editorial standards, um, um, more, more consistently across the board. What I was finding is I worked with, um, super talented freelance editors, but, but like, but sort of the, the, the work just came back at a different level from each of them just because they were different people and, you know, in very different backgrounds and not all sort of inculcated in the, in the company. And I was having to just spend a lot of time sort of get each draft, um, to a certain level. And it turns out that, again, AI, if you can, you can tell it your patterns and your roles, we basically created, I don't know if it was initially a chat, then it was a project, and then it was an artifact, basically, like, as each, as each, you know, new thing came out, but basically a project where we, for every draft before it came to me, if it was an internal writer, they would need to just like run it through our editor, which is, you know, we have a style guide. I'd written a style guide when I came here, it was just like 400 rules. And, you know, have it have it essentially transferred to this to this project. And then basically before something comes to me, have have the writers use you and editors use this this guide such that hopefully by the time it gets to me, the sort of floor has been. lifted yeah um as we have um been able to to build up a little bit more of a team and infrastructure i actually do that very little now but the editors who are on the team um and the writers do that themselves um so that's that is one key way um and then uh i mean and then there's lots of other ways i guess Well, I guess I'm curious if, you know, someone is listening to this or watching this and they are maybe they're an IC and they're like, I need to apply this to my writing and editing. Or maybe they want they're an IC now, but they want to manage like teams of writers and editors in the future. Or maybe they're currently managing teams of writers and editors in the future. Like. What do you think are the skills required that might be different from what you might have learned in English class or journalism school? And how are you setting up the editorial arm of every differently now than you might have before? And what does that look like? It's not really a newsroom, but what does a writer's room look like in this age that is different? Well, I think we, you know, we publish a newsletter daily and we are a pretty small team. Um, the team consists of myself, a managing editor, um, a senior editor writer, and then, um, another writer who also does our, who does a lot with, with AI. And so we all have to do a lot. And I think one thing that has been, you know, really clear is that a, like we need to know what are the standards that we're trying to enforce. And, we have to the thing is that if you are going to do that with ai you have to sort of um you have to be the one to teach the ai and you have to be the one to enforce it with ai and so i think something that we've really learned over the past months is like actually how let's say claude can read a style guide is maybe not in the lane is like not in like how i would normally write a style guide but actually just needs to be like structured slightly differently to actually get um the work done the way we want it to There's been an incredible amount of trial and error of like, okay, it might not work this way the first time. It needs to work this way the second time. We expect our writers, again, the writers who are here, not necessarily freelance writers who are involved in our day-to-day, to also be using these systems themselves. They're going to work with an editor. But... They should know that there are both things that we are looking for from the perspective of, again, our style, but also like what makes a good every piece and having a really good sense. We have, we have guides to that, um, to say what are, what makes a great every piece, you know, is it from a, you know, first person perspective, is it from, you know, sharing expertise that has been earned, um, all sorts of things. And, um, yeah, So they, they, I think there's been a lot of like in, in, in newsrooms or traditional newsrooms, it's like, you're a reporter, you're an editor and you're, and the, the, you know, a reporter is never writing their own headlines. We are testing headlines. We test them with AI. We use AI to generate lots of ideas and then riff on them from there. I, again, not, not necessarily for full time with us or, or involved with us on a daily basis. But like, that is something we work with, with together as a team. Um, and I think, I think another thing that has been really important is like, you can set up these tools, but then you have to make sure people use them. Yeah. There are different things. That's really different. Yeah. And sort of being the person who's like, okay, you know, can you confirm that, like, you use this tool before you send it to me? Because I don't want to, you know, I don't want to be looking at the same sort of changes that I always want to make. I think another thing that we have done is each week at our editorial meeting, and we've actually done. done this a little bit less now more recently, but particularly when we just had, you know, we're, we're sort of getting up to speed with this and had newer people coming on board, we would go through every piece we published that we, we would look at the, this, the head, the subject, the, the, you know, the headline, the deck, the subtitle and the lead, the introduction and be like, let's, let's break it down. And, you know, we, uh, Email is a primary delivery system for how we distribute our content. And so what that subject line is and what that first paragraph is that's going to keep you reading are just really, really important. We want people to read our stuff. And so we basically would go through each week... you know, head, deck, and lead of each piece and be like, was this good? Could it have been better? Did it work? Did it not work? And basically fed all of that feedback into our cloud project to be like, this is what we're looking for going forward. So we're really trying to train, as I like to say, like, You don't have to. It's not about accepting what AI says blindly at all. But it's like this is not it's not generic and it's not random. It's trained on our stuff and is trained on what's worked. And so your job as a writer or editor is to consider it. Yeah. Yeah. And to, again, not that the expectation is you have to accept it, but it's basically a stand in for another editor. And so you have to consider it. And if you don't think this suggestion is good, that's your prerogative. But like you, you need to wrestle with each of them. Totally. Like a way to summarize some of that is. Yeah. There is a way to use it where you're constantly pushing the best of your taste and your learnings into written artifacts that the AI can consume and that that can be used by writers and editors at the moment when they might eat it. Not as a never think for yourself tool or as a like just push out spam tool, but like actually just as a. here's the best of what we know from the past and what we've been able to write down. Like, does this help? Because a lot of times you're making repeated mistakes that it's like really helpful to have a little helpful friend that's like, hey, like Kate would probably say this, you know, without you having to do it. And I think that's really, really cool. And watching that kind of like blossom internally inside of the editorial organization is really cool. One thing that one experience I had recently that I think is cool that we haven't really had a chance to talk to you, but we do these vibe checks. Mm-hmm. Um, and so new models come out and, um, uh, we get them before they come out and we often have very little notice. And so it's like a, it's a scramble to do that. And recently had two models come out at the same time, Codex 5.3 and Opus 4.6. And we were like testing them just super intensely for like a week and then had like a very short amount of notice. So like we had to write the vibe checks. And one of the things that we do when we test these things is we just have a Discord channel where everyone's throwing their thoughts in. And I just had cowork like go in and summarize all that stuff into a notion doc that it was like constantly updating. And then I was able to like kind of vibe code that into a web, into a website for the vibe check. It was like the coolest thing. And then I sent the, I sent a PDF of the notion doc to one of these companies and it like caused it to like fact check. It wreaked havoc. Yeah. I unintentionally, it was like, I was like at 2 a.m. Here's like, here's our initial testing. Like, I just want to give you a heads up. And it was just, yeah, it was very funny. Sorry about that. If you're listening, I will not say who it was, but sorry about that. But yeah, I think we can go a lot faster and there's a lot more. There's a lot more like multimedia aspect of this. Like, you know, I was, you know, I was looking at, I was looking at the first article I ever published about AI, which is AI in the age of the individual 20. Yeah. 2022. And this was like a big deal. Yeah. So first of all, I think this is actually a really great articulation of exactly what I feel like right now. Like, I do feel like we have like I have like four computers at my disposal that are just like working all the time for me, especially with Clause. So I'm very happy about the call. And like, if you look at this, it's like, I don't like you're going to need vision, taste, ability to prioritize. It's like that's pretty good. having these kind of images was a big deal. And look, it has, it has, uh, the prompt in it, a man with four arms typing on four typers at once hyper-realistic. Like that was like a whole thing for a long time. And now that's just like the sort of like old hat. But I think there's something about the new expectations for, for publishing that is not just about the, the like processes, but also what you can, what you can produce at the small team. Yeah. And in what time frame. Yeah. And I think there was a whole era, like the Gawker era where it was like, every writer has to like publish like once a day or whatever. And it was like kind of. Once a day. My gosh, it was like maybe a whole time today. Yeah. And it was like shitty stuff basically. And I think that obviously we publish once a day, but. I think you can raise your standards for what is possible for a single person to do well in a short amount of time. Maybe not in like the gawker sense, but just in a like you can if you're the right kind of person and you've you've spent time with this, you can like write the article, make a really great image to go with it. Vibe code a website for it and then like do a little video. And like that's all possible now in a way that it wasn't. And the way and then the way that organizations support those kinds of people is different. And that's also really interesting. Yeah, I think as a company, we all really felt step change between late December and then early January. And we've written about this and we've talked about it with Opus 4.5 and Cloud Code and Co-Work. But I will say that I feel like we as a company have been sprinting from January 2nd or whatever day we came back. And just like... an absolute sprint where the amount that we are doing feels like we're just doing more. Yeah. You know, even this vibe check that you're talking about, you know, to be able to do all of that for two major models. So vibe checks are our version of breaking news. Like, that's it. That's like, you know, breaking news. The newsroom is, you know, on fire, so to speak. That's us. Model is coming. We know the embargo. We've got a plan for it. We know what we have to pull together. Yeah. And it's not always easy. We have a far flung team with really different perspectives. And most of whom are not professional writers and aren't writing is not their full-time job. So you're like pulling them away from their actual job to review it, which is like how we get good reviews. Cause it's like people that use this stuff for their job, but also it's like, you've you're you have a job and now we're going to be like tell us you know you need you to test it and then not only we need you to test it we need to like go over how we phrased it and make sure it actually captures what you said and all the rest um and um it just is like it really is this like monumental sort of cross-team effort and cross-functional effort and um You know, we we've been really investing a lot in our vibe checks and want them to feel like a special experience. So feel, you know, not just be the average, like our average post page, feel like a really different website experience and much more interactive. And we probably did that all in like 24 hours for two major models that released at exactly the same time. You know, normally we're just doing it for one. Yeah. Um, and so, you know, certainly had to take ups along the way and we, we learned a lot for, for what we can do going forward. But it was, it was a huge, huge, uh, it was a huge effort. Are you using your claw? I am not using my claw. Did you ever use your claw? No, I have one though. What's his name? Strunk. Strunk. I think you told me that that's hilarious. That is the best. Okay. We've got to find some, I have some claw ideas for you. I didn't talk about it. I haven't used it, but. I think that Strunk could actually be a good copy editor inside of proof, this markdown editor I've been building, along with your, with the style guide. But anyway, that probably comes in a little while. Yeah. Okay. Okay. Um, but we got to get you to your, for your claw magic moment. I need my claw magic moment. Um, I, uh, yeah, I have one. And again, I, it's like, I have been taken by the hand, helped to set it up here. I have it. I know what to do. I know technically what to do with it. And, um, as soon as I asked it to do something and it needed to integrate with one of my apps and it, it need, it was like needing something that I didn't have immediately. I was like, I'm not going to focus on this right now. What is your prediction for at what point I will finally succeed in automating your copy editing? I mean, I don't certainly hire higher odds this year than at any point. I think the challenges is both the challenges sort of twofold. One is like just consistency. Right. You've always had trouble with just like is it consistently capturing and not just like making errors. Yeah. And then the other is the judgment. Yeah. You know, I, we haven't talked that much about taste and that's been obviously like such a such a big word, important word, loaded word. But often at least when I am reading a piece and I'm reading everything before it goes on the site, like it's the first time I'm seeing it, which is by the way, great. That's like, cause I used to be like in involved in every piece of the, in the heavy editing of it. And that just wasn't sustainable for, for after a while. And so if I'm seeing it for the first time after it's been edited, like, And it's basically been through our process. That's a huge win. But I am reading it not just for, oh, how does it, it's the copy, I'm reading it like, how is this piece? Does it fit? I want to be super clear. I'm talking very specifically about this, the repeated little copy edits that you do all the time that I think you shouldn't have to spend your time on. No, I appreciate that. You've long said, like, there are other things you could be doing. What I end up doing, though, is like I'm basically reading something for the first time and then doing a top edit at the same time. And so it's just like those steps are conflated for me versus like if I have read the draft and then I'm like, great, just like have a mechanical copy editor copy edit. I'm going to say June. Hi, it's what February? June of this year. That's my goal. Okay. I think the models are almost there. I mean, they're certainly closer than they have been before. Closer than they have been. Absolutely. Yeah. I mean, I will say you were hoping for this vibe check, this double vibe check that we published. You were like, we're not going to use Google Docs. And I was like, absolutely not. This is not the time. I'm going to get what I want at some point. Maybe not on something that bad. My only problem is that Google Docs is not AI friendly. Yes. And I don't like that. That's fair. That's fair. It's not. Any final words before we sign off? Any final words? Gosh, I don't know. I'm just really excited about the future. Um... you know, our, the recent time, the, you know, more recent time and whether that's six months or nine months, I don't know exactly what the time period is. Like, it's been really sort of fun and exciting because I haven't felt like, from an early stage perspective now, my previous companies were incredible companies, but like, you know, Strike was extremely established. But like an early stage company of being like, is this working? You know, is this working? And for a while, you know, you're just sort of like fumbling along, trying to figure out what will. And for the you know, this past moment in time, it's been like, OK, like it's working. It's working. And so, you know, let's keep doing this because this is working and let's do this better. And that has been really. really, you know, just really exciting and really, and really fulfilling. And, and, and I have had to learn, you know, whole different ways of doing my job, both because like, I do now manage people, so I'm not the IC anymore. And I have a lot of opinions about how I want things to be. And so I need that to be clear and articulated and instituted. And then also like, You know, every time you're like, there's a new model coming, I'm like, oh, my gosh. OK, let's check the calendar. What do we have going on? You know, like just try to keep up. Just try to keep up with everything that's everything that's happening. Well, it's been a pleasure doing this with you and excited for what comes next. Me too. Oh my gosh, folks, you absolutely positively have to smash that like button and subscribe to AI and I. Why? Because this show is the epitome of awesomeness. It's like finding a treasure chest in your backyard. But instead of gold, it's filled with pure unadulterated knowledge bombs about chat GPT. Every episode is a roller coaster of emotions, insights, and laughter that will leave you on the edge of your seat, craving for more. It's not just a show. It's a journey into the future with Dan Shipper as the captain of the spaceship. So do yourself a favor. Hit like, smash subscribe, and strap in for the ride of your life. And now, without any further ado, let me just say, Dan, I'm absolutely hopelessly in love with you.