The Product OS

0:00 Now, in this video, I want to walk you through the full process, my exact system, in a definitive guide on exactly how to build real software with AI, not just five coded AI. How to decide exactly what you should be building, and how to get it in front of real paying customers, or how to get it actually working inside of your business. I'm going to be doing this using my exact system, which is called Product OS.

0:20 Now, this is going to be a long one, and there's going to be chapter notes down below in the description so that you can follow along in multiple sessions if you want to. And so I'm going to be breaking down the exact system that I use to build and launch any type of software using AI tools like cloud code, codex, and can. It's going to be a full step-by-step walkthrough to build real software using these AI tools and deploy them.

0:40 It can give you the confidence that they are actually going to work, and also to show you exactly how you can do the exact same thing, and either start making money from the software that you build, or get it set up so that you can start using it to grow your business. And if you don't know me, my name is Chris, and for the last 15 years, I've been working with and advising and designing real apps and software for startups.

1:00 I've gone on to exit for millions of dollars, raised millions of dollars, including Y Combinator backed startups as well. And so with that all said, let's jump straight into the full process. I'll walk you through every single step that you need to do here, how to set up product OS, and how to build any software with AI inside of your business, or to get real customers. Let's get stuck in. So before we get started, I want to just give you an idea of why you might want to listen to me.

1:00 Well, I have been running a design agency called Telescope for the last five years. And this is a growth and design agency. We've helped over 50 high growth startups, including Y Combinator backed startups, not only just design apps and software that actually work for their users, but to grow and scale their businesses, their technology businesses, and their software products to thousands and thousands of users. Helped these companies to build products that have allowed them to exit for millions of dollars, and to help design products that won Apple design awards, and allowed them to raise millions of dollars as well.

1:40 And what is amazing about the time that we're in now is that anyone can build these type of software companies and these types of software using AI tools. And although everyone is saying that software is dead because of AI agents, I actually think the very opposite is true. There is going to be more software than ever. There's going to be more people building software than ever. And what I've seen from speaking to hundreds and hundreds of people through my community and across a bunch of different industries, is that there is just so much demand still for really, really good software that solves a really, really clear problem.

2:00 That is targeted at a specific type of customer. And so the opportunity right now to build software with AI, not just in the traditional sense, but also alongside a lot of other AI tools, is just massive. And if you have any knowledge or expertise in a specific field, then you are going to have a software idea inside of your head, inside of all that experience and knowledge that you already have, that is going to be able to be built and help hundreds and hundreds of other people to solve their problems, and also either turn into a software business in itself, or help you to build a business that is powered by software, that enables you to grow even faster, all because of these AI tools like cloud code, codex, and can.

2:20 Now, I've also helped hundreds of people inside of my own community. We've had people who have got real sign ups for their apps, so seven sign ups. We've got people who have launched real iOS apps. We've got people who have made over $15,000 from lifetime deals when they launched their products. We've had people who have created short form content that's got them hundreds of thousands of views for their app that they've launched. People who have built and launched their first apps on their app stores.

2:20 People who have built software for other businesses and landed $10,000 deals for the 23k add on. People who have launched startups that are making $10k plus, and actually things like that. And people who have even accidentally made their first $1,000 with their app because what they built was something that people actually wanted. And they were able to find the right people to actually take their idea to and put it in front of them. And that is the entire reason I'm doing this video.

2:40 And it's the entire reason why I've built this process that I use to do this called Product OS, to help you build and launch real software that is actually useful to people and agents. And to turn that into a software company or to empower your own business. And just to show you that this is. I've done myself as well. I've actually launched multiple apps, including making over $1,000 in just 30 days from launching my own apps and turning my own expertise into a sellable software product.

5:10 And this is just some quick screenshots from last year from the dashboard, basically showing the amount that I had made from this software. I actually decided not to continue growing this software because my business ran in a different direction, but just to show you how possible this is, and that you can do it too. And so what are the problems with actually building software with AI? Well, I think there are four key problems that I have managed to solve with this system.

