# The Exact AI Skills This Solo Founder Uses to Build 5 Apps at Once | Josh Pigford

## Метаданные

- **Канал:** Peter Yang
- **YouTube:** https://www.youtube.com/watch?v=GdxLaeyu33c
- **Дата:** 31.05.2026
- **Длительность:** 31:33
- **Просмотры:** 6,315

## Описание

Josh sold his last startup for $4M and is now building 5 products solo with agents. He showed me his exact AI skills stack, including a 4-step /build skill, an /adversarial-code-review skill where he pits Opus against GPT, a /but-for-real skill that makes the AI catch its own mistakes, and a /learnings skill that improves AI’s output over time. Josh has been a solo builder for 25 years and it was fascinating to watch how he works.

Josh and I talked about:
(00:00) Why launching fast beats months of planning
(01:02) A tour of the 5 AI products Josh built solo
(05:22) /build skill: Research, plan, track, implement
(10:52) /adversarial-code-review skill: Getting GPT to review Opus' code
(16:02) /learnings skill: Make AI update its own CLAUDE.md
(16:47) /but-for-real skill: Make AI fix its own mistakes
(19:11) Live demo: How to design non AI slop websites
(28:55) Advice for builders without technical experience

Thanks to our sponsors:
Oceans: Hire AI-native EAs http://oceanstalent.com/peter
Wispr Flow: Don't type, just speak https://ref.wisprflow.ai/peteryang
Linear: The AI agent platform for modern teams. https://linear.app/behind-the-craft

Get the takeaways: https://creatoreconomy.so/p/the-exact-ai-skills-this-solo-founder-uses-josh-pigford

Get my personal AI operating system with all my skills and prompts: https://www.behindthecraft.com/

Where to find Josh:
X: https://x.com/Shpigford
Website: https://initialcommit.co/

Subscribe to this channel — more interviews coming soon!

## Содержание

### [0:00](https://www.youtube.com/watch?v=GdxLaeyu33c) Why launching fast beats months of planning

It's terrifying launching something. I've been doing it for 25 years, launched hundreds of different products, and like every single time it's just like, "God, like what if zero people care? " I'm like textbook ADHD. Now I can just sort of like feed the beast a little bit more. I use Opus for the bulk of everything. I'll then do a review pass using GPT 3. 5, and it invariably finds three to five bugs that Opus overlooked. And then I'll run But for Real, and that But for Real skill is basically like kind of bullies the AI, the LLM into like, "You almost certainly screwed some stuff up. " — How long do you work on it before you put it out there? — There's been stuff where I've launched within 24 hours, or even like same day. The idea of like spending months working on something before you put it out for other people to use, I think that's a real bad idea. — Hey everyone, I'm really excited today to chat with Josh who sold his last startup Baremetrics for 4 million, and is now building at least five AI products in parallel. Josh is going to show us exactly how he builds with AI as a solo founder. So, welcome, sir. — Hey, thanks for having me, Peter.

### [1:02](https://www.youtube.com/watch?v=GdxLaeyu33c&t=62s) A tour of the 5 AI products Josh built solo

