I mapped my 168 hours and found 30 hours going to nothing - so I built a tool to see it
I have a day job and a side project. For months I kept telling myself "I don't have enough time to work on it."
Then I did something simple. I sat down and tried to account for every hour of my week. All 168 of them.
The result was uncomfortable.
My side project was getting 4-5 hours/week. That sounds reasonable until you do the math: at that rate, it takes 15 years to put in what someone working full-time does in 3.
But the real shock wasn't the side project hours. It was the ~30 hours I couldn't account for at all. Not scrolling. Not resting. Not working. Just... gone. Time leaking into transitions between things, half-activities, low-grade nothing.
I was never "too busy." I was invisible to my own allocation.
So I built a free tool that does this exercise in 60 seconds. You allocate your 168 hours across life categories (work, health, side project, relationships, etc.) and it shows you where that schedule leads in 5 and 10 years.
The projection is what makes it hit. Seeing "4 hours/week on your side project = 1,300 hours over 5 years" makes the tradeoff concrete in a way that vague guilt never does.
No login. No signup. Just the math.
https://app.timera.co/?utm_source=indiehackers&utm_medium=organic&utm_campaign=w06
A few things I've noticed from people who've tried it:
- Almost everyone underestimates their "unaccounted" time by 10+ hours
- The side project number is usually the most painful one
- People who see the 5-year projection change their behavior faster than people who just track daily
I'm building this into a full product (connects to Google Calendar, shows your guess vs reality, projects your trajectory forward). Still early.
Would love honest feedback - especially from other builders juggling a day job and a side project. What does your 168 breakdown look like?
The time audit angle is underrated. Most side project advice focuses on what to build — almost none of it addresses where the hours actually go once you start. I ran into a similar awareness problem from a different direction: I was spending hours manually browsing Reddit trying to understand what users in a niche actually struggle with. No structure, no prioritization — just vibes. What changed it for me was treating research like you treated your calendar: make it measurable. I started scoring pain points by frequency × emotional intensity instead of just "feels important." Suddenly 40+ hours of scattered reading compressed into a clear priority matrix I could actually act on. The meta-lesson seems to be the same: you can't improve what you can't see. Whether it's hours or user insights. Curious — now that you can see where the 30 hours went, what surprised you most about the breakdown?
Quick update — I've since built this into a full service at airiya.org, including a live case study and free tool. If anyone wants to see the full output, it's all there.
The biggest surprise was how much time was going to transitions - not scrolling, not resting, just moving between things. That was about 60% of the unaccounted block. The other 40% was low-grade phone use that I'd been mentally categorizing as "breaks" but was actually just default behavior with zero recovery value.
The transition cost finding is fascinating — and makes sense once you see it. Context switching has a well-documented cognitive cost, but most people only think about it in terms of work tasks, not the micro-transitions between phone, desk, conversation, back to phone.
The "zero recovery value" framing for default phone behavior is sharp. It looks like rest because it feels passive, but it's not actually restoring anything. That's a real blind spot most time tracking tools miss — they log what you did, but not whether it actually recharged you.
Did tracking this change how you structure your transitions, or mostly just make the problem more visible?
It did, once you see how much time you're waisting, it's hard to unsee it. So you start switching the way you operate, in a way; I became much more cautious with my time
did this exact exercise last month. my breakdown was brutal: 40 hours day job, 50 hours sleep, 14 hours eating/hygiene, 10 hours commute/errands, 20 hours on the side project, 15 hours "downtime" that was actually just scrolling. that left 19 hours unaccounted for.
the 5-year projection idea is killer though. i calculated mine for my outreach business: at 20 hours/week, i'll have put in ~5,200 hours over 5 years. that's not a side project anymore — that's a second career worth of hours.
what actually changed my productivity wasn't tracking time though. it was making the side project the first thing i do each day instead of the last. before work, not after. the energy difference is massive.
the no-login approach is smart for adoption. friction kills tools like this.
That 19 hours unaccounted is the number most people never find because they never look. And you're right that it's not just about tracking - it's about what you do with the visibility once you have it.
The "first thing in the day" shift is interesting. Sounds like your allocation didn't change much in total hours, but the sequencing made the same 20 hours twice as productive. That's a dimension most people miss - it's not just how many hours, it's which hours.
5,200 hours over 5 years is a serious number. At that rate you're basically running two careers simultaneously. Curious - at what point do you think the side project hours overtake the day job in terms of what they produce?
Tracked my week once, found the same thing. The surprising part wasn't the wasted hours — it was realizing I'd been mentally accounting for them as "work." Hard to fix what you've already convinced yourself doesn't exist.
That's the most dangerous version of the problem - when the unaccounted time is wearing a "work" costume. You're not even procrastinating in the traditional sense. You're just... existing inside a work context without producing anything, and your brain files it as productive because you were at your desk.
I found the same thing. The fix wasn't discipline. It was just being able to see the real breakdown clearly enough that I couldn't lie to myself anymore.
The projection framing is really smart — I had a similar "oh crap" moment when I started tracking my own time during the early days of building briefpeak. I was convinced I was spending 20 hours/week on product work, but when I actually mapped it, it was closer to 11. The other 9 hours were this weird mix of "research" rabbit holes and Slack conversations that felt productive but weren't moving anything forward.
One thing worth thinking about as you build this out: the gap between perceived time and actual time is where the real insight lives, so the Google Calendar integration could be gold if you nail that comparison view. Are you planning to categorize calendar events automatically or have users tag them?
This hits close. The 30 “missing” hours didn’t show up for me as downtime, they showed up as false starts. Opening one project, doing 20 minutes, switching to the other, then back again. It all felt like work in the moment, but nothing actually moved.
The 5-year projection framing is sharp because it exposes that fragmentation, not just the total hours.
Did you find any way to reduce the switching itself, or just become more aware of it?