# Twitter/X Campaign - Week 1 Content

**Issue:** FRE-687 / FRE-691  
**Created:** 2026-04-26 17:00 PM  
**Owner:** CMO  
**Status:** ✅ Ready to Post

---

## Content Strategy

**Goal:** 1,500 waitlist signups from Twitter/X (15% of 10K goal)  
**Frequency:** Daily threads + engagement  
**Timeline:** April 27 - May 7 (11 days)  
**Tone:** Educational, builder-focused, slightly provocative

**Key Themes:**
1. Screenwriting pain points (WriterDuet/Final Draft criticism)
2. Building in public (founder journey)
3. Technical deep-dives (Tauri, SolidJS, CRDT)
4. Feature showcases (real-time collaboration, AI)
5. Social proof (beta tester testimonials)

---

## Week 1 Content Calendar

### Day 1 - April 27 (Monday)

**Thread:** "10 things WriterDuet gets wrong"

**Tweet 1/11:**
```
10 things WriterDuet gets wrong about screenwriting software 🧵

After 3 years of using every screenwriting tool, I'm building an alternative.

Here's what's broken (and how we're fixing it):
```

**Tweet 2/11:**
```
1. Real-time collaboration is an afterthought

WriterDuet: "Here's Google Docs from 2015"
Scripter: Native CRDT sync, zero conflicts, true simultaneous editing

If 3 people edit the same line, you shouldn't need a merge tool.
```

**Tweet 3/11:**
```
2. Desktop apps feel like web wrappers

WriterDuet: Electron app that eats RAM
Final Draft: Looks like Windows 95
Scripter: Tauri + Rust, 50MB RAM, native performance

Your screenwriting tool shouldn't need 2GB of memory.
```

**Tweet 4/11:**
```
3. AI features are either missing or creepy

WriterDuet: No AI
Some tools: "Our AI will write your script for you!" 🤖

Scripter: AI that assists, not replaces
- Outline suggestions
- Dialogue alternatives
- You control everything
```

**Tweet 5/11:**
```
4. Export options are limited

WriterDuet: PDF, maybe Fountain
Final Draft: FDX (proprietary)

Scripter: PDF, FDX, Fountain, RTF
Your script belongs to YOU, not the platform.
```

**Tweet 6/11:**
```
5. Mobile support is non-existent

WriterDuet: "We have an app" (it's bad)
Final Draft: No mobile app

Scripter: Progressive Web App
Works on iPhone, Android, iPad, any browser

Write on your phone without installing anything.
```

**Tweet 7/11:**
```
6. Pricing is insane

WriterDuet: $15/month or $60/year
Final Draft: $200 one-time (then $100 for upgrades)

Scripter: Free tier (unlimited scripts)
Pro: $9.99/month

Professional tools shouldn't cost $200.
```

**Tweet 8/11:**
```
7. No version history

WriterDuet: Limited history
Final Draft: Manual save-as copies

Scripter: Automatic version history
Go back to any point in time
"Undo" from 3 weeks ago

Your words matter. Never lose them.
```

**Tweet 9/11:**
```
8. Analytics are basic

WriterDuet: Page count, that's it
Final Draft: ???

Scripter: 
- Character count per scene
- Dialogue vs action ratio
- Scene length distribution
- Readability scores

Data-driven writing = better scripts.
```

**Tweet 10/11:**
```
9. Collaboration tools are weak

WriterDuet: Comments and chat
Final Draft: Revision mode (from 1990)

Scripter:
- Real-time cursors
- In-line comments
- Suggested changes
- Video chat integration

Writing is a team sport.
```

**Tweet 11/11:**
```
10. No student discounts

WriterDuet: Full price for everyone
Final Draft: "Student discount" (still $100)

Scripter: 50% off for students
Free for first 10,000 beta users

We're building for the next generation of writers.

---

Try Scripter free: scripter.app

Follow me for more on building in public and screenwriting tech.
```

