WEBVTT

00:00:00.240 --> 00:00:33.150
Cloud Code is one of the most powerful tools that I've ever used. Within my first week using it, I figured out how to automate my $1,000,000 per year software agency. Each client project of ours used to take a project manager, a designer, and a developer about six weeks. But now, one person with AI can do it in under an hour even if they have no technical expertise. So in this video, I'm gonna show you the exact agency model that I used to make multiple 7 figures, and then I'm gonna show you how to use Claude code to automate the service delivery and build a $10,000

00:00:33.150 --> 00:00:36.590
software MVP. From 2022 to 2025,

00:00:36.590 --> 00:01:08.630
I ran a software development agency that built software apps for creators with an audience. When we ran our agency, we basically had two ways to structure deals. First, we would charge our clients a monthly subscription, usually around $6,000 per month to build their app. Or second, if we really believed in the idea, we would take equity in the app instead. The monthly clients gave us cash flow so we could pay the bills and then the equity clients gave us long term upside in case one really worked out. And that thesis has worked out really well. One of the apps we had equity in was Atlas AI, and it's now making over $500,000

00:01:08.630 --> 00:01:35.170
per month. Now, I'm no longer part of the day to day team, so I really can't take any credit for its success, but I can show you why the model works so well. That's because the founder is Sebastian Georgiou. He is an ecommerce YouTuber with over a million subscribers. Now, besides the obvious baked in distribution he had from this channel, he had a few other unfair advantages that really mattered. First, he was his own customer. He had been doing ecommerce for years, so he deeply understood the problem that he was solving, and that made his product intuition

00:01:35.330 --> 00:01:38.465
really strong. Second, his network was massive,

00:01:38.545 --> 00:02:00.600
and interestingly, the main growth channel wasn't even his own YouTube channel. It was actually the other YouTube channels that he could sponsor. When you're a peer in a niche, people reply, people want to work with you, they give you favorable rates, and you get distribution way faster, and that's how we scaled. Partnering with creators to build software for them is advantageous because they understand the problem, they have distribution,

00:02:00.680 --> 00:02:08.435
and they have a network that can help you scale. And I really don't see too many people talking about this. Everyone is really trying to sell creators like short form editing,

00:02:08.515 --> 00:02:09.635
growth operating,

00:02:09.715 --> 00:02:25.660
or helping them sell paid courses, but almost nobody is offering to help them build software that their audience could use. And to me, that is your opportunity. If I was in college or starting a new business from scratch, this is what I'd do. I would pick a specific niche and look for educational creators in that space.

00:02:25.900 --> 00:02:35.020
Sebastian was in e commerce, but you could find a finance YouTuber and build them a budgeting app. You could find someone in video editing and build them a VFX marketplace.

00:02:35.545 --> 00:03:31.265
You could find someone in fitness and help them build a coaching tracker. Just pick a niche that interests you and send creators a simple message like, hey, I'd be down to build you a custom VFX marketplace. I'm a software developer and would be happy to build it in exchange for equity. It'd just be worth a quick chat. And by the way, creators do actually see your DMs. People think that if someone has a huge audience, they'll never actually read your message. That's just not true. As a creator myself with over 500,000 subscribers on YouTube, I maybe get five DMs a day, maybe. Today, I got three, and I read every single one of them. I have hired a lot of people from cold DMs, and if I don't, it's simply because I probably just don't need what that person is offering, not because I didn't see it. It. So there are really two takeaways here. One, large creators see your DMs. And two, there's really no one offering to build them their own apps. Now, if you're new, I wouldn't over complicate the deal structure. There's really three ways that you could go. Option one is a monthly build fee, maybe anywhere from 2 to $6,000

00:03:31.265 --> 00:03:57.410
per month depending on your skill level, the scope of the project, and how much proof you have. Option two is equity. If you really believe in the creator or the idea, then you can just build it in exchange for ownership. And then option three, which is probably my favorite, and that's a hybrid, a smaller monthly fee plus upside in the app. That way, you're not broke while you're building, but you still have exposure if the app really works. So that is the whole model. Creators bring the problem, the audience, and the distribution.

