Sync Tax — Micro Tool Specs (Final)
Campaign: The Sync Tax Tools: 2 (Meeting ROI Scorecard + Implementation Diagnostic) Primary CTA: $27 Sync Tax Toolkit Secondary CTA: Systems Diagnostic (booking)
How the Tools Relate to the Article
The article opens one front: your meetings are full of information transfer disguised as collaboration.
The tools open a second front and prescribe.
| Article | Tool 1: ROI Scorecard | Tool 2: Implementation Diagnostic | |
|---|---|---|---|
| Question | What's this meeting made of? | Is this meeting producing anything? | What's keeping it this way? |
| Confrontation | Transfer vs. collaborative split | Decision output vs. zero | The specific blocker |
| What's new | Nothing — this IS the article | A meeting can be 100% collaborative and still produce nothing | Names why knowing hasn't fixed it |
| Bridges to | Tools | Toolkit or diagnostic | The right section of the toolkit |
The Scorecard is the one the article can't deliver. A reader can finish the article thinking "my Monday meeting is mostly broadcasts, but it's still useful." The Scorecard asks: when was the last time it produced a decision? That kills the defense.
Tool 1: The Meeting ROI Scorecard
Type: Revelation Tagline: Your meetings might be collaborative. Are they productive? Time to complete: Under 3 minutes
What It Does
The reader enters their 3 most important recurring meetings. For each one, two questions about output — not content. The tool grades each meeting and shows them the distribution.
The Revelation
Most readers will see 1 meeting that produces decisions and 2 that don't. The surprise: meetings they thought were valuable because they feel collaborative score C or D because they haven't produced a decision in months.
This is the question the article never asks.
Screen 1: Intro
Headline: The Meeting ROI Scorecard Subhead: Your meetings might be collaborative. That doesn't mean they're productive. Grade your top 3 recurring meetings in under 3 minutes.
One input before they start:
- Your team's average blended hourly rate (dropdown: $50 / $75 / $85 / $100 / $125 / $150 / $200 / Custom)
Button: Score Your Meetings
Screen 2: Meeting Entry + Scoring
Repeat for each meeting (one at a time, 3 total):
Meeting [1 of 3]
Meeting type: [dropdown: All-Hands / Team Meeting, 1:1 Check-In, Pipeline Review, Client Status Call, Internal Standup, Strategy Session, Process Training, BD Debrief, Project Check-In, Leadership Meeting, Custom] Custom name: [text field, only visible when Custom is selected] Frequency: [dropdown: Weekly / Biweekly / Monthly] Duration: [dropdown: 15 / 30 / 45 / 60 / 90 minutes] People in the meeting: [dropdown: 2-20]
Q1: When was the last time this meeting produced a decision?
- (a) This week or last week
- (b) Sometime in the past month
- (c) I'd have to think about it — maybe a few months ago
- (d) I honestly can't remember
Q2: If this meeting didn't happen for a month, what would break?
- (a) Specific things would fall through — decisions would stall, people would be blocked
- (b) Some things would slow down, but we'd find workarounds
- (c) People would feel disconnected, but nothing operational would break
- (d) Honestly, not much
Button: Next Meeting (or See My Scores on last meeting)
Scoring
Each question maps to a point value:
| Answer | Points |
|---|---|
| (a) | 3 |
| (b) | 2 |
| (c) | 1 |
| (d) | 0 |
Total per meeting: 0-6 points
| Score | Grade | Label |
|---|---|---|
| 5-6 | A | Producing decisions. Protect it. |
| 3-4 | B | Occasionally useful. Candidate for restructuring. |
| 1-2 | C | Running on momentum. |
| 0 | D | Running on habit. Nobody would miss it. |
Screen 3: Results
Hero display:
Meeting type (or custom name), grade (color-coded), label — one row per meeting. Sorted worst to best.
| Meeting | Grade | Verdict |
|---|---|---|
| Pipeline Review | D | Running on habit |
| Client Status Call | C | Running on momentum |
| Strategy Session | A | Producing decisions |
Color coding:
- A: Green (#5a9a6a)
- B: Gold (#b79d64)
- C: Amber (#c49a4a)
- D: Red (#c45a4a)
Summary box:
"[X] of your 3 meetings scored C or D — running on momentum or habit, not producing decisions."
"Those meetings consume [total hours] hours per week across [total person-hours] person-hours."
"At $[rate]/hour, that's $[weekly cost] per week — $[annual cost] per year — in meetings that aren't producing outcomes."
The twist line:
"These meetings might not be full of broadcasts. They might feel collaborative. But if they haven't produced a decision in months, the time is still lost."
Result tiers:
Tier 1 (2-3 meetings scored C/D): "Most of your meeting calendar is running on momentum. The meetings feel productive — people talk, ideas come up, everyone leaves feeling busy. But decisions aren't happening. That's the more expensive version of the Sync Tax: not broadcasts eating the calendar, but meetings that exist without producing anything."
Tier 2 (1 C/D, 1-2 A/B): "You have meetings that work and meetings that don't. The A meetings are earning their time. The C/D meetings are consuming time without returning decisions. The question is whether you know which is which without this scorecard in front of you."
Tier 3 (0 C/D — all A/B): "Your meetings are producing. That's rare. If you're still feeling calendar pressure, the issue may not be meeting quality — it may be meeting volume. Each one might be valuable individually, but together they crowd out the deep work that doesn't have a calendar slot."
CTA section:
"The Scorecard shows you which meetings are broken. The Sync Tax Toolkit shows you what to do with each one — restructure, replace, or retire."
Get the Toolkit — $27
Smaller, below: "Want someone to audit the whole calendar with you? Book a Systems Diagnostic"
Even smaller: "See what's keeping these meetings in place → Take the Implementation Diagnostic" [link to Tool 2]
Tool 2: The Implementation Diagnostic
Type: Diagnostic (category-sorting) Tagline: You've seen the problem. This is what's keeping it in place. Time to complete: Under 2 minutes
What It Does
Five questions about the firm's communication habits, infrastructure, and leadership patterns. Sorts them into one of three root cause categories. Each category maps to a specific intervention level — and a specific section of the toolkit.
The Insight
The article's Constraint section says "knowing doesn't fix it." This tool names the specific reason it doesn't fix it for THEM. That's different from naming the pattern. That's prescribing.
Screen 1: Intro
Headline: The Implementation Diagnostic Subhead: You know your meetings aren't working. This tells you what's keeping them that way — and what kind of fix actually sticks.
Button: Start the Diagnostic
Questions (Q1-Q5, single-select each)
Q1: When you've tried to shorten or change a recurring meeting, what happened?
- (a) Never tried — it hasn't come up [AC]
- (b) Tried once, it crept back within a month [AC]
- (c) Tried, got pushback from leadership or the team [FD]
- (d) Made a change that stuck [CD]
Q2: If a team member missed your biggest recurring meeting, how would they find out what was covered?
- (a) They'd ask someone [AC]
- (b) They'd ask the founder specifically — they're the one who knows [FD]
- (c) They'd check email or Slack, but it's hit or miss [CD]
- (d) There's no record — you had to be there [AC]
Q3: Who decides what gets a meeting vs. a message?
- (a) The founder — meetings follow their habits [FD]
- (b) Nobody — it's informal [AC]
- (c) There's a loose norm but no rule [CD]
- (d) There's a clear default for different types of communication [CD]
Q4: If the founder recorded a 5-minute voice memo with this week's updates instead of scheduling a meeting, what would the team do?
- (a) They wouldn't know where to find it [AC]
- (b) Some would listen, most wouldn't [CD]
- (c) The founder wouldn't do it — meetings feel more like leadership [FD]
- (d) They'd listen and prefer it [CD]
Q5: What's the real reason the biggest meeting on your calendar still runs every week?
- (a) There's nowhere else for the information to go [AC]
- (b) Nobody's questioned it — it just runs [CD]
- (c) Leadership wants face time with the team [FD]
- (d) We've tried async but people don't check it consistently [CD]
Scoring
Count which category has the most selections across Q1-Q5.
Category distribution across all answers:
- Announcement Creep: 7 options (Q1a, Q1b, Q2a, Q2d, Q3b, Q4a, Q5a)
- Calendar Debt: 8 options (Q1d, Q2c, Q3c, Q3d, Q4b, Q4d, Q5b, Q5d)
- Founder Dependency: 5 options (Q1c, Q2b, Q3a, Q4c, Q5c) + tie-break advantage
Tie-break order: Founder Dependency > Calendar Debt > Announcement Creep. Breaks toward higher-intervention category. This ensures Founder Dependency is reachable with 5 scoring options — a reader with 2 FD + 2 CD + 1 AC ties FD vs CD, and FD wins.
Scorecard grade distribution note: With 2 questions on a 0-3 scale, the 16 possible combinations per meeting distribute as: A (5-6) = 19%, B (3-4) = 37%, C (1-2) = 37%, D (0) = 6%. D requires both answers to be (d) — a genuinely dead meeting. Most readers will see a mix of A/B/C across their 3 meetings. This is intentional: the A meeting validates their judgment, the C meeting confronts it. The contrast drives action more credibly than telling them everything is broken.
Screen 2: Results
Category label (color-coded, large) + Diagnostic title (reframes their situation)
Category 1: Announcement Creep
Color: Gold (#b79d64) Title: "The broadcasts ate the calendar."
What this means: "Your meetings aren't broken structurally — but the agenda keeps absorbing announcements. New client, new policy, new reminder. Each one is small. Together they consume the entire meeting. The collaborative work that actually needs live time gets whatever's left."
What fixes it: "Channel-level fix. Move the broadcasts to async — a standing weekly update, a Slack channel with a clear format, a voice memo protocol. Protect the remaining meeting time for work that requires multiple people thinking together."
What doesn't fix it: "Trimming the agenda. Putting a timer on each section. Asking people to save questions for the end. You've tried these. The announcements creep back because there's no other place for them to go."
CTA: "The Sync Tax Toolkit builds the async channel — what goes where, what format, what cadence — so the broadcasts have a home outside the meeting."
Get the Toolkit — $27
Category 2: Calendar Debt
Color: Amber (#c49a4a) Title: "Every initiative added a meeting. None were retired."
What this means: "Meetings have accumulated over time. A new client added a status call. A new hire added a check-in. A new initiative added a weekly update. Each one made sense when it was created. None of them were removed when the reason ended."
What fixes it: "Audit-level fix. Classify every recurring meeting — is it producing decisions? Is it information transfer that belongs async? Is it still serving its original purpose? Then restructure, replace, or retire each one based on what the audit reveals."
What doesn't fix it: "Canceling a few meetings this week. The calendar absorbs new ones at the same rate you cancel old ones. Without a recurring audit process, calendar debt compounds."
CTA: "The Sync Tax Toolkit includes the calendar audit framework and the restructure/replace/retire decision tree for each meeting type."
Get the Toolkit — $27
Smaller, below: "If the calendar is too deep to audit alone — meetings stacked across teams, clients, and internal functions — Book a Systems Diagnostic and we'll map it together."
Note for Calendar Debt readers who answered Q1(d) "Made a change that stuck": The results copy addresses this directly. They've proven they can change a meeting when they focus on it. The problem is how many are waiting. The toolkit gives them the systematic process to audit the whole calendar, not just one meeting at a time.
Category 3: Founder Dependency
Color: Red (#c45a4a) Title: "The calendar follows the founder's habits."
What this means: "The infrastructure may exist — Slack, shared docs, project tools. But the founder defaults to meetings because it feels like leadership. Standing in front of the team feels productive. The team mirrors that default. When the founder is out, meetings still happen — but nothing flows without them."
What fixes it: "Behavior-level fix. The founder goes first. Records the voice memo. Posts the update. Skips the meeting once and lets the team see that nothing breaks. This isn't a template problem — it's a leadership default that has to change before any system can work."
What doesn't fix it: "Better tools. More Slack channels. A team agreement. None of it sticks if the founder's default is 'let's hop on a call.' The system follows the founder's behavior, not the firm's intentions."
CTA: "The Sync Tax Toolkit includes the founder's migration playbook — the specific sequence for shifting your own defaults without losing visibility or control."
Get the Toolkit — $27
Smaller, below: "If this pattern runs deeper than meetings — if the whole firm's communication routes through you — Book a Systems Diagnostic. That's an infrastructure build, not a calendar fix."
How the Two Tools Work Together
| Meeting ROI Scorecard | Implementation Diagnostic | |
|---|---|---|
| Opens | A new front the article doesn't touch | The question the Constraint section raises |
| Asks | Is this meeting producing anything? | What's keeping it this way? |
| Shows them | Which meetings are C/D grade | Which root cause they have |
| The surprise | Collaborative ≠ productive | The specific reason they haven't fixed it |
| Emotional response | "I thought these meetings were working" | "That's exactly why nothing changed" |
| Bridges to | Toolkit (what to do with C/D meetings) | The right section of the toolkit (root-cause-specific fix) |
Sequencing in the Campaign
- Wednesday email delivers the ROI Scorecard — it's the bigger revelation, the new front
- The Scorecard's results page links to the Diagnostic as secondary: "See what's keeping these meetings in place"
- Both tools bridge to the $27 toolkit as primary CTA
- Both tools offer the diagnostic call as secondary CTA (with Founder Dependency weighted toward the call)
- Friday's Direct Ask email can reference what the tools revealed
The Reader's Journey
| Step | Asset | They finish thinking | Next step |
|---|---|---|---|
| 1 | Article | "My meetings are full of broadcasts" | "But are they still useful?" |
| 2 | ROI Scorecard | "2 of my 3 meetings haven't produced a decision in months" | "Why can't I fix this?" |
| 3 | Implementation Diagnostic | "I have Announcement Creep — the broadcasts have no other home" | "Give me the templates" |
| 4a | Toolkit ($27) | "I have the playbook for my specific root cause" | Implementation |
| 4b | Diagnostic call | "My problem is bigger than templates" | Engagement conversation |
Open Questions
- What's in the $27 toolkit? The CTA copy references: async channel setup guide, calendar audit framework, restructure/replace/retire decision tree, founder migration playbook. See
sync-tax-microtools-toolkit.mdfor the full proposed contents. Need to confirm. - Toolkit delivery method: PDF? HTML? Notion? Affects CTA mechanics.
- Hand-raiser keyword: MEETINGS? SYNC? SCORECARD? Recommendation: MEETINGS — most natural in a LinkedIn comment.
Changes from v2
- Scorecard capped at 3 meetings (was 3-5). Reduces interaction count. 3 is enough to show the pattern.
- Dropped Q3 (has anyone tried to cancel it). Q1 and Q2 are sharper. Q3 measured organizational politics, not meeting ROI. Two questions per meeting = 18 total interactions.
- Meeting type dropdown replaces free text input. Faster, cleaner results display, no layout issues. Custom option preserved for meetings that don't fit.
- Rescored for 0-6 scale (was 0-9). Grade boundaries adjusted for 2-question scoring.
- Rebalanced Founder Dependency scoring. Q2 option (b) remapped from Calendar Debt to Founder Dependency ("They'd ask the founder specifically — they're the one who knows"). Distribution now: AC 7, CD 8, FD 5+tie-break. FD is reliably reachable.
- Q1(d) Calendar Debt confusion addressed in results copy. Reader who "made a change that stuck" but landed in Calendar Debt sees: "You've proven you can change a meeting when you focus on it. The problem is how many are waiting."