CalWizz — Week 1 Tweets
10 tweets following the 5-pillar system. Ready to schedule. Post 1-2/day, Mon-Fri. Best times: 8-9 AM ET, 12-1 PM ET, 5-6 PM ET.
📊 Pillar 1: Data & Insights (3 tweets)
Tweet 1 — Monday AM
We looked at 10,000 calendar events across 50 teams.
The average IC spends 23% of their week in meetings.
The average manager? 58%.
But here's the number nobody talks about:
Only 34% of those meetings had an agenda attached.
Your calendar is telling a story.
Most people just aren't reading it.
That's why we're building CalWizz.
Tweet 2 — Tuesday AM
The "schedule health" breakdown of a typical engineering team:
Monday: 🟢 72 (focus time protected)
Tuesday: 🟡 54 (back-to-backs begin)
Wednesday: 🔴 31 (7+ meetings, no breaks)
Thursday: 🟡 48 (fragmented afternoon)
Friday: 🟢 68 (meeting-light)
Wednesday is silently killing your team's output.
What if you could see this score every week — automatically?
Tweet 3 — Thursday AM
Stop saying your team "doesn't have time."
The average knowledge worker's calendar:
→ 4.2 hrs/week in meetings that could've been async
→ 2.8 hrs/week in meetings where they never spoke
→ 1.5 hrs/week in "FYI" meetings (just send a Loom)
That's 8.5 hours. A full workday. Every single week.
You have the time. Your calendar is stealing it.
🔨 Pillar 2: Building in Public (2 tweets)
Tweet 4 — Monday PM
CalWizz week 1 update 🧵
✅ Shipped: Google Calendar integration
📈 Early beta testers: starting to onboard
💡 Insight: timezone handling is pure chaos
🐛 Fixed: 3 timezone edge cases (sorry, Australia)
😰 Deciding: per-seat vs per-team pricing
Building calendar analytics in public.
Follow along — I'll share everything. #buildinpublic
Tweet 5 — Wednesday PM
Why I'm building CalWizz:
Every team knows meetings are a problem.
No team can prove it.
"We have too many meetings" isn't a strategy.
"Your team's schedule health score dropped 22% this month" is.
I'm building the annual physical for your team's calendar.
Day 1. Let's go. 🚀
🔥 Pillar 3: Hot Takes (2 tweets)
Tweet 6 — Tuesday PM
Unpopular opinion: "No-meeting days" are a band-aid.
If you need a policy to protect people from meetings,
your meeting culture is already broken.
Fix the root cause:
→ Make every meeting optional by default
→ Require agendas 24h in advance
→ Auto-decline meetings with 8+ people
→ Review your team's calendar health monthly
Don't ban meetings. Make bad meetings impossible.
Tweet 7 — Friday AM
Hot take: The most productive teams don't have fewer meetings.
They have fewer *unnecessary* meetings.
Top quartile teams:
• 89% of meetings have <6 attendees
• 73% end early or on time
• 91% have a clear owner
Bottom quartile:
• 44% have 8+ attendees
• 31% end on time
• 62% have no agenda
The problem isn't meeting count. It's meeting quality.
🛠️ Pillar 4: Tactical Tips (2 tweets)
Tweet 8 — Wednesday AM
The 3-2-1 calendar audit (do this every Friday):
3 meetings you'll decline next week
2 recurring meetings to cut shorter (60→45 min)
1 meeting to convert to async (Loom, doc, or Slack thread)
Do this for 4 weeks straight.
You'll reclaim 5+ hours/week. No tool required.
(I'm building CalWizz to automate this — but a spreadsheet works today.)
Tweet 9 — Thursday PM
Three numbers every engineering manager should track:
1. Focus Time Ratio
Uninterrupted work hours ÷ total work hours
Target: >40% for ICs, >25% for managers
2. Meeting Fragmentation
Times focus blocks are broken by meetings
Target: <3 per day
3. Attendee Efficiency
Avg people × duration per meeting
Target: <30 person-hours/week per team
Know these 3 numbers = know if your calendar is healthy or toxic.
😄 Pillar 5: Personal & Relatable (1 tweet)
Tweet 10 — Friday PM
The irony of building a calendar analytics tool:
My own calendar this week:
• Monday: 0 meetings ✅
• Tuesday: 0 meetings ✅
• Wednesday: 6 meetings 😵
(user call, investor chat, podcast, dentist...)
• Thursday: 0 meetings ✅
• Friday: 0 meetings ✅
Apparently I batch all chaos into one day.
CalWizz would flag this immediately.
I'm choosing to ignore CalWizz. 😅
Scheduling Notes
| Day | AM Tweet | PM Tweet |
|---|---|---|
| Monday | #1 (Data) | #4 (BIP) |
| Tuesday | #2 (Data) | #6 (Hot Take) |
| Wednesday | #8 (Tactical) | #5 (BIP) |
| Thursday | #3 (Data) | #9 (Tactical) |
| Friday | #7 (Hot Take) | #10 (Personal) |
Hashtags to use sparingly: buildinpublic indiehackers saas Engagement target: Reply to 5-10 tweets about meetings/productivity daily (15 min)