5:40 And that is firstly, that you can build anything with AI. And so we want to be in a position where we know exactly what to build. So let's figure out what is the right thing for us to build, and what is the right way for us to actually get it in front of people and get it in front of real paying customers. Or, what is the right way to determine if this is something that we're going to build that's actually going to work for our business.

6:10 And instead of jumping between every single different tool, just to build something that we know is going to work. The second problem is that building fast is no longer the advantage. Yes, anyone can build software in, you know, 24 hours. AI created a system to build any application in 24 hours. But the difficult part is not just building something now. You know, you can just have an idea and then build it in a few hours with AI.

6:40 But you want to be able to build something that people and agents actually want to use. And that process, that a little bit of time, and I've baked into Product OS, the steps to figure out how to actually do that. The third problem is that you don't, if you especially if you're non-technical. I imagine a lot of people watching this will probably be non-technical. And will not know how to code. And that's okay, because the new type of software engineer, the people who are going to be building, using these AI powered tools like Claw Code, Codex and Cursor.

7:20 And because you're non-technical, you have no confidence that whatever you build is going to be scalable, secure, or even works. There's a lot of fear around, will what I build even work for people, and is it secure enough to not have to basically not have any risk of leaking data or any of these other things? So we want to be able to build on the tech stack with tech and follow a process that's going to give you the confidence that will building actually works.

7:50 And is going to follow a process that you can trust every step of the way. The fourth problem is that you are launching to silence. So people will build something, they'll get it live, they'll put it out there, and then nobody actually responds. Either because it's the wrong channel, the wrong target customer, or the positioning and the business strategy and the pricing strategy behind their app was just completely wrong in the first place. So we want to fix those issues, and we want to map out the exact path to your first $5k.

8:20 Either making $5k through the software that you build. Or making an additional $5k through your business by using that software inside it. And so those are the problems with building with AI and the solutions that I have figured out with Product OS and using this process to actually solve these problems. And this is it. And this has all been put together off the back of working with hundreds of people, taking people through my coaching program, the Product Studio, and also working with people inside of my builders Academy over on school to figure out exactly where people are getting stuck.

8:50 How to help people the best to actually build real software and get it in front of real paying customers, and to implement it inside of their business. And so here are the steps we're going to actually be going through in this video. And we're going to be going through four key phases. The first phase is called Define, which is about what is the idea that we're building? Let's figure out if it's actually got legs. Let's figure out if the pricing strategy and the business strategy is correct, and let's quickly validate it to figure out if anybody actually wants this.

9:30 The second phase is called Design, which is where we create our design system, our design style before we actually build the product. And we create a minimum viable brand identity for our product, a logo, a visual style, a worldview, to help us actually differentiate ourselves in the market. Or to align with our own businesses brand identity and visual direction. And the third part of design is about mapping out our onboarding flow for our product. As well as anything else we might need, like a landing page or our App Store listing, if we're building a mobile app.

10:10 And these are the key touch points from a design point of view, when we think about a product that is successful. And these are the key touch points that I have seen have the most impact to focus on for any early stage startup, which is your onboarding flow, your landing page. And the first product experience that converts someone into becoming what we call an activated user. I.E. someone who is going to use your software on a regular basis.

10:30 And then again, we want to do a quick validation here. Share designs with someone, get some feedback with some from, get some feedback from the people that we shared our idea with initially to see if we're going in the right direction. Then the third phase in Product OS is called Develop, which is where we create the. across software in this basically includes a PID and a roadmap file as well as a product vision document which outlines our vision for the products that we're building as well as our Claude and Agent's dot MD files which are going to guide our coding agents in exactly how to build the software that we want to create.

10:20 And we're going to build the MVP using is it a scale to build the full thing for us from scratch through the entire roadmap. We're going to test and improve this software that we've built and then we're going to deploy our project live to a real environment where either customers can access it or people in our business can access it and use it on their teams. And this is all using skills inside of the product OS systems.

11:00 So this used the launch checklist field just to map out exactly the step-by-step process that you can use to get your software live. And again then we're going to do a quick validation, some sort on waitlist, launch or comment, basically a comment and if you're interested to get people to sign up to actually access the thing that you've built. And you can even record a quick demo video here showing the actual software that you've built and a part of it or some of its interactions, to get people a little bit excited about what you've built.

