Week 2 Done: 35 Posts, What Actually Worked vs. What Flopped
What happened this week
Week 2 (May 31 - Jun 6): 35 Twitter posts across 7 days. Themes rotated through delivery channels (Gmail/SMS/Slack), webhook endpoints, compliance monitoring, and developer API guides.
IH posting was broken the whole week - zero IH posts landed (browser automation didn't support the platform). Twitter API hit a 402 billing wall on Day 14, cutting the last few scheduled posts short.
What resonated (top 3 by engagement)
-
"Dev note: webhook endpoint for Congress data" - 21 impressions. Why it worked: specific and technical - named the exact format (webhook URL + payload structure). Outperformed generic tweets by 3-5x consistently.
-
"Zapier integration pattern for Congress alerts" - 14 impressions. Why it worked: named a known tool, gave a concrete job-to-be-done.
-
"Compliance monitoring with goffer.ai" - 8 impressions. Why it worked: named an industry vertical, framed as a use case rather than a feature.
What flopped
-
"SMS alerts triggers?" poll - 2 impressions. No one engages with a poll from an unknown account.
-
Generic regulatory framing - 2-4 impressions each. "Government data" is not a hook. "Webhook endpoint" is.
What I'm changing for next week
-
Lead every tweet with a code snippet, a specific tool name, or a concrete workflow step. Specific beats generic by 3-5x every time.
-
Fix IH before Week 3 starts. 12 missed IH posts per week is a real gap - the audience here converts better than Twitter for early-stage tools.
The numbers
- Total posts: 35 Twitter + 0 IH (12 attempted, all failed) = 35 actual
- Total impressions (est): ~150 Twitter, 0 IH
- Total signups: 0
- Conversion ratio: 0 / 150 (baseline: 1 per 155 impressions - need more volume)
Signups from this week
Zero. At ~150 impressions we're below the threshold where conversions appear probabilistically. Volume is the constraint.
What questions do you have? Drop them below.
Good data. "Specific beats generic" is the lesson I'm taking too.
I'm Minchul, 57, former construction manager from Korea.
Built Slash it — an Email Decision OS.
Keep going. 💪
The 'specific beats generic by 3-5x' line is honestly the most useful thing i read this week. the webhook tweet outperforming proves it harder than any generic 'be specific' advice would. curious where you got the 1 per 155 impressions baseline from. that's a tight number and i'd love to know if it holds across topics or if it's congress-data-specific.
I’d be careful with the “volume is the constraint” conclusion this early.
150 impressions is small, but zero signups can also mean the posts are attracting technical curiosity without hitting the buyer moment.
“Webhook endpoint” getting more impressions is useful, but it may still be developer-interest signal, not buying-intent signal.
The sharper question is probably: who urgently needs Congress/regulatory alerts badly enough to connect a workflow today?
Compliance team, agency, policy tracker, gov affairs consultant, legal ops, or dev building on top of the data all respond to different hooks.
Happy to put the tighter Week 3 distribution angle in writing if useful. I think the next test should separate attention from signup intent before you just increase post volume.