reconstruct billable hours
Reconstruct Billable Hours, without turning Friday into archaeology
the week ends with archaeology across calendar, chat, commits, and email. Superscribe helps capture the spoken context, notes, and time trail before the details go cold.
Superscribe
Stop rebuilding work after the fact
Use Superscribe to capture the words, context, next steps, and time while the work is still happening.
It’s Friday afternoon. You just pushed the last commit for a client feature. The code is clean. The work is done. But now a different kind of work begins- the billing archaeology.
You stare at a blank invoice line, trying to remember what you did on Tuesday morning. You start digging. You open your calendar, Git logs, Slack history, and that one stray notes file. The next hour is a painful, manual process to reconstruct billable hours from digital breadcrumbs. You piece together a vague narrative of your week, knowing you’re probably missing things. You round down because you’re not sure. You lose money.
This isn’t just an administrative headache. It’s a leak in your freelance business.
The Real Cost of Billing Archaeology
When you have to reconstruct work after the fact, you’re not just losing time. You’re losing revenue and client trust. Every forgotten five-minute bug fix, every quick Slack call to clarify a spec, every bit of research- it all adds up. When you can’t remember the specifics, you can’t bill for them.
This leads to two problems:
- Underbilling: You leave money on the table because your memory isn’t a perfect ledger. You bill for the big chunks you remember, but the smaller, connecting pieces of work fall through the cracks.
- Vague Invoices: Your invoice ends up with lines like “Programming” or “Development work.” This does nothing to communicate value to your client. It looks generic and can create friction, making clients question what they are actually paying for.
The weekly scramble to build a time-proof case for your own work is a tax on being a freelancer. It’s a frustrating end to a week of creative, high-value problem-solving.
Try it on the real workflow
Turn the next spoken note into finished work
Use Superscribe while the context is still fresh. Speak naturally, keep working, and let the output land where it belongs.
A Timer is a Leaky Bucket
The common answer to this problem is the start-stop timer. But timers are fragile. They only work if you remember to use them perfectly every single time. You forget to press start. You forget to press stop. You come back from a distraction and realize the timer has been running on the wrong task for an hour.
Worse, a timer only captures duration, not context. It tells you how long you worked, but not what you did or why. You still have to do the archaeology, cross-referencing your timer entries with your project notes and tickets to write a meaningful invoice description. A timer just adds another administrative task without solving the core problem of capturing context. It’s a leaky bucket that still requires you to patch the holes at the end of the week.
My Own Search for a Better System
I built Superscribe because I got tired of guessing my hours at the end of every month. I would look through emails, code, chat messages and random notes trying to remember what I actually did. The numbers were never right and I knew I was losing money. It felt like running a business with a hole in its pocket.
Three years ago I had the idea for a phone app that could automatically catch client calls. I gave up on it back then because it seemed too hard. In the years after that I kept making other voice tools. Each one taught me something new. I was solving adjacent problems without realizing I was circling back to the original one.
The missing piece became clear when I added automatic time tracking to the main desktop app. The moment that feature went live, I knew I needed to revive the phone app idea for real client calls, so everything would connect without extra work. After all those other voice projects, the answer was finally obvious. New AI tools helped turn what once seemed too difficult into something practical. The work you speak on a call and the work you speak at your desk are just two parts of the same whole.
The best proof came on a flight. I made normal business calls with my regular phone number over the plane’s Wi-Fi. The calls got written down, cleaned up, and sent straight into my work system. That used to be just a wish. Now it is how the product works.
This is the tool I always wanted. You speak. Clean words appear right in the app you are using. The time, notes and next steps happen by themselves in the background. No timers. No guessing. Just good work that gets counted.
Stop the billing leaks
Get the Billable Hours Recovery Checklist
A practical guide to identifying and capturing the billable work you're probably missing every week. Stop the guesswork.
How to Reconstruct Billable Hours By Not Reconstructing Them
The best way to solve the Friday archaeology problem is to prevent it from happening in the first place. This means capturing the work, context, and time trail while it’s fresh. The simplest way is to just narrate your work as you go.
Think of it like a developer’s rubber duck, but one that takes notes.
As you finish a task, a bug fix, or even a thought process for a tricky bit of logic, you simply speak it out loud. You’re not performing for anyone. You’re creating a private, high-context work log for your future self- the one who has to write the invoice.
Here’s a practical workflow:
- Speak the “Why” and “What.” When you finish a commit, just say what you did. “Okay, just pushed the fix for ticket 1138. The issue was a null reference in the user service. I added a guard clause and a unit test to cover it. Moving on to the password reset flow.”
- Let the Trail Build Itself. Superscribe captures your words as clean text, right inside your IDE, ticket, or notes app. In the background, it also captures the time associated with that work. There is no start-stop button. The time trail is created automatically from your activity.
- Export a Client-Ready Log. At the end of the week, you don’t have a list of vague timer entries. You have a detailed, chronological log of your work, in your own words. Copy and paste these notes into your invoice. “Fixed null reference in user service (ticket 1138), added guard clause and unit test” is infinitely more valuable to a client than “1 hour - Bug fixes.”
This approach turns a painful administrative task into a seamless part of your development workflow. You stay in creation mode, and the paperwork takes care of itself.
Take the next step
Open your next pull request and test this workflow
After your next commit, dictate your notes directly into the PR description. Capture the context, save the time, and see how it feels.
FAQ: Reconstructing Billable Hours
Isn’t it weird to talk to my computer while I code? It might feel strange for the first ten minutes. But it’s just for you. Think of it less like a performance and more like a private voice-powered work journal. It’s faster and more detailed than typing, and it keeps you focused on the code instead of switching to a different app to log your time.
How is this different from just running a timer? A timer captures duration. Superscribe captures context. The output isn’t just a number of hours; it’s a client-ready work log that explains the value you delivered during that time. The automatic time tracking is a byproduct of you capturing your work, not a separate task you have to remember to do.
Does this work with my existing tools like VS Code or Linear? Yes. Superscribe is a desktop utility that works wherever you can type. There’s no complex integration to set up. You press a hotkey, you speak, and the text appears in your active window- whether that’s your IDE, a project management tool, a Slack message, or an email.