12:00 The fourth part of product OS is the distribution phase, where we're going to go through these three kind of key steps which I have seen work from all of the early stage startups that I have worked with in the past, which is basically first to figure out your go-to market strategy. What are the channels you should focus on and how should you prioritize your efforts in terms of the best place for you to market your product to.

12:40 Second is is turning those channels into a set of growth experiments that you can run very very quickly to figure out what is going to work. So not an experiment broadly across a wide range of channels, a wide range of types of different creatives, different headlines, different videos, different messages, different all of these different things to find essentially to find something that works as quickly as possible. And then once we've found something that works, we will then automate it so that we can scale to more and more people.

13:40 And this means doubling down on what works, doing more of what works, doing better at what works and then using AI to automate it so that we can actually scale. And this is my full process for building a product from ideas to in to distribution, which is called, which is called Product OS. And this is what I teach inside of my coaching program, the product studio as well. We go through this full thing in about 30 to 60 days, get your product up and running and then spend a ton of time figuring out the distribution part or how to embed it inside of your actual business to make sure that it works and it's going to get you at least that minimum of 5K return on building any piece of software.

15:00 And so what are we going to actually build in this video today? What I want to build a product based on my own expertise, which sits primarily in this space of design. I'm going to show you how to set up product OS inside of an existing codebase or inside of a fresh project, which is what we're going to do from here. We're going to set up a fresh project, bring that installed Product OS, and I'm going to show you how to go through all of these steps inside of the process, define, design, develop, and distribute.

15:20 So that by the end of this video, we're going to have a working piece of software which we can deploy to a live environment that has a go-to market strategy mapped out for us, a set of growth experiments and a plan for how to automate and scale that as well as full confidence from us that we have built this in the right way, is a professional level of design quality and that we are building the exact right thing that is going to work for us as a product to either turn into a software business or to unlock our own business by using software inside of it.

15:20 And so my idea that I'm going to be building because I have this design background in product and building apps and software with companies and with the early stage startups is I want to solve this problem that I have seen in white coding, which is low consistency of design styles across multiple projects. Across building websites, landing pages, apps, software, all of these different things, even marketing creatives. Because there is no shared source of truth for your AI agents when it comes to design.

15:20 There is no design system and brand guidelines that exist that your coding agent can access on a regular basis in order to design everything in a way that matches that. And I'm going to build this so that I can use it myself. Primarily, but also so that I can get customers for this and start to grow it as a separate software product alongside my existing business. And later I have this idea that I want to do and of a product design like audit platform as well.

15:20 But the first thing I'm going to start off with is this cloud-based design system app idea. And I'm going to show you exactly how to build it. And don't worry if you have a slightly different type of app idea if you're building something more with agents. You can still follow this exact process. This process is called Product OS for a reason because it's not app OS. It's not just about building apps. It's about building real products.

15:00 that actually work and a product is not just a an app on the App Store. A product can be a set of AI skills, a combination of agents and skills, it can be a combination of services and software, it can be any of these different types of combinations that will work for your business. It could be a set of internal tools that your team uses to automate work so that they can scale and produce more content, for example, or introduce efficiencies into your team.

15:20 There's a ton of stuff that you can do with this. But what I've got here is something I like to call the product offer, which is the starting point for any product idea. And it's the starting point for our entire process here. Once you've found an idea, to then create the product offer and figure out exactly who the customer is, who what the pain is that you're solving, what the outcome is that you're getting that customer, what the mechanism is that you're going to use to do that.

15:40 Then any proof that you have that this is going to work. And any guarantee that you can offer in order to minimize the risk for your customers for the products that you're building. And this product offer is the single most important thing that I think you can create before you actually go into building any piece of software, whether that's to bring in front of customers or whether that's for your own business. That's why it's the first part of the product OS.