— All right, Josh. So, maybe to start, can you give us a super quick tour of some of the products that you're working on right now? — So, today, I actually launched this. It's called Proxy User. So, this is sort of like synthetic users that use actual browsers to QA your apps. So, gives you a screen recording of it functioning or breaking, so you can fix stuff pretty quick. — Nice. — Last one, Friday, launched Rumored, which is, you know, everybody's sort of familiar with LLMs hallucinating. This catches them hallucinating about your brand, and so you can go and fix that. So, that could mean updates to copy on your website. It could mean publishing certain blog posts. It could be adding like schema code to your site. So, it monitors this stuff constantly and gives you updates about when you need to fix stuff. Let's see, replies, social This was I launched this earlier in the year. So, you know, I happen to get a decent amount of uh of replies and uh mentions of all the different products that I've mentioned that I build, but it's hard to stay on top of that stuff. Uh so this puts it all in one place. So this is like a health thing here. So I built this last month or so like so my mom was recently diagnosed with stage four pancreatic cancer, um which is pretty terrible, but there's just already like massive amounts of medical stuff to sift through. Every single day there's some new thing. So you know, I had initially thought like let me dump all this stuff in like Claude code, but then it's like well how do I give my parents access to that? And then like, you know, grandparents and who want to keep up to date or like my mom's siblings like that kind of stuff. So built this uh tool to keep everybody up to date. You can um you know, chat with all the different medical documents. — Yeah, there's a big need for sure. My parents have the same problem like I need to track all their doctor notes and stuff. Nice. — All right, dude. So let me ask you the question on people's heads then. How do you work on all these products at the same time? And I guess like do you feel like your attention's distracted from all these products or like it's just the way it is now with age? It's you just kind of work on all this stuff at the same time. — I'm like uh textbook ADHD. Like so my brain naturally already is just ping-ponging all over the place. Like just it all and always has. Now I can just sort of like feed the beast a little bit more, which is pros and cons to that, but I think for me, you know, it depends on the day. Like some days I can feel myself a lot of days like I'm more mentally exhausted because I'm context switching a lot, but at the same time I find myself also simultaneously maybe more fulfilled. Like so like you mentioned Baremetrics at the beginning here. So like that was a business analytics company I built over the course of seven years, I think. So I was essentially working on one thing for seven years. And I was just done. Like I was tired of working on one thing for seven years. And um and so it's like my I already I just have so many different interests and like I'm desperate to constantly learn new things and I find myself limited if I have to sort of like focus on one thing. Now, is that the best business move? I don't know. There's an argument that no, it's a terrible idea. Um you know, if you want to grow something to be as profitable as possible, okay, you know, you should focus. Whatever. From like a defining success perspective, I find much more fulfillment in sort of having my hand in a lot of different things. — Yeah, we talked about uh we talked about how like a typical a great day for both of us is just like, you know, working in a garden and also working at the agency. It's kind of similar, right? Like in the garden, you're trying to grow like multiple plants. And then here, you're trying to grow multiple products, you know. — That's exactly it. Yep. — Yeah. Yeah, so I would love for you to show us how you kind of build these features end to end using conductor or these other tools. — This episode is brought to you by WhisperFlow. WhisperFlow saves me at least 3 hours a week and is one of my favorite AI apps by far. It's just so much faster to dictate to AI using your voice than to type. You just talk naturally and it outputs clean, ready to send text. WhisperFlow even removes filler words and formats your sentences for you. I use WhisperFlow for everything including drafting newsletter posts, writing product specs, replying on Slack, and more. It works on Mac, Windows, iPhone, and Android across all of your favorite apps. Try it free at whisperflow. com and use my code Peter WhisperFlow to get 6 months free. That's Peter WhisperFlow. Now, back to our

### [5:22](https://www.youtube.com/watch?v=GdxLaeyu33c&t=322s) /build skill: Research, plan, track, implement

