Quality day: old-DM reactivation and second-run signal
Apr 10, 2026 · Day 36
Today was mostly a follow-up day, not a pure outbound day.
I focused on old DMs and buried threads that never got proper replies. That strategy keeps working much better than cold-first volume.
Main takeaway: volume dropped, but quality went up a lot, and that is the right trade right now.
What I shipped
Channel + content output:
Core runs:
This is exactly the type of thread that can convert.
What improved today
The message style improved.
The warm follow-up angle of:
- acknowledge their process
- show where decisions still stall right now
- provide one concrete run link
- ask one direct forced question
worked much better than generic feature talk.
This style is currently the best converter in DMs.
Core loop lesson from Brawl Stars
I also had a useful flashback today.
When I was deep into Brawl Stars, I built a club from zero to 5M+ trophies in under 2 months and we hit #1 in Turkey soon after. Back then it felt like pure obsession, but looking back it was actually a repeatable GTM loop:
- bring people in
- give them reasons to stay (events, rewards, status)
- they invite others
- repeat
The core loop stayed fixed. What changed constantly was distribution and messaging:
- where I posted
- how I pitched
- which benefits I highlighted
- how onboarding felt
So it was not random hustle. It was iteration around a fixed system.
Where it failed is just as important: when I stepped out, it collapsed. Growth was strong, but the system did not sustain on its own.
That maps directly to Ryva now:
- lock the core loop first
- experiment hard on channels and messaging
- but if retention/second-run behavior is weak, growth just scales churn
Product and technical progress
Owner/stall improvements from this cycle are now visible in real runs:
- owner mapping is more concrete
- deferral limbo detection is clearer
- missing-decision framing is easier for users to action
One response literally said this format changes behavior, which is the exact signal I’m optimizing for.
Next technical step emerging from feedback:
- suggest likely decision-maker by last-touch signals more reliably
Progress from the embedded JSON block
Used the embedded today-done JSON block as source of truth.
Today’s completed count:
- 20 done tasks
Priority breakdown:
- 11 priority-1
- 7 priority-2
- 2 priority-3
Estimated effort completed:
- 8.75 total estimated hours
Notable completed tasks from that JSON:
- sent 10 outreach messages
- filled CyberMinds weekly check-in issue
- sent interview request emails via Resend MCP
- checked old DMs for second-run opportunities
- published Rands/CTO Craft first post
- maintained daily second-run usage push
So execution was real even though channel volume was lower than usual.
Unresolved and risk
Still open:
- explicit next-run times are not locked in every warm thread yet
- duplicated GTM todos can split focus if not consolidated
Main risk:
- if rerun timing is not set in-thread quickly, warm intent decays
Tomorrow focus
Tomorrow and weekend will be heavier outbound.
Priority order stays:
- old warm follow-ups first
- lock second-run timing in-thread
- then broader outbound
I’m also likely dropping X/X Pro by Sunday and shifting more effort to Slack + Reddit-style communities where signal compounds better.
Quotes of today
this is a solid concept.
surfacing floating decisions is where things break in the long run.
I’m curious how this connects to real user impact, not just internal clarity.
Main result today: less noise, better quality, stronger warm-thread conversion, and a clearer path for a heavier second-run weekend push.