16:00 It's why it's the first part of my coaching program that I take people on. And we create your product offer, we map out your exact path through product OS. And this is where it's slightly different. You're just setting up product OS following this video. And you'll get the generic product OS set up. If you're doing this inside of my coaching program, for each person, we will create a specific, custom plan tailored to your idea, tailored to your path.

16:20 And it can also work if you're already building something, but you've just got stuck. Most people have already started building, and they're just stuck. They don't know what to do next. So product OS and my product studio coaching program is exactly tailored for this as well. So we can kind of pick up exactly where you are in your existing product, based on whatever you're stuck with. To get you to a point where you're making five to fifty K from your product idea, either inside of your business, for has a software business.

16:40 So what are the tools that you're going to need? Well, the tools that you're going to need if you want to follow along with this video, is we're going to be building a web app. And we're going to be building this web app based on these pieces of tech. And there are alternatives that you can use down here as well, if you want to. So I'm going to be using Claude code as my primary agent to build my app, where you can use kind of several codex alternatively.

17:00 I'm also going to be using convex as my database and back-end layer. You can alternatively use Supabase, Cloudfare, or Firebase. I would highly recommend combat, convex, because convex lives inside of your coding base, which means it is super easy for your agent, which means it is super easy for Claude code, codex or curser to make changes to your back end or database without you having to go to a separate dashboard somewhere else. I'm going to be using clerk for my authentication layer, but I think it is the easiest one to set up when you're building apps.

17:20 But alternatively, you could use Supabase, convex, or workflow as or better off. There's a bunch of different authentication providers out there. For payments, I'm going to be using stripe to manage payments. But you can alternatively use polar or autumn. I'm going to be use I'm going to be using stripe minute payments because this is the easiest setup to get started with. And for deployment, we're going to be using BSL. Again, because this is this, this is the easiest setup to get started with.

17:40 And but alternatively, you could also use something like railway or for render. But if you're building more enterprise grade applications, you could build use something like AWS or Google Cloud platform as well. And the assistant that we're going to be using is called product OS, which is my full system of skills, context, documentation, and guidelines to build, launch, and scale any product using these AI coding tools, regardless of your level of coding experience. And I want to explicitly state that here as well, is that you do not need to know how to code to be able to do this.

18:00 You can get started with any of these tools. You don't have to look at any of the code. You just need to understand some of the fundamentals, and that's what we're going to be able to cover going through this, so that you can follow along easily, step by step, as we go. So with that all covered, now that we've got all of the basics out of the way, you know who I am, and problem we're solving, how to build using product OS, the idea that I'm going to be building here, and the tools that you need to start building to follow along with this process.

18:40 Let's get stuck into the actual build and start building our app idea with product OS. So the first thing we're going to want to do is you're going to want to set up product OS. And we're going to get our product folder created on our machine. So the first thing we're going to do here is create a folder wherever you want the folder for this project to live. Just create a folder there. I've created a folder and I've called it I dropper dash app, because the app is going to be called I dropper and that is the folder that I want to build this in.

19:00 Next, we're going to want to set up product OS inside of this folder. So we're going to want to install product OS. uh and product OS. is a Claude, a Codex, and a cursor plugin. And there are instructions in the README as well as to exactly how to install the plugin for each of these. I'm going to be using Claude code to build. Well, you want to install Product OS inside of this project here. So, what you're going to want to do is you're going to want to go to the Product OS GitHub repository.

20:19 And this is saying it's private for now, but this is going to be publicly available by the time you're you're watching this video. So you'll be able to get that from a link in the description down below. You're going to want to download Product OS. Once you have downloaded Product OS, you're going to get this Product OS main zip. Now, what you need to do is you need to go over to Claude code in the desktop app.

20:39 Now, you can do this with the terminal, but for most people, and especially non-technical people, the easiest way to build software with AI is going to be inside of the desktop apps. So Codex, Claude code, and cursor. So you're going to want to get hold of the Claude desktop app if you don't already have it. If you don't have it, you can just go to Claude.ai/download. And this is where you can download the Claude desktop app.

