My Blog

Blog

  • Marketing & Lead Gen: cold email in europe gets 4-5x more replies

    Watch on YouTube: https://www.youtube.com/watch?v=Rfg9rqu7AMc

    Channel: Nick Saraev Daily

    Introduction

    Nick Saraev’s recent video explains why cold‑email outreach that is tailored to European markets can generate substantially higher reply rates than similar campaigns run in the United States. He frames the tactic as a high‑value, low‑risk channel when the messages are genuinely helpful and professionally presented.

    What the video covers

    • The claim that localized EU cold email can yield 4‑5× more replies than US‑focused outreach.
    • The importance of high‑quality, custom icebreakers and why generic AI‑generated lines often fail.
    • A practical workflow for scaling personalization: start with manual icebreakers for a small seed set, let AI detect patterns, then automate the rest.
    • Specific tools Nick mentions for automating and refining the process.
    • His own business metrics (revenue, YouTube growth, video view spikes) as context for why he is experimenting with this approach.
    • Operational tips such as using a professional domain, staying within EU‑friendly compliance, and measuring results.

    Step‑by‑step walkthrough

    • Identify target EU countries – Nick highlights Germany, Spain, and the Netherlands as examples where decision‑makers are reportedly receptive to well‑crafted cold mail.
    • Gather a small seed list – Choose the first 5‑10 leads you intend to contact.
    • Manually craft icebreakers – Write a personalized opening line for each seed lead that references a specific detail (e.g., a recent project, a shared interest, or a local event). The video stresses that these must be high‑quality and offer clear value.
    • Let AI analyze the manual icebreakers – Feed the handwritten lines into a tool such as Claude Code or an AI agent. The model extracts the underlying pattern (tone, structure, value proposition).
    • Generate variations for the rest of the list – Use the AI to produce icebreakers for the remaining prospects, ensuring each output follows the discovered pattern while still being tailored to the individual lead’s data.
    • Set up the sending infrastructure – Purchase or configure a professional domain (avoid Gmail) to improve credibility and reduce spam‑filter risk.
    • Launch the campaign – Send the emails, tracking opens, replies, and any downstream conversions.
    • Measure and iterate – Review reply rates, test alternative subject lines, tweak icebreakers, and adjust offers based on what the data shows.

    Tools and numbers mentioned

    • Revenue claim: over $400 k per month.
    • Reply‑rate uplift: 4‑5× higher in the EU compared with US‑focused cold email.
    • YouTube growth: ~1,000 new subscribers per day, rebounding to a 2,000‑subscriber‑per‑day level after slower periods.
    • Historical reference: previously ~600 k subscribers per day (as noted in the video’s metrics).
    • Growth descriptors: 4× growth, 8× peak (referring to subscriber or view increases).
    • Recent video view spikes: ~500 k views in 48 hours, with individual examples of 92 k, 84 k, and 1.25 M views.
    • Tools for personalization: Claude Code, AI agents, Opus 5.5.
    • Other platforms referenced for context: Marketplace, Kijiji, Craigslist (mentioned as examples of where cold outreach can be applied).

    Caveats and hype check

    The video presents several impressive figures without providing screenshots or third‑party validation. The $400 k monthly revenue statement, the rapid subscriber jumps, and the half‑million‑view spikes are described as anecdotal. Likewise, the 4‑5× reply‑rate improvement for EU cold email is offered as a confident expectation but lacks cited split‑test data or external studies. Viewers should treat these numbers as illustrative rather than proven benchmarks and consider running their own small‑scale tests before committing significant resources.

    “Cold email is a lot like crossing the zebra crossing.”

    “If you send truly high‑quality, custom‑made cold emails that offer value… you are almost certainly on the right track.”

    “Germany, Spain… many of these other EU countries are desperate for cold mail right now.”

    “It is a sign of professionalism. Take care of your own domain.”

    “You have to do that [hyper‑personalize]. And you need to use AI to help you with that.”

    Concrete next actions

    • Select a target EU country (e.g., Germany, Spain, Netherlands) and build a list of 50‑100 prospects.
    • For the first 5‑10 leads, write a custom icebreaker that references a specific, verifiable detail about the recipient or their company.
    • Export those icebreakers into a text file and run them through Claude Code (or a comparable AI agent) to ask the model to identify the underlying pattern.
    • Prompt the AI to generate icebreaker variations for the remaining leads, ensuring each output retains the pattern while staying personalized.
    • Set up a sending address on a professional domain you own; avoid free‑mail services like Gmail.
    • Launch the email sequence, using a mail‑merge or outreach tool that allows you to track opens and replies.
    • After 48‑72 hours, review reply rates. If they fall short of expectations, test alternative subject lines, tweak the value proposition, or refine the AI‑generated lines.
    • Document the results and decide whether to scale the campaign to additional countries or larger lists based on the data you collect.
    • Periodically revisit compliance: ensure each email contains a clear opt‑out option and that the content is genuinely helpful rather than purely promotional, to stay within EU‑friendly guidelines.

  • AI Receptionist: call your leads in 10 seconds

    Watch on YouTube: https://www.youtube.com/watch?v=_KumygjKZQA

    Channel: Nick Saraev Daily

    Call Your Leads in 10 Seconds – Overview

    The video from Nick Saraev Daily demonstrates how to build a “speed‑to‑lead” system that contacts a prospect within ten seconds of a form submission. The core idea is that rapid outreach creates a competitive advantage, while the rest of the business—especially marketing—remains the primary bottleneck that must be fed with leads to make any optimization worthwhile.

    What the Video Covers

    The presentation walks through the mechanics of triggering an immediate call using Twilio (or a comparable telephony service) as soon as a lead fills out a web form. It shows how to optionally follow that call with an instant SMS or email acknowledgment. Beyond the technical setup, the speaker emphasizes marketing as the driver of revenue, the importance of measuring outreach activity, using focused work blocks to reduce context‑switching, and niching by time zone to avoid overload when serving multiple markets. Additional systems—such as proposal generators, post‑call email automation, and call recording—are suggested to improve close rates after the first contact.

    Step‑by‑Step Walkthrough

    • Create a web form that captures the prospect’s name, phone number, and any qualifying questions.
    • Configure the form’s submission handler to start a timer that expires after ten seconds.
    • When the timer fires, invoke Twilio’s API (or an equivalent service) to place an outbound call to the number supplied in the form.
    • Optionally, trigger an immediate SMS or email that confirms receipt of the form and promises a call within a short window (e.g., “We’ll be on the line in the next 15 seconds”).
    • Log the call outcome (answered, voicemail, no answer) in a CRM or spreadsheet for follow‑up.
    • After the call, activate a post‑call automation that pulls any notes or recordings into a templated follow‑up email.
    • Record the call (with consent) for quality assurance and training purposes.
    • Use a shared calendar as the single source of truth for any booked meetings that result from the call.

    Tools and Numbers Mentioned

    • Twilio – primary telephony platform for the ten‑second call.
    • make.com (formerly Integromat) – suggested for wiring the form timer to Twilio.
    • NAN, cloud routines, cloud code, skill in co‑work – referenced as auxiliary automation components.
    • Monday.com, Google Doc, one‑hour work form – tools for tracking outreach and logging focused work sessions.
    • CRM systems – highlighted as valuable only when populated with leads and equipped with follow‑up pipelines.
    • Call recording software – recommended for post‑call review.
    • Commission‑based cold email lead agency, cold outreach course, maker‑school members – examples of communities or offers that can support the outreach effort.
    • Revenue illustrations: $10 million per month (HVAC example), $200 000 per year deal, $4 000 monthly, $10 k target.
    • Time frames referenced: 10 seconds (call trigger), 15 seconds, 1 minute, 5 minutes, 15 minutes, 30 days.
    • Activity benchmarks: 2 500 doors knocked, 300 applications sent, 0 % reply rate (as a starting point for measurement).

    Key Takeaways and Caveats

    The video stresses that marketing fills the pipeline; without a steady stream of leads, any sales or operational tweaks have limited impact. Quantifying effort—such as counting emails sent, calls made, or doors knocked—provides a factual basis for improvement, counteracting vague feelings of “hard work.” Focused work blocks (e.g., a dedicated one‑hour session with a completion log) help reduce context‑switching and increase measurable output. When serving clients across multiple time zones, the speaker advises either specializing in one region or stacking clients with similar working hours to avoid scheduling overload.

    Additional systems—proposal generators, post‑call email automation, and call recording—are presented as force multipliers that can lift close rates after the initial rapid contact. The speaker also notes that a CRM only becomes useful once it contains leads and a defined follow‑up process.

    “Most of business is just marketing.”

    “If you get good at marketing, you’re good at like 50% or more of business.”

    “Systems only matter if people are using them.”

    “Go fill your shitty ass pipeline with as many people as humanly possible.”

    “The first one that picks up gets the deal.”

    “You need to quantify it.”

    “Don’t complain unless you have quantifiable metrics.”

    “I’m just a dude.”

    “You’re 80% of the way there; just add a little thoughtfulness.”

    “Effectiveness beats efficiency at any point in time.”

    Concrete Next Actions

    • Set up a form timer that triggers a Twilio call (or comparable service) within ten seconds of submission.
    • Configure an immediate SMS or email that confirms receipt and promises a call within a short window (e.g., 15 seconds).
    • Begin logging daily outreach numbers—emails sent, calls made, replies received—to establish a measurable baseline.
    • Implement a one‑hour focused work block and fill out a simple log of what was accomplished during that block.
    • Choose a primary time‑zone cluster (e.g., US‑East or UK) for your client base to reduce scheduling conflict when scaling.
    • Build a post‑call email automation that pulls call notes or recordings into a templated follow‑up message.
    • Add call recording to your calendar‑booked meetings for later review and training purposes.
    • Review and update any existing cold‑outreach course with the latest best practices highlighted in the video.
    • Join a maker‑school‑style community or accountability group to track progress and share results.
    • Launch a small test campaign: aim for 300 cold emails in 30 days, then analyze the reply rate and adjust your approach based on the data.

  • Marketing & Lead Gen: The Most Valuable Personal Brand Training You’ll Ever Watch

    Watch on YouTube: https://www.youtube.com/watch?v=XiCGdzwJ-jc

    Channel: Sam Gaudet

    Introduction

    Sam Gaudet presents a structured approach to building a personal brand that aims to reach a large audience, using a six‑part system that covers positioning, ideation, scripting, delivery, production, and distribution. The training emphasizes daily tracking of key metrics and anchoring content creation in a mission to serve the audience.

    What the Video Covers

    The video walks through each component of the system, providing definitions, examples, and practical tactics. It explains how to craft a clear promise, stack proof, share a unique perspective, and inject personality. It then moves into idea generation, outlining techniques, delivery methods, production principles, and distribution strategies designed to increase volume and omnipresence across platforms.

    Six‑Part System Breakdown

    • Positioning – define a single clear promise, consistently deliver proof to build credibility, stack proof over time, share a unique perspective to stand out, and inject personality by showing behind‑the‑scenes aspects of your life.
    • Ideation – generate ideas by matching in‑demand topics with your unique angle and a suitable format; remember that an idea equals topic plus angle plus format.
    • Scripting – use outlines instead of full scripts, apply asymmetric pacing (first points faster than last points to create an illusion of progress), introduce unique mechanisms (label familiar‑but‑unknown concepts then explain them), and include a road‑map at the start to show viewers the steps they’ll get and create curiosity.
    • Delivery – practice the off‑the‑dome method: review the outline, recall key points, riff naturally, and repeat key messages repeatedly to let authenticity compound.
    • Production – keep editing simple; only add graphics, cuts, or text overlays that help the audience understand better, removing anything that does not serve comprehension.
    • Distribution – create platform‑dedicated content rather than repurposing the same file, cross‑promote each piece to tell viewers where to go for a specific benefit, engineer omnipresence, and increase volume with low‑effort hacks such as Instagram trial reels and double‑posting the same MP4 to trial reel then main feed.

    Tools, Formats & Numbers Mentioned

    • Target audience size: 10 million followers; reference point: Dan Martell’s brand at 12 million followers.
    • Proof examples: Sam’s Instagram proof‑stack of 75 000 followers; Dan’s meeting‑waster video with 3 million views.
    • Example view ranges: 100 views, 100 k views, 100 million views.
    • Fifteen short‑form formats: clone, red flag, green flag, listical, rapid fire listical, tier list ranking, top 10 ranking, this or that, bad good great yap, reaction, don’t versus do, split screen, screen share, sticky note, overrated underrated.
    • Four core metrics to track daily: views, followers, leads, revenue.
    • Tools and tactics: Instagram (message ‘YouTube’ for a template), YouTube scripting template, trial reels, double‑post tactic, Slack message automation for daily metrics, AI assistance for automating Slack updates.

    Caveats & Hype Check

    Your number one goal on social media is to share a compelling promise with your audience.

    While the framework is detailed and provides actionable steps, the claim that following the system can grow a personal brand to over 10 million followers is aspirational. The video cites Dan Martell’s 12 million‑follower brand as proof but does not present concrete revenue figures or guaranteed outcomes. The offer of a free YouTube scripting template via Instagram functions as a lead‑generation tactic rather than a paid product push.

    Concrete Next Actions

    • Write down one clear promise for your brand and review it before creating each piece of content.
    • List three pieces of proof (results, testimonials, metrics) and plan to share them regularly.
    • Identify a unique perspective or contrarian take rooted in your experience.
    • Add a monthly behind‑the‑scenes carousel or story to showcase your personality.
    • Brainstorm topics using internal sources (sales/coaching calls) and external validation (Reddit, Google Trends), then filter by demand, fit, and interest.
    • For each chosen topic, devise at least two distinct angles that reflect your perspective.
    • Pair each topic‑angle combo with one of the 15 short‑form formats listed.
    • Create an outline (not a script) for each video, applying asymmetric pacing, a unique mechanism, and a road‑map at the start.
    • Practice the off‑the‑dome method: review the outline, recall key points, riff, then repeat delivery.
    • When editing, ask whether each graphic, cut, or text overlay aids viewer understanding; remove anything that does not.
    • Produce platform‑dedicated videos (e.g., a YouTube video, a separate Instagram Reel, a TikTok) instead of repurposing the same file.
    • Cross‑promote: in each video, tell viewers to follow you on another platform for a specific benefit (e.g., free template).
    • Use Instagram trial reels and the double‑post tactic to double output without extra filming.
    • Set up an automated daily Slack (or similar) message that reports views, followers, leads, and revenue.
    • Before creating content, ask: ‘How does this help my audience achieve their goal?’ and align with your mission.

  • AI Tools: The \”Arbitrage\” Secret That Built a $100k/Month Business

    Watch on YouTube: https://www.youtube.com/watch?v=coe4fmu5cE8

    Channel: Pace Morby

    Introduction

    In the Pace Morby video titled “The “Arbitrage” Secret That Built a $100k/Month Business,” the host explains how a simple referral model turned a Craigslist lead into a recurring revenue stream. By acting as an estimator or middleman, Pace connected home‑service buyers with licensed providers, added a markup, and collected a finder’s fee without performing the work himself or holding a contractor license. The video walks through the original paint‑contract deal, the scaling process across multiple trades, and the practical steps anyone can follow to replicate the arbitrage approach.

    What the Video Covers

    The presentation is broken into several core sections:

    • The origin story: how a $2,500 finder fee for 15 houses per week at $1 per sq ft with Tom from Luxor Paints grew into roughly $25,000 per month.
    • The mechanics of service arbitrage: finding a buyer, referring the work to a provider, and retaining a fee or markup.
    • How Pace expanded the model to other home‑services such as cabinet refinishing, carpet, roofing, plumbing, HVAC, and landscaping.
    • Specific numbers he used for markups (flat $1,000‑$1,500 per job or per‑unit amounts like $25 per cabinet door).
    • Why a contractor license is not required when you act as the estimator/middleman.
    • The role of lead generation channels—Craigslist and Facebook Marketplace—and the importance of a “yes” mindset.
    • How AI‑generated before/after images can improve ad performance for these services.
    • Practical action items for launching and scaling an arbitrage‑based business.
    • A hype check that contextualizes the $80‑$100k/month claim as personal experience rather than a guaranteed outcome.

    Step‑by‑Step Walkthrough of the Arbitrage Model

    1. Identify a service niche – Choose a home‑service that is easy to estimate (e.g., cabinet refinishing priced per door, exterior paint priced per sq ft, carpet priced per yardage, roofing).
    2. Source a licensed provider – Use Craigslist, Facebook Marketplace, or local trade directories to find a contractor willing to work at a wholesale rate. Example: a cabinet refinisher charging $50 per door.
    3. Negotiate the wholesale rate – Agree on a base price that the provider will accept for completing the work.
    4. Determine your markup – Add either a flat fee (e.g., $1,000 per job) or a per‑unit fee (e.g., $25 per cabinet door) to the provider’s price. Pace’s example: provider $50/door + Pace $75/door = $125/door quoted to the customer.
    5. Create a simple estimate – Count cabinet doors, measure square footage for paint, or measure yardage for carpet. No specialized training is required; basic arithmetic suffices.
    6. Post free‑estimate ads – List the service on Craigslist and Facebook Marketplace, emphasizing a free estimate and quick turnaround.
    7. Close the lead – When a prospect says yes, confirm the scope, collect payment upfront or set a milestone schedule, and forward the job to the provider.
    8. Manage the job – Act as the point of contact, ensure the provider completes the work to the agreed standard, and handle any customer service issues.
    9. Collect your fee – After the provider is paid, retain your markup as profit.
    10. Repeat and scale – Replicate the process across additional niches, increase ad frequency, and aim for roughly one closed job per three estimates (≈30% close rate).

    Tools, Numbers, and Resources Mentioned

    • Initial deal: $2,500 finder fee; later $400 per job as a quality check.
    • Luxor Paint contract revenue: ~$25,000/month.
    • Scaled revenue range: $80,000–$100,000/month after adding multiple services.
    • Paint pricing context: $1.00 per sq ft (historical deal), $2.15 per sq ft (two‑story exterior), $1.50 per sq ft (one‑story exterior), current market ~$2.50 per sq ft.
    • Cabinet refinishing example: provider $50 per door, Pace markup $75 per door → $125 per door quoted.
    • Flat markup examples: $1,000 per job or $1,500 per job.
    • Lead platforms: Craigslist, Facebook Marketplace.
    • Key contacts/meeting places: Bank of America (where Pace met Tom), Invitation Homes / American Homes for Rent, Dun Edwards paint store.
    • AI usage: generate before/after images to boost ad credibility and response rate.

    Caveats and Hype Check

    Claims of earning $80‑100k/month are based on Pace’s personal experience and may not be typical; success depends on consistent lead generation, negotiation skill, and market conditions, and there is no guarantee of similar results.

    The video emphasizes that the arbitrage model works best when you can reliably source leads, negotiate wholesale rates, and maintain a “yes” mindset—acting quickly when a prospect agrees. Payment risk is mitigated by collecting upfront or using milestone payments, especially important in home‑services where clients may otherwise delay or withhold payment.

    Concrete Next Actions

    • Post daily free‑estimate ads on Craigslist and Facebook Marketplace for services such as cabinet refinishing, exterior paint, carpet, or roofing.
    • Identify a licensed provider for each chosen service and negotiate a wholesale rate (e.g., $50 per cabinet door).
    • Add a markup—either a flat amount ($1,000‑$1,500 per job) or a per‑unit amount ($25 per door)—and present the total price to the customer.
    • Perform simple estimates: count doors, measure square footage, or measure yardage; no specialized certification needed.
    • Use AI tools to create before/after visuals for your ads to increase credibility and response rate.
    • Track leads and aim for at least one closed job per three estimates (≈30% close rate).
    • Collect payment upfront or establish a milestone schedule to reduce non‑payment risk.
    • Reinforce the “yes” mindset: when a lead says yes, figure out how to deliver within 30 minutes.
    • Consider building a simple lead‑capture website or landing page to automate inquiries.
    • Review results regularly, refine your markup and lead sources, and add new service niches as confidence grows.

  • AI Tools: How to Build a Personal Knowledge Base with Claude In 2027

    Watch on YouTube: https://www.youtube.com/watch?v=LP7bfT4vOlo

    Channel: Nick Saraev

    Introduction

    The video from Nick Saraev’s channel explains a practical way to create a personal knowledge base—sometimes called a “second brain”—using the Claude family of models. Rather than loading every piece of information directly into the model’s context window, the approach keeps data external, indexes it with a lightweight search algorithm, and retrieves only the most relevant snippets before generating an answer. This retrieval‑augmented generation (RAG) setup aims to keep responses up‑to‑date while reducing the computational cost typically associated with vector‑database solutions.

    What the video covers

    The presenter outlines why large context windows (now able to hold the equivalent of 35‑50 books of tokens) can lead to stale answers when all stored data is given equal weight. He introduces recency‑weighted retrieval as a solution: each incoming item is timestamped, and the system biases retrieval toward newer entries. The video then walks through a complete pipeline that continuously pulls new data via connectors, summarizes and extracts key “atoms” with a cheap LLM, stores those summaries in a plain‑text BM25 index, and monitors connector health to maintain freshness.

    Step‑by‑step walkthrough

    • Identify the information sources you want to feed into the knowledge base (e.g., email, Slack, call transcripts, closed AI sessions).
    • Build or adapt a connector script that queries each source for only new items since the last run, attaches the current timestamp to each record, and writes the raw text to a staging area.
    • Schedule the connector to run on a regular cadence—such as every 15 minutes—using a cron job or similar scheduler, adjusting the frequency based on API limits and system capacity.
    • Pass each newly captured item through a cost‑effective LLM (Claude Haiku 5.5) to generate two outputs: a concise summary and a list of atoms, which are discrete pieces of information like error messages, solutions, commands, or decisions.
    • Store the summary and atom list as plain‑text entries in a BM25‑indexed collection; the index enables fast keyword‑based retrieval without the overhead of vector embeddings.
    • Deploy a background monitoring script that checks connector health (API keys, permissions, network connectivity) and logs any failures, triggering alerts if the pipeline stalls.
    • Periodically review the index to prune outdated or redundant entries, keeping the searchable corpus lean and ensuring that recency weighting remains effective.
    • Test the end‑to‑end flow by asking Claude a question that should be answered using the knowledge base; verify that the returned answer cites recent, relevant summaries or atoms.
    • Visit the Maker Zero repository (referenced in the video description) to copy the ready‑to‑use prompt for summarization/atom extraction and to join the community for updates and troubleshooting.

    Tools and numbers mentioned

    • Claude Haiku 5.5 – the inexpensive model used for summarizing incoming data and extracting atoms.
    • Gmail API (read‑only) – example connector for pulling email messages.
    • BM25 – the plain‑text search algorithm that powers the knowledge‑base index.
    • Context window size – current consumer LLMs can hold roughly 35‑50 books worth of tokens.
    • Scale of the presenter’s engram – about 35‑50 k records stored in the searchable index.
    • Connector interval – every 15 minutes in the demonstrated setup.
    • Cost and speed improvement – the BM25‑based RAG reduces inference time and maintenance cost by roughly 9/10ths compared with traditional vector‑DB‑driven RAG.
    • Resources – prompts and starter code are available in the Maker Zero repository (second link in the video description).

    Caveats and hype check

    The video mentions that the presenter’s knowledge base powers a business that “generates a good income every month” and that “multi‑billion dollar companies” use similar systems, but it does not provide concrete revenue figures, case studies, or independent verification. These statements should be treated as anecdotal marketing claims rather than proven results. As the presenter notes, “Simple search is much more effective than all other methods,” yet the effectiveness will depend on the quality of the connectors, the relevance of the extracted atoms, and the frequency of updates.

    > “It will answer with great confidence because to it, things are like, ‘Hey, there’s a text here, there’s a text there. I don’t know which one is correct. I’ll just give you the first one I find.’”

    Concrete next actions

    • List all data sources you wish to include (email, Slack, call transcripts, closed AI sessions, etc.) and note any API requirements.
    • Write a connector script for each source that fetches only new items since the last run, timestamps them, and saves the raw text to a temporary folder.
    • Set up a scheduler (cron, Windows Task Scheduler, or a cloud‑based trigger) to run each connector every 15 minutes or at a cadence that matches your usage patterns.
    • Export closed AI chat sessions as plain‑text files and feed them into the same pipeline for long‑term reference.
    • Configure a cheap LLM (Claude Haiku 5.5 or an equivalent model) to produce a summary and an atom list for each new item, using the prompt provided in the Maker Zero repository.
    • Store the generated summaries and atoms in a BM25 index; many open‑source libraries (e.g., Whoosh, Elasticsearch with BM25 similarity) can be used for this purpose.
    • Implement a monitoring script that pings each connector’s API, checks for authentication errors, and logs success/failure status to a file or monitoring service.
    • Schedule a weekly maintenance job to review the index, remove entries older than a chosen threshold, and deduplicate similar atoms.
    • Copy the summarization/atom‑extraction prompt from the Maker Zero repository and adapt it to your specific terminology if needed.
    • Run a test query through Claude, asking a question that should be answered by your knowledge base, and confirm that the response cites recent, relevant information.

  • AI Tools: Claude Can Now Watch Videos (100% Free)

    Watch on YouTube: https://www.youtube.com/watch?v=mOy7JQjTYwE

    Channel: Moritz | AI Systems

    Introduction

    The video from Moritz | AI Systems shows how to give Claude the ability to “watch” YouTube videos without relying on its native text‑only processing. By installing an open‑source skill called eyes, Claude can index a video’s frames, transcript, on‑screen text, timestamps, and audio/color data. Once indexed, the model can answer detailed questions about the video quickly and consistently, at a cost of only a few cents per video.

    What the Video Covers

    The presentation walks through the limitations of Claude’s built‑in capabilities, explains how the eyes skill works, demonstrates its core features, provides cost estimates, and outlines practical use cases. Key points include:

    • Claude cannot natively process video; it only handles text and static images.
    • The eyes skill extracts frames, transcript, on‑screen text, timestamps, and audio/color data to create a local index.
    • Indexed data enables fast, repeatable queries for search, burst analysis, layout detection, and video DNA comparison.
    • Costs range from approximately 1 cent for a short clip using a cheap model to about 30 cents for a 20‑minute video processed with the top model.
    • Installation is performed via a GitHub repository; after setup, the agent invokes the skill with the command /eyes <YouTube‑URL>.
    • Use cases highlighted are tutorial step extraction, competitor video analysis, clipping, style copying, and edit validation.
    • The tool improves consistency compared with Claude’s ad‑hoc FFMPEG approach, which can vary depending on the prompt.

    Step‑by‑Step Walkthrough

    1. Install the eyes skill – Copy the GitHub repository link from the video description and instruct your agent to install it. This step sets up the necessary dependencies and makes the /eyes command available.
    2. Index a video – Run /eyes <YouTube‑URL> pointing to the target YouTube video. The skill will:
      • Extract frames at a configurable rate (the demo mentions bursts of 8 frames per second).
      • Download the transcript and any on‑screen text.
      • Capture audio and color information for later analysis.
      • Store all extracted data locally so subsequent queries are fast and consistent.
    3. Run queries – Once indexing is complete, you can ask Claude specific questions. Examples from the video include:
      • Searching for on‑screen text or keywords.
      • Using the burst feature to capture a rapid series of screenshots from an interesting segment.
      • Applying the measure command to generate an editing DNA report (e.g., cuts per minute, percentage of shots under one second).
      • Comparing two videos by analyzing their DNA reports to spot similarities or differences in editing style.
      • Cropping or extracting specific frames for further use.
    4. Apply insights – The DNA report can be used to:
      • Edit a raw clip to match the pacing and style of a reference video.
      • Validate your own edits before publishing by checking against reference metrics such as layout changes or shot length distribution.

    Tools, Numbers, and Technical Details

    The video provides concrete figures that help estimate the expense of using the eyes skill:

    • ≈ 1 cent for a 45‑second video processed with a cheap model.
    • ≈ 2 cents for the same length with a mid‑tier model.
    • ≈ 10 cents for a 45‑second video using the top model.
    • ≈ 20 cents for a 2‑minute video with the top model.
    • ≈ 30 cents for a 20‑minute video with the top model.

    Other technical mentions include:

    • The skill relies on FFMPEG for frame extraction when used ad‑hoc, but the eyes tool provides a consistent, repeatable alternative.
    • Burst mode captures approximately 8 frames per second.
    • The measure feature can report metrics such as 70 cuts per minute and T7% of shots lasting under one second.
    • Installation source is the public GitHub repository linked in the video description.

    Caveats and Hype Check

    “Claude can’t actually watch videos. It will kind of rebuild everything from scratch.”

    The presenter emphasizes that the tool is free and open‑source, with no affiliate promotions or hidden revenue claims. Cost estimates are approximate and depend on the model selected; the core functionality is presented as genuinely accessible without upsells. However, users should note that:

    • Initial indexing requires processing time proportional to video length and the chosen model’s speed.
    • Local storage is needed to hold the indexed frames, transcript, and audio data.
    • While the skill improves consistency over ad‑hoc FFMPEG prompts, the quality of on‑screen text extraction depends on the underlying OCR capabilities.

    Concrete Next Actions

    To start using the eyes skill with Claude, consider the following steps:

    • Obtain the GitHub repository URL from the video description and run the installation command via your agent.
    • Test the skill on a short YouTube clip (e.g., a 45‑second tutorial) using /eyes <URL> to verify indexing and query response times.
    • Experiment with the burst feature on a segment containing fast motion or animation to see how many frames are captured per second.
    • Generate a measure report for two competing videos and compare their editing DNA (cuts per minute, shot length distribution) to identify stylistic differences.
    • Search your indexed library for specific on‑screen text or keywords relevant to a research task.
    • Apply the DNA report to edit a raw clip, aiming to match the reference video’s pacing and layout changes.
    • Before publishing any edited video, run a validation check against the reference metrics to ensure consistency.

  • Grok Bot: 14 Grok Bot Employees You Can Steal

    Watch on YouTube: https://www.youtube.com/watch?v=-4EqgYJuCE0

    Channel: Jordan Rafealov

    Introduction

    The video “14 Grok Bot Employees You Can Steal” presents a collection of ready‑to‑copy prompts that turn the GrokBot platform into a suite of virtual employees. Each prompt is designed to replace a specific software tool or routine task, promising time savings, cost reductions, and streamlined workflows. The presenter walks through the purpose of each bot, shares the claimed savings, and explains how to deploy them using the GrokBot interface.

    What the Video Covers

    The core of the video is a rapid‑fire tour of 14 distinct GrokBot prompts, grouped by function:

    • Chief of Staff – delegates tasks and delivers daily reports.
    • Dr. Eggbot – designs new bots, audits existing ones, and can replace Zapier‑style automation.
    • Matcha – acts as a project manager, aiming to replace ClickUp.
    • Potato – monitors X/Twitter mentions every 30 minutes for engagement opportunities.
    • Podcast – converts long documents or videos into short audio summaries.
    • Crum – scans hard drives monthly to flag large files for deletion.
    • Sookie – handles travel, lunch, and reorder requests, booking via DoorDash or hotels when a credit card is supplied.
    • Designer – creates brand‑consistent graphics and repurposes them for ads, social media, and banners.
    • Inbox – manages email junk, labeling, and drafting replies, positioned as a Superhuman alternative.
    • Idea Team – simulates an advisory board with personas such as Bezos, Hormozi, and Buffett to critique ideas.
    • Calendar – books meetings from screenshots or messages, removing the need for Calendly.
    • Writer – mimics your email/Slack style to produce human‑sounding copy, aiming to replace Grammarly Pro.
    • Marketplace Seller – lists items from photos, writes descriptions, and handles negotiation on Facebook Marketplace or eBay.
    • JobProof – posts finished‑job photos to your site and automatically requests customer reviews.

    Alongside the bot descriptions, the video highlights the GrokBot subscription model: a $30/month plan advertised with a 50 % discount, bundling access to GrokBot, Cursor, Grok, and X/Twitter integration. The presenter also invites viewers to join the free Dopamine Digital School community to obtain the full prompt library.

    Step‑by‑Step Walkthrough

    To replicate the setup shown in the video, follow these general steps for each bot:

    1. Access the GrokBot dashboard and navigate to the “Prompts” or “Employees” section.
    2. Select the desired prompt (e.g., “Chief of Staff”) from the library provided in the Dopamine Digital School group.
    3. Copy the prompt text into a new bot configuration.
    4. Connect any required external accounts via the GrokBot apps panel (Gmail, X/Twitter, DoorDash, etc.).
    5. Set the bot’s trigger frequency or schedule (e.g., daily report at 8:00 a.m., Twitter scan every 30 minutes).
    6. Test the bot with a sample input to verify output matches expectations.
    7. Activate the bot and monitor its performance for the first week, adjusting parameters as needed.

    The video emphasizes that once a bot is live, you can interact with it through multiple channels—directly in the GrokBot app, via Slack, Gmail, text messages, or Telegram—and that the bots can communicate with each other, allowing you to delegate to a single point of contact.

    Tools, Numbers, and Claims

    The presenter ties each bot to specific quantitative benefits:

    • Chief of Staff: ~5 hours saved per week.
    • Matcha: ~3 hours saved per week, up to $7,670 annual savings (positioned as a ClickUp replacement).
    • Designer: ~$4,700 saved per year.
    • Inbox: ~5 hours saved per week and ~$200 saved per year (Superhuman alternative).
    • Podcast: generates audio summaries for on‑the‑go consumption (no specific dollar figure).
    • Crum: frees storage by identifying large files (no specific dollar figure).
    • Sookie: handles travel/lunch requests and can book via DoorDash or hotels when a credit card is provided.
    • Marketplace Seller: automates listings and negotiations on Facebook Marketplace or eBay.
    • JobProof: automates review requests after job completion.

    The video also cites a daily earning figure of $208, which appears to be an aggregate projection based on the combined savings of the bots. The GrokBot plan is presented at $30/month with a 50 % discount, and the Dopamine Digital School group is noted to have 8,700 members.

    Caveats / Hype Check

    The video makes bold earnings claims (e.g., $208 per day, $7,670 per year savings) that are presented as typical results without evidence or disclaimers; these should be treated as speculative projections rather than guaranteed outcomes.

    Because the savings figures are not backed by case studies or user data within the video, viewers should approach them as optimistic estimates. Actual results will depend on how well the prompts are tailored to individual workflows, the accuracy of the AI’s outputs, and the extent to which external integrations are configured correctly. Additionally, the claim that the bots “will talk to each other so you only have to communicate with one bot” assumes proper setup of inter‑bot communication features, which may require additional configuration.

    Concrete Next Actions

    If you decide to experiment with the GrokBot employee concept, consider the following actions:

    • Join the free Dopamine Digital School group to access the full prompt library.
    • Upgrade to the $30/month GrokBot plan to take advantage of the advertised 50 % discount.
    • Begin with the Chief of Staff prompt: copy it, create a bot, connect your Gmail and calendar, and set a daily 8:00 a.m. report.
    • Repeat the copy‑and‑configure process for each of the remaining 13 prompts, adjusting triggers (e.g., Potato’s 30‑minute Twitter scan, Crum’s monthly drive scan).
    • Test the Podbot by feeding it a lengthy report or video link and listening to the generated audio summary.
    • Activate Sookie for a travel or lunch request, providing a test credit card to verify booking flow.
    • Deploy the Marketplace Seller bot by uploading a product photo and letting it draft a description and negotiate price on Facebook Marketplace or eBay.
    • Use Dr. Eggbot to audit your existing bots and suggest new automation opportunities.
    • Monitor time saved and cost avoided over a four‑week period to assess whether the projected savings align with your actual experience.

  • Marketing & Lead Gen: My AI Agency Is Boring, But I Make $35,015/mo (WITH PROOF)

    Watch on YouTube: https://www.youtube.com/watch?v=KvAaZfj5uTI

    Channel: Caleb Kuechly

    Introduction

    Caleb Kuechly explains how he built a modest‑sounding AI agency that generates more than $35,000 per month by selling three repeatable AI systems to local businesses. The focus is on specialization, targeting clients whose average new customer is worth at least $1,000, and using a simple outreach process to land the first paying client.

    What the video covers

    The presentation walks through three AI‑driven pathways that all aim to book appointments for a client:

    • Pathway 1 – AI voice or SMS follow‑up that contacts leads instantly until they schedule a call.
    • Pathway 2 – An AI chatbot on a clean, one‑page website that answers questions, books appointments, and re‑engages old leads.
    • Pathway 3 – An AI “content engine” that watches social‑media comments for a keyword and sends a direct message to book a call.

    He also shares pricing structures, the tools he uses, and a step‑by‑step client‑acquisition workflow that requires no coding background.

    Step‑by‑step walkthrough

    • Set up a professional email address on your own domain.
    • Create a simple one‑page website with a single “Book a free AI audit” button and embed your calendar link.
    • Use an AI lead‑generation tool (e.g., search “your business type + your city”) to collect 100 local businesses, capturing owner name, email, and website.
    • From that list, pick the top 30‑40 prospects and reach out 20 per day with a short screen‑recorded video that points out one specific leak on their site and invites them to the free audit.
    • Send a one‑line bump email a couple of days later, then follow up with a personalized selfie‑video text a few days after that.
    • During the audit call, ask how they currently acquire customers, show the gap on their website, and present three ways to work together (setup fee + monthly retainer).
    • When the client pays, onboard them and deploy the pre‑built AI system (voice/SMS follow‑up, website chatbot, or content engine) within a week.
    • Monitor booked appointments, deliver results, and repeat the outreach process to replace any churned retainer clients and scale toward $35k+/month.

    Tools and numbers mentioned

    • Monthly retainer: ≈ $2,450 per client.
    • Setup fees: range from $5,000 to $7,800 (examples given: $5k, $6.8k, $7.8k).
    • Recent 4‑week revenue: $41,100 (shown as proof).
    • Target monthly income claim: $35,000/mo.
    • Number of businesses contacted in the example: 563.
    • Core tools: AI lead‑generation tool, own‑domain email, one‑page website, calendar link, payment processor, voice/SMS AI follow‑up, website AI chatbot, AI content engine, free AI audit offer.

    Caveats / hype check

    The $35,000/mo figure is based on a selective four‑week snapshot ($41,100 shown) and is not presented as a guaranteed average. Caleb also promotes a paid program in the video description, so the income claim should be viewed as aspirational. Success depends on finding a market where a new customer is worth at least $1,000 (e.g., law firms, HVAC, med spas, coaches) and executing the outreach process consistently.

    “Specialists get paid, not generalists.”

    “The first client is really the only thing standing between you and the start of all this.”

    “If a law firm or a roofer is consistently losing jobs, those might be worth 20,000, 50,000, even 100,000 dollars each.”

    Concrete next actions

    • Set up a professional email on your own domain.
    • Build a simple one‑page website with a single “Book a free AI audit” button and embed your calendar link.
    • Use an AI lead‑generation tool to gather 100 local businesses (owner name, email, website).
    • Select the top 30‑40 prospects and reach out 20 per day with a short screen‑recorded video highlighting one site leak and inviting them to the free audit.
    • Send a one‑line bump email a couple days later, then a personalized selfie‑video text a few days after that.
    • On the audit call, ask about their current customer acquisition, show the website gap, and offer three collaboration options (setup fee + retainer).
    • Upon payment, onboard the client and deploy the pre‑built AI system (voice/SMS follow‑up, website chatbot, or content engine) within a week.
    • Track booked appointments, deliver results, and repeat the outreach to replace churned clients and scale toward $35k+/month.

  • Marketing & Lead Gen: Make cool things with AI that people buy (Gemini 4 Argon)

    Watch on YouTube: https://www.youtube.com/watch?v=jEOUUAPC1sc

    Channel: Greg Isenberg

    Introduction

    Greg Isenberg shares a week‑long hands‑on experiment with Gemini Argon, Google’s frontier model, demonstrating three concrete ways to turn the AI into sellable products. The video is framed as a practical guide for marketers, product builders, and indie hackers who want to move beyond static content and create interactive experiences, customizable physical goods, or upgraded legacy SaaS tools.

    What the video covers

    • How Argon can generate interactive, game‑like websites when supplied with visual references.
    • Techniques for getting the model to write in a personal voice by feeding it writing samples and turning those into reusable skill packages.
    • A workflow for designing customizable physical products (e.g., snowboard graphics, espresso portafilter stations) as STL files and sending them to on‑demand 3D‑print services.
    • How embedding a product‑customizer widget in a Shopify store creates a niche physical‑AI business with reported 40‑70 % margins.
    • A strategy for identifying boring, recurring problems on G2, Capterra, or Idea Browser, building a free utility with Argon, then upselling premium features.
    • Six Argon‑specific prompt‑engineering methods: /plan, /sub‑agents, /goal, /browser, /learn, and running in high mode.
    • Pricing and subscription details for Google AI Ultra versus the Pro plan, and the token limits associated with each.
    • Revenue and cost anecdotes from Greg’s earlier website project, and suggested price points for customizable physical goods.

    Step‑by‑step walkthrough

    1. Building an interactive website

    Start by gathering a visual reference — such as a mood board or a screenshot of a site you admire. Prompt Argon with that reference and ask for a “better version” of the site. Use the /plan command to outline the desired pages and interactions before letting the model edit files. Enable /browser so Argon can test live URLs or UI flows during development. Iterate with /learn to turn corrections into reusable rules for future prompts.

    2. Creating a customizable physical product

    Ask Argon to generate STL files for a product you want to customize (e.g., a snowboard design or an espresso portafilter station). Provide any brand guidelines or reference images via the /goal command to steer the output toward higher‑quality designs. Once the STL files are ready, connect them to an on‑demand 3D‑print API such as Slant 3D or send them directly to a Bambu printer. Embed the resulting product‑customizer widget in a Shopify store, set a price (the video suggests $39‑$49 range), and fulfill orders through the 3D‑print API. The cited margin range for this model is 40‑70 %.

    3. Rebuilding a legacy SaaS tool

    Search G2, Capterra, or the free Idea Browser for boring, recurring problems that users complain about. Build a free utility that solves the core pain point using Argon — leverage /sub‑agents to parallelize research and skill‑creation tasks. After the free tool gains traction, add premium features and monetize. The video notes that this approach mirrors the pattern of offering a free entry point then upselling, a common SaaS growth tactic.

    Tools and numbers mentioned

    • Google AI Ultra – $100 / month (includes Anti‑gravity app/CLI and up to 1 M output tokens)
    • Google AI Pro – $19.99 / month (lacks Ultra features)
    • Anti‑gravity app & CLI
    • Slant 3D print‑on‑demand API
    • Bambu 3D printer
    • Shopify (for storefront and widget embedding)
    • G2.com, Capterra.com, Idea Browser (free)
    • Estimated effort for Greg’s earlier website: 40,000 hours
    • Estimated build cost: ~$200,000
    • Reported revenue from that website: >$40 million
    • Suggested retail price for customizable product: $39 (espresso portafilter station example at $49)
    • Physical product margins: 40‑70 %
    • Maximum output tokens with Ultra plan: up to 1 million

    Caveats / hype check

    Greg makes strong revenue and margin claims (e.g., his website allegedly generated >$40M from a $200k build, physical product margins of 40‑70 %, and the ability to quickly rebuild legacy SaaS) without providing verifiable data or third‑party validation. These statements should be treated as aspirational rather than proven results.

    The video is sponsored by Google, which gave Greg early access to Argon. While the prompt‑engineering techniques and workflow ideas are concrete, the financial outcomes presented lack independent verification. Readers should treat the revenue and margin figures as illustrative possibilities rather than guaranteed benchmarks.

    Concrete next actions

    • Give Argon visual or textual references (mood boards, writing samples) before requesting creative output.
    • Use the /plan command to outline what you want built before letting Argon edit files.
    • Leverage /sub‑agents to parallelize research and skill‑creation tasks.
    • Apply /goal with a reference image to steer Argon toward higher‑quality designs.
    • Enable /browser to let Argon test live URLs or UI flows during development.
    • Turn corrections into reusable rules with /learn to improve future prompts.
    • Run Argon in high mode for better overall output after testing on medium to understand the tool.
    • Build an interactive website by prompting Argon with a reference site and asking for a “better version.”
    • Create a physical product customizer: ask Argon for STL files, then connect to Slant 3D or a Bambu printer for on‑demand production.
    • Identify a boring SaaS pain point on G2/Capterra/Idea Browser, build a free tool with Argon, then monetize with premium features.
    • Embed the product‑customizer widget in a Shopify store, set price (e.g., $39), and fulfill via 3D‑print API.
    • Track demand signals from niche Reddit communities (e.g., r/espresso) to validate product ideas.

  • Grok Bot unlocked my business

    Watch on YouTube: https://www.youtube.com/watch?v=RM8ZwhoJdeg

    Channel: Brian Casel

    Introduction

    Brian Casel explains how he has restructured his use of Grok Bot so that each bot functions like an employee rather than an on‑demand assistant. By giving the bots defined jobs, background work such as marketing, growth experiments and operations runs automatically, freeing him to focus on product development in Claude. The approach relies on reusable agent skills, a nightly sync from a private GitHub repository, and dedicated email addresses for approvals and reporting.

    What the video covers

    The video walks through the full system Brian has built around Grok Bot. It shows how skills are stored in a GitHub repo called “HQ operations,” how each bot pulls the latest version of those skills every night, and how a simple routine in Grok Bot merely triggers the skill that contains all the instructions. He describes daily growth run experiments that start at 7:00 a.m., weekly growth experiments, quarterly bookkeeping reviews, and the use of Agent Mail to give each bot a unique email address for KPI pulses, experiment bets, task approvals and quarterly strategy reviews. The discussion also touches on the time he spends in Claude refining skills rather than chatting with the bots, and how the model scales when adding new bots or products.

    Step‑by‑step walkthrough

    • Define a clear job for each bot (e.g., “Chief bot handles marketing reports,” “Muse manages experiment tracking”).
    • Write the full set of instructions for that job inside an agent skill document.
    • Store all skill documents in a private GitHub repository (HQ operations).
    • Configure each Grok Bot to sync the repository nightly, ensuring it always runs the latest version of the skill.
    • Create a routine in Grok Bot that does nothing more than trigger the skill; the routine itself contains no logic.
    • Set up a unique email address for each bot using Agent Mail.
    • Establish email conventions: subject lines for KPI pulses, experiment bets, task approvals, and quarterly reviews to keep the inbox organized.
    • Schedule the daily growth run experiment to start at 7:00 a.m.; the bot logs results automatically.
    • Run weekly growth experiments and quarterly strategy reviews via the same email‑based approval flow.
    • Spend the majority of working time in Claude refining and updating skills, rather than interacting directly with the bots.
    • When adding a new bot or product, give it an email address, point it at the GitHub repo, and let the nightly sync bring it up to speed.

    Tools and numbers

    • Grok Bot – the platform hosting the bots.
    • Agent Mail – service that provides each bot with a unique email address.
    • GitHub repo (HQ operations) – stores all agent skills and SOPs.
    • Claude – environment where Brian refines skills.
    • Buildermethods.com/workshop – free workshop on designing agent skills.
    • Approximately half of Brian’s total workload is handled by the bots.
    • Six items typically require approval in the weekly cycle.
    • Named bots in the example: Chief bot, Muse, Dots, Open Claw.
    • Daily growth run experiments at 7:00 a.m.
    • Weekly growth experiments and quarterly bookkeeping reviews.

    Caveats and hype check

    Brian’s claim that the bots handle about half of his workload is based on his personal experience and has not been independently verified. The video does not promise specific revenue gains or include affiliate promotions. The system’s effectiveness depends on the quality of the agent skills, the reliability of the nightly GitHub sync, and the discipline to maintain email conventions. As with any automation, initial setup time and ongoing skill maintenance are required.

    Concrete next actions

    • Watch the free AI skill‑design workshop at buildermethods.com/workshop to learn how to create reusable agent skills.
    • Treat each bot as an employee with a defined job rather than a task‑by‑task assistant.
    • Create a private GitHub repository to store all agent skills and standard operating procedures.
    • Configure each Grok Bot to sync the repository nightly so it always runs the latest version of its skill.
    • Set up a unique email address for each bot using a service like Agent Mail.
    • Design email subject‑line conventions for KPI pulses, experiment bets, task approvals, and quarterly reviews to reduce inbox friction.
    • Build skills that encapsulate the full set of instructions; keep Grok Bot routines simple (just trigger the skill).
    • Automatically log bot runs (e.g., experiment results) to maintain visibility without micromanaging.
    • Iterate on email content with Claude to further reduce noise and improve clarity.
    • Schedule regular reviews to retire outdated skills and update the repository as processes evolve.