episode. — Sure, absolutely. So, um we'll kind of go in reverse here. So, I have this build skill, which is an it's open source. It's like a GitHub um that has these that you can see kind of here. It's prob- probably pretty small on the screen, but um these like research phases, planning, implementation. And what those do is um they've each got different sort of sets of instructions. So, when you first build like in this case I was like, "Okay, I want to build this Botblock implementation into Reply Social. " Um and what the output of that initial thing was a research document. So, this went and took my previous code base that I'd already built out for the now defunct Botblock product. Uh used that and then kind of like also merged that in with the Reply Social code base and did a bunch of research over you know, sort of high-level technical stuff, different API calls you might need, pros and cons, what you could ignore from the original sort of Chrome extension, what needed to be brought over, how those systems would interact, but it's high-level. So, that's what gets generated first is just a research document. From there, I run an implementation command from that build skill. — Mhm. — And that gets into like narrows into uh different phases. So, it creates in this case there's a there's four different phases that it's going to implement this in. These are going to be four different pull requests, four separate branches essentially in Git, so that it's not trying to do all of this in one massive pass. It's doing them in these sort of contained chunks that I can um that I can verify. — Yeah. — Yeah, so and the way that I have that um that build skill set up is I've told it to make phases that are user testable. So, um sometimes like these implementation docs will have 30-plus different phases because I want to at each step I need to personally be able to test it out. So, you know, I have stuff in place here to like as part of its build process, it will open up a browser, it'll do some testing itself, but like I at the end of the day need to be sort of like the final uh — To play with it. Yeah. — Yeah, I need to just I need to feel right or like, "Oh, this is a really slow. Like this loads really slow. Like we're missing something here or this doesn't work the way that I pictured it. " Whatever. Um — And as part of your process, do you review these do you read through these documents or was saying? — You don't have to read through the whole thing. — Yeah, so I will I'll do like a quick scan. — Um, okay. — Till I make sure that it's especially not so much these tasks that it generates, but like uh the objectives. And like it's there's another step here that actually doesn't get saved in a document, but so like if I want to work on phase one here, I would write like build phase one bot block. So that says build phase one from this implementation document uh from the bot block sort of project. So like I have these other ones which was like uh adding Facebook support, adding Reddit support, uh adding this like marketing tools thing. These are like self separate self-contained things. So what phase what saying to build the phases is to like okay, take this phase chunk from implementation and now do even deeper research. So this is like go do web searching. So this is, you know, to check like competitor stuff, like who else has this feature, how have they implemented it? Do searching for like uh latest [snorts] documentation. So this might be using context seven for that. Then um this also has uses that UI. sh skill. So this is like do a design pass, like what needs to be accounted for here as far as like colors and components and all that kind of stuff. So it's incredibly in-depth. Yeah. So then that's what does the actual building is this like build phase. And um the byproduct of that is after each step is done, it updates the progress file that includes all the stuff that was done in that phase. It includes these decisions made. So you know, I'll go back and forth. These aren't like a one-shot thing. Like I'll have to iterate as I'm going and it will take these like oh, here's things that the system learned as it was going and it adds that to the progress file. — And the reason for the progress file is so that it can have like not make the same mistakes and it can refer to this. — So not make the same mistakes, but also like each one of these so after I did phase one, I would need to do phase two, I'm opening up a new work tree that it doesn't have any other context. Like it doesn't know what was done. And so this lets it reference future phases reference the past phases to know where it's at in the whole implementation plan. — Okay, got it. So basically okay, so just to summarize, research is kind of like yeah research and then implementation is basically kind of like a spec, like a product technical spec. And then you always have like three or four phases. What what's the reason to start a new work tree per phase? Like it's just to save the tokens or — What was the reason? No, it's So like I think of a work tree as a shippable thing. Like something I'm going to push to production or yeah, there's lots of different sort of use cases there. But like for me, it needs to be self-contained because yes, in part because of context, but a lot of this is also like rolling back. So like if I screw up a bunch of stuff, it gives me checkpoints that I can roll back to. — Oh, I see. — Um so it's like save points essentially. But yeah, each time it's like fresh so that there's not yeah, context rot. It hallucinates a lot less. Um — Got it. So each phase is kind of like a PR that then you play test, I guess. Yeah? — Absolutely. Each one is 100% a PR.

### [10:52](https://www.youtube.com/watch?v=GdxLaeyu33c&t=652s) /adversarial-code-review skill: Getting GPT to review Opus' code