21:01 Just click download here, and then install it. That way. And you're going to get the Claude desktop app here. Now, let me collapse all of these projects inside of the Claude desktop app here. And what we're going to do is we're going to click new. And if you haven't already used Claude code inside the Claude desktop app already, you're going to basically start off on this home screen, and you're just going to want to click onto code on the right hand side here.

21:22 That is going to take you into Claude code here. And all I'm going to want to do first is I'm actually going to install Product OS as a plugin. So we're going to want to go to this customize link in the left hand navigation here. And then you go, scroll all the way down and go to plugins at the bottom here. Go to add, and then upload plugin here. And then I want you to drag and drop that zip file for Product OS into Claude here.

21:46 And that is going to allow us to upload Product OS as a plugin to use inside of the Claude desktop app. And this is all of the skills inside of Product OS, which we can use by typing forward slash and then naming the skill in chat. And basically, all of these are named by the phase inside of Product OS that we're going to be doing. So we've got define here, design, develop, and distribute, as well as a bunch of other skills inside of Product OS that you can use.

22:33 And now that that's installed, let's go through actually setting up inside of our project. So now that we've added that plugin, let's go to new here inside of Claude code. And I want to go to my local folder, because I'm going to be building this locally. And I also want to choose the iDropper app folder that we set up before. So I'm going to open this iDropper app folder here. So this is the project that we're going to be working inside of inside of Claude code.

22:56 And then all I'm going to do here inside of this iDropper app folder is just do forward slash studio, setup. And that is going to set up Product OS inside of this project. Now, I do have this set to Fable 5 and high, which I would recommend using as you go through these skills. But you can also use it with Opus 5 and get really good results with Product OS. I'm also going to set the mode here to auto slide.

23:13 Don't have to keep doing mission requests as we go through. And this studio setup skill will basically copy all the files from Product OS over to your project folder. And it will guide you through getting started with Product OS to build your product. And the first thing we're going to do here inside of Product OS is to create this product offer that we're talking about. So that we can understand our product in a lot more detail.

23:39 We're going to do on product offer, we're going to figure out our pricing strategy, and we're going to dig deeper into our customer persona as well. And this information is really going to help us figure out the right direction to go with our piece of software before we start building anything. And this is the part that most people skip, is actually figuring out how do you build the right thing before we actually start writing any code at all.

24:08 So it's now said Product OS is installed and wired into your new iDropper app repo. So here's what setup did. It created the repo. iDropper app was an empty folder, so it started A, it did Git init, which basically initializes Git. If you don't know what Git is, or GitHub, basically Git is a version history control for any sort of code or file based projects that lives locally on your computer. And you can use it to manage your versions as you build or to build new things, and you can also roll back to previous versions if you need to as well.

24:36 So it kind of gives you that control. And it also allows you to get your project into GitHub, which we're going to need to do later in order to deploy it using Vercel. And the studio setup skill here in Product OS will basically just set all this up for you. Is wired the right route guidelines. So basically it's installed a Claude.MD and an agents.MD file. And this is a set of instructions built on top of the carpathy at four rule Claude.MD file, as well as a few additions from Product OS, including secure by default and design fidelity as well as this intro piece about design about product OS here.

25:08 This is going to be your basically your guide and set of instructions for building your product. And if you're using Codex or cursor, you're going to use an agent.md file as well here. It's also get ignored by the system. So what this means is that it excludes product OS when you actually push your app live, when you get your app, when you get your code base into GitHub and when you deploy your code to a live environment, it's going to ignore all of the product OS files, so none of this stuff is going to be uploaded to your repository.

25:43 And it says no plan shipped because it's got no custom plan from myself, from going through the product studio, which is my coaching program. You're basically starting from scratch here with product OS, which is completely fine because you can pick and choose what you want to do, but if you do want that custom plan, that is something that I do as part of my coaching program. So the first action here is to go into the define section.

26:12 So what we're going to do is we're going to work through these sections one by one. We're going to start with define, and then we're going to go into design, we're then going to go into develop our actual products, and we're then going to go into distribution. So let's start off with define, and inside of product OS, this is basically a checklist file with every step that you need to do through each phase. Although I do think it will still be super valuable for them to have the free tier here.

