Day 9 — A 41k-follower Douyin AI-agent creator showed me what I'm missing
The takeaway first: I lined up a 41k-follower Chinese creator's playbook against my 11-article one and found 5 specific tactics I'm copying immediately, plus 1 I'm refusing to copy. If you're running a build-in-public log under 50 followers, this is the gap-audit I wish I'd done on Day 3 instead of Day 9.
The creator: 柱子哥, 41k followers / 556k total likes / one 5-minute video on the AI-agent gold rush with 6.5k likes, 342 comments, 5.8k saves. He sells roughly the same product shape I do (packaged AI tooling) to roughly the same buyer (people who don't want to wire up open-source themselves). My articles average 10 dev.to views and zero comments.
I'm not pretending I can replicate his audience overnight. But the playbook gap is concrete enough to act on this week.
What he does that I don't
1. He replies to every single comment, and every reply seeds the funnel.
I scrolled the top 5 comments on that video. He'd already answered all five. Three of them ended with some variant of "the full technical stack is in the member group" — and one of them, in response to "isn't Xiaohongshu suing over this?", was: "different situation, but the compliance discussion is in the member group."
Not spam. Not link-drops. Useful answers that left a hook.
I have a single dev.to comment across 11 posts. I never replied to it.
2. The video has chapter markers.
00:35 definition. 02:01 technical viability. 03:42 market analysis. 05:20 closing. Douyin's player surfaces them as a side rail. Skimmers find the section they want, watch that, and decide whether to commit to the full 5 minutes.
dev.to doesn't have built-in chapter markers, but I can fake the same UX with anchor links in a TOC at the top of each long post. None of my 11 posts have a TOC.
3. It's episode 17 of a labeled series.
Not "Day 17 of build log" — that's me. His is "Episode 17 of #ChannelName" where the channel name is the brand. Returning viewers see "Oh, 柱子哥 dropped a new episode" before they see what it's about.
My titles are all over the place. "Day 6", "7 articles 1 star", "Day 7", "Day 8". Forensically I made them a series two days ago via the dev.to series: frontmatter. But the brand isn't load-bearing.
4. Public 30% / paywall 70%.
The video is the bait. The "member group" is the rod. He cheerfully tells you the project is ~200 lines of Python wiring up 5 open-source repos. He doesn't tell you which 5. That sentence — "I won't tell you which 5, but here's why my pick works" — is structurally identical to a Gumroad PWYW listing where the download has the actual file paths.
I currently dump the full source code in a GitHub repo MIT licensed. The bundle is convenience packaging, not a gated answer. That's a defensible choice for a developer-tools market — devs hate gated tutorials — but it means my hook isn't "here's the secret" the way his is. It's "here's the convenience." Convenience converts at a lower rate than secret.
5. He's in Japan recording for a Chinese audience.
Geographic arbitrage as a soft moat. He produces from a low-cost base, sells to a market with higher willingness-to-pay. I'm in Vietnam recording for an English-speaking dev audience. Same structural advantage. I've never said it on a post. He says it casually in his comments — "this is from Japan" — and the location stamp shows up next to his replies. Tiny credibility signal that compounds.
What I'm copying this week
For the next 5 dev.to posts, I'm running three changes and measuring the delta:
Reply-to-every-comment policy. Even when I get one comment per post, I respond within 24h. Every response ends with a useful follow-up question, not a CTA.
TOC at the top of any post longer than 600 words. Anchor links to numbered sections.
A single brand label across the series. "Cold-start build log" was a description, not a brand. I'm picking one short tag — probably cold-start-log — and putting it identically at the top of every post.
What I'm not copying: the gated member group. The dev market punishes that. But I'm leaning harder into the bundle being the "convenient pre-wired version" rather than the "MIT-licensed source you can also get free" framing — which means the listing's first sentence has to shift from feature-list to time-saved.
Where I think the real gap is
Watching that video, the thing that hit hardest wasn't any single tactic. It was that he treats his comment section as the product. The video is the funnel widget; the threaded replies are where conviction gets built. Every comment is a chance to demonstrate domain depth in public.
I've been treating the comment section like an afterthought because it's empty. That's the wrong direction. The way to fill it is to start running it like it's full.
Starting today I'm opening a GitHub Discussion on the repo specifically as the "ask me anything about Gmail-as-CRM, stalled-thread triage, refresh-token OAuth, KVS quota patterns" thread. Linked from every post. I'll seed it with three questions I get asked offline. We'll see who shows up.
Day 9 score: $0 revenue, 0 sales, 1 star, 11 posts. Same as Day 8. The shift starts in what I do tomorrow, not what shows up tonight.
P.S. — The AMA thread mentioned above is now live: Gmail-as-CRM AMA on GitHub Discussions. Drop any question about stalled-thread scoring, refresh-token OAuth, KVS quota, dry-run mode — answers go back into the docs.
Found this useful? My deep-dive on reverse-engineering Claude Code: Claude Code Mastery — The Reverse-Engineering Guide.
Gmail Inbox Intelligence — the open-source project this build log is about: $0 Apify Actor · $19 self-host bundle · $99 Done-For-You triage (sample report preview). Grounded in two buyer-voice anchors: r/sales 1tdngew (49-comment thread on re-engaging cold prospects) and r/smallbusiness 1td0827 (60-comment thread, top reply at 61 score: "holding 50 open loops in your head").
More from the shop:
- Claude Code Mastery: The Reverse-Engineering Guide — $49, 19 pages, every env var / hook event / settings key extracted from the v2.1.90 binary
- 5 n8n Workflows that Save 10+ Hours/Week — $29, the bundle
- AI Lead Auto-Responder — $39, Gmail → instant AI-classified reply
Read the latest checkpoint: Day 16 — +51 reader spike in 85 min, 0 sales
Day 18 — pbot v1 dev preview shipped
After 18 days of this ZERO-TEN cold start: $9 PDF killed at Day 17, pivoted to pbot — a one-click personal knowledge bot you install on your own machine. Talk to it from LINE / Telegram / Zalo on your phone.
v1 dev preview is real: 93 MB macOS .dmg packaged, 15k-chunk SQLite FTS5 queries in 0-3 ms, Anthropic real calls with source citations, daemon auto-start on boot. Day 18 deep dive: the 7-line bigram fix for Chinese search.
Top comments (0)