Yeah, so like I'll So my process here is I use Opus for the bulk of everything. It does all the planning. It does the first pass on everything. And then after it's built out the code in that work tree, I'll then do a review pass using GPT 5. 5. So it does a sort of like adversarial review of everything in the work tree. And it invariably finds, you know, three to five bugs that Opus overlooked. And then after that, yeah, it gets merged in. — Also, you have a you have another scale or is that part of your build scale too? Like or yeah? — inside Conductor, but it'll show like a little review button and you can set a review model. So, there's a default model. Yeah, so then you can pick however whatever you want. This is what I found works best for me. — Okay. — And so, that's very much part of the process is like big first pass by Opus, have GPT basically find all the gaps that were missed, and then yeah, push it into a pull request. — Yeah, I was going to ask you why you're using conductor because, you know, Codex and Claude are both pretty good now, but I guess like it has these features, right? You can switch between models. — I can switch a lot. Yeah, and the like automated work tree management stuff. So, every one of these each time I open a work tree, it's running a set up command that goes creates like it's got a unique port, so I can be running 10 of these at the same time and open them all separately in different browsers. It's copying over environment variables, you know, depending on iOS stuff, it's setting up different processes. Like, there's just a bunch of setup stuff that happens automatically that's really convenient. — And you pretty much use this build process the planning process for like every feature that you build or — Yes. So, the that's like anytime there's a new if it's just so like take clearly for instance, um we can I'll show you kind of how interesting thing there. So, clearly is open source, so there's tons of feature requests that people put into GitHub. So, there's a GitHub integration here, so I can see things that people have requested. So, then what I can what I'll do here is I have for sort of one-off things. So, here somebody wants a zoom feature on these like mermaid diagrams. So, what I'll do is I'll just attach it here, and then I have a research skill that basically kind of pulled out something from like my overall build skill, but like pulls in the GitHub stuff, goes and does a bunch of web search, UI stuff, document searching, and then I basically just have it Yeah, it starts researching this stuff and like decides how to integrate it and build it out. It'll give me a plan and then I'll approve it and — When you say it look at like sometimes look at how competitors do it, it would like go browse the website I guess. — It's doing like actual web searching. Yeah, and then it'll browse, read it, sometimes take screenshots if like it just determines as necessary. — I actually did something pretty similar like cuz Substack right now doesn't have a API. It's like pretty backwards. So to implement like off on my website, Substack off, I had to like go research how other people do it and then like Codex figured it out. — Yeah. Yeah, it's pretty crazy. — Yeah. And your build skills are open source you said? So it's on GitHub? — Everything is. Yeah, all any skills that I've like personally put together are all bundled. There's probably a dozen of them. — Do you have like some sort of a Well, I guess I'm not using you know cloud code, but like I was going to ask you like do you have some sort of a cloud. md or agents. md where it's like a list of best practices like you know, always write tests or like something like that? — Yes, but like it's very I'm happy to show it. It's super rails focused cuz that tends my stack is like rails plus inertia and postgress. — Okay. Got it. — But it is very rails focused and it covers a lot of like best practices on rails, but also like how I like to do testing which is like I use agent browser to open things up and then like it specifically mentions conductor has some variables like conductor ports that are unique and so it needs to mention that kind of stuff. Like it's just like stuff I've picked up over the years. — Do you mind showing it for just a second? Yeah. — Every So as part of like my project setup process, I get it to create a unique cloud file, but like from the same general template. So it's give some context about what the product is so it just knows what it's talking about like what the actual product is. — User personas. Yeah. — Yeah, basically just like how to speak in marketing, that kind of thing. In this case, so this is like a mono repo that's got a web app and an iOS app. So, basically gives direction up front of like where things are. So, that's important. — Okay. — Um different commands that it will need access to. So, it'll have a tendency to want to use certain commands that it thinks are like typical for a given app. Uh for or for given like framework or something like that. So, this clarifies what to use and when to use it, how to run different tests. — And this is not stuff that you manually type down, right? This is like stuff that you — No, this is generated itself. But I it's like told to like here are the big Here's the shape of the document. Fill it out for me. — Okay. — yeah, basically how to do things. Um mentioning the — that So, it's actually pretty long.

### [16:02](https://www.youtube.com/watch?v=GdxLaeyu33c&t=962s) /learnings skill: Make AI update its own CLAUDE.md

Yeah. — Yeah, it is pretty long. Um and a lot of it's like So, I keep mentioning new skills here. So, what I'll do a lot of times is I have a separate learnings skill. And so, it takes the current work tree after I've gone through it all, like done shipped that phase, I'll run this learnings skill, and it basically says like look at all the stuff that was done in this work tree, look at our conversations, like our actual sessions, the stuff that I had to sit there and like tell you over and over like no, that didn't work. Try this. That didn't work. — Yeah. — And if it basically says review all this stuff and distill it into anything that we might could add to the Claude file so that you don't keep making these same mistakes. Uh — Oh, that that's very smart. Yeah. That — Yeah, so the Claude file is constantly getting updated. — And is this learning Is learning skill open source, too? Or or I guess

### [16:47](https://www.youtube.com/watch?v=GdxLaeyu33c&t=1007s) /but-for-real skill: Make AI fix its own mistakes

