Первый заказ на вайбкодинг на фриланс биржах

Business goal & go-to-market approach (as a freelancer)

• The creator rejects “classic” lead-gen for wipe coding (e.g., Telegram spam and cold calls) because it requires continuous outreach and repeated rejection, making a stable pipeline difficult.
• Alternative strategy: get the first order via freelance marketplaces, where buyers have already posted demand—reducing “coldness” and increasing reply/job probability.

Playbook mindset

“First you work for your gradebook, then your gradebook works for you”

• Early focus on reviews/portfolio to enable more passive incoming orders later.

---

Marketplaces tested + operational learnings

1) pro.ru (initial test)

• Seed budget: 1,000 rubles
• Observations:
  • Many posted tasks weren’t a fit (e.g., Tilda/Bitrix templates, unclear scope, or tasks that can’t be “wipecoded” under stated constraints).
  • Some tasks had insufficient detail or high risk.
  • Outreach cost: spent ~1.5 rubles on a set of responses while iterating quickly (the video later notes the budget being fully spent, but exact per-response cost fluctuates across mentions).
• Outcome:
  • Took a lot of time “waiting and responding,” but produced almost no meaningful traction.
  • Only 2 responses led to money being returned:
    • One client cancelled.
    • Another didn’t proceed/consider the bid.
  • After that, the creator largely abandoned pro.ru due to low ROI.

2) Kwork (later, longer effort)

• Timeframe:
  • “Almost a month later” got the first real order.
  • Started roughly in the 19th–20s of August.
  • Fulfillment timeline shows replenishment date: Sept 19.
• Activity:
  • Completed 20 responses, with 10 of 30 remaining (mid-process state described).
• Outcome:
  • The first actual order was secured after spending most of the effort on Kwork rather than pro.ru.

---

Response/offer process (tactical execution)

• The creator learned that response writing matters; they use a structured, benefit-focused approach rather than generic “I can do it.”

Example response structure

• Describe the problem you solve for the client (the benefit), not just your capabilities.
• Keep the pitch short and dynamic—suited to MVP-style tasks.

Concrete response examples

• For a Telegram Mini App MVP:
  • Goal: fast registration/access, show progress, login via Telegram, personal account, balance/status, QR confirmation.
  • The response was drafted around authorization/security and “shop-free” registration, emphasizing a mobile-native fast interface.
• For image generation / landing-page photo filling:
  • Initially offered full work, but realized better conversion comes from offering 1–2 test previews first, so clients may approve quickly and close faster.

Conversion assumptions

• On average, you need to leave 10–15 responses to get a task.

Outreach cost sensitivity

• The creator argues it’s not practical when marketplace bid economics imply you can’t profit (e.g., spending ~1,000 rubles budget to land work that effectively pays ~500 rubles).

---

KPI / metrics explicitly mentioned (business performance indicators)

• Outreach volume
  • pro.ru: only 2 responses resulted in refunds; the overall period involved many attempts with minimal success.
  • Kwork: 20 responses submitted (with 10 remaining out of 30).
• Time to first paying order
  • pro.ru: no first paying order “before abandoning it.”
  • Kwork: roughly within ~1 month from repeated response activity.
• Budget & spend
  • pro.ru seed budget: 1,000 rubles; later noted the money was spent with little left.
  • pro.ru earlier exchange segment: ~1.5 rubles spent on responses.
• Revenue
  • First completed order value: 1,552 rubles.
• Conversion quality
  • pro.ru responses often ended in cancellation/no engagement, implying low effective conversion and wasted bid spend.
• Deliverable delivery
  • Completed website in 3 days (from the final review).

---

Concrete case study: first successful marketplace order

Task

• Create a website for a publisher of a scientific electronic journal.

Process

• Several rounds of correspondence before starting.
• The creator proposed layout/style options generated using GPT Chat.

Delivery

• Built on WordPress
• Time: 3 days

Result (review + monetization)

• Review excerpt:

  “Excellent work… created a website on WordPress in 3 days… good design taking into account wishes.”

• Payment received: 1,552 rubles

• Portfolio: added immediately; promised a separate build video.

---

Actionable recommendations distilled from the video

• Prefer marketplaces over cold outreach early on because:
  • Buyers already posted needs → higher relevance and less “coldness.”
  • Early reviews/portfolio can create more passive inbound.
• Response writing playbook:
  • Replace “I can do X” with: “here’s how I help you and what you receive.”
  • Provide scope clarity and propose a fast next step (especially for MVP/approval tasks).
• Bid strategy / risk management:
  • Avoid unclear scope, template-heavy requirements, or where you can’t reliably match the “wipe coding” constraints.
  • Watch economics: ensure the cost to bid/respond doesn’t exceed likely payout/ROI.
• Offer structure for higher acceptance rate:
  • For creative/AI-deliverable tasks: offer 1–2 test previews first to speed approval and reduce wasted effort.

---

Frameworks / playbooks referenced

• “Gradebook flywheel”: early effort → reviews/portfolio → improved incoming opportunities.
• MVP framing (Telegram Mini App): prioritize speed/simplicity of the core user journey.
• Pricing/scope structure expectation: staged estimates and timeline per stage as a quality filter for proposals.

---

Presenters / sources

• Presenter/source: the video’s single creator (freelancer) documenting freelancing experiments on pro.ru and Kwork (name not provided in subtitles).