Setting Money on Fire and Looking Busy Doing It: Why Startup Activity Isn't the Same as Startup Progress
Every founder knows the feeling.
The calendar is full. Slack is buzzing. New features are shipping. Meetings never stop. The team is busy.
But here's the uncomfortable question:
Are you actually reducing risk—or are you just staying busy?
In a recent episode of the Zero to Traction podcast, Josh David Miller and Cameron Law explored one of the most common traps facing early-stage founders: confusing activity with progress. They argued that before product-market fit, the most important metric isn't revenue, downloads, or even product development—it's learning velocity.
Here's why that distinction matters.
Busy Founders Often Feel Productive
Many startups celebrate visible accomplishments:
Hiring new executives
Rebranding the company
Building new features
Launching marketing campaigns
Preparing for Product Hunt
Updating onboarding flows
These activities certainly create momentum.
But momentum isn't always progress.
The real question is:
Did any of those activities reduce uncertainty about the business?
If not, they may simply be expensive ways to look productive.
The Real Job of an Early-Stage Startup
Every startup begins with assumptions.
Examples include:
Customers actually have this problem.
They'll pay for a solution.
This feature solves the problem.
This marketing channel reaches the right buyers.
Customers will keep using the product.
Until those assumptions become evidence, they're simply educated guesses.
That's why the goal of an early-stage startup isn't to build as much product as possible.
It's to eliminate uncertainty as quickly as possible.
Learning Velocity Is the Metric That Matters
Josh and Cameron describe learning velocity as the speed at which founders turn assumptions into validated learning.
The faster a startup can answer important questions, the faster it reduces risk.
For example:
Instead of spending three months building a feature...
A founder might spend three days interviewing customers.
Instead of redesigning an application...
They might test whether customers even care about the problem first.
Learning compounds.
Every answered question reveals the next question worth testing.
Are You Solving the Biggest Risks?
Not every assumption deserves equal attention.
Founders should prioritize work that is:
Important
Risky
If an assumption could determine whether the business succeeds or fails, it deserves attention first.
Examples include:
Do customers actually experience this pain?
Is the problem urgent enough to solve?
Can customers be reached consistently?
Will they pay?
Everything else can wait.
Features Are Not Progress
One of the podcast's recurring themes is that founders often mistake product development for business development.
Adding features feels productive.
Shipping updates feels productive.
Completing roadmaps feels productive.
But unless those features help validate customer demand, they don't necessarily move the business forward.
As the hosts point out:
A product isn't moving forward simply because it's getting bigger.
It's only moving forward if it's creating more value for customers and reducing uncertainty about the business.
Shorter Learning Loops Win
Another key takeaway is the importance of reducing Time to Customer (TTC).
Time to Customer measures how quickly an idea gets in front of real users.
Great startups minimize that time.
Instead of weeks spent debating ideas internally, they rapidly test assumptions with customers.
That might mean:
Customer interviews
Landing pages
Clickable prototypes
Mockups
Concierge services
Manual experiments
The faster customers react, the faster founders learn.
Customer Conversations Beat Perfect Planning
Many founders delay customer interviews because they want to prepare the "perfect" interview script.
Ironically, that preparation often delays the very learning they're seeking.
The podcast emphasizes a simpler approach:
Start talking.
Real conversations quickly reveal:
Better questions
Unexpected pain points
Hidden objections
New assumptions worth testing
No script can replace actual customer feedback.
Your Time Is Your First Investment
One of the more memorable ideas from the discussion is this:
Before you invest money, you're investing time.
Unlike capital, time can never be recovered.
That means founders should constantly ask:
Is this task worth the next three weeks of my life?
If the answer is uncertain, there's probably a smaller experiment that can produce the same learning much faster.
When Activity Creates the Illusion of Progress
The hosts examined several hypothetical startups that looked busy on the surface.
Examples included teams that were:
Hiring executives before validating growth
Rebranding before finding customers
Building major features before proving demand
Optimizing onboarding before understanding why users left
Preparing for launch without validating distribution
Each company appeared active.
None demonstrated meaningful learning.
The lesson was clear:
Startups don't succeed because they work harder. They succeed because they learn faster.
Every Experiment Should Answer a Question
Before beginning any new project, founders should ask:
What assumption are we testing?
How will we know if we're right?
What metric proves success?
What will we do differently after learning the result?
If those questions can't be answered, the activity probably isn't reducing risk.
Final Thoughts
Being busy is easy.
Looking productive is easy.
Building features is easy.
The difficult part is consistently testing the assumptions that determine whether your startup will survive.
The founders who move fastest aren't necessarily the ones writing the most code or attending the most meetings.
They're the ones who learn the fastest.
If every week ends with fewer assumptions and more evidence, your startup is moving forward—even if the product changes dramatically along the way.
Frequently Asked Questions
What is learning velocity?
Learning velocity is the speed at which a startup turns assumptions into validated knowledge through customer feedback and experimentation.
Why is learning velocity more important than revenue early on?
Before product-market fit, startups need to reduce uncertainty. Learning helps founders discover whether customers have a real problem and whether the business model works before scaling.
What is Time to Customer (TTC)?
Time to Customer measures how quickly a founder can take an idea or hypothesis and put it in front of real customers for feedback.
How can startups increase learning velocity?
Founders can increase learning velocity by running smaller experiments, talking to customers earlier, shortening feedback loops, and focusing on testing their riskiest assumptions first.
How do I know if my startup is making progress?
Real progress isn't measured by features built or hours worked. It's measured by whether your startup has reduced uncertainty, validated important assumptions, and gained evidence that moves the business closer to product-market fit.
About Josh David Miller
Over the past decade, Josh David Miller has empowered over 100 startup founders and innovators to launch and scale their ventures. As the driving force behind the Traction Lab Venture Accelerator,
Josh specializes in guiding early-stage startups through the intricate journey from ideation to product-market fit. His expertise lies in transforming innovative concepts into viable, market-ready solutions, ensuring entrepreneurs navigate the challenges of the startup ecosystem with confidence and strategic insight.
About Cameron R. Law
Cameron R. Law is a Sacramento native dedicated to building community, growing ecosystems, and empowering entrepreneurs.
As the Executive Director of the Carlsen Center for Innovation & Entrepreneurship at California State University, Sacramento, he leverages his passion for the region to foster innovation and support emerging ventures. Through his leadership, Cameron plays a pivotal role in shaping Sacramento's entrepreneurial landscape, ensuring that innovators and builders have the resources and support they need to succeed.
