232 lines
6.8 KiB
Markdown
232 lines
6.8 KiB
Markdown
# X/Twitter Promotion Plan for inou
|
|
|
|
*Draft prepared: January 26, 2026*
|
|
*Status: For Johan's review*
|
|
|
|
---
|
|
|
|
## Executive Summary
|
|
|
|
inou has a powerful origin story and a genuine problem it solves. The challenge is building presence on X without feeling like marketing spam. This plan focuses on authenticity, value-first content, and strategic engagement.
|
|
|
|
---
|
|
|
|
## 1. Profile Setup
|
|
|
|
### Handle
|
|
- Ideal: `@inou` (likely taken) → check `@inouhealth`, `@getinou`, `@inou_health`
|
|
- Personal account (`@johanjongsma` or similar) for founder presence
|
|
|
|
### Bio Elements
|
|
- What it does (one line)
|
|
- Who it's for
|
|
- Link to inou.com
|
|
- Maybe: "Built because I needed it for my daughter"
|
|
|
|
### Pinned Tweet
|
|
Origin story thread (see Section 4)
|
|
|
|
---
|
|
|
|
## 2. Content Pillars
|
|
|
|
### Pillar 1: The Problem (40%)
|
|
Posts about fragmented health data, missed diagnoses, overwhelmed patients.
|
|
|
|
Examples:
|
|
- "Your MRI has 4,000 slices. It was read in 10 minutes."
|
|
- "Your doctor has 15 minutes. Your AI has your entire history."
|
|
- "Three specialists. Three portals. Zero communication."
|
|
|
|
### Pillar 2: AI + Health Education (30%)
|
|
Teach people what's possible without being salesy.
|
|
|
|
Examples:
|
|
- "Did you know your 23andMe raw data contains pharmacogenomics info?"
|
|
- "What FLAIR sequences actually show on brain MRI"
|
|
- "How to export your MyChart data (and why you should)"
|
|
|
|
### Pillar 3: Building in Public (20%)
|
|
Share the journey — technical decisions, user feedback, challenges.
|
|
|
|
Examples:
|
|
- "Today we added DICOM support for [X]. Here's why it was harder than expected."
|
|
- "User asked for [feature]. Shipped it same day."
|
|
- "Running on dedicated hardware, not Big Tech clouds. Here's why."
|
|
|
|
### Pillar 4: Personal/Founder Story (10%)
|
|
Sparingly share the Sophia story. Powerful but must be handled with care.
|
|
|
|
---
|
|
|
|
## 3. The Sophia Story — Handling It Right
|
|
|
|
### Why It Matters
|
|
- It's the authentic origin — not manufactured marketing
|
|
- It demonstrates real stakes and real expertise
|
|
- It differentiates from generic health apps
|
|
|
|
### The Risk
|
|
- Can feel exploitative if overused
|
|
- Privacy considerations for Sophia
|
|
- Emotional manipulation concern
|
|
|
|
### The Approach
|
|
1. **Tell it once, well** — A single origin story thread, pinned
|
|
2. **Reference, don't repeat** — "I built this because I needed it" without retelling details
|
|
3. **Focus forward** — The story is *why*, the product is *what*
|
|
4. **Let others share** — When users share their own stories, that's more powerful
|
|
|
|
### The Origin Thread (Draft)
|
|
|
|
```
|
|
Three years ago, my daughter was in an accident.
|
|
|
|
The doctors diagnosed anoxic brain injury from cardiac arrest.
|
|
|
|
But the labs didn't match. The imaging didn't match. The EEG said "metabolic encephalopathy" — not anoxic.
|
|
|
|
I'm not a doctor. I'm a backup systems engineer. But I know how to read data.
|
|
|
|
So I learned to read MRIs. I pulled every record. I built tools to analyze them.
|
|
|
|
What I found: the diagnosis was wrong. The radiologist saw what he expected to see.
|
|
|
|
Three years of wrong treatment. Because no one connected the data.
|
|
|
|
That's why I built inou.
|
|
|
|
Your health data is scattered across a dozen systems. No single doctor sees all of it. No single specialist has time to connect it.
|
|
|
|
But you have access to everything. You just need help making sense of it.
|
|
|
|
inou brings it all together — labs, imaging, genetics, vitals — encrypted, private, yours.
|
|
|
|
Then lets your AI connect the dots no human could.
|
|
|
|
Your health, understood.
|
|
|
|
[link to inou.com]
|
|
```
|
|
|
|
---
|
|
|
|
## 4. Engagement Strategy
|
|
|
|
### Who to Follow
|
|
- Health-tech founders and builders
|
|
- AI/ML practitioners interested in health
|
|
- Patient advocates
|
|
- Medical professionals who use tech
|
|
- Privacy-focused technologists
|
|
- Quantified-self community
|
|
|
|
### How to Engage
|
|
- **Reply thoughtfully** — Add value, not "Great post!"
|
|
- **Quote tweet with insight** — "This is why we built [specific feature]..."
|
|
- **Share relevant threads** — Other people's content that aligns with mission
|
|
- **Answer questions** — Be helpful in health-tech discussions
|
|
|
|
### What NOT to Do
|
|
- Don't spam replies with product links
|
|
- Don't argue with critics
|
|
- Don't post more than 2-3x per day initially
|
|
- Don't automate engagement (feels fake)
|
|
|
|
---
|
|
|
|
## 5. Grok Integration
|
|
|
|
Use Grok for X-native intelligence:
|
|
- Analyze trending health/AI topics
|
|
- Understand what content performs in your niche
|
|
- Draft posts with X-native voice
|
|
- Research who's talking about relevant topics
|
|
|
|
Example workflow:
|
|
1. "What health-tech topics are trending on X this week?"
|
|
2. Draft content that connects inou to those conversations
|
|
3. Identify accounts to engage with
|
|
|
|
---
|
|
|
|
## 6. Timeline
|
|
|
|
### Week 1-2: Setup
|
|
- Finalize handle and profile
|
|
- Write and refine origin thread
|
|
- Follow 50-100 relevant accounts
|
|
- Engage (don't post product content yet)
|
|
|
|
### Week 3-4: Soft Launch
|
|
- Post origin thread
|
|
- Begin regular content (1 post/day)
|
|
- Continue engagement
|
|
- Note what resonates
|
|
|
|
### Month 2: Build Rhythm
|
|
- Increase to 2 posts/day
|
|
- Start "building in public" content
|
|
- Engage with early followers
|
|
- Iterate based on what works
|
|
|
|
### Month 3+: Scale
|
|
- Consider threads on specific topics
|
|
- Guest appearances on podcasts/spaces
|
|
- Collaborate with aligned accounts
|
|
- User testimonials (when available)
|
|
|
|
---
|
|
|
|
## 7. Metrics to Track
|
|
|
|
- Follower growth (but don't obsess)
|
|
- Engagement rate on different content types
|
|
- Click-throughs to inou.com
|
|
- DMs and conversations started
|
|
- Sign-ups attributed to X
|
|
|
|
---
|
|
|
|
## 8. What I Can Help With
|
|
|
|
- **Draft posts** — Give me a topic, I'll write options
|
|
- **Review threads** — Check tone, clarity, impact
|
|
- **Research** — Use Grok to analyze X trends
|
|
- **Engagement suggestions** — Who to reply to, what to say
|
|
- **Schedule planning** — Remind you to post, suggest timing
|
|
|
|
---
|
|
|
|
## Questions for You
|
|
|
|
1. Do you want a separate @inou account, or post from personal?
|
|
2. Comfort level with Sophia story — as drafted, less, or more?
|
|
3. What aspects of inou do you most want to highlight?
|
|
4. Any accounts/people you already follow that I should know about?
|
|
5. Target launch date for X presence?
|
|
|
|
---
|
|
|
|
*Ready to discuss when you wake up.*
|
|
|
|
---
|
|
|
|
## Pitch Angles — Strong Examples Found
|
|
|
|
### Hans Amato thread (Mar 12, 2026) — 13k likes, 2k RTs
|
|
https://x.com/HansAmato/status/2032139819313480071
|
|
|
|
The story: $12k therapy for anger → real cause was gut leakage → inflammation → cortisol → low magnesium → no GABA. Fixed with data, not talk.
|
|
"3 practitioners. 2 years. $12,000+. Zero blood draws."
|
|
|
|
**Why it works for inou:**
|
|
- Visceral, relatable (not a rare tragedy — everyday dysfunction)
|
|
- Demonstrates the fragmentation problem at scale
|
|
- Proves the market gets it — 13k people immediately understood
|
|
- Lower emotional barrier than origin stories involving serious injury
|
|
- The fix was data connection, not a new treatment — exactly inou's angle
|
|
|
|
**Potential inou framing:**
|
|
"This is why we built inou. Your labs, your inflammation markers, your genome — in one place. The connection no single practitioner has time to make."
|