---

### Day 2 - April 28 (Tuesday)

**Thread:** "How I wrote 50 pages in 1 week using my own tool"

**Tweet 1/8:**
```
How I wrote 50 pages in 1 week using my own screenwriting tool 🧵

I built Scripter to solve my own problem: I couldn't write fast enough.

Here's the system I used (and the tool that made it possible):
```

**Tweet 2/8:**
```
Day 1: Outline with AI assistance

- Brainstorm logline
- AI suggests 3-act structure
- I tweak beats manually
- Export to scene list

Time: 2 hours
Result: Complete outline, ready to write
```

**Tweet 3/8:**
```
Day 2-3: Vomit draft

- No editing, just writing
- Scripter auto-formats as I type
- Analytics show I'm at 25 pages
- Turn off "inner critic" mode

Time: 6 hours total
Result: 25 pages of terrible first draft
```

**Tweet 4/8:**
```
Day 4: Collaboration pass

- Share with writing partner
- Real-time editing (both of us in the doc)
- Comments on weak scenes
- Video chat while we work

Time: 3 hours
Result: 25 pages, now coherent
```

**Tweet 5/8:**
```
Day 5-6: Rewrite

- Fix plot holes flagged by partner
- AI suggests dialogue improvements
- I accept ~30%, reject the rest
- Version history saves everything

Time: 8 hours
Result: 40 pages, actually good
```

**Tweet 6/8:**
```
Day 7: Polish

- Read aloud mode (hears clunky dialogue)
- Analytics: "Scene 12 is 5 pages, too long"
- Cut 2 pages from Scene 12
- Export to PDF, send to producer

Time: 3 hours
Result: 50 pages, submission-ready
```

**Tweet 7/8:**
```
The key insight:

Most screenwriting tools are designed for typing, not writing.

They format your text. They don't help you:
- Generate ideas
- Structure your story
- Collaborate effectively
- Know when you're done

Scripter is designed for the entire writing process.
```

**Tweet 8/8:**
```
Results after 1 week:
- 50 pages written
- 1 producer reading
- 0 all-nighters
- Actually proud of it

The tool matters. The process matters more.

Try Scripter free: scripter.app

What's your writing process? Drop it below 👇
```

---

### Day 3 - April 29 (Wednesday)

**Product Demo:** Real-time collaboration feature

**Tweet 1/5:**
```
Watch 2 writers edit the same screenplay in real-time 🎥

This is Scripter. No conflicts. No merge hell. Just writing.

[Screen recording: 2 cursors, different colors, both typing simultaneously]
```

**Tweet 2/5:**
```
The magic: CRDT (Conflict-free Replicated Data Types)

Same tech as Figma, Notion, Google Docs.

Every edit is tracked. Every conflict is resolved automatically.

You never see a loading spinner. You never lose work.
```

**Tweet 3/5:**
```
Built with:
- Tauri (Rust backend)
- SolidJS (reactive frontend)
- Yjs (CRDT library)
- Turso (edge database)

Result: 50MB RAM usage, instant sync, works offline.

Tech stack matters.
```

**Tweet 4/5:**
```
Why this matters:

Most screenwriting collaboration is:
1. Email FDX files back and forth
2. "Final_FINAL_v3_REALLY_FINAL.fdx"
3. Merge conflicts manually
4. Lose someone's changes

Scripter: Everyone edits together. Always in sync.
```

**Tweet 5/5:**
```
Real-time collaboration is not a feature.

It's the future of screenwriting.

Try it free: scripter.app

[Link to waitlist]
```

---

### Day 4 - April 30 (Thursday)

**Thread:** "Building in public: Month 8 update"

**Tweet 1/7:**
```
Building a WriterDuet alternative: Month 8 update 🧵

- 0 → ??? waitlist signups
- First beta testers onboarded
- Product Hunt launch: May 7
- Revenue: $0 (coming soon)

Here's what happened this month:
```

