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
/plancommand to outline what you want built before letting Argon edit files. - Leverage
/sub‑agentsto parallelize research and skill‑creation tasks. - Apply
/goalwith a reference image to steer Argon toward higher‑quality designs. - Enable
/browserto let Argon test live URLs or UI flows during development. - Turn corrections into reusable rules with
/learnto 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.
Leave a Reply