people would just use it. Yeah. — It is. Um and also, there's another major one that I This is again a sort of like the adversarial like method here, but I have a but for real skill that I run. So, like I'll it'll do the plan, uh it'll implement the plan, and then I'll run but for real. And that but for real skill is basically like kind of bullies the AI, the LLM, into like hey man, like you almost certainly screwed some stuff up. Like go back over it again. Um, and it'll find three to five bugs. Which is separate from the like GPT review process. There's a lot of just being like making it go back over stuff again. — Yeah, cuz this is like uh, you know, for a human to review like, you know, a lot of code is takes a long time, but for a lot of them it's just — I The way I think about it is like in a typical sort of a team setting where you're both working on a uh, or both, I mean like your whole team of people you could have three, five, 10 developers working on a project or hundreds. You make a pull request and then like the concept there is you have a you have another developer review it, right? Like you get another set of eyes on it. And invariably they'll find something or be like, "Ah, it's like this isn't really like how I would do it. " Or here's another way to do it. And it's just doing that, but having the AI play that role instead of another human. — That's great, dude. That's great. Do you mind showing this skill? This this skill sounds pretty interesting to me. Do you have the empty file? — So, I have this other open source Mac app called Chops. Which is basically just handling skill files. — Oh, nice. — So, these are all the different skills um, that I use. But like, yeah. So, for instance, this like butt for real one. — Yeah. — Do you get AI to write this? Or — Uh-huh. But I I iterated over a bunch. So, like Chops has this built-in sort of AI iterator where I can just open up Chops and like have the AI keep you know, give it some kind of guidance over like be meaner or something. And it'll, you know, it'll update the whole thing. So. Um. — Wow, this is my favorite skill I've seen so far from you. — It's shocking how good it is. And it kind of feels good to like cuz when you're really frustrated how it just keeps breaking stuff and like, you know, whatever. It's a machine, but — Yeah, you kind of have to be mean to it sometimes, right? Like I'm pretty nice to him. Like, "Hey, please do this. Please do that. " But yeah, if you could just keep going and — a breaking point though and you know, I'll end up typing in all caps. Like it cares. — Um, how about let let me ask you a little bit more about the is part. You

### [19:11](https://www.youtube.com/watch?v=GdxLaeyu33c&t=1151s) Live demo: How to design non AI slop websites

