resources

← prev · next →

Ryva Weekly Playbook

Ryva Weekly Playbook

Week of Apr 13, 2026 One metric: did one team ask for the next run without you prompting it? Win odds if you execute: 70-80%

The Only Metric This Week

Did one person ask for the next run without you prompting it?

That is it. Everything else is noise.

Daily Non-Negotiables

These run every single day regardless of what else is happening:

  • 10 high-quality ICP replies split between X and Reddit, under 1 hour total
  • Follow up every active thread before opening new ones

Outreach Channels, Ranked by Trust Speed

Warm intro via CyberMinds, do this today first

Ask them one thing: Do you know any other dev teams who deal with the same coordination mess? I would love an intro.

One yes from them beats everything below. The CTO already trusts the source, you skip the entire credibility-building phase. Time to first run: same day if the intro lands.

Active pain threads, today and tomorrow

Find threads posted in the last 48 hours where a CTO or eng manager is actively complaining about standups feeling useless, PRs sitting idle, nobody knowing what is actually decided, or context dying between tools.

Reply publicly in the thread with a Ryva run on their repo. Not a DM. Public. So they see proof before you ever ask for anything. They are mid-pain when they see it, trust is instant.

White glove cold, 10 funded startups, throughout the week

Find startups with a public repo, active commits in the last 30 days, and a CTO identifiable on LinkedIn or GitHub. Run Ryva on each repo. Find the single sharpest gap. Send one line:

Subject: [repo name] Ran this on your repo. [specific gap], no owner assigned. Still the case?

No pitch. No demo link. No explanation of what Ryva is. Just the gap. Expected reply rate: 1-2 out of 10 if the gaps are sharp.

The Stickiness Formula

The first run gets curiosity. The second run has to show a delta, what changed and what is still unresolved. The third run has to feel like they would be missing something without it.

After every run, always end with: I will recheck this after your next PR batch, Wednesday work?

Name the trigger. Name the day. They either confirm or correct it. Either way you own the next move.

Full Weekly Schedule

Monday, Apr 13

Priority: get everything in motion today.

  • Message CyberMinds, ask for the warm intro, do this first before anything else
  • Message George Rios, one question only: did you show your client the run yet? Do not pitch, do not explain Ryva
  • Rayan run 3, reply immediately with a delta: what changed since last run, what is still unresolved, one question. Ask: before or after your next standup?
  • Run Ryva on s2.dev, find the sharpest gap, find founder email, send the one-line message
  • Run Ryva on 21st.dev, same
  • Client conversation, run their repo before the call, go in with the gap visible
  • 10 ICP replies X/Reddit under 1hr
  • X post 1, proof post, 1 of 3 this week

Tuesday, Apr 14

  • Follow up George Rios if no reply yet
  • Follow up on client thread
  • Run Ryva on Notte, gap, one-line message
  • Run Ryva on Moss, gap, one-line message
  • Run Ryva on Kernel, gap, one-line message
  • 10 ICP replies X/Reddit under 1hr

Wednesday, Apr 15

Follow up every active thread before opening new ones.

  • Follow up on every thread that has replied
  • Run Ryva on Trigger.dev, gap, one-line message
  • Run Ryva on Signadot, gap, one-line message
  • Run Ryva on Inngest, gap, one-line message
  • 10 ICP replies X/Reddit under 1hr
  • X post 2, proof post, 2 of 3 this week
  • Ryva blog post, SEO, under 30 mins. One focused topic: a gap Ryva found in a real repo, anonymised. Publish.

Thursday, Apr 16

  • Follow up active threads first, no new outreach until this is done
  • New outreach only after follow-ups are closed
  • 10 ICP replies X/Reddit under 1hr

Friday, Apr 17

  • Follow up active threads first
  • New outreach after
  • 10 ICP replies X/Reddit under 1hr
  • X post 3, proof post, 3 of 3 this week
  • Verify: 10 runs sent total by end of day
  • Check the metric: has anyone asked for the next run without you prompting it?

Saturday, Apr 18

  • 10 ICP replies X/Reddit under 1hr
  • Light follow-ups only, no new repo runs today

Sunday, Apr 19

  • egeuysal.com blog post, SEO, under 30 mins. Write it, publish it, done. Do not let this bleed into Monday.
  • 10 ICP replies X/Reddit under 1hr
  • Review the week, did one person ask for the next run unprompted?

Target Repos

Monday: s2.dev, 21st.dev Tuesday: Notte, Moss, Kernel Wednesday: Trigger.dev, Signadot, Inngest Thursday and Friday: close active threads first, then new targets

Active Threads to Manage

  • CyberMinds warm intro, ask today, first thing. One yes from them is worth more than all cold outreach combined.
  • George Rios, one question Monday: did you show your client the run yet? Follow up Tuesday if no reply.
  • Rayan run 3, Monday. Reply with delta immediately. What changed. What is still open. One question. Ask before or after next standup.
  • Client conversation, Monday. Run their repo first. Go in with the gap already visible, not with a pitch.

Content Schedule

  • Three X posts this week, Monday, Wednesday, Friday. Proof posts only, not general posting.
  • One Ryva blog post, Wednesday. One topic, one gap, under 30 minutes.
  • One egeuysal.com blog post, Sunday. Under 30 minutes. Write it, publish it, move on.

No other content. No Reddit posts. No LinkedIn. No diary. No IBX.

Kill List

Anything on this list kills your momentum. If you catch yourself doing any of these before someone has replied, stop.

  • Blog posts beyond the two scheduled ones above
  • IBX improvements
  • Diary entries
  • Tooling
  • Reddit mass DMs
  • X posting beyond the 3 scheduled proof posts
  • LinkedIn, dead, do not touch
  • Opening new outreach before closing the active threads that replied
  • Sending a full report dump instead of one sharp gap
  • Not embedding a next-run trigger in the same message as the run

What Will Kill It

Sending a full report dump instead of one sharp gap will kill it.

Not naming the next run trigger in the same message will kill it.

Opening new outreach before locking the warm thread that replied will kill it.

Spending Monday on IBX, blog posts, or tooling instead of this list will kill it.

Finding Their Email

For each founder, check their GitHub profile first. Most technical founders have an email in their bio or commit history. If not, check their personal site. LinkedIn DM is a fallback but email converts better.

Do not use contact forms. Do not use info@. Do not send a LinkedIn connection request first.