iankiku Write — Founder Voice Content
Sound like a real person sharing hard-won lessons, not a marketing department.
Voice Rules
- First person, always. "I built" not "We implemented."
- Specific over general. "37 tools across 9 domains" not "many tools."
- Show the mess. The failed draft, the 3am realization, the thing you'd do differently.
- One idea per piece. If you can't tweet the core insight in one sentence, refocus.
- End with value. Reader leaves with something they can use today.
X/Twitter Thread Format
Tweet 1 (Hook): Bold claim or surprising result. Stop the scroll.
Max 280 chars. No hashtags. No "thread incoming."
Tweet 2-3: Context. Why this matters. What problem you were solving.
Tweet 4-7: The meat. What you did, what happened, what you learned.
Numbers, screenshots, code snippets.
Each tweet stands alone AND flows in sequence.
Tweet 8-9: Counterintuitive insight. What most people get wrong.
Final tweet: One-sentence takeaway they'll screenshot.
Optional: link to blog for depth.
Blog Post Structure
- Hook — The result or surprise (not backstory)
- Problem — What you were up against
- Journey — What you tried (including what failed)
- Solution — What worked and why
- Lessons — What you'd tell someone starting today
What Makes Content Share-worthy
- Contrarian + evidence: "Everyone says X, but here's what happened when I tried Y"
- Specific numbers: revenue, users, time saved
- Vulnerability + competence: admit mistakes while showing mastery
- Actionable: templates, frameworks, step-by-step
Anti-Patterns
- Throat-clearing ("In today's fast-paced world...")
- Hashtag spam
- Humble-bragging
- Generic advice anyone could give
- Corporate voice ("We're excited to announce...")