said, "Do you get it to make some sort of design system thing first like some sort of, you know, or you just use that thing? Cuz like a landing page you need copy, you need to like the colors, the fonts. Do you do it step by step or — Um, so the way that my design process typically works here is um I Like I have to have a name first whatever I'm working on. Um, and then like this is like a new if we've got a new business or project or whatever. So name uh a logo logos are 99% of the time done in Adobe Illustrator. Like I I'm just like in there you know, doing actual uh using the pen tool and going through a thousand different fonts and all that kind of stuff. Um, I haven't found a great way to shortcut that really. Then so that involves some color scheme stuff too. Like that's where I'm typically setting figuring out like the colors that I want before I've touched any code. So this is for Rumored. So where this started was me trying out a bunch of different fonts. Uh, and I kind of landed on this like okay like quotes like the concept being that like LLMs are just like saying things out of context or quoting you incorrectly or, you know, so that the idea of like quoting is kind of what stuck in my head. — Yeah. So I started playing around with different fonts then like okay well which typefaces have sort of interesting quotation marks. So I just went through a bunch of them and you know, they all end up kind of running together. looking the same. — But I kind of landed on uh liking this particular typeface and it's So then I start playing around with um colors. So I'm just trying out different, you know, light dark colored black and white whatever. So that's end up on there. Then I decide I like this sort of deeper orange. So then I start throwing that in a different scenarios, trying out these textures. Here's what it would look like with just in like a sort of avatar favicon kind of scenario. And so this is where I end up picking, again, like I've designed or built nothing. It's just brand stuff. Um and that's where I end up landing on that. And then I take that and say like here are the colors that I want. Um here's the logo like SVG files. And I and then I'll jump into code. — Then you're like maybe working on the value prop the copy and stuff with the with AI, right? — Correct. Yeah, yeah. And I'll, you know, I the marketing page stuff is kind of interesting cuz it's I usually do that after I've built the app because I'm like figuring out what the app actually does. You know, I'll have a high-level idea of what I want, but like how that actually translates into features is there's a whole, you know, it's a multiple days of iterating on that. And so then after I've feel really solid in that, I'll then say like let's generate a marketing site. Here's again brand stuff. I like the these textures. I kind of want this like urgent sort of tech not like military is the wrong word here, but this is a sort of like a little bit more sort of edgy like not soft typical. — Yeah. — So I like that sort of vibe. Now also like look through the entire feature set of the app we've built and like generate marketing copy. — Oh, that's interesting. That's really interesting because um that those are what I was going to ask you next like like what kind of MVP or how do you evaluate demand? But it sounds like you actually just built the product first. — Let us build the whole thing. Cuz I guess it's cheap now to build the whole thing with the AI. Just Sure. — Hey yeah, I mean which is that is not always been the case. — Um — But I still think people have a tendency to want like it's terrifying launching something period. — Yeah. — You know, I've been doing it for 25 years, launched hundreds of stuff uh different products. And like every single time it's just like ah like what if zero people care? That sucks. Uh and so as humans we tend to delay that stuff by having a landing page where we collect email addresses and then like try to translate that into demand or something and it's just not. Um it's a distraction. So, I just suck it up, build the thing, and shove it out there and see what happens. — So, yeah. So, like yeah, you're like a serial builder and um So, ba- basically, my understanding is you pay kind of just like build something to solve your own problems. And then you just build it a landing page and then maybe like how do you get eyeballs? demand? Do you um — It's social media. I mean, yeah, you know, I got whatever 60,000 followers on uh Twitter and it's like that helps get it started at least. — And do you worry that like you know, like does this still happen to you? You launch something and no one cares? Like — Oh, absolutely. Oh, man, yeah. — For sure. And some of this is like that's not because what I have to what I battle against is not that like I think if I I'm so quick to like move on to other things that um I'll stop talking about something and then like just people forget about it. So, like where I um sort of need to like do better is you talking more about the things that exist that I've built already instead of just, you know, building new stuff. Um — And do you usually launch something with like a paid version or are you just kind of like how do you know what what's product market fit, you know? — Right. I yes, I try to always have a paid version of something. The open source stuff is kind of like clearly for instance like the Markdown editor, um I don't know that I'll ever charge for that. Um it doesn't cost me anything. So, but anything that has some sort of hosted, you know, infrastructure, servers that have costs, I yeah, I charge for it and hopefully somebody pays for it. And if they don't, then like it gets to a point where it's like, "Okay, well, then like I'll shut it down. " — I got it. Do you worry that um one thing like, you know, I'm I'm much more of a novice builder, but one thing I worry is like maybe I need to get over this is like my reputation is on the line if I launch something shitty and no one cares about it. Like do you How do you get past that, you know? — Um I feel like I've just been I've been building stuff for so long that um, I don't I don't worry that somebody's going to like think it's dumb. It's just because everybody's different and like I might I have this itch, but I might be the only one who has the itch. So, that's fine. Doesn't invalidate that there's an itch, but like maybe there's not enough there to you know, cover the costs. I think that's where it comes down to for me is like does it pay for the servers that like Reply Social for instance has all these like API data sources that cost money and if it's not covering the cost like it's not a charity. Like I'm not it needs to cover its costs. Um, but that's kind of tends to be the the line for me is like okay, if I spent thousands of dollars just like fronting the costs of this and I still can't get anybody to pay for it then like uh, I probably need to rethink some stuff. — But if you have some paying customers and you shut down then you just have to send them an email be like hey, you know, I'm sorry. — Yeah, which sucks. Like I I do try to be a little sensitive to that where if somebody's paying for something, you know, what I'll do is if I shut it down then I just refund them the past few months or something. Um, it doesn't take away from the fact that they now don't have access to a tool that they needed, but so that's sort of the reality of business as well as like things yeah, I'm not paying for other people to use it. — I think one thing I worry about you even just with the Substack newsletter like I used to have a monthly subscription. And then people are just like if you charge too low like a couple of you know, 20 bucks or something then people are just like hey, I want to refund I want to refund. And there's just like a ton of support that comes in. It's just a pain in the ass. So, eventually I decided to just like charge a couple hundred bucks. Like if you can't afford it then you know, yeah, do you have that kind of yeah. — Yes, so um, that which is like that's very typical of like any kind of product stuff is like the these like really low cost plans tend to have the highest uh support overhead. — Yeah. Uh but I guess for your like since you have five products or like you know how you manage like um you probably do you have a support email for each so you like do you worry about just like managing support? Yeah. — No, so like I do have a central or I have an email address for each service that all just comes to my inbox. I also um man I'm I'm sounding like a shill here for all my skills. I have a skill that generates an entire in-app chat support system within your app. So people can like it's like Intercom replacement but like inside the app. So um people can just chat inside the app and it sends it to there's a whole like support well but it's still just me in there but like I'm not having to um I it lets me do more efficient support because I have the context of their account inside that chat and uh you know I also can kind of um compartmentalize it like I'm ready to work on support for this product. Okay, let me go other product. — Got it. Okay. Yeah, it feels like um as a solo builder anything that you don't want to spend time doing you can just kind of build a scale to try to — try to automate as much as possible. — Yeah, I think like you know the AI has leveled the playing field in a lot of ways. Um — Yeah. — but at the same time I think like I'm able to do things very efficiently because I've got 25 years of you know sort of boots on the ground like experience in the trenches of like building all these things pre-AI and so I like I know the general shape of how I want things to work and so I can very quickly get to that point and decide like this is going to work fine or this won't is going to be a real problem in a couple of months, you know, whatever. So um I can get to like a shippable point on stuff or fix problems pretty quickly just because I've dealt with these problems pre-AI, I think. — Just a few more questions. Um