00:03:57.490 --> 00:04:39.205
You bring the software, the AI workflow, and execution. Now let me show you how this actually works because what makes this so exciting is that you don't need to be a senior engineer to run this business model. When we built software MVPs for clients, it usually took us around six weeks, and it usually happened in three phases. First, we needed to build a product requirement doc so we actually knew what we needed to build. Second, we actually needed to design the app. Then third, we started coding the back end functionality and started connecting everything together. That typically took a three person team around six weeks. But now, I'm gonna show you how to build a premium software MVP as a non technical person with Claude code in under an hour. The key is to automate each phase separately.

00:04:39.285 --> 00:05:17.880
So phase one is the PRD. When you start working with a new client, the first thing you need to do is make a list of everything they want to build. That is basically what a PRD or a product requirement document is. A PRD is a clear document that breaks down what the app is, who it's for, what features are needed, and what the first version should look like. Usually, this requires a project manager to talk to the client, ask questions, take detailed notes, and then write out a long document listing every feature we need to build. But now, we can automate pretty much all that process with AI. There are four steps. Get on a call with the creator, record the call with an AI notetaker, transcribe the meeting, then have AI turn that transcript into a PRD.

00:05:17.880 --> 00:05:33.555
I'm using Zapier for this because it's the easiest way for non technical people to automate this workflow. They also partnered with me on this video, but this is genuinely the tool I would use here because it's simple and fast. So let's build this in sixty seconds. So I'm gonna go to Zapier. I'm gonna hit create a new workflow.

00:05:33.955 --> 00:05:37.955
And then we're actually gonna search for fellow AI which is the AI notetaker I use.

00:05:38.355 --> 00:05:52.630
We're gonna connect our accounts, and then we're gonna choose new AI note as the trigger event. So now Zapier can access each meeting transcript from Fellow. So next, we need to send that transcript to Claude. So I'm gonna add a new step. I'm gonna select Anthropic.

00:05:53.095 --> 00:05:54.935
I will connect my account.

00:05:55.415 --> 00:05:58.695
And then I'm gonna choose the send message event.

00:05:58.775 --> 00:06:04.455
Okay? Next, we just need to hit configure. And then in the user message section, I'm gonna hit slash.

00:06:04.855 --> 00:06:11.690
And then I'm gonna select the transcript data point from Fellow. Okay? So this is how we send the call transcript to clot.

00:06:12.010 --> 00:06:18.570
Next, we need to add a system prompt so the AI actually knows how to turn the transcript into a PRD specifically.

00:06:18.570 --> 00:06:47.380
So I'm gonna paste in this prompt that I'll link in the description for free. Basically, it just says that you're a senior product manager and technical lead. You will be given a raw transcript of the client discovery meeting for a software MVP. I need you to convert it into a clear, build ready PRD. Okay? Now, there's a lot more underneath this. One thing I wanna point out is that there's a pro tip here that you can actually add your preferred tech stack into this prompt. So then when we give this to Claude to code it later, it automatically knows what back end, database, authentication payments,

00:06:47.725 --> 00:07:19.915
and hosting stack we want to use. But more on that later. Now, let's just select the cloud model I want to use and the PRD step is ready. The last thing we need to do is send the output to a Google Drive folder so we stay organized. It's gonna output this into a dot m d skill file so it's easy for AI to read. So I'm gonna add another step. I'm gonna click Google Drive and then I'm gonna choose the create folder event. Okay? I already made a folder in my drive called client PRDs so I'm gonna choose that. And then to stay organized, I'm gonna click folder name. I'll hit slash.

00:07:20.235 --> 00:07:39.700
And I'm actually gonna choose the attendee or the meeting title data from Fellow. That way it names the folder after each client or project. So now I just need one quick final step to actually save the PRD inside of the folder we just created. So again, I'm gonna add a step. I'm gonna choose Google Drive and choose create file from text.

00:07:40.420 --> 00:07:47.575
For the folder, we're gonna choose the folder ID we just created. For the file name, let's do something like PRD plus.

00:07:48.055 --> 00:08:11.935
Then I'll do slash the title from the fellow meeting. And now, the most important part, we need to actually pull the file content from Claude. So the output aka the PRD. So to do this, we'll just hit slash. We're gonna select Claude. And we're gonna choose response content. So it's the response that Claude gave us. Now, we just need to hit publish. And just like that, we can turn client meetings into beautifully written PRDs on autopilot.

