
🧞♂️ New to Exponential Scale? Each week, I provide tools, tips, and tricks for tiny teams with big ambitions that want to scale big. For more: Exponential Scale Podcast | Scalebrate | Scalebrate Hub
Founding Supporters: Support the following people and companies because they supported us from the beginning: DataEI | Dr. Bob Schatz | .Tech Domains | Fairman Studios | Jean-Philippe Martin | RocketSmart AI | UMBC
In today's newsletter:
Latest Podcasts: What You Missed
Want to Scale? ICP: Do You Know Me? – If your business feels busy but not scalable, this episode shows how a fuzzy ICP quietly kills leverage, margins, and momentum and how dialing it in changes everything.
The 10 Money Skills Every Microteam Should Master - You’re great at what you do. But if the money side of your business feels confusing, stressful, or weirdly fragile, this episode is required listening.
What Can You Learn from 22 Microteam Success Stories? (…Plus 1) - Real microteams, real results, and the repeatable patterns behind outsized growth with tiny teams… and one notable failure.
Interview with Wade Foster, CEO of Zapier - How Zapier scaled with leverage, automation, and focus instead of hiring and organizational bloat.
The Output Question: Measuring Impact, Not Activity
End of the day. You look at your calendar.
Eight meetings. Eighty messages answered. Countless emails sent and received.
You were busy.
But what did you actually produce?
This is the activity trap. You measure hours worked, tasks checked off, meetings attended, but none of that tells you if you moved the business forward.
The question isn't: "How busy was I today?"
The question is: "What did I produce today?"
Output > activity. Always.
New rule: Every day must produce at least one tangible output.
Examples of output:
Proposal sent
Blog post published
Sales call completed
Contract signed
Feature shipped
Hire made
Not output:
Meetings
Emails
Slack replies
"Thinking about strategy"
The Difference Between Activity and Output
Activity = Things you do.
Output = Things you produce.
Most founders confuse the two.
Activity:
Attended 5 meetings
Sent 20 emails
Answered 30 Slack messages
Reviewed 10 documents
Feels productive. But produced nothing.
Output:
Closed 1 deal
Shipped 1 feature
Published 1 blog post
Hired 1 person
Feels like less work. But moved the business forward.
Think of it like a factory.
Activity = Workers showing up and moving around.
Output = Actual products leaving the factory.
You don't pay workers for showing up. You pay them for what they produce.
The same applies to you.
Why This Matters for Microteams
Big companies can afford to have people in meetings all day. They have layers of middle management whose job is coordination.
You? Every hour you spend in low-output activity is an hour not spent moving the business forward.
Here's why measuring output is critical:
Time is your only non-renewable resource. You can't buy more hours. Spend them on output.
Activity feels productive but delivers nothing. Busy ≠ effective.
Output compounds. 1 blog post drives leads for years. 1 meeting is forgotten by tomorrow.
Investors/customers care about output, not activity. They don't care if you worked 80 hours. They care if you shipped the feature or closed the deal.
The best microteams don't optimize for hours worked. They optimize for output produced.
The Output Question Framework
Here's how to shift from measuring activity to measuring output.
Step 1: Define What "Output" Means for Your Role
Output = Tangible deliverables that move the business forward.
For a founder:
Deals closed
Revenue generated
Product shipped
Hire made
Strategic decision executed
Content published
For a salesperson:
Proposals sent
Demos delivered
Contracts signed
For a developer:
Features shipped
Bugs fixed
Code reviewed and merged
For a marketer:
Campaigns launched
Content published
Leads generated
Not output:
Meetings attended
Emails sent
"Thinking about strategy"
"Working on X" (without finishing)
Step 2: Track Daily Output (Not Hours)
At the end of each day, ask: "What did I produce today?"
Template:
Date | Output | Impact |
|---|---|---|
March 1 | Sent 2 proposals | Potential $30K revenue |
March 2 | Published blog post | 500 views, 8 leads |
March 3 | Closed 1 deal | $15K revenue |
March 4 | Shipped feature | Unlocks enterprise sales |
March 5 | Hired engineer | Doubles dev capacity |
If you can't list at least 1 tangible output, your day was wasted.
Step 3: Block Time for Output (Not Meetings)
Design your calendar around producing output, not attending meetings.
Example:
Time | Activity | Output Goal |
|---|---|---|
9-11am | Deep work: Write proposal | 1 proposal sent |
11am-12pm | Sales calls | 2 demos delivered |
1-3pm | Deep work: Ship feature | 1 feature deployed |
3-4pm | Reactive work (email, Slack) | Inbox zero |
Notice: Output is the goal. Activity (meetings, email) is minimized.
Step 4: Say No to Low-Output Activities
Every time someone requests your time, ask: "Will this produce output?"
Examples:
Request | Output? | Decision |
|---|---|---|
"Can we have a status meeting?" | No (just talking) | Decline. Request async update instead. |
"Can you review this draft?" | Yes (if feedback unlocks their output) | Accept, but batch reviews. |
"Can we brainstorm ideas?" | No (unless decisions are made) | Decline. Send ideas async or schedule decision-making session. |
"Can you hop on a call to discuss?" | Maybe (depends on outcome) | Ask: "What's the decision we need to make? Can we do this async?" |
Rule: If it doesn't produce output, decline or delegate.
Step 5: Batch Low-Output Work
Some activities are necessary but don't produce output (email, Slack, admin).
Batch them.
Example:
Email/Slack: 2x per day (30 min each) instead of all day
Meetings: Tuesday/Thursday only instead of scattered throughout the week
Admin: Friday afternoons instead of randomly during the week
This frees up blocks for high-output work.
Step 6: Measure Output Weekly
At the end of each week, tally your output.
Template:
Week of March 1-5:
Output:
3 proposals sent
2 deals closed ($35K revenue)
1 blog post published
1 feature shipped
1 engineer hired
Activity (for comparison):
12 meetings attended
150 Slack messages
80 emails sent
Which list mattered? Output.
If your output list is short, your week was wasted—no matter how many meetings you attended.
Step 7: Optimize for Output-Per-Hour
The goal isn't just output. It's maximum output per hour worked.
Ask:
Can I produce the same output in half the time? (Efficiency)
Can I produce 2x the output in the same time? (Leverage)
Examples:
Output | Time (Before) | Optimized | Time (After) |
|---|---|---|---|
Write proposal | 4 hours | Use template | 1 hour |
Sales call | 1 hour | Pre-qualify leads | 30 min (only qualified) |
Blog post | 6 hours | Repurpose existing content | 2 hours |
The best founders produce more output in less time.
High-Output Habits
1. Start the day with one high-output task
Before checking email or Slack, produce one thing
Example: Write proposal, ship feature, publish post
2. Block 3-4 hours daily for deep work
Deep work = high-output work
Meetings = low-output work
3. Batch low-output work
Email, Slack, admin: do it all at once, not scattered
4. Decline meetings that don't produce decisions
Meetings are only valuable if they result in output (decision, plan, approval)
5. Use templates and systems
Proposals, onboarding docs, sales scripts—templatize everything
Speeds up output 5-10x
6. Delegate low-output work
Admin, scheduling, data entry—hire a VA or automate it
Your time is for high-output work only
7. Track output, not hours
Don't celebrate "I worked 60 hours this week"
Celebrate "I closed 3 deals, shipped 2 features, hired 1 person"
The Output Test
At the end of every day, ask:
What did I produce today?
Did it move the business forward?
Could someone else have done this? (If yes, delegate it)
If you can't answer #1 with at least one tangible deliverable, your day was wasted.
Common Excuses (and Why They're Wrong)
Excuse 1: "I was in meetings all day."
Reality: Meetings are activity, not output. Decline unnecessary meetings.
Excuse 2: "I was putting out fires."
Reality: Firefighting is reactive. Build systems to prevent fires (then you can focus on output).
Excuse 3: "I was thinking/planning."
Reality: Thinking without execution produces nothing. Turn plans into output.
Excuse 4: "I was helping the team."
Reality: Helping is good—if it unlocks their output. But if you're doing their work, you're blocking your own output.
Excuse 5: "I need more time to finish."
Reality: Ship imperfect output today instead of perfect output never. Iterate.
Today's 10-Minute Action Plan
You don't need to overhaul your entire workflow today. Just measure today's output.
Here's what to do in the next 10 minutes:
Open a doc or spreadsheet
Write: "What did I produce today?"
List every tangible output (proposals sent, deals closed, content published, etc.)
If the list is empty, ask: "What can I produce in the next 2 hours?"
Block 2 hours tomorrow for high-output work (no meetings, no interruptions)
That's it. One output measured, one block scheduled, 10 minutes.
Next week, do this daily. In a month, you'll be producing 5x more output in the same hours.
A Final Thought
Busy is a trap.
You can be busy answering emails, attending meetings, and checking Slack all day, and produce nothing.
Or you can work 4 focused hours and ship a proposal, close a deal, and publish a blog post.
Output is what matters.
Not hours logged. Not meetings attended. Not Slack badges earned.
What did you produce?
That's the only question that counts.
So stop optimizing for activity.
Start optimizing for output.
Because at the end of the day, no one cares how busy you were.
They care what you built.
Refer Folks, Get Free Access
What This Is
A plug-and-play daily/weekly output tracking system that forces you to measure what you produce instead of what you do. This is your scoreboard for impact, not busywork.
Why You Need This
Most microteam founders are drowning in activity but starving for results. You work 50+ hours, attend endless meetings, answer hundreds of messages and wonder why revenue is flat and nothing ships.
The problem? You're tracking the wrong metrics.
You count hours worked, meetings attended, emails sent. But none of that moves the business forward.
This Output Scoreboard fixes that. It replaces vanity metrics (hours, meetings, messages) with impact metrics (deals closed, features shipped, content published). It's the dashboard that shows you—at a glance—whether you're building a business or just staying busy.
How to Use This Dashboard
1. Choose Your Output Categories: Identify 5-7 categories of output that matter for your role (examples below)
2. Track Daily: At the end of each day, log what you produced (not what you did)
3. Review Weekly: Every Friday or Sunday, review your output totals and identify patterns
4. Optimize: Double down on high-impact activities, eliminate low-output work
5. Make It Visible: Put this dashboard somewhere you see it daily (Notion dashboard, spreadsheet on second monitor, printed sheet)
Subscribe to our premium content to read the rest.
Become a paying subscriber to get access to this post and other subscriber-only content.
Upgrade