Video summary
No One Wants a Website - Build this instead!
Main summary
Key takeaways
Business shift: from “websites” to “business outcomes”
- Tech cycles reset roughly every 10–15 years (mainframes → PCs → web → smartphones), and the current reset is generative AI.
- Websites used to be a viable product (and a career/agency hook), but are now easy to generate:
- Website creation is increasingly automated (full sites from prompts; “build in 60 seconds”).
- Therefore, clients don’t pay for “pretty pages”—they pay for measurable results.
- Core repositioning:
- Stop selling websites
- Sell outcome systems that produce:
- More customers
- Better retention
- Smoother operations
- Less admin work
- More revenue
- A static website “sits there”; if it doesn’t convert, it’s not valuable.
Revenue model & unit economics (key numbers)
- One-time website project: ₹50,000–₹70,000 (up to ~₹1,00,000 for strong work)
- Monthly systems retainer: ₹40,000–₹50,000/month
- Retainer value comparison:
- 1 retainer client ≈ six one-time projects (as stated)
- Example earning claim:
- Freelancers can reportedly do ₹1.5–₹2 lakhs/month with 3–4 retainer clients (solo + AI coding agent + tools paid by client).
“Three builds” playbook (turn a gym website into a revenue system)
The speaker demonstrates converting a basic gym site into a money-making engine via three outcome modules.
1) Authentication + member dashboard (Operations + retention)
Problem in example
- Gym runs member management manually via WhatsApp groups (class bookings, attendance, payment reminders).
- Need real member login and member tracking.
Implementation approach (tools/frameworks)
- Clerk for authentication
- Middleware for protected routes
- Dashboard page
- Clerk hooks to fetch:
- logged-in user name, email, profile picture
Time-to-ship claim
- Setup took about ~5 minutes for the demonstrated flow.
Outcome/pitch framing (business outcomes, not “website features”)
- Members get accounts
- Can see training history, book classes, track progress
- Owner can see who is active vs churning
- “No more WhatsApp” (reduces admin burden and friction)
2) Automated email sequences (Retention + churn reduction)
Churn root cause (example)
- Members stop attending because they forget to show up (skip a week → skip two → churn).
Email cadence logic (rules)
- Welcome email upon signup
- Reminder 24 hours before booked class
- Re-engagement (“we miss you”) if no bookings in 2 weeks
Implementation approach (tools/frameworks)
- Resend for email automation (free tier highlighted)
- React Email templates
- Webhooks from Clerk (event-driven)
- Cron job for scheduled re-engagement:
- check bookings tables
- find users with no bookings in 14 days
- send the re-engagement email
Outcome/pitch framing
- “You never have to manually follow up again.”
- The system becomes a retention machine, not a “website feature.”
3) Programmatic SEO (Customer acquisition + predictable top-of-funnel)
Business problem (example)
- Local gyms aren’t ranking for searches like “Hyrox training Bangalore.”
- Without SEO, the site remains effectively invisible.
Strategy: Programmatic SEO (PSEO) pages
- Generate many targeted pages covering different intents/topics (e.g.,):
- Hyrox training
- nutrition
- windows (and other topic variants mentioned)
Implementation approach (process requirements)
- Create dynamic routes
- Generate topic data
- Ensure each topic has unique meta tags to avoid duplicate content
- Create SEO-optimized pages including:
- clean keyword targeting
- schema markup
- Google Search Console submission:
- manual sitemap submission or
- Indexing API / ping Google when publishing new pages
Outcome/pitch framing
- Create a landing page for every topic your customer searches
- Goal: gym shows up in Google for those keywords to drive free traffic “forever”
- Framed as a customer acquisition system, not a website update
Timing expectation (high-level claim)
- Shows up in Google “in a few months if we keep at it” (no specific KPI targets provided).
How to sell the offer (positioning + delivery model)
- The speaker’s “sales conversion” method:
- Take a pretty static site → add:
- authentication
- automated follow-up
- programmatic SEO
- Then pitch as:
- retention machine (emails + login + tracking)
- customer acquisition system (programmatic SEO)
- Take a pretty static site → add:
- Operational advantage:
- One person + AI coding agent can deliver work that used to require:
- designer, developer, marketing person, and ops manager
- One person + AI coding agent can deliver work that used to require:
- Competitive moat shifts:
- Instead of competing with other freelancers for “websites,” you’re replacing an entire team’s function by packaging outcomes.
Frameworks / playbooks explicitly used or implied
- Outcome-based productization (sell measurable business results monthly)
- Automated lifecycle messaging workflow:
- trigger-based (Clerk
user.created) - schedule-based (cron; inactivity threshold of 14 days)
- trigger-based (Clerk
- Programmatic SEO system:
- dynamic page generation
- unique meta tags per topic
- schema markup
- sitemap + indexing automation
Concrete deliverables and actionable recommendations (from the example)
- Client onboarding
- Add member login/authentication (Clerk) so members have accounts and dashboards.
- Retention
- Deploy welcome + pre-class reminder (24h) + 2-week inactivity “we miss you” emails using:
- Clerk webhooks + cron jobs
- Deploy welcome + pre-class reminder (24h) + 2-week inactivity “we miss you” emails using:
- Acquisition
- Build topic-specific programmatic SEO pages and keep them indexable via:
- sitemap / indexing API in Google Search Console
- Build topic-specific programmatic SEO pages and keep them indexable via:
- Packaging
- Charge monthly retainer for ongoing system maintenance and improvements, rather than charging only for initial build.
Presenters / sources
- Presenter/source: One unnamed speaker/creator (no additional names provided in the subtitles).
- Tools/systems referenced:
- Clerk, Resend, React Email, OpenCode, Google Search Console (and Indexing API)
- Payments mentioned: Stripe and Razorpay