AI Knowledge
Welcome to '🧲 Marketing Foundations', where we’ll transform your innovative product into a market-ready success story.
Start ReadingSteve Jobs stood on stage in 2001 holding a small white device. He could have said "5GB MP3 player with FireWire connectivity and 2MB cache buffer."
Instead he said: "1,000 songs in your pocket."
Same product. Completely different positioning. And it changed everything.
Microsoft's Zune had better specs, larger storage, wireless sharing. But their message was all about technical features. Apple's iPod had inferior technology but superior positioning.
It doesn't matter how good your product is if you can't communicate why someone should care about it. The best product doesn't win.
You've built something that works. Your beta testers love it. But if you can't explain it in a way that makes new people want it, you'll struggle to grow beyond your initial supporters.
This week is about fixing that gap - turning what you've built into something people understand and want. We’re putting together your basic marketing assets and getting ready to launch.
Let’s get started:
Building marketing assets for our waitlist launch
Component parts that become landing page
User language beats feature lists
Real outcomes over technical specifications
Descriptions that convert
This week we're gathering the marketing assets you need for your waitlist launch. Think of it like collecting the right ingredients before you cook - you need quality components before you can create something that works.
We’ll build towards an early bird waitlist launch to the communities that helped you during beta testing. That’s the goal. And to get there we need (deep breath):
Product descriptions using real user language (today)
Social proof from your beta testing (tomorrow)
Landing page assembly (Day 28) - this is when we actually build the page
Soft validation with champions (Day 29)
Waitlist launch to communities (Day 30)
We're not building the landing page yet! That's Day 28. Right now we're gathering the raw materials we'll need to make it effective.
We're also not launching payments yet - that's Week 7. This week is about building anticipation and collecting email addresses from people who want early access.
We’ll build up step by step to make this all doable!
OK first let’s get the language we use about our product locked in.
You've spent weeks building your product. You know every feature, every technical detail, every clever bit of functionality you've created.
We actually have all this language in our research, product specs and build guides from before. It’s all in our AI chats. And it’s super tempting to recycle. Don’t!
Your users don't care about any of that language.
They care about the outcome your product delivers to them. They care about the problem it solves and how it makes their life better. That’s it.
They don’t care about how you built it. What you used. What neat technical tricks are involved. When you describe your product using technical features, you're speaking your language, not theirs. When you use the exact words they used to describe their problems and outcomes, you're speaking their language. That’s the switch we need to make.
Look at your Week 5 feedback. Notice the difference between how you think about your product and how they describe what it does for them. You might say: "Advanced workflow optimisation with intelligent task delegation." Blurgh. They might say: "Finally, something that helps me stop dropping the ball on important projects."
Their version wins every time. And we’re going to use it.
Time to go back through all those conversations and feedback from Week 5. You're looking for three specific things:
Problem Language: How do they describe the issue you're solving? What exact words do they use? How do they explain it to others?
Outcome Language: When they talk about the results or benefits, what words come up repeatedly? How do they describe the change or improvement?
Emotional Language: What frustrations, relief, excitement, or other emotions come through in their feedback?
If three different people said your tool "saves time," use "saves time." If they said it "stops the chaos," use "stops the chaos." We want to mirror their exact words in what comes next.
Don't summarise or paraphrase. Use their exact words. If you did calls we want the full transcripts. If we talked via email or text get a file with the messages. We want the raw material. Your job is to become a translator between what you built and what they experience.
What’s our goal here? We’re going to mine all that material and pull out a few different formats that we can use in marketing. You need descriptions for different contexts, but they should all use the same core user language. Start with the shortest and work your way up:
One-Sentence Value Proposition: The clearest, most compelling way to explain what you do using user language. This goes everywhere. This is your tagline.
Short Description (2-3 sentences): For social media, email signatures, quick explanations. Problem + solution + outcome.
Medium Description (paragraph): For landing pages, longer social posts, email announcements. Problem + solution + outcome + proof.
Long Description (multiple paragraphs): For detailed pages, blog posts, comprehensive explanations. Full story with examples.
The key is consistency. The same core message, just expanded based on context. We need them all. But they all come from the same root - the language of our users.
Thankfully we can get all of these from our users’ language using AI.
I need to create product descriptions using real user language from my beta testing feedback. Here's my collected feedback and conversations: [PASTE ALL FEEDBACK FROM WEEK 5] My product is: [BRIEF DESCRIPTION OF WHAT YOU BUILT] Help me extract and organise: 1. Problem Language: Exact words users used to describe the problem I'm solving
2. Outcome Language: How they described the results or benefits they experienced 3. Emotional Language: Frustrations, relief, excitement they expressed
4. Feature Translation: How they described what my product does (not technical features) Then create these descriptions using their language: 1. One-sentence value proposition (under 20 words)
2. Short description (2-3 sentences for social media)
3. Medium description (paragraph for landing page)
4. Long description (multiple paragraphs with examples) Use their exact words and phrases wherever possible. Focus on outcomes and benefits, not features and functionality.Feed in everything from your beta testing week. This is what AI is great at. Let the AI help you spot patterns and extract the language that actually resonates. We’re just guiding the process with the prompt.
Before you build anything, test these descriptions with a few people who know your product. Send them to 2-3 of your beta testers with a simple question: "Does this make sense? Would you describe it differently?"
Also test them on people who don't know your product. Read them the one-sentence value proposition and see if they immediately understand what you do and who it's for. There should be no confusion.
Good descriptions pass both tests: they resonate with people who've used your product AND make sense to people hearing about it for the first time. We need both!
Create your complete set of product descriptions:
Use the AI prompt to extract user language from your Week 5 feedback
Write your one-sentence value proposition using their words
Create short, medium, and long descriptions
Test with 2-3 beta testers for clarity and accuracy
Refine based on their feedback
These descriptions become the foundation for everything else this week. Get them right and the rest flows much easier. Get them wrong and the rest of the marketing assets will be compromised. This simple step of copywriting is super important - don’t rush it.
Share your learning process with a post along these lines:
"Day 26 of AI Summer Camp: Rewriting how I describe my product.
Went back through all my user feedback from beta testing. The disconnect is mental.
I was describing features: 'AI-powered workflow optimisation' Users described outcomes: 'stops me forgetting important stuff'. Made me realise I need to listen more.
Their version is 10x better. Building my landing page with their language, not mine.”
Tomorrow we collect social proof from your beta testing - testimonials, case studies, and results that show your product actually works. Combined with today's user-language descriptions, you'll have the core content for a landing page that converts.
Keep Prompting,
Kyle
Think about it. If your landing page says "our tool is the best solution for productivity," why the hell should anyone believe you? Of course you'd say that - you built it!
People are completely inured to marketing claims now. "Revolutionary!" "Game-changing!" "Industry-leading!" - it all sounds like white noise because every company says the same things.
We've trained people not to trust what companies say about themselves.
But they do trust what other people say.
When Sarah from accounting mentions "this saved me 3 hours last week," people listen. When James says "I finally stopped missing deadlines," that hits different.
Thankfully, we have a secret weapon from last week - our beta testers and champions. Real people who've used our product and seen real results.
People don't trust companies. They trust people. Quite right too.
So along with our user-language copywriting from yesterday, we need social proof. That's the focus of today.
Let’s get started:
From marketing fluff to actual proof
Mining gold from your beta conversations
Text vs video testimonials
Making it easy with the right tools
Building credibility that converts
Yesterday you gathered the language your users actually use to describe your product. Perfect descriptions in their own words. And we used that as the basis of our copywriting - ie. how we talk about our product.
Today we're collecting the proof that those descriptions are true. We're working towards a landing page that converts visitors into waitlist signups. Yesterday gave us the words. Today gives us the credibility.
Tomorrow we’ll pull all this together into a landing page. But let’s continue to collect up our material.
Your potential customers have heard every superlative in the book. "Revolutionary," "game-changing," "industry-leading" - it all sounds the same. Especially in the overhyped world of AI. It’s frankly exhausting.
But they haven't heard from Sarah who saved 3 hours last week. They haven't heard from Joe who stopped missing deadlines. They haven't heard the specific, real outcomes that real people experienced. This is called “social proof” and it’s what we use to make our marketing claims credible.
I’ll give you 3 ways (from easy, low hanging fruit to more systematic) to get your first social proof locked in.
OK easiest first as always. First step: go back through all your Week 5 conversations and feedback. You're looking for testimonial gold that might already be sitting there.
Look for phrases like:
"This saved me..."
"I used to struggle with... now I..."
"The difference is..."
"I can finally..."
"Before this, I was... now I'm..."
These are natural before/after stories that make perfect testimonials. Extract them exactly as written or said. Let’s use this prompt to do the heavy lifting for us:
I need to extract testimonial content from my beta testing feedback. Here's all my feedback and conversations: [PASTE ALL WEEK 5 FEEDBACK] Help me identify testimonials that are READY TO USE as-is by finding: 1. Before/After Statements: Clear "I used to... now I..." language
2. Specific Results: Concrete outcomes, time saved, problems solved
3. Complete Thoughts: Full testimonials that need no editing
4. Natural Language: Statements that sound authentic and conversational For each ready-to-use testimonial, extract:
- The exact quote (keep their exact words)
- Who said it (name if provided)
- Context of when they said it
- Type of result/outcome mentioned Only include testimonials that are complete and landing-page ready without any editing.This AI prompt will help you spot testimonial content you might have missed in your conversations. Sometimes they’ll be perfectly formatted already - these are good to go.
Sometimes you'll find great testimonial content, but it's not quite landing page ready. Maybe it's too casual, or buried in a longer message, or needs slight rewording for clarity. Basically it’s 80% of the way there but will be a little confusing on the page if publish as-is.
For these we want to rewrite.
First, use AI to help identify and rewrite these almost-perfect testimonials:
Now go back through the same feedback and find testimonials that are CLOSE BUT NEED REWRITING. Here's all my feedback and conversations: [PASTE ALL WEEK 5 FEEDBACK] Look for feedback that contains great testimonial content but needs refinement because it's:
- Too casual or conversational for a landing page
- Buried within longer messages
- Needs slight rewording for clarity
- Has the right sentiment but unclear language
- Contains great results but rambling delivery For each piece that needs rewriting:
1. Extract the original quote
2. Identify the core value/outcome mentioned 3. Rewrite it as a clean, natural testimonial while keeping their authentic voice
4. Make it specific and results-focused
5. Ensure it sounds like something they'd actually say Provide:
- Original quote
- Proposed rewrite
- Who said it
- Brief explanation of what you changed These will need the person's permission before using, but give me polished versions to show them.This prompt will do another pass of the feedback and extract language that is close to usable but not quite there. It’ll then propose a more polished version.
Then take the AI's rewrite (with your edits!!) back to the person and ask something like this:
'“You mentioned that [original quote], which was amazing feedback. I'd love to feature this on my landing page and wanted to rephrase it for readability to: [AI rewrite]. Does that work, or would you mind helping me with a rewrite in your words?"
Most people are happy to help refine their testimonial, especially when you're being transparent about how you want to use it and you've done most of the work for them.
We’re not putting words in their mouth here - we’re instead doing the heavy lifting for them so they can say “yup that looks good to me”. We’re reducing the pressure on them which is something people are always thankful for!
The first two steps will give us a nice basis. But we can do better. We can get purpose-built testimonials. For your most enthusiastic beta testers, go back and ask for fresh testimonials using specific guided questions.
Don't just ask "can you give me a testimonial?" That puts all the work on them. Again, make this as easy as possible. Instead, ask specific questions that make it easy for them to give you great content. Here are some examples but the exact questions you use will depend on what your product is and what you want to prove.
For Time/Efficiency Gains:
"Before using this, how long did [specific task] typically take you?"
"How much time do you estimate you're saving now?"
"What was the most noticeable difference in your workflow?"
For Problem Resolution:
"What was the biggest frustration you had with [problem area] before?"
"How has that changed since using this?"
"What would happen if you had to go back to your old way?"
For Emotional Impact:
"How did you feel when [specific outcome] happened?"
"What was your reaction the first time it worked properly?"
"Would you recommend this to someone facing the same problem?"
These guided questions help them give you specific, useful testimonials rather than generic praise. Whilst making their lives easier.
OK I’ve avoided this until now but we need to address it. Do we want text or video testimonials. You already know the answer: both!
Both formats have their place, and you'll want to collect both:
Text Testimonials:
Go for volume here - easier for customers to provide
Faster to collect and organize
Perfect for landing pages and social media
Can be extracted from existing conversations
Video Testimonials:
Use sparingly but strategically
Higher emotional impact and authenticity
Great for landing page headers
Here's the key: most videos won't get watched, but that doesn't matter - they still act as proof!
Start with text since it's easier to collect in volume. Once you have several good text testimonials, ask 1-2 of your most enthusiastic beta testers if they'd be willing to record a quick video saying similar things. The presence of video testimonials on your page signals authenticity, even if visitors don't watch them all. So we want to sprinkle a handful across our landing page.
For collecting testimonials systematically, I recommend Senja. It's designed specifically for this job and makes the whole process much easier. Doing this manually is frankly a pain - not just for you but also for your users. Remember we need to make it as easily as humanly possible for them - Senja helps here with a nice easy to use interface, especially if we are asking them for video.
Use my affiliate link (if you want): Senja. Alternatively Google it. Or if you don’t want to use Senja then Google Forms is fine for text testimonials. Video is trickier - basically get them to record on their phone and email you the video. If it’s too large they’ll need to use WeTransfer or similar. Again, all of this adds friction! Which is why I use Senja.
As a bonus once you have Senja set up, you can add a testimonial collection link directly into your product for ongoing feedback. This helps you collect testimonials automatically as people use your tool.
Fair warning…people won’t do it unless there is an incentive for them. Senja has features like their "spin the wheel" tool that can incentivise testimonials with small freebies or bonuses. Worth exploring once as a way to get a drip feed of testimonials coming in automatically over time. But don't worry about that yet! Focus on collecting from your existing beta testers first.
Use the AI prompt to extract existing testimonial content from Week 5 feedback
Identify testimonials that need refining and collaborate with users on rewrites
Set up a Senja account and create a testimonial collection form
Identify 3-5 beta testers to approach for fresh testimonials using guided questions
Collect and organise your best testimonials ready for tomorrow's landing page build
Aim for at least 5-7 strong text testimonials plus 1-2 videos if possible.
Share your testimonial collection process:
"Day 27 of AI Summer Camp: Turning beta feedback into social proof that actually converts.
Went back through all my user conversations looking for testimonials. Found loads of great stuff I'd missed the first time.
And then I set up proper collection with @Senja to make it easy for people to leave testimonials.”
I’d recommend tagging in Senja here to get a reshare from them.
Tomorrow we assemble everything into a landing page. Your user-language descriptions from yesterday plus your social proof from today will create a page that actually converts visitors into waitlist signups.
Keep Prompting,
Kyle
A landing page is a single web page designed to get visitors to take one specific action. Unlike your main product or a website with multiple pages and menus, a landing page has one job.
In our case, that job is getting people to join your waitlist.
Later it’ll be (you guessed it) to get them to make a purchase. That’s next week.
Most landing pages are absolutely terrible at this job. Generic stock photos of people pointing at laptops. Vague benefits like "increase productivity." Seventeen different sections that nobody reads. No clear next step.
Your landing page should take someone from "I don't know what this is" to "I want early access to this." That’s what we’re doing today.
Let’s get started:
What goes on a landing page
One job: get waitlist signups
Pulling all our work together with a prompt
You've been gathering assets all week like ingredients for a recipe. Today we finally cook. The goal isn't to create the world's most beautiful landing page. It's to create one that works.
We're building in Lovable since you're already set up there from Week 4, and it can handle the waitlist functionality we'll add on Day 30.
Also…it’s really good at doing landing pages. Generally it can one-shot them.
But first…what actually is a landing page?
Landing pages are where web visitors “land” from a search engine, a social media post or wherever else you are sending traffic from. The purpose of a landing page is to get someone to do something. We don’t want them browsing or clicking around on menus - we want them to carry out an action.
This could be to learn more, download a file, give their email or make a purchase. These are all valid uses of a landing page. In our case we’ll start with having people join a waitlist (to help validate our product before we charge money). But next week we’ll be converting the landing page so that the call to action is to purchase.
Landing pages normally have these following elements. Sometimes more, sometimes less. But these are a good starting point for now.
Hero Section: This is the first thing visitors see at the top of your page. It contains your main headline (using your Day 26 user language ideally!!), a brief explanation of what you do, and who it's for. This section answers "What is this and why should I care?" within seconds. If the hero doesn’t work and people click away then nothing else on the page matters.
Social Proof Section: This is where you display your best testimonials from Day 27. Real quotes from real people showing they got real results. This answers "Does this actually work?" and builds trust with visitors who don't know you yet.
Benefits List: We’ll be adding three main outcomes users get from your product, written using the exact language they used to describe these benefits. Not features ("AI-powered analytics") but outcomes ("saves 3 hours per week"). This answers "What's in it for me?"
Call-to-Action (CTA): A prominent button that says "Join Waitlist" or "Get Early Access." This should stand out visually and be the obvious next step. And the only next step! This answers "What do I do now?"
That's it. Four elements for now. Resist every urge to add more sections, more features, more explanations, more cleverness.
Rather than trying to write landing page copy manually (which is a big job!), we're going to create one comprehensive prompt that pulls together everything you've learned and built, then outputs a complete Lovable prompt.
This approach works because:
It uses all your prior research automatically
It asks for missing details if needed
It maintains consistency with your user language
It creates a complete, ready-to-build page specification
For clarity we’ll use this prompt outside of Lovable to generate instructions that we copy/paste into Lovable. So we’ll use ChatGPT or Claude or whatever AI tool you’ve been using up to now, ideally below all of your other work.
I need to create a high-converting landing page for my product waitlist. Help me gather the information and create a complete Lovable prompt. BUSINESS CONTEXT:
My business idea: [If you have this clearly defined from previous weeks, paste it. If not, I'll ask follow-up questions]
Target market: [From your Week 1 research]
Main problem solved: [From your user interviews] CONTENT ASSETS I'VE COLLECTED:
Product descriptions from user language: [PASTE YOUR DAY 26 DESCRIPTIONS]
Social proof testimonials: [PASTE YOUR DAY 27 TESTIMONIALS] DESIGN INSPIRATION:
Before I create the landing page, help me think about design by asking me questions:
- What's a landing page you've seen recently that made you want to sign up for something? What did you like about it?
- Do you prefer clean/minimal design or more detailed/rich design?
- Any specific colors or styles that fit your brand/product?
- Should this feel professional/corporate or friendly/casual? MISSING INFORMATION CHECK:
Review what I've provided above. If any crucial information is missing for creating a high-converting landing page, ask me specific follow-up questions about:
- Target audience details
- Key benefits/outcomes
- Unique selling points
- Brand personality/tone
- etc. FINAL OUTPUT:
Once you have all the information, create a complete Lovable prompt that will build a landing page with:
1. Compelling hero section using my user language
2. Social proof section with my testimonials 3. Clear benefit statements
4. Strong waitlist call-to-action
5. Mobile-responsive design
6. Professional but approachable styling The Lovable prompt should be detailed enough that I can paste it directly and get a working landing page.This prompt will walk you through everything systematically and create a complete specification for Lovable. Use it below your previous work to pull in all the context about your market and product. I’ve also set the prompt up to query you on missing information as needed - when it does this answer fully in order to help the AI.
It’ll also interview you briefly about design preferences and pages you like, so the final result matches what appeals to you. If you don’t know any design styles you want to mimic that’s fine - just tell the AI this!
Finally, it outputs a complete Lovable prompt that you can copy and paste to build your landing page.
Once you have your Lovable prompt from the AI above, head over to your Lovable project and paste it in.
Lovable is brilliant at one-shotting pages like this - taking a detailed prompt and building a complete, working landing page from it. Much faster than trying to build it manually or using other website builders. It’s actually one of my top uses of Lovable.
This landing page will sit BEFORE the actual product you created in Week 4. Think of it as your front door - visitors see the landing page first, join your waitlist, and then later (when you're ready to sell) they'll access your actual product. We'll sort out the mechanics of the waitlist functionality and redirections between your landing page and product later. For now, we're just getting the page built and looking good.
As always if the first version isn't quite right, you can ask Lovable to adjust specific elements. Just as you did when you vibe coded your product.
Build your landing page:
Use the master AI prompt to gather all your information and missing details
Get a complete Lovable prompt as output
Take that prompt to Lovable and build your landing page
Make any obvious visual improvements using Lovable's editing
By end of today, you should have a live landing page ready for tomorrow's soft validation with your champions. Then we’ll add the waitlist functionality (if Lovable hasn’t already done so - it might!) and go wide.
Share your landing page creation process:
"Day 28 of AI Summer Camp: Finally turning weeks of research into one landing page.
I’ve just used AI to compile all my user language + testimonials + business context into one prompt for Lovable. Then Lovable took all that research and made me a beautiful landing page.
Here’s the end result: link. What do you think??”
Tomorrow we do soft validation - sharing your landing page with your champions and beta testers for feedback before the wider launch. This is your chance to catch any issues and make improvements before Day 30's community launch.
Your landing page is almost ready to meet the world.
Keep Prompting,
Kyle
I have a confession to make: I sometimes move too fast.
Speed in business is good buuuut….can lead to mistakes.
Landing page finished? Boom done! Launch immediately! Product ready? Tell everyone! New idea? Share it with the world!
Wait what do you mean the cart isn’t working? Ooops.
This has bitten me more times than I care to admit. Launching with obvious typos. Broken links on launch day. Messaging that made perfect sense to me but confused everyone else.
Thankfully I have a detail orientated business partner who smoothes the edges off my most hasty move!
Because the problem isn't just the errors - it's the bad first impression. You only get one chance to make a first impression with your audience. Blow it with sloppy execution, and people remember.
There's one small extra step that saves your hide: the soft validation launch.
It's a micro-action that takes one day (today!) but prevents weeks of reputation repair. What we’ll do is share with our champions first - people who know your journey and want you to succeed. They catch the obvious issues before strangers see them.
Let’s get started:
Moving too fast burns bridges
First impressions matter forever
Champions catch what you miss
Yesterday you built your landing page. It looks good to you. The messaging makes sense in your head. Everything seems to work.
It’s tempting to just hit the button and launch.
But you're too close to it.
You know your product intimately. You understand the context. You can fill in gaps automatically. Your potential customers can't. Stuff that is obvious to you won’t be to them. And that’s not because they are stupid - they’ve just spent less time with the product. No-one will ever know it as well as you.
Your champions bridge that gap. Beta testers who've used your product, build-in-public followers who've watched your journey, supportive friends who want you to succeed. They know enough about what you're building to give intelligent feedback, but they're not so close that they miss obvious issues. We’ll leverage that today.
This soft launch serves three purposes. It catches obvious (dumb) errors like broken links, typos, or confusing messaging that you've gone blind to after staring at it all day. It tests whether your value proposition makes sense to people who aren't living inside your head. And (sneakily!) it builds anticipation with your champions, making them feel special and more likely to share when you launch wider.
It's insurance against embarrassing yourself tomorrow.
Your soft launch audience should be people who are already invested in your success.
Beta testers from Week 5 who've used your product and understand what you're building.
Build-in-public followers who've been commenting on your updates and have context about your progress.
Close friends and family who want you to succeed and will tell you honestly if something doesn't make sense.
Supportive LinkedIn connections who've engaged with your content and shown interest.
and so on..
Aim for 10-15 people. This isn't about scale - it's about quality feedback from people who care before we launch wide.
Don't just send your link and ask "what do you think?" That's too vague and puts all the work on them. Remember, we need to make this frictionless - always! You do the work so they don’t have to.
Instead, be specific about what you need. Tell them you're launching your waitlist tomorrow and would love their eyes on the landing page first. Ask specifically whether it makes sense what you're offering, whether they'd know what to do next, and if anything seems obviously broken or confusing.
Frame it as taking just two minutes to check and looking for glaring issues before you go wider. Basically: “am I being dumb?”. Most people are happy to spend two minutes preventing you from making a public mistake. Frame it as helping you avoid embarrassment rather than asking for a favour. People like feeling helpful, especially when the ask is small and specific.
Here’s a quick prompt to generate the message for you.
I need to do a soft validation launch of my landing page before tomorrow's wider launch. Help me create outreach messages for different types of champions. My landing page: [PASTE YOUR LANDING PAGE URL]
What I'm launching: [BRIEF DESCRIPTION OF YOUR PRODUCT/WAITLIST] Create personalised outreach messages for: 1. Beta testers from my testing week - reference their involvement in testing, ask for feedback on whether landing page matches their experience, make it feel like exclusive early access 2. Build-in-public followers - reference them following my journey, position as "almost ready to launch publicly," ask for quick feedback before wider announcement 3. Close friends/family - personal tone asking for honest opinion, focus on "does this make sense to someone outside tech," ask them to be brutally honest For each message type, keep it very brief, be specific about what feedback you need, make it easy to respond quickly, and show appreciation for their time. Also create a simple follow-up template for collecting and organising their responses.This will give you ready-to-send messages for each audience type. All you need to do is send them out et voila.
And when they send in messages go ahead and make the fixes. Importantly remember to thank them! Like before we want to make sure our champions want to be part of our success - so gratitude is important! Don’t forget to say thank you!
Super basic day today. Use the prompt to generate “plz help” messages and send them out. Then apply any fixes and thank them.
Doing so sounds mundane and unimportant. But it’s going to make tomorrow a lot smoother and avoid us from making silly mistakes.
Share your soft validation approach:
"Day 29 of AI Summer Camp: Soft launching to supports before going wide.
Tomorrow I go wide so making sure everything is ready!
Let’s see what embarrassing errors we can catch before going public.”
For fun you can also talk about some of the worst mistakes you made. It makes for good content.
Tomorrow is launch day - sharing your waitlist with the communities that helped you build and test your product. We'll add the waitlist functionality and then finally start getting the word out.
Keep Prompting,
Kyle
Remember last week? You were nervously reaching out to communities, asking strangers to test your rough prototype. "Would you mind trying this thing I built? I think it might be useful but need real people to see if I'm heading in the right direction."
You felt like you were asking for favours.
Today you're going back to those same communities with something completely different. A polished landing page. Real testimonials. Proof that it works. You're not asking for favours anymore - you're offering early access to something valuable.
We’ve come a long way in a week! It's the returning hero moment, but without the boastfulness. You followed through. You listened to feedback. You improved. You delivered.
This isn't about showing off - it's about completing the circle with the communities that helped you get here. And pushing to our wait list with real “strangers”.
Let’s get started:
The returning hero (humble version)
Following through on promises made
Early access for people who helped
Community launch strategy
From waitlist to revenue next week
We’re going to first put in place a waitlist. This waitlist isn't just about collecting emails. It's about validation before we start charging money. We love validation! It makes us feel…well, validated!
We're moving towards payment next week but first we need to test whether people actually want what we've built.
The waitlist response tells us everything we need to know:
Zero interest? That tells us something important. Maybe the messaging is off. Maybe the problem isn't as urgent as we thought. Maybe we need to pivot or significantly adjust our approach before we start trying to charge money. If we struggle to get interest in the form of an email we’ll definitely struggle to get paid.
Huge interest? Here we go. Roll straight into next week and start getting paid. People want what you've built and are ready to buy. Jackpot.
Some interest? This is the most likely scenario. Keep going. We don't need this to hit 1000 signups immediately. We're moving towards your first ever online revenue, and even 10-20 interested people is enough to start generating income.
Before you launch to communities, you need the waitlist to actually work. You have two options - choose based on your comfort level and time available.
Head back to Lovable with this prompt:
I need to add a waitlist system to my existing landing page. Place this in my current Call to Action section.
Please create: 1. FRONTEND - Email Collection Form: - Simple email input field with clear label "Enter your email for early access" - Optional first name field - "Join Waitlist" button that stands out visually - Form validation (proper email format required) - Success message after signup: "Thanks! You're on the waitlist. We'll email you when it's ready." 2. BACKEND - Database Setup: - Create a waitlist table/collection to store signups - Fields needed: email, first_name (optional), signup_date, timestamp - Basic data validation and error handling 3. ADMIN PAGE - Password Protected Dashboard for me to access: - Simple admin page at /admin (or similar URL) - Password protection (I'll set the password) - Display all waitlist signups in a simple table - Show: email, name, signup date - Basic stats: total signups, signups per day - Export functionality (CSV download of all emails) Keep everything simple and functional. This is a basic waitlist system, not a complex CRM. Make sure the admin dashboard is easy to use and the signup process is smooth.This will get Lovable to build a basic waitlist system for you. It’ll add a form and button to your landing page for the visitors. And then in the backend (for your eyes only) it’ll create a simple “Admin” page where you can see who has signed up for the waitlist.
If this is too complex or you want to launch faster, use this dead simple approach:
Create a Google Form:
Go to forms.google.com
New form titled "Early Access Waitlist"
Add email field (required)
Add first name field (optional)
Set to automatically save to Google Sheets
Update Your Landing Page:
Set your "Join Waitlist" to link to your Google Form (ask Lovable to do this for you)
Add text like "Get early access - join our waitlist"
Test the Flow:
Fill out your own form on your live page to test
Check that responses appear in your Google Sheet
This option is literally 10 minutes to set up and pretty bulletproof. No coding, no complex setup, just works. It’s less pretty and slick looking but it gets the job done.
Remember to test whichever option you choose before launching to communities!
You're going back to the places where you found your beta testers, but the approach is completely different now. Week 5 was about asking for help. Today is about saying thank you and offering value.
The communities that helped you during beta testing deserve to see what came of their support. Reddit communities where people answered your questions. LinkedIn groups where professionals gave you insights. Facebook groups where you found testers.
Your message to these communities should acknowledge their previous help and offer early access as a thank you. This isn't just good manners - it's smart business. Importantly we are showing them that you follow through. You are dependable and do what you say. That’s important.
If there are particular champions that you can call out in these groups then do so. Make them look good!
Your community messages should feel grateful rather than promotional. And we' aren’t selling anything yet - just saying you have a waitlist. You're completing a conversation that started weeks ago, not starting a new sales pitch.
I need to create launch messages for communities that helped me during beta testing. Help me create messages that feel grateful rather than promotional. My product: [BRIEF DESCRIPTION]
My waitlist page: [LANDING PAGE URL]
Communities I'm targeting: [LIST THE SPECIFIC COMMUNITIES/PLATFORMS FROM WEEK 5] Create launch messages for each platform. For each message:
- Keep it genuine and appreciative
- Reference specific previous interactions when possible
- Make it about thanking them, not promoting yourself
- Include clear next step (visit landing page and sign up for waitlist if interested) The key is making it feel like completion of a story they were already part of, not a random promotional post. Which is made a lot easier because we aren’t directly selling anything. We’re just bringing people to a waitlist. (But next week we’ll sell to those on our waitlist! We just don’t mention this part yet).
Execute your community launch:
Add working waitlist functionality to your landing page using the Lovable prompt or the basic Google Form
Test the signup flow to ensure everything works properly
Use the AI prompt to create grateful, community-specific launch messages
Post to the communities that helped you during Week 5 beta testing
And then over the weekend see how your waitlist goes! Don’t keep refreshing it - it’s tempting but give it some time!
Share your launch milestone:
"Day 30 of AI Summer Camp: Launch day.
Six weeks ago I started with just market research. Today I'm launching my waitlist to the communities that helped me build and test.
From idea to working product to landing page to early access launch. In just 6 weeks?”
Week 6 complete! You've gone from scattered feedback to polished marketing assets to live waitlist with real signups.
Week 7 shifts to Basic Revenue Systems. Now that we have potential customers on the hook we’re going to set up payment processing, create pricing strategies, and turn your waitlist into paying customers.
But here's the key: the waitlist response determines how confident you should feel going into Week 7. Strong signup numbers mean you're ready to start charging. Weak response means you might need to revisit your messaging or approach before setting up payments.
Either way, you'll know where you stand. That's the power of validation before monetisation. We enter each stage knowing exactly what’s what rather than blindly.
Keep Prompting,
Kyle
Welcome to '🧲 Marketing Foundations', where we’ll transform your innovative product into a market-ready success story. In this playbook, we delve deep into the art of communicating your value proposition, ensuring potential customers understand not just what your product does, but why it matters to them. With actionable strategies and user-centered language, you’ll learn how to position your offering effectively and build anticipation for your launch. This is your opportunity to make a significant impact and drive growth by connecting meaningfully with your audience.
This playbook is designed for entrepreneurs and product developers who are ready to launch their innovative solutions but struggle with articulating their value in a way that resonates with potential customers. You may have built a fantastic product, but if you're facing challenges in conveying its benefits or garnering interest, this playbook is perfect for you. Whether you're in the early stages of startup development or preparing for your first launch, '🧲 Marketing Foundations' provides the insights and tools necessary to bridge the gap between your creation and its market success.
You can still utilize existing market research or conduct surveys to gather insights on potential user needs and outcomes.
While implementation times can vary, you can expect to see initial interest and engagement within weeks of applying the strategies.
No prior marketing experience is necessary; this playbook is structured to guide you through each step, regardless of your background.
You will learn to create product descriptions, landing pages, email capture forms, and social proof elements that effectively communicate your product's value.
Yes, the principles and strategies outlined can be applied to a wide range of products and services across various industries.