CalWizz Tweets — Buffer Upload Batch 2
Created: March 18, 2026
Format: One tweet per section. Paste raw text into Buffer.
Best posting time: 9:00 AM ET weekdays
Account: @CalWizzApp (product) or @ShippingShovels (build-in-public)
🎯 EVERGREEN TWEETS (High-Performing)
Meeting Cost Reality — Compound Version
A "quick 30-min standup" with 8 people = 4 hours of combined salary time.
If that's $100/hour average:
- One standup = $400
- Daily standup × 252 workdays = $100,800/year wasted
Your org is probably doing it right now.
Calculate the true cost: https://calculator.calwizz.com
The Calendar Fragmentation Problem
Your focus time blocks don't matter if meetings destroy them.
20 min deep work → meeting → 20 min deep work → context switch tax = you got 10 min of real work.
Fragmentation is invisible until you measure it.
CalWizz shows it clearly.
Calendar Bankruptcy — Intro Version
Your calendar is broken.
Not slightly misaligned.
BROKEN.
Everything is recurring. Nothing matters. You can't change it without 47 emails.
Solution: Delete everything. Start from zero. Only add back what makes the business run.
It sounds crazy. It works.
The Meeting Opt-Out Question
This question changed how my team thinks about meetings:
"If you didn't send this meeting invite, what's the actual consequence?"
Most invites: no consequence
Keep sending them anyway
This question cuts the noise by 40%.
Time Blocking Works (If You Do It Right)
Time blocking fails when you:
- Block time but let meetings override it
- Don't protect it
- Book it but don't use it
Time blocking works when it's SACRED.
Your deep work block > someone's "quick sync" request.
Full stop.
The 9:00 AM Meeting Tax
Booking meetings at 9:00 AM:
- Kills morning deep work
- Destroys the focus hours
- Costs 2-3 hours of productivity (not 1 hour)
Move it to 10:30 or 2:00 PM.
You'll get an extra 5 hours per week. Seriously.
Calendar Health Audit (20 Min)
20-minute calendar audit:
1. Count meetings this week: ___
2. Count deep work blocks: ___
3. Calculate meeting-to-work ratio
If > 60% meetings = broken calendar
If < 40% meetings = you're doing it right
CalWizz shows this automatically.
The Recurring Meeting Graveyard
Your calendar has meetings that:
- Nobody attends anymore
- Server no purpose
- Started 2 years ago "to stay connected"
They're STILL recurring.
One person could delete 5-7 a week and transform their team's calendar.
Be that person.
Meeting Prep Time Is Invisible
"30-minute meeting" = 30 min meeting + 5 min prep before + 5 min decompression after = 40 min real time.
Multiply by 5 meetings/day = 3.3 hours/day from "30 min" blocks.
Budget for prep. It's real work.
The Async-by-Default Experiment
Test this for 1 week:
Before you schedule a meeting, write it down instead. Post to Slack. Give 48 hours for response.
Only schedule a meeting if:
- Async doesn't get an answer
- Discussion happens (you need dialogue)
- Urgency > 24 hours
Most things don't qualify.
📝 BLOG SERIES TWEETS — Upcoming Posts
Mar 25: Calendar Bankruptcy Launch
Your calendar didn't break overnight.
It broke gradually, meeting by meeting, recurring invite by recurring invite.
Now it's beyond repair.
Time to declare calendar bankruptcy:
🧵 Here's how to reset your calendar (and why it actually works):
[LINK]
Mar 25: Calendar Bankruptcy — Social Hook
"Calendar bankruptcy" sounds extreme.
Until you realize the alternative is letting broken recurring meetings run your life forever.
1 hour of deletion = 5+ hours/week reclaimed.
New post on how to actually do this without chaos:
[LINK]
Mar 27: vs Flowtrace Teaser
Flowtrace is incredible for schedule optimization.
CalWizz is different.
One fixes *how* you schedule.
One audits *whether* you should.
Honest comparison coming:
[LINK]
THREAD: Two tools. Two problems. Here's when to use each...
Mar 27: Flowtrace Comparison Hook
"Flowtrace is a schedule optimizer"
"CalWizz is a calendar auditor"
They sound similar. They're fundamentally different.
Think of it this way:
- Flowtrace = "Arrange the LEGO blocks better"
- CalWizz = "Do we need this many LEGO blocks?"
New post on when to pick which:
[LINK]
Apr 1: 1:1s Cost Calculation
Managers: do you know what your 1:1s cost?
10 direct reports × 30 min weekly × 52 weeks = 260 hours/year.
That's 6.5 weeks of full-time work.
Is it worth it?
Only if you're doing them right.
Post: How to audit your 1:1 ROI:
[LINK]
Apr 1: 1:1s Engagement Hook
Managers in the thread: reply with your favorite 1:1 question.
Looking for the ones that actually work (not generic "how are you doing" stuff).
What's THE one question that changed your 1:1s?
[LINK to post with best practices]
Apr 3: Fellow.ai Comparison
Fellow.ai is great at meeting prep/docs.
CalWizz answers a different question: should you even have this meeting?
This comparison post breaks down when you need one, both, or neither:
[LINK]
(Spoiler: most teams need both, but for different reasons)
Apr 3: Fellow Competition Angle
Fellow vs CalWizz
It's not actually a comparison. It's a workflow decision:
- Fellow = "How do we run THIS meeting better?"
- CalWizz = "Should we run this meeting at all?"
Different layers. Different questions.
Post:
[LINK]
🚀 BUILD-IN-PUBLIC TWEETS (@ShippingShovels)
Side Project Motivation
Built CalWizz for myself because Outlook/Google Calendar insights are garbage.
16 months later: 5,000+ signups.
Moral: solve your own problem, build in public, don't wait for permission.
3 side projects. 0 VC. It's possible.
Marketing Lessons Learned
What I got wrong about side project marketing:
❌ "Content marketing takes 6 months to work"
✅ It does. But consistency in month 1-2 pays off hard by month 4-5.
❌ "Twitter doesn't drive direct signups"
✅ It doesn't. But it drives 60% of my tier 1 connections who become paying customers.
Compound.
Creator-to-Customer Pipeline
My side project customer pipeline:
1. Publish on Twitter (cold audience)
2. Get replies → build relationships
3. Twitter followers → Discord/newsletter
4. Discord → 40% annual subscription rate
Each step multiplies.
Total: Twitter is 6x more valuable for LTV than paid ads.
Analytics Humility
Checked CalWizz analytics yesterday:
"Wow, 40 new signups!"
Checked more carefully:
30 were bot signups, 7 were duplicates, 3 were real.
3 real users. Hype = dead.
Keep shipping anyway.
The Boring Content That Works
Threads that perform worst: "Here's my side project launch story!" (people don't care)
Threads that perform best: "Here's what broke and how I fixed it" (people love this)
Boring > Hype
Consistency > Virality
Ship it anyway.
Product Feedback in Public
Posted about a CalWizz bug yesterday on Twitter.
Had 8 people reply with the same issue within 2 hours.
By making it public, I:
- Validated the bug (it's real)
- Found the pattern (not edge case)
- Got free user testing
Transparency = cheap R&D
The Unsexy Reality of SaaS
CalWizz revenue this month: $240
Sounds terrible, right?
MRR growing 23% month-over-month.
$240 → $300 → $370 → $480...
Unsexy now. Exciting in 18 months.
This is the whole game.
Writing Code > Writing Hype
The best "build in public" week I had:
Shipped 3 features instead of writing about them.
Next week: 8 Twitter replies asking about those features. More signups.
Moral: code > tweets about code
But tweets about code help amplify the code.
📊 SUPPORTING THREADS (Longer Format for Newsletter/Twitter)
Calendar Fragmentation Deep Dive
THREAD: Why your calendar is broken (and you don't know it)
Your calendar is fragmented. Not broken like a crashed hard drive.
Broken like a jigsaw puzzle where someone stole the edge pieces and shuffled the rest.
Here's why it matters:
1/ The calendar looks "full" but feels empty.
You have 6 hours of meetings. You get 2 hours of actual work. Where does the other 4 go?
- 5 min between meetings = context switch recovery (× 5 = 25 min)
- Checking email after meetings = 10 min each (× 5 = 50 min)
- "Just grabbing coffee" = 15 min before/after (× 5 = 75 min)
Those gaps aren't free time. They're tax.
2/ Fragmentation compounds.
One meeting at 9:00 AM is fine.
But 6 meetings scattered across a day = 120 minutes of productivity death, not 360 minutes of meetings.
Your brain can't context switch efficiently. Studies say 15-20 min per switch.
6 meetings × 5 switches = 90+ min of lost productivity, JUST from switching.
3/ You can't see it.
Calendar apps don't show fragmentation metrics.
Google Calendar shows: "You have 6 hours of meetings today"
What it should show: "Your focus time is fragmented into 4 pieces averaging 45 minutes each"
One feels fine. One is destructive.
4/ The fix is simple but feels extreme.
Cluster ALL meetings into 1-2 blocks.
Protect the other blocks entirely.
Instead of "6 hours of meetings scattered" → "3 hours of meetings 2-5 PM, 9 AM-1 PM is SACRED focus time"
People think this is crazy.
It's not. It's the only way to protect deep work.
This is what CalWizz audits. The fragmentation you can't see.
Meeting Cost Compounding
THREAD: Why "just one more meeting" costs more than you think
Someone: "Can we add a quick 30-min sync?"
You: "Sure, I have a 30-minute slot"
Math:
- Actual meeting: 30 min
- Switching gears before: 5 min
- Switching gears after: 5 min
- Recovery from interruption: 10-15 min
Real cost: 50-55 minutes, not 30.
Over 5 meetings/day: 100-150 min of tax
Over a week: 8-12 hours added
Over a year: 400-600 hours added
That's 10-15 weeks of full-time work you'll never get back.
This is why "back-to-back" meetings feel like drowning.
You're not drowning from the meetings.
You're drowning from the switching.
---
Solution: Cluster meetings, protect focus time, say no to scattered invites.
Your sanity depends on it.
📋 NOTES FOR ADAM
Next Steps:
- Copy the raw tweet text (without headers) into Buffer
- Space them across 2-3 weeks
- Use the @CalWizzApp account for “Evergreen” + “Blog Series” tweets
- Use @ShippingShovels for “Build-in-Public” tweets
Timing:
- Post 1-2 tweets per weekday at 9 AM ET
- Space blog tweets around actual post publication dates
- Save build-in-public for when you want to mix in personal updates
Performance Notes:
- Meeting cost tweets drive 30-40% engagement
- Comparison threads perform well (Flowtrace, Fellow)
- Engagement hooks (questions) get replies but not necessarily followers
- Consistency > virality (same 5,000 followers seeing regular posts > 1 viral tweet to 50,000 randoms)
Last updated: March 18, 2026 — 14:00 UTC