DEV Community

edhiblemeer
edhiblemeer

Posted on • Originally published at tasteck.tech

Build-in-Public Day 18: How I Turned PR Into an Evolving System with 3-Stage Cron + Self-Improving Loop

#saas #ai #productivity #buildinpublic

TL;DR

  • Day 17 used "v3 rules" (numeric AND-conditions + 60min observation loop) — followers +8/day pace established
  • Day 18: migrated 2-stage Cron to role-separated 3-stage Cron (12:30 量回 / 19:30 GT mix / 22:00 静的質回, 60 min each = 180 min/day)
  • Added self-improving feedback loop: metrics_collector → retro_analyzer → strategy_synthesizer → integrator (4 layers)
  • Strategic framework v2: Clausewitz hierarchy + Cialdini sequence (量 → 質) + 2-stage branding strategy
  • Followers 25 → 37 in 24h (+12, 4x previous pace)
  • Tier 1 fan signals achieved: 3 (DM + 2 conversational reply chains with industry keymen)

Why I Moved From 2-Stage to 3-Stage Cron

Day 16-17 used 2-stage Cron (11:30 / 20:00) — but this forced mixing quantity + quality + static work in same 60-min window, causing scattered focus.

Three types of work have different optimal timing:

  • Quantity (mechanical: likes, follows, cross-posts): Anytime, but X golden hours (12-13 / 19-23 / 23-25 JST) maximize impressions
  • Quality (context-dependent: deep replies, quote tweets): Match keyman online hours + thinking time
  • Static (blog/SEO/Pinned): Concentration block, separate mode from SNS

→ Solution: role-separated 3-stage Cron

Cron 3-Stage Design

Cron Time Role Tag Goal Required
1st 12:30-13:30 quantity_signal Lunch-hour quantity signal reply 5 / likes 30 / follow 10 / post 1
2nd 19:30-20:30 quantity_signal + quality_demo GT quality+quantity balance deep reply 5 / quote RT 2 / SEO axis 1
3rd 22:00-23:00 branding_close + seo_entry Static assets + next-day prep blog 1 / GSC 5 / dev.to series / Pinned / next-day kickoff memory

Safety rules (carried from v3): bulk-like upper limit + reply blanket approval + selector verification + memory log block + termination prohibition.

Strategic Framework v2

Clausewitz Hierarchy 

[Political Goal] Revenue
  ↓
[Strategic Goals = 2 Revenue Axes]
  A. SaaS subscription (B2B 7-verticals + B2C 2-verticals, scale-by-volume)
  B. Consulting / contract work (relationship-driven, ¥600k-900k per project)
  ↓
[Operations = PR overall = A·B shared infrastructure investment]
  ↓
[Tactics = Daily Cron 3 cycles]
Enter fullscreen mode Exit fullscreen mode

This hierarchy prevents the typical indie hacker trap: "+N followers" becoming an end in itself rather than a means.

量 → 質 Sequence (Cialdini Social Proof + Authority)

Signal What's seen Effect
Quantity (follower count) "○○ followers" displayed on profile visits Social Proof = first impression
Quality (keyman conversations) Conversations flowing in TL / quote RTs / Pinned Authority = fan conversion

"Quantity attracts attention → quality converts to fans → followers." Followers don't see other followers' quality directly — they see the quality of conversations flowing in TL.

Blog Dual Role

  1. SEO entry (Google traffic)
  2. Branding closure (SNS followers → profile → blog → authority confirmation → fan)

→ Each blog post gets both seo_entry + branding_close tags. This is why blogs intuitively have high ROI.

Self-Improving Feedback Loop (4 Layers) 

[Layer 1] Metrics (daily)
  metrics_collector — X / GSC / Note / signup → JSONL

[Layer 2] Evaluation (weekly)
  retro_analyzer — actions × metric trends → ROI table / Tier 1-3 fan conversion rate / warning flags

[Layer 3] Lateral Synthesis (monthly)
  strategy_synthesizer — untried combinations + competitor adaptation + external signals → 5-10 new strategy candidates

[Layer 4] Integration (on adoption)
  strategy_integrator — auto-update Cron prompts + deprecate underperforming tactics
Enter fullscreen mode Exit fullscreen mode

ROI formula:

Action ROI = (achievement × importance weight) / (tokens × 1000 + minutes × 0.1)
Enter fullscreen mode Exit fullscreen mode

Key insight: evaluate by time/token efficiency, not day-fixed targets.

2-Stage Branding Strategy (Long-Term TAM Breakthrough)

Niche vertical SaaS has a TAM ceiling. Solution:

  • Phase 1 (now → authority established): tasteck.tech brand, night-leisure industry focused
  • Phase 2 (after authority): vertical-neutral content, SaaS developers / indie hackers / consulting clients

Migration triggers: X 1,000+ followers / B-axis monthly 3+ deals / GSC #1 for brand-name search

Day 18 Morning Numbers (Reality Check)

Metric Day 17 end Day 18 morning Diff
X followers 25 33 +8 (while sleeping)
X following 82 85 +3
GSC 7d clicks - 88 (5/4-5/10)
GSC 5/10 daily - 13 / CTR 6.81% Highest recent CTR

End of Day 18: 37 followers (+12 / 24h, 4x previous pace)

Next Verification Points (Day 19-24)

  • Quantity/quality balance impact of 3-stage Cron (incl. Cron auto-fire reliability — REPL idle dependency is a structural issue)
  • Static-stage blog ROI (60 min writing → how many impressions / clicks)
  • Fan funnel conversion rate (Tier 3 → 2 → 1) initial measurement
  • Memory-based past-issue avoidance (selector conflicts / dialog blocks / etc.)

Closing

Strategy shouldn't be locked-in — it should be a system that evolves. AI-driven era allows building self-improving loops into the design itself.

Day 30 / Day 60 retrospective + meta-improvement scheduled.

🤖 Building tasteck (vertical SaaS) in public. Real-time logs at tasteck.tech/blog.

Top comments (0)