resources

← prev · next →

Ryva Master GTM Plan (Second-Run Focus)

Ryva Master GTM Plan (Second-Run Focus)

Date: 2026-04-03 Owner: Ege Window: Next 30 days

Objective

Turn first-run curiosity into second-run habit, then paid dependency.

Core Thesis

  • First run = interesting.
  • Second run = behavior change.
  • Third run = dependency.
  • No second run = no GTM progress, even with high reply volume.

What We Optimize For

  • Depth over breadth.
  • 3 active teams at a time (CyberMinds + 2).
  • Delta updates over full summaries.
  • Urgency and risk, not just correctness.

Non-Negotiables (Every Run Message)

  1. Reference last run.
  2. Show what changed vs what is still unresolved.
  3. Tie unresolved item to concrete risk/cost.
  4. Ask one forced binary question.
  5. Time-anchor next run (“after next merge cycle”, “before standup”, “EOD”).

If a message misses any of the 5, it does not ship.

Offer Structure

  • Do not sell on first run.
  • Ask for continuation, not commitment:
    • “Want me to run this again after your next merge cycle?”
  • Payment ask only after run #2 or #3:
    • “If this replaced standup reconstruction this week, would you pay for it?”

Daily Execution (Simple)

  1. Active-team block (first 2 hours)
  • Send second-run delta updates to all 3 active teams.
  • Include 1 forced binary question per team.
  • Lock next-run timing in-thread for responders.
  1. Warm-responder conversion block
  • Send first-run artifact to 5 warm responders (not cold leads).
  • Use their exact pain wording.
  • End with one forced question.
  1. Outreach block (top-of-funnel maintenance)
  • 10 targeted X replies/DMs.
  • 10 targeted Reddit replies/DMs.
  • Insight-first, no feature pitch.
  1. Proof distribution block
  • Publish 1 short proof post (X/LinkedIn/Reddit rotation).
  • Show one real missed decision + one “do this now” action.

Message Templates

First Run (Warm Responder)

You mentioned [pain]. Pulled a pass from your last 24h:
- Decisions made: [x]
- Missing decision: [y]
- Next action: [z]

Is [y] actually decided or still open?

Second Run (Delta)

Since last run:
- Changed: [x]
- Still unresolved: [y]
- New risk: [z impact]

Is [y] still blocked or resolved?
I will rerun this after your next merge cycle and send what changed.

Payment Trigger (After Habit Signal)

This is the third cycle where we caught decision drift before it became rework.
If this replaced standup reconstruction this week, would you pay for it?

Qualification and Drop Rules

  • Keep only teams with:
    • explicit standup/context pain
    • active project motion
    • at least one real reply
  • Drop when:
    • no response after 2 high-quality run attempts
    • generic interest but no workflow engagement

Metrics That Matter (Daily)

  • Runs sent
  • Second runs completed
  • Follow-ups scheduled
  • Meaningful replies
  • Teams with weekly cadence
  • Payment conversations started

Ignore vanity metrics (views, likes, impressions) for decision-making.

30-Day Targets

  • 20-30 meaningful conversations
  • 10+ repo runs
  • 5+ second-run loops completed
  • 3-5 teams using weekly
  • 1-2 payment conversations

Weekly Review (30 min)

  • Which messages created second runs?
  • Which risk framings triggered replies?
  • Which teams are approaching dependency?
  • Which threads should be killed?

Start Today (No Warm-Up)

  1. Select 2 teams besides CyberMinds.
  2. Send 3 second-run delta messages in the first 2 hours.
  3. Get 2 next-run timings confirmed in-thread.
  4. Drop low-signal threads immediately.

This plan wins only if run cadence is enforced daily.