**Tweet 2/7:**
```
Product Progress:

✅ Real-time collaboration (CRDT sync working)
✅ AI writing assistant (outline + dialogue)
✅ Export to PDF/FDX/Fountain
✅ Cross-platform (Web, Mac, Windows)
✅ Analytics dashboard

⏳ Mobile apps (iOS/Android beta)
⏳ Offline mode
```

**Tweet 3/7:**
```
Lessons Learned:

1. CRDT is hard. Like, PhD-level hard.
2. Screenwriters are passionate (and opinionated)
3. Final Draft has 40 years of technical debt (we have 8 months)
4. Free tier is the right call
5. Building in public = free marketing
```

**Tweet 4/7:**
```
Biggest Mistake:

Spent 3 weeks perfecting the export engine.

Writers don't care about perfect export. They care about:
- Does it format correctly?
- Can I send to my agent?
- Does it look professional?

Good enough > Perfect. Ship faster.
```

**Tweet 5/7:**
```
Next Month Goals:

1. 10K waitlist signups
2. Product Hunt launch (May 7)
3. 500 beta users
4. First paying customers
5. Linux support (you asked, we're building)

Ambitious? Yes.
Possible? We'll see.
```

**Tweet 6/7:**
```
Tech Stack (for the devs):

Frontend: SolidJS + Vite
Backend: tRPC + SQLite/Turso
Desktop: Tauri (Rust)
Real-time: Yjs (CRDT)
AI: OpenAI API
Hosting: Vercel + Fly.io

Total cost: ~$200/month
```

**Tweet 7/7:**
```
If you're building in public:

1. Ship faster than you're comfortable with
2. Talk to users daily
3. Steal from the best (Figma, Notion, Linear)
4. Document everything
5. Be honest about failures

Follow along: [Twitter handle]
Try early: scripter.app
```

---

### Day 5 - May 1 (Friday)

**Thread:** "Screenwriting formatting hacks you didn't know"

**Tweet 1/9:**
```
Screenwriting formatting hacks that will save you hours 🧵

Most writers fight their software. Here's how to make it work for you:
```

**Tweet 2/9:**
```
1. The "O.S." vs "V.O." shortcut

O.S. (Off-Screen): Character is present but not visible
V.O. (Voice-Over): Character is narrating or on phone

Don't mix them up. Readers notice.

[Scripter: Auto-suggests based on context]
```

**Tweet 3/9:**
```
2. Dual dialogue is rare. Don't abuse it.

Only use when:
- Characters interrupt each other
- Overlapping speech is critical
- Both lines are short

[Scripter: One-click dual dialogue]
```

**Tweet 4/9:**
```
3. Parentheticals should be 1-3 words max

BAD:
          JOHN
     (angrily, while walking to the door)
     I'm leaving.

GOOD:
          JOHN
     (angry)
     I'm leaving.

Action lines show emotion. Parentheticals show delivery.
```

**Tweet 5/9:**
```
4. Scene transitions are dying

CUT TO: (redundant - every cut is implied)
DISSOLVE TO: (use sparingly, for time jumps)
SMASH CUT: (for shock/comedy)

Modern scripts: 95% no transitions. Let the editor decide.
```

**Tweet 6/9:**
```
5. Character intro format

First time we see JOHN (30s), write:

          JOHN (30s)

Not:
          John Smith, a rugged detective in his early 30s 
          who's seen too much

Save the backstory for action lines.
```

**Tweet 7/9:**
```
6. Page count ≠ screen time

1 page = 1 minute is a guideline, not a rule.

- Action-heavy scenes: 1 page = 30 seconds
- Dialogue scenes: 1 page = 90 seconds

Track actual screen time, not page count.

[Scripter: Shows estimated runtime]
```

**Tweet 8/9:**
```
7. The "Monday Morning Read" test

Print your script. Read it on Monday morning.

If you're bored by page 10, rewrite page 1-9.

Your script is only as good as its weakest scene.
```

