You researched the thing. Research said "all systems go", here is your pricing, positioning, hooks and angles for marketing. So you build the offer. Now you need eyes on the offer. First, I suggest you pick 1 lane and go vertical 1) Only cold call 2) Only cold email These 2 are the fastest wins with the least upfront cost. Cold calling is free: If I was broke, with nothing, no offer, and an idea. I would pick up the phone and start calling people to see if they're is any interest [pain]. Then I can close a deal and now I'm paid to build the thing. $0 up-front... Just have thick skin and be prepared to "Mayweather" (boxer defense) the "EFF YOU!" when you do it. Personally, I'm a maniac and cold calling is a fun challenge for me Cold emailing you need to buy a warmed up inbox and/or warm up domains for a weeks. There are minimal costs involved but I'd set aside about $150 for a real shot at getting a system up and running the same day (I show the high level of how I do this in #Build A Lead Generating Machine Today ) 3) Run paid ads If you don't know what to do, and most people don't, you'll just loose a shit ton of money and blame the method instead of yourself. If you want to do this and you don't know what you're doing - I'd suggest against it. This is why: This is a form of pattern interrupt - people aren't actively seeking the solution. They may be in the market based on pixel data but they're not looking at the moment they see your ad. You're just bidding with other companies and whomever has the most money wins. Running paid ads is when you want to pour gasoline on something already working and you need another channel. 4) The Patience man's game and the ultimate, best form of traffic: SEO (search traffic) Search traffic is the ultimate high-intent traffic. People are actively looking for a solution to their problem but it can take months to gain traction. My YouTube channel is an example of that high-intent traffic and half this room came from it.

Yesterday, one of the members in Jake's Skool community, a fellow ICM builder name Eugene shared a GitHub repo with me. A Japanese digital business card for realtors. QR code, AI chat, mortgage calculator. Live site, real customers, 140 merged pull requests, still shipping daily. Nice build. So I spent some of the day working out how to make the Western version. Here's what I found instead. That product works because the company behind it is a Tokyo brokerage that already owned 4.5 million sales records and 6,000 new listings a day. The app is a skin on a filing cabinet they already had. Strip the data out and you have a link-in-bio page with a chatbot. In the US that data is MLS-licensed. You need a contract with every single MLS you want data from, even going through an aggregator. One company built 300+ connections to get coverage. A national feed runs low six figures a year and still has gaps. Fine. Skip the data. Except digital business cards are already Blinq at 4.9 stars across 150,000 reviews, with a free tier. And AI chat for realtors is Ylopo at $395 a month, Structurely at $300 to $1,000. Fine. Something smaller. Since 2024, buyers have to sign a written agreement about agent compensation before they tour a single house. Everyone's confused about it. Nobody has built the tool. I got genuinely excited about this one. Then I checked whether an agent is even allowed to explain a contract to a client. They are not. Explaining what a clause means is unauthorized practice of law, in all fifty states, and the agent handing it over is the one carrying the exposure. Insurers started adding generative-AI exclusions this January, so it wouldn't be covered either. I had the whole thing designed before I checked. It would have shipped. Six shapes, six different walls. Around the fifth one the pattern showed up. Every time, the moat was somebody else's data, or the thing was illegal for the person who'd be using it. Which left one place to stand. Whatever gets built stays on the agent's side of the table and never crosses over to the client.

You need to go watch this video, I think it's the biggest mistake I have seen people make, including me. Rymac brakes down the buyer awareness ladder. https://www.skool.com/buildmarketclose/classroom/4f32951c?md=8f45d31af05643a3bc0f144fc59fd4c9

I’ve been testing various skills on my Video Worker, which is part of a larger ICM-based Suite I’ve been building over the last few weeks. The idea started with a question: "Can I take the power of an ICM workspace and make it genuinely useful to someone who has no interest in becoming technical?" I had already built a collection of workers for myself — Conductor, Research, Writing, Transcription, Design, Builder, Video and Marketing. They grew out of my own needs as a teacher and content creator. Over time, I realized the real value wasn't any individual worker. It was that they shared context. Research could inform the Writer. The Writer could feed Design. A transcript could become content. Video could work from the same source material. Marketing could understand what had actually been created rather than starting from a generic prompt. The problem was that the architecture that made this possible was also the thing most non-technical users would never want to deal with. So I built a GUI over it and called it Quiet Scribe. The organizing concept is a nonfiction book. Not because everyone necessarily wants to become an author, but because a book is a great way to force knowledge into structure. Once that knowledge is captured and organized, the same context can become articles, posts, visuals, videos, a course, a website, or marketing material. My first demo failed pretty badly. 😂 The interface looked great, but exposing the workers through the GUI revealed architectural gaps I hadn't noticed while using them directly. That sent me into three days of auditing the workers: folder structures, instructions, retained context, unfinished changes, handoffs, and things we'd learned through use that had never made it back into the architecture. The second demo was probably 80% better. More interestingly, improving the underlying architecture improved what the workers could do together. The Video Worker in this clip, for example, can now take a long demo/transcript, work from timestamps, identify different storylines, and develop shorter video treatments from the source material.

I'm making a new video today, it's in production right now, and it's going to be fulfillment of what I "closed" Dr Chen on (ai front desk to capture missed calls). On deck: 1) I just rebranded the entire sales training module in Skool. 8 Videos with new skins, new packaged files, and descriptions with 1 prompt to Claude + Files + Folders. It's the ICM doing WORK. 1 prompt rebranded an entire training module. I just had to delete the old, upload the new, copy and paste the descriptions. (images attached) 2) My video production line: research -> script -> spec -> voice over -> uploads -> packaged files -> blog post - all done in 1 prompt, 2 approvals, 1 recording of audio, and I upload. Claude Code and the ICM structure does the rest. I did make a video of making a video while you watched me make the video you already saw the opener too...https://youtu.be/sCwd1uiOaLg?si=P--0_AbrI3AbLPjF The new one won't build in the terminal, it will be the updated production line and how it's structured so that I can type a few things and have a whole production line done with minimal effort on my end. If you have any things that you think I can help you or video ideas... I'm all ears! Well, eyes in the case but ya'.