5:40 It's something that I'm a definitely used. I don't think we'd. So it started off, I actually wanted to make coloring books as quickly as possible because the coloring book creation process was really painfully slow. You used to have to use like chat GPT to generate every image one at a time. You had to generate like 40 at a time, so it could take like hours and you'd get rate limited. So I discovered make.com where I could build my own make.com automations to create coloring books.

6:10 And through that, I decided, you know, I could really turn this into an app or a software. And I just went down the whole rabbit hole of vibe coding and building things out. I started off with like Bolt and like these various tools. Tell me learned how to do this. And then eventually, and then eventually I ended up, uh, launching the software and in. And the ban from the persona is 29 to 49 and a hard ceiling around 100.

5:40 Might propose all 29 per month, uh, brand. So reasoning is Sam's supplemental slot for a tool in my stack is 20 to 25 and $29 sits one notch above. Enough to signal that this covers the whole team and every project, not enough to trigger the compare with Claude, Max. Flinch. And launch, you want a number low enough that the split screen demo closes the deal on the spot because your first 100 customers are worth far more as proof than has revenue.

7:00 Now, if we get 100 customers at 49, that is 4,900. So we're going to have to aim and this is where we want to do a little bit of reverse math here to figure out. If our ideal starting point is say $5,000 per month, then okay, 100 customers of $49 dollars a month or $50 dollars a month, $100 dollars, 100 people at $50 dollars a month is $5,000. How feasible is it for us to get 100 people to use this on a team basis.

7:40 And are there any other ways that we could kind of go about this. So we could also do. Now, I think it's pretty feasible to be able to get 100 companies to spend $49 dollars on a tool that it's going to get them consistency across all of their services from a design point of view with all of their coding agencies. I also think for the amount of time and money that this is going to save teams, $49 dollars feels pretty low as well.

8:20 So I think maybe we should do it like 49 is the floor for founder pricing, and then 99 as like maybe for like the first 100 spots, let's say. So that we get our $5,000 MR. And we can get that pretty quickly. And then we up it to maybe 79 or 99 further down the line. So let's go with that instead. Let's go with 49 as as founder pricing for the first 100 spots here. And then 79 as post founder pricing after we've built.

5:33 Or, so it's done some research as you can see by the text above this question. I'll get into that in a bit more detail once we've answered this question as well here. The first question that we're being asked after we've confirmed our name direction and the name is going to be the first thing that you're asked to do here as part of the product identity is which world view or contrarian belief here is the brand's spine.

5:57 And there's two really powerful things about that come together that give a brand really its kind of character and soul and meaning. And these two things are your world view and your contrarian belief. So what do you see in the world? What is the And the gallery wall brand. I like it. I drop itself says monochrome and Swiss, so the customer's design system is the only color in the room. It also unifies everything because the literal i dropper is clear glass.

6:00 The color it carries is always yours. I really like that connection actually that Claude has helped to come up with here, that connection between here, and actual i dropper and the UI and we can lean into that kind of glass effect UI as well. Tone lock as a plate warm plain talk with a dash of deadpan. Let me run coherence checks and write the files. So now it's going to go through all of these things that we've defined as our brand.

7:00 So worldview is taste shouldn't depend on who's in the room. And then a belief is the system is infrastructure, not a document. And so the belief leads into the tone, which is an infrastructure conviction delivered in calm, dry plain talk. Degrees. We're going for deadpan plus Swiss minimal is a classic pairing. Dry wit lands hardest in stark type. So it's basically checking that all of these things work well together. All the decisions that we've made are going to work well in combination for our full brand identity.

8:00 And you can start to see how all of these small little decisions make a huge difference when it comes to the feel and the character of the brand. And this is going to be something that stands out versus everything else. We've got also the name, which is a precision instrument, clear until filled with the customer's pigment, the name is the visual concept, which is great. And then distinctiveness against zero hype, which is corporate SASS blue, frontify, which is an enterprise portal, Figma, which is a colorful dev tool, 21st.dev, which is a dark component grid, Moda, an on-brand, which is generic, and a monochrome Swiss with the borrowed color is a tell-up.