**Tweet 9/9:**
```
Formatting shouldn't be hard.

The software should handle it. You should focus on story.

Scripter auto-formats everything:
- Scene headings
- Character names
- Dialogue
- Parentheticals
- Transitions

Write. Don't format.

Try free: scripter.app
```

---

### Day 6 - May 2 (Saturday)

**Beta Testimonial:** User story

**Tweet 1/4:**
```
"We wrote our pilot in 3 weeks using Scripter"

Sarah & Mike are writing partners. They live in different cities.

Here's how they did it:
```

**Tweet 2/4:**
```
The Problem:

Sarah: "We were emailing FDX files back and forth"
Mike: "Lost 2 weeks of work when my laptop died"
Sarah: "Collaboration was a nightmare"
```

**Tweet 3/4:**
```
The Solution:

- Real-time collaboration (both edit together)
- Cloud sync (never lose work)
- Version history (undo anything)
- Video chat built-in

Mike: "It's like we're in the same room"
```

**Tweet 4/4:**
```
The Result:

- 3 weeks: 90-page pilot
- Sent to 5 producers
- 2 requested meetings
- 1 option deal in talks

"We couldn't have done it without Scripter"

Try it free: scripter.app
```

---

### Day 7 - May 3 (Sunday)

**Reddit Cross-Post:** Link to r/Screenwriting post

**Tweet:**
```
Just posted on r/Screenwriting: "Building a WriterDuet alternative - AMA"

Answering questions about:
- Screenwriting software
- Building in public
- CRDT and real-time sync
- Taking on Final Draft

Check it out: [Reddit link]

Ask me anything! 👇
```

---

## Engagement Strategy

### Daily Actions (30 min/day)

1. **Morning (15 min):**
   - Post thread/demo
   - Reply to first 10 comments
   - Retweet beta tester mentions

2. **Afternoon (10 min):**
   - Reply to remaining comments
   - Engage with screenwriting Twitter
   - Quote-retweet relevant content

3. **Evening (5 min):**
   - Check analytics
   - Respond to DMs
   - Schedule tomorrow's content

### Target Accounts to Engage

**Influencers:**
- @JohnFinn (YouTube)
- @NoFilmSchool
- @ScriptLab
- @ScreenCraft
- @GoIntoTheStory

**Beta Advocates:**
- [List from /marketing/beta-advocate-contact-list.md]

**Competitors:**
- @WriterDuet (monitor for feature gaps)
- @FinalDraft (monitor for complaints)

---

## Hashtag Strategy

**Primary:**
- #Screenwriting
- #Writing
- #IndieFilm
- #FilmTwitter

**Secondary:**
- #ProductHunt
- #BuildInPublic
- #IndieDev
- #SaaS

**Launch Day:**
- #ProductHunt
- #Screenwriting
- #NewProduct

---

## Success Metrics

| Metric | Target | Current |
|--------|--------|---------|
| Thread impressions | 10K+ per thread | TBD |
| Engagement rate | 3%+ | TBD |
| Click-through rate | 1%+ | TBD |
| Waitlist signups | 1,500 | TBD |
| Followers gained | 500+ | TBD |

---

## Notes

**Best Times to Post:**
- Weekdays: 9 AM - 12 PM PT
- Weekends: 10 AM - 2 PM PT
- Avoid: Monday 8 AM, Friday 5 PM

**Thread Best Practices:**
- Hook in first tweet (controversial stat, bold claim)
- 8-12 tweets per thread (sweet spot)
- Include visuals when possible
- End with CTA (link + follow ask)

**Visual Content:**
- Screenshots of Scripter UI
- Screen recordings (GIFs)
- Before/after comparisons
- Quote graphics from beta testers

---

**Status:** ✅ Ready to post  
**Next:** Start posting April 27, monitor engagement daily  
**Blocker:** None - can post without scripter.app being live (use mockups)