00:08:11.935 --> 00:08:53.390
So I built this earlier and to give it a test, spun up a Google Meet on my calendar. I started the meeting. I hit record with Fellow, and then I just kinda talked through the features of a VFX marketplace, and then I ended the meeting. And now, when I look at Zap, I can see each step is firing. And if I go to my Google Drive, I can see the folder was created and the PRD is sitting right there. So phase one is done. We have a beautifully written PRD. And now, anytime I hop on a call with any future clients, I can just record that and immediately after the call, it's going to filter through everything we said and build a PRD that we can then just add to Cloud Code and have AI build for us. It's time for phase two. We're actually gonna start designing our app with AI. I'm gonna do this in Cloud Code by actually turning that PRD

00:08:53.390 --> 00:08:55.470
into a visual wireframe

00:08:55.550 --> 00:09:05.150
and get it a working app preview. So for this example, I'm gonna build a visual effects marketplace for a cinematography creator. Let's just assume the creator has a large audience of filmmakers

00:09:05.455 --> 00:09:36.375
they wanna help their audience find and buy VFX assets, overlays, and basically different editing packs. So I downloaded that PRD from my Google Drive. Now I'm gonna open the Claude app on my computer. I'm gonna click the code tab. I'm gonna upload the file, and then I'm gonna tell Claude to build this app for me based on the attached PRD, create a local host link so I can preview the app, and then hit enter. After a few minutes, Claude gives me a local host link so I can see what it looks like on my browser. So I'll click it, and now I can see that it built a pretty solid marketplace

00:09:36.775 --> 00:09:39.255
with the core features that I asked for.

00:09:39.815 --> 00:09:41.575
But if I click around,

00:09:41.975 --> 00:09:42.855
I see a big problem.

00:09:43.650 --> 00:09:45.570
Most AI built apps

00:09:45.730 --> 00:09:46.450
look

00:09:46.690 --> 00:10:18.970
AI built. You know, they have that generic low quality vibe coded feel and like the layout exists, the buttons are working, and the pages are here, but it does not feel premium. Okay? And if we're building software for a creator with a real audience and we're charging $6,000 per month, it cannot feel like a toy. Okay? So to make the app feel premium, I need to do two things. I need a brand kit and a component library. Okay? These will give the app an elevated feel and I can reuse these on every project in the future. Getting a brand kit, super simple. I'm just gonna go to Canva.

00:10:19.050 --> 00:10:21.930
I'm gonna hit templates and I'm gonna search brand

00:10:22.085 --> 00:10:22.965
guidelines.

00:10:22.965 --> 00:10:34.325
Now I'm just gonna look for one that I like. This one looks cool. And then I'll just go ahead and hit customize and then I'll save the brand guideline as a PDF on my computer. So this is gonna help me with the aesthetic, like the color palette and the typography.

00:10:34.690 --> 00:11:27.425
But now I wanna make sure that all the components in my app feel premium, so I'm gonna use a component library. Component libraries are collections of pre designed interface elements like buttons, drop down menus, cards, navigation bars, forms, dashboards, and modals that developers can reuse across software projects. So this can really become your style as a development agency. There are a ton of free component libraries to choose from on Figma. So I'm just gonna find one that fits the look that I want, and then I'm gonna open it up in Figma, and I'll just copy this Figma link. Okay? Now I'm gonna go back to Claude, and I'm gonna say redesign the app using this brand kit and this component library, and then I'm gonna upload the PDF from my brand kit, and I will paste that Figma link here, and I'll hit enter. And after a few iterations, the app already feels a lot less like a prototype and more like a real product. You can tell there's like a cohesive brand here that really feels familiar

00:11:27.425 --> 00:11:42.675
to videographers and cinematographers. Okay? This like black look, these sharp edges. If I even click on the checkout modal, can see how much more clean that looks, how the description looks better laid out, where the profiles are being displayed. I just think this is a much better feeling marketplace.

