바이브 코딩으로 돈 벌 수 있을까?

Business goal & outcome

• The presenter experiments with “no-code/low-code” website creation (Vibe coding + GPT) to build a static monetizable service.
• Reported earnings: $12 in the first month (small, but positioned as ongoing passive revenue with minimal maintenance).
• Revenue claim: the site generates money “little by little” even while the creator sleeps, implying automated traffic + ads rather than manual sales effort.

Core strategy: small micro-service → monetize with AdSense

• Start by identifying a small personal inconvenience that could become a useful tool for others.
• Avoid building a “massive” service initially; instead create something concise and clear.
• Example pain point: as a solo game developer, resizing screenshots to meet store size limits.
  • Solution built: makejpg.com, an image editing site (Windows XP-themed images mentioned).
  • Positioning: useful and repeatable for the creator and potentially others with similar needs.

Execution framework / playbook (step-by-step)

1) Reduce operational costs using static hosting

• Problem with typical website operations:
  • Web server uptime
  • Domain purchase costs
  • Ongoing maintenance
  • Traffic management
• Proposed solution: use Cloud Player page (static hosting).
  • Benefit: no need to rent a server → avoids recurring monthly server/ops costs and reduces maintenance burden.
  • Tradeoff: only static pages (HTML/JavaScript) are supported—no dynamic features like accounts or boards.

2) Choose a “static-friendly” service scope

• Recommended constraints:
  • Build services that can be done with static pages.
  • Don’t plan features requiring server-side state (e.g., bulletin boards, user registration).

3) Build the site with an AI-assisted workflow (Vibe coding + GPT)

• Create a project folder → run Codex with a detailed service prompt.
• Mentioned settings/source:
  • Using GPT 5.5 High Mode.
• The AI prompt includes:
  • The service definition (static image editing; Windows XP theme)
  • A request to prepare for AdSense review
  • A request to structure the site so functions can be extended later
• Local verification:
  • Use Live Server in VS Code to test and confirm functionality (e.g., image size changes correctly).

4) Deploy and connect to hosting

• Upload the generated site to GitHub.
• Connect GitHub to Cloud Player so the homepage/content is published.

5) Monetization via Google AdSense: pass the review checklist

• Key challenge: AdSense review (“Adbot” is referenced as notoriously difficult).
• Core requirement: the site must not look like meaningless AI-generated spam.
  • The presenter emphasizes adding genuinely useful features and content.

AdSense preparation: 3 explicit requirements

• Functionality actually works
  • Avoid non-functional AI content that may be flagged as spam.
• The page must not be too empty
  • Include feature descriptions, how-to usage instructions, FAQs, and related tips on one page.
• Provide a basic policy set
  • Privacy policy
  • Contact page
  • About page

Process details

• AI can help draft “final preparations,” but:
  • Don’t submit AI output as-is—verify and check yourself.
• Timeline: review took about two weeks before approval.

Growth / marketing execution (without paid ads)

The promotion approach focuses on discoverability and community distribution.

Distribution + SEO basics

• Register the site with:
  • Google Search Console
  • Naver Search Advisor
• Add SEO items:
  • sitemap
• Goal: increase exposure when users search relevant keywords.

Community-based marketing (avoid spam)

• Post promotional messages in communities where target users already gather (image editing-related).
• Warning: don’t spam—can lead to criticism and no effect.

Organic outreach via community participation

• Join KakaoTalk design-related open chat rooms:
  • When users ask for tools (e.g., where to use a feature), respond with the site link and offer them a try.
• Tradeoff: described as inefficient (time/energy consuming), but free.

Metrics & costs mentioned

• Revenue: $12/month initially (AdSense-driven; not high, but covers some expenses).
• Domain cost: 20,000 KRW/year for makejpg.com.
• AdSense timeline: ~2 weeks to approval.
• Ops costs (qualitative): renting servers would create recurring monthly costs of “tens of thousands of won”, avoided via static hosting.

Risks / limitations (business execution realities)

• Static-site limitation:
  • Can’t implement dynamic community features (accounts, boards).
• Dependency on ongoing relevance:
  • Since growth relies on search/community discovery, traffic generation matters.
• Content quality gate:
  • AI output alone isn’t enough; AdSense rejects spammy-looking, low-value pages.

Recommended “order of operations” (concise playbook)

1. Identify a small personal inconvenience worth solving.
2. Ask AI to build a static web tool addressing it.
3. Deploy to Cloud Player (GitHub → hosting).
4. Prepare and submit for AdSense, ensuring:
   • working functionality
   • sufficient content (instructions/FAQs)
   • privacy/contact/about pages
5. After approval, drive traffic via:
   • Search Console + Naver tools + sitemap
   • community promotion in relevant groups (non-spam)
   • active participation to surface user needs.

Concrete example / case study

• makejpg.com
  • Purpose: image resizing/editing for a specific theme (Windows XP), inspired by the creator’s need to comply with screenshot size limits in a game store.
  • Built with Vibe coding + GPT with little/no manual coding.
  • Monetized with AdSense after passing review (about 2 weeks).
  • Growth via SEO tooling and community engagement in design/image-editing spaces.

Presenters / sources

• Presenter: The YouTube video creator (unnamed in the subtitles)
• Tools/platforms mentioned:
  • Vibe Coding
  • GPT (GPT 5.5 High Mode) / Codex
  • Cloud Player (static hosting)
  • Google AdSense
  • VS Code Live Server
  • GitHub
  • Google Search Console
  • Naver Search Advisor
  • KakaoTalk (open chat rooms)