5:40 And that is why this super long video here is actually not too much focused on how do you build and do software development with Claude code. It's more focused on how do we define the idea properly. How do we design it? And then how do we get it live? How do we deploy it? Make sure all the tech works? And then how do we actually distribute it after we've got our app live? How do we start to think about distribution and do these mini launches along the way?

6:20 So you can see here that basically it's starting to set up our project. It's configured Tailwind config with the clear glass tokens, so it's taken our design.MD file and created all of the styles. And now it's going through building the rest of our app here, rest of our product. Now, I'm going to leave this to actually build. And this might take 30 minutes, 45 minutes to an hour to actually finish building the application. And I'm going to sort of jump in and out as and when I need to, based on what is happening with Claude code.

7:00 But for the most part, we can just put this to auto. Tell it to run this skill and it will go away. Run this develop MVP build skill. And it will just build it for us. And we don't have to do anything here. We can just come back to a 70 to 80 to 90% finished app. After about an hour of Claude code working by itself to actually build this for us. So, I'll stop there. And I'll come back in a bit.

7:40 Show you anything interesting. And then we'll see what this app looks like once Claude code has finished building it using this skill. Now, one thing I want to show you whilst Claude code is building this is that Claude code is going to use a number of different tools whilst it goes through and builds this at its disposal. To help validate and verify that things are working. It's going to start local development servers for you. So if you're not familiar with local development, that just basically means that it's going to build your app inside of code inside of this I dropper.

5:40 Well, we didn't actually use this dash in there anyway. Phase five made the package publish ready, but publishing was on the credential block list. NPM login was never done, so NPM publish never ran. Someone else claimed the name iDropper on 2025 published this and then our published it for me. Four minutes later. NPM keeps a tombstone record for unpublished packages. The name exists in the registry, but with zero versions. That's exactly what Eeno versions means and never registered name would give a plain 404 instead.

6:20 The good news, NPM only blocks reclaiming an unpublished name for 24 hours, and that was almost a year ago. So the name should be free to claim now. The only version number burned forever is this. So, we need to do the publish yourself since it requires my NPM credentials. Okay. All right. So I have my NPM account here. And this is, now that we've built MVP, this is now the tricky bit of getting all of these things wired up so that everything works correctly.

7:00 So we're going to do these two commands here. First, NPM login, so that we can log into our account in the terminal. And then second, to navigate to this folder and then do NPM publish. So, what I'm going to do is copy this code. I'm going to open up a new terminal here. And I'm going to do this outside of Claude code because this is going to give us a But if we're going to be delayed, we need to notify the client.

5:47 If we're going to need an extension, and if you don't, you lose money effectively. So all of this We're going to call this I dropper as the name. And this is going to be a repository for the I dropper app. And I'm also going to set this to private as well. Because this is going to be a commercial project. Where people, now if you're doing something where you're where you're doing this open source or you want to share the code, which is completely fine and a lot of projects are done that way as well.

6:04 Then you can set this to public. For this one, I'm going to set it to private. We're going to create this repository. We're going to create this repository. I'm going to copy this URL at the top up here as well. And then we're going to go back to Claude code. So this was never going to be a "put it on the App Store, 30 pound a month type product" because it's too integral to the business. So for us, that means our distribute phase is quite literally getting in the car and going to see these people.

5:52 You know, so at best, it will be doing demos over teams and so on. But actually, we need to get into the business with a scrap of paper with a sketch on. Creators, Greg Eisenberg's podcast, how a how AI show whose format is literally guest demoring their workflow. Our strong bench material for after a channel works, and SEO on the pay and vocabulary is real, but crowding fast. One strategic warning, the window is narrowing. Google open-sourced the design.md stack, Claude design added design system sync, and Zero High front five both shipped MCPS.

6:10 The research argues for speed on channels one and two, not polish. So this is an area where a lot of people are building, so we want to move fast. Since you couldn't confirm my channel hypothesis mid session, I proceeded on the launch is launch logs own read. Lead launch number two with X red continuation. If you'd ranked differently say