00:11:42.675 --> 00:12:17.025
And when you're building software at the end of the day, it's all about your taste and how good your product makes people feel. Okay? So I really want you guys to understand that. AI can give you the first version quickly, but the brand kit and the component library are what's gonna make it feel polished enough to really show to a client. So now that we have the UI designed, it's time to actually build the core functionality of the platform. And so, yeah, this all looks good but like I can click around but none of this stuff really actually works. So we can make it actually work. So since I'm building a marketplace, there are really two core things that I need. First, we need to set up payments so customers can transact on the marketplace.

00:12:17.185 --> 00:12:45.085
And then second, I want a chat system so buyers can actually talk to sellers about their orders. K? So and this is where most people get confused about AI coding. Like AI can make it easier to build the first version of an app but it does not magically solve the hardest parts of building real software. Try vibe coding a real chat system from scratch and see how fast it gets complicated. Like, at first, it's gonna feel simple. You send a message, the other person receives it, done. But then real users show up and you need real time delivery,

00:12:45.165 --> 00:12:46.205
notifications,

00:12:46.285 --> 00:12:48.380
file uploads, emojis,

00:12:48.380 --> 00:12:51.580
permissions, moderation, performance. It gets so confusing.

00:12:51.820 --> 00:13:10.865
And then the app needs to stay fast when like hundreds of thousands of people are using it at the same time. K? So these are not just features. These are infrastructure problems. And that is where AI coding tools still have limits. So Cloud Code and Cursor can help you build the app way faster, but if you ask them to build your own payments or your own messaging system from scratch,

00:13:11.105 --> 00:13:25.610
you're gonna run into problems. So the smarter move is not to ask AI to build every piece of infrastructure from zero. The smarter move is to just tell AI to plug in pre built components. So for this marketplace, I'm gonna embed WAP's pre built components for the hard infrastructure.

00:13:25.690 --> 00:13:33.435
Specifically, payments and chat. So first, let's set up payments. Since this is a marketplace, sellers are gonna need to be able to list products,

00:13:33.595 --> 00:14:07.375
collect payments, and then actually withdraw that money into their bank account. Okay? AKA pay ins and payouts. To set this up, I'm just gonna paste this prompt into Claude, basically saying I wanna use WAP's API to set up pay ins and payouts for my marketplace. Please use their SDK to embed checkout for every listing on my site so sellers can list their products, collect payment, and withdraw to their bank. And as I said before, all my prompts are in the description for free. So once I put that into Claude, it's gonna give me the steps I need to follow to get this set up. That's the nice thing about AI. It will just tell you step by step what you need to do. But really, I just need to go create a business on WAP.

00:14:07.615 --> 00:14:09.695
I'm gonna name it VFX Marketplace.

00:14:09.935 --> 00:14:11.695
I'm gonna hit the developer section.

00:14:12.335 --> 00:14:14.095
And then I'm gonna create an API key,

00:14:15.110 --> 00:14:16.630
set all permissions,

00:14:16.790 --> 00:14:19.590
and give it a name. I got that API key.

00:14:19.750 --> 00:14:30.525
I'm just gonna put this in Claude. And then it says I also need to get my business ID. So I'm just gonna go ahead and grab this from the URL on my dashboard. So it's just biz underscore

00:14:30.925 --> 00:14:39.165
long code. I will put that in Claude and I will hit enter. Okay. And then lastly, this thing, I just need to create a webhook secret key.

00:14:39.325 --> 00:14:40.605
So I'll go create a webhook.

00:14:41.110 --> 00:14:43.910
I'm gonna add the payments, memberships,

00:14:43.910 --> 00:14:45.510
and payouts permissions.

00:14:45.990 --> 00:14:56.915
And I'll hit create and I'll copy that inside of Cloud as well. Okay. Cool. So I just hit enter. It's running. And if we look at the site, you'll see that it looks like I can buy my products now. But if I actually hit purchase,

00:14:57.235 --> 00:15:15.500
it's just gonna say congrats. It never actually collected money. So we're setting this up right now. So WAP's embedded checkout will actually work in a platform. All of the checkouts are now embedded. If I go to a listing, I'm gonna refresh. We should see WAP's embedded checkout model so all the sellers can accept payment with credit card, crypto, cash app,

00:15:15.900 --> 00:15:31.845
and more just natively on the marketplace. Okay? So just like that, we have real payments infrastructure set up and people can actually get paid for the products. So it's awesome. It's really easy to do. And obviously, this is not just for a VFX marketplace. You could use this to create a marketplace like eBay or Airbnb,

00:15:31.845 --> 00:15:59.385
maybe a job listing platform like Fiverr, an affiliate network, a coaching marketplace, really whatever you want to do. Just really anything that involves people coming onto a platform and earning money, you can use this. So next, I wanna create a DM system so buyers can contact sellers and really just message them about their product. And this can also just be used for customer support if people aren't happy. So to embed the chat, again, just gonna use another prompt that I have, and that is just gonna basically say, I wanna add a DM feature where buyers can message sellers about their listing.

00:15:59.625 --> 00:16:01.305
I'm gonna put that into Claude,

00:16:01.465 --> 00:16:43.790
and this one should be pretty quick. There we go. Yeah. That was just a few minutes. And we have a message seller button on the checkout page. So now we have a real chat experience so sellers and buyers can message each other. But we actually need one more thing for this to actually work, and that is an account creation and sign in flow. People need to make their profiles so we know who can message who. So this is also called onboarding, and that's where I'm gonna start. And onboarding really matters because it's the user's first real experience with the product. If the flow is confusing, your conversion rate dies before people ever experience the core product. So It doesn't matter how good your product is, if your onboarding sucks, they never get there. K? So instead of guessing what the best onboarding flow in the world is, I'm just gonna take inspiration from the best apps in the world. And to do this, I'm gonna use a website called mobbin.com.

00:16:43.790 --> 00:17:09.960
Mobbin basically shows you the biggest software companies in the world onboarding flows page by page with screenshots of everything. So really all we have to do is find a company similar to ours, then we're gonna tell Claude to create a similar flow. Now, I'm gonna use my own design and I do not want to steal their IP, but there really is no harm in using the same general steps for account creation that the biggest software companies in the world use because they've invested millions of dollars in optimization. So I'm gonna search shop because it's a cool marketplace.

00:17:10.120 --> 00:17:11.640
I'm gonna hit flows

00:17:12.095 --> 00:17:14.655
and I'm gonna find the onboarding flow.

00:17:15.135 --> 00:17:19.055
Then I'll just take a few screenshots of each step. I'm gonna put this into Claude

00:17:19.615 --> 00:17:32.420
and I'm gonna say create an onboarding flow for our marketplace inspired by the structure. Alright. So now that step by step flow is created. Now we actually need to add the functionality of creating accounts. And to do that, we need to set up something called user authentication

00:17:32.500 --> 00:17:50.085
or OAuth. To set up authentication, I'm just gonna tell Claude, hey, help me set up authentication using WAP OAuth. Then again, I just follow the steps Claude gives me. I'm gonna go to the developer section again. I'm gonna hit create app this time. And then I'm gonna hit this tab up here called auth, A 0 U T H.

00:17:50.405 --> 00:17:52.805
And then we need to create the redirect URL.

00:17:53.390 --> 00:17:58.590
I'm just gonna paste in the local host link for now. It eventually it's gonna have to be my real domain but we'll do that later.

00:17:58.830 --> 00:18:38.425
Now I'm just gonna copy and paste the keys back into Claude and it should be able to get everything set up. And just like that, we now have our account creation and sign in flow functioning. So now users and sellers can come onto the platform, make an account and actually start using the marketplace. That is most of the functionality. People can create accounts, they can list products and actually collect payments and they can actually start talking to each other through the embedded chat. Now, the last two things we need to set up are actually our database and our hosting. So your database is where you store all your user information and data. For this app, that means sellers, product listings, purchases, categories, and whatever else the marketplace needs. Your database is very important And for this, I'm gonna use Supabase

00:18:38.425 --> 00:19:14.195
really just because it's very simple to set up. So I'm just gonna tell Claude, create my database using Supabase. Set up the schema for users, seller profiles, product listings, purchases, categories, and saved products. This way that when someone actually uploads a listing on the platform, it gets saved. So as usual, after I put that prompt in, I'm just gonna follow the steps Claude gives me. And if you're ever feeling stuck, you guys do remember that the Claude Chrome extension can just take control of your computer and do the steps for you. So it's not gonna tell you that, but if you just say, hey, just use the Chrome extension and do it for me, it will. So I'm gonna go ahead and create a super base project.

00:19:14.675 --> 00:19:16.755
I will add my environment variables,

00:19:17.510 --> 00:19:19.430
run the database migration,

00:19:19.910 --> 00:19:54.640
and now my database is set up. So the final step is really hosting the site. Okay? Up until now, I've been using local host to build the app. And if you try to share that link with anyone else, they'll not be able to open it because it's running locally on your computer. Hence why it's called local host. So to host a site and get it on a custom domain, I like to use Vercel because it's really easy. So I'm just gonna tell Claude, help me host this site on Vercel and connect it to a custom domain. So I already have a Vercel account and I'm already connected to the CLI. It's very simple. You just copy a code right when you make your account and put it into Claude.

00:19:54.880 --> 00:19:59.040
Now Claude has already made me my project. And then I'm just gonna go to domains.

00:19:59.195 --> 00:20:03.355
I'm And actually going to look for the domain I want. Okay. So it's purchase.

00:20:03.355 --> 00:20:05.355
Okay. So I purchased the domain.

00:20:05.515 --> 00:20:16.510
Now I just need to connect the domain and verify it. Just like that, my client's VFX marketplace is live. So hosting is very important. It's how you get your app off of Cloud Code and onto the live internet.

00:20:16.670 --> 00:20:27.230
And it's where all of the images that your sellers upload to promote their product will live. So hosting is very important. That is literally the first MVP that used to take my software agency

00:20:27.675 --> 00:20:30.075
six weeks to get into one of our client's hands,

00:20:30.555 --> 00:20:48.660
and every one of those projects required a team of three to four people. We had a project manager hop on the call to actually scope out the work and build the PRD. Then he would send that to our UI designer who'd have to manually design every single page in Figma. Then that Figma file got sent to our developers

00:20:48.740 --> 00:20:52.740
who would code the site and manually set up the database authorization

00:20:52.740 --> 00:20:57.295
payments chat and hosting. This is the part that's hard to overstate.

00:20:57.775 --> 00:21:00.255
AI did not just make coding faster,

00:21:00.575 --> 00:21:02.815
it compressed the entire

00:21:02.895 --> 00:21:08.095
workflow. My development agency's profit margins were roughly 55%

00:21:07.530 --> 00:21:09.770
and the main expense was headcount

00:21:10.090 --> 00:21:11.930
and this changes that

00:21:12.250 --> 00:21:13.050
drastically.

00:21:13.050 --> 00:21:24.685
And again, like I said, now that I've created the accounts for my tech stack in this first project, Clog can actually help me create new projects with the exact same design style, the same stack, and the same core infrastructure

00:21:24.925 --> 00:21:29.725
every time in the future. And to do that, all I have to do is embed my stack into every PRD

00:21:29.965 --> 00:21:34.605
inside of Zapier. Yeah. In theory, I could get on a call with a client, record the conversation,

00:21:34.845 --> 00:21:36.685
turn that call into a PRD,

00:21:36.925 --> 00:21:58.195
send that PRD to Claude, and have Claude build the entire first version of the app with my design style and my stack already baked in. That is what automated AI services actually look like. That means one person can now deliver what used to require a full agency team. And if you pair that with creators who already have distribution,

00:21:58.435 --> 00:22:08.195
you're not just building random software anymore. You're building something with built in demand. So I don't know about you, but to me, this is a really cool opportunity. AI helps you build faster. Creators can get you distribution.

00:22:08.630 --> 00:22:34.525
And then WAP just has all the infrastructure for you to use. Now, I didn't talk about getting customers in this video because I actually made a full course on how to automate your outreach with AI. That will be the first link in the description below. It's completely free to watch and it actually is a full course on how to start your own AI powered service business start to finish. It's one of the best pieces of content I think I've ever made and again, it's 100% free with the most up to date way to run an AI first agency.

00:22:34.525 --> 00:22:41.164
So again, that's in the description. Other than that, I hope you got value from today's video. Have a wonderful day, and I'll see you in the next one.