### [28:55](https://www.youtube.com/watch?v=GdxLaeyu33c&t=1735s) Advice for builders without technical experience

I think there's going to be a lot more builders now, right? Like if people who are who don't have like 15 years of experience like you you do. Like do you have any advice for them uh as they kind of vibe code all this stuff? Like how can they actually learn some of the technical stuff that's actually important to work with the agents? Yeah. — Yeah, I think it's just failing a lot. So like people give, you know, they use like vibe coding as like a slur. And like the reality is that's fan- it's fantastic that anybody's building anything and the only way that they'll ever figure out what not to do is by doing the thing incorrectly. Um I think uh any kind of like AI-assisted coding reduces the number of mistakes that you'll make, but like this idea that mistakes didn't exist pre-AI is insane. So, um I think it's just making the mistakes as fast as you can and recognizing what the mistake was so that you don't repeat it. Um but you know, there's no like real replacement to just jumping in there and doing it. And I think and like putting stuff out there. So the idea of like spending months working on something before you put it out for other people to use, I think that's a real bad idea. Um there's no reason not to just throw it out there now um and see what happens. — Well, what you say like a lot of projects you worked on, like how long do you work on it before you just put it out there? Like like a week or something or a couple days even? — There's been stuff where I've launched within 24 hours. Like uh or even like same day. Um that's not always possible, but as fast as I can, absolutely. Yeah. — That that's actually something I struggle with, too. Like I kind of want to make it really good and perfect, but then like maybe no one cares. Like so yeah, you can launch fast. — [snorts] — Yeah, and there's so many times where you'll build something based on your own assumption of what the problem is and maybe it solves the problem exactly for you, but what the problem is for somebody else is similar, but like it looks a little different and you can't know what that is until somebody else is in there and it's like, "Well, what about this use case? " Like, "Oh, I hadn't thought of that. " Well, yeah, cuz it's somebody else. And so, you just need to get those other perspectives as fast as possible. — That's good advice. All right, dude. What Where can people find you online? your projects? — Sure. The the best place is just on Twitter. So, uh @shpigford. Um I I'm just, you know, I post there a hundred times a day and talk about all my products and stuff there. And my bio's got all the links to my 50 different things going. — I also really like your blog everydayisayear. ai is is very well written and very practical. And uh I love the rats ball open claw and we can talk about that next. — Yeah. — Perfect. — Yeah. All right, Justin. Thank you so much, man. — Thanks for having me, Peter.

---
*Источник: https://ekstraktznaniy.ru/video/51917*