One I Have to Push, One That Runs Itself — What VoiceDoz and StockDoz Taught Me
In the past two weeks, I shipped two products at the same time: VoiceDoz and StockDoz.
On the surface, they’re both “products I built.” But the more I work on them, the more I realize these aren’t two products — they’re two completely different species.
One I have to push forward every day. One walks on its own.
VoiceDoz: The One That Needs Me in the Room
VoiceDoz is a locally-running voice-to-text tool. It takes your “umm, you know, like…” rambling and turns it into clean, readable text using AI.
It’s a textbook active product. Current status:
- Mac version is essentially complete, payment flow wired up
- Windows version is built, now in testing
- Website is 80% done, still missing login and dashboard
Three tracks running in parallel. Every inch of forward motion comes from me pushing.
And that’s just pre-launch. After launch I still have to:
- Fix bugs and ship features
- Handle user feedback and support
- Drive acquisition — content, marketing, ads
- Maintain pricing, subscriptions, refunds
- Keep filling platform-specific gaps across Mac, Windows, iOS, Android, Linux
VoiceDoz’s lifeline is tied to my continued effort. The moment I stop, it stops.
This isn’t a bad thing — every product with a real upside works this way. If I get it right, it grows. If I get it wrong, it dies. But either way, I have to be in the room.
StockDoz: The One That Runs Without Me
StockDoz is the opposite.
It’s a stock market indicator dashboard. 30 financial indicators × 8 languages = over 2,000 static pages. Every day, a Cloudflare Worker pulls fresh data, triggers a rebuild, and auto-deploys.
Setting up the templates took me about one to two weeks. After that, I left the room.
Not “semi-automatic.” Not “I check on it once a day.” I can go a month without opening the project and it keeps running just fine.
Annual cost: $10 for the domain. Daily time investment: 0. Expected revenue: $100–$200/month.
It’s not a lot of money. But the point isn’t the amount — it’s that I am not a variable in this revenue equation.
Data flows in from public APIs → templates auto-generate content → pages auto-deploy → search engines bring traffic → ads generate revenue.
Not a single step in that chain needs me.
The Real Difference Between the Two
Most people will compare these two products by asking “which one makes more money.” But the amount isn’t the point. The point is whether value gets created without you being there.
| Dimension | VoiceDoz (Active) | StockDoz (Passive) |
|---|---|---|
| Ceiling | High (potentially thousands or even five figures per month) | Low ($100–$200/month) |
| Decay risk if I stop | High (revenue declines once I disengage) | Low (keeps running long after) |
| My role | Operator — has to be there every day | Architect — builds it once and leaves |
| Source of value | My continuous effort | A one-time system design |
| Best fit | Building a real indie product that wins | Earning cash flow that doesn’t depend on you |
This isn’t a question of which is “better.” These are two different bets.
Active products bet on “can I get this thing right?” Passive products bet on “can this system design keep producing value?”
Why I’m Doing Both
The traditional indie dev advice is: focus. Build one product. Take it as far as it can go.
That advice was correct — in the past.
Setting up a passive income system used to be heavy work. Servers to maintain, content to update, SEO to grind on. Anything “passive” was actually quite hands-on.
But the AI era changed that.
The cost for a single person to build a genuinely passive system — from data scraping to content generation to multilingual translation to auto-deployment — has collapsed. One person, one or two weeks, and you have a site running 2,000+ pages.
In this environment, “focus on one product” deserves a rethink. Because:
Active products fund the dream. Passive products fund the patience.
VoiceDoz is the dream. Building an indie product people actually pay for. Proving I can win on the active track.
StockDoz is the patience. It doesn’t earn much per month, but it tells me: even if VoiceDoz doesn’t make money right away, I’m not backed into a corner. I have room to take my time and get VoiceDoz right — instead of making bad decisions because next month’s mortgage is staring me down.
The biggest value of a passive product isn’t the $100–$200 it earns — it’s the patience it buys for your active product.
The Real Shift
Building these two projects made me realize something:
The most important shift for an indie dev isn’t from “employed” to “independent.” It’s from “what product can I build” to “what kind of product portfolio can I build.”
A single product is a bet. A portfolio is a system.
- One passive product, as a floor;
- One active product, reaching upward;
- Maybe an AI content machine on top of that, for long-tail traffic;
- Given time, each becomes its own independent cash flow.
None of them will make me financially free. But together, they give me the staying power to keep going — and that’s the real reason indie dev works over the long run.
One I push. One that pushes itself.
They’re both products I built. But what they’re really doing is showing me two sides of the same thing.