Micro Pomodoro: Free Timer Tool That Killed My Burnout

Micro Pomodoro: The Free Lightweight Timer I Built to Beat Burnout and Track Billable Hours

There's a specific kind of tired that only freelancers understand. It's not the tired that comes from doing too much in one day. It's the tired that comes from sitting in front of a screen for five hours straight, barely moving, barely blinking, running on deadline pressure and cold coffee — until suddenly you can't think clearly, can't write a clean sentence, and can't remember what you were doing before you opened that last tab.

That was my working life for longer than I should have allowed. No breaks. No structure. Just an open browser, an open task list, and a vague plan to "rest when it's done" — which meant never resting, because something was always still undone.

The Pomodoro technique was supposed to fix that. And in theory, it's exactly right: 25 minutes of focused work, 5-minute break, repeat. But every web-based timer app I tried either consumed memory I couldn't spare, got accidentally closed when I was switching tabs, or disappeared entirely when I went full-screen. I needed something that stayed on my screen, used zero browser resources, and just worked — quietly and reliably, all day.

Key Takeaways:

• Freelancer burnout from unstructured work sessions is a real productivity killer, not just a wellness cliché
• Web-based Pomodoro timers drain RAM and get accidentally closed during normal browser use
• I built Micro Pomodoro & Billable Timer — a floating, offline dual-mode timer that never competes with your browser
• It took 32 days of scripting and 31 failed attempts before the tool functioned correctly
• Sold on Gumroad for $24.99 — free to download at rifins.com
• Windows only, requires AutoHotkey v2.0 — no technical skills needed to run it

Why "Just Use a Timer App" Doesn't Work for Serious Freelancers

I've tried most of the popular options. Browser tab timers, Chrome extensions, web apps with accounts and dashboards. They all share the same fundamental flaw:

They live inside the same environment you're trying to manage.

When your timer is a browser tab, it's competing with every other tab for your attention and your RAM. I run research-heavy content projects — at any given moment I might have 20+ tabs open across two windows. Adding a timer tab into that mix means it gets buried, forgotten, or accidentally closed when I'm cleaning up tabs between tasks. I've lost Pomodoro sessions mid-sprint more times than I can count.

Here's the problem that actually cost me money:

Beyond focus sessions, I also take hourly projects on Upwork. Accurate time tracking for those isn't optional — it's how I get paid correctly and how I prove my work to clients. Browser-based stopwatches had the same accidental-closure problem. I'd be 90 minutes into a tracked session, close the wrong tab, and lose my entire billing log. Then I'd have to estimate — and estimating billable hours is a fast way to either undercharge yourself or create invoice disputes with clients.

I needed one tool that handled both problems. It didn't exist, so I built it.

What Burnout Actually Looks Like in a Freelance Workflow

I want to be specific here, because "burnout" gets used so loosely online that it's lost its meaning.

For me, it wasn't a dramatic collapse. It was a slow erosion of quality.

First my writing speed dropped. Then my editing judgment got foggy — I was approving sentences I would have rewritten two months earlier. Then I started avoiding complex tasks by doing easy busywork instead, which felt like productivity but wasn't. By the time I noticed what was happening, I was billing fewer hours, producing lower-quality work, and feeling worse than when I'd started the day.

The root cause was simple:

I wasn't taking real breaks. Not because I didn't know I should, but because nothing in my workflow enforced them. There was no friction between "finishing one task" and "immediately starting the next one." Without a structured pause, I just kept going — until I couldn't.

The Pomodoro method works precisely because it builds that friction in deliberately. The break isn't optional; it's structural. But only if the timer actually runs reliably and stays visible. A timer you can accidentally close isn't a system — it's a suggestion.

32 Days, 31 Errors, One Tool That Actually Works

I'll be honest: I thought this would be the easiest of my AutoHotkey projects. A timer, visually, seems simple. Start, count down, alert, reset.

The reality of building it was significantly more complicated.

The core challenge was state management across two different timer modes. Pomodoro mode needed a countdown with a precise 25-minute ceiling, a visual alert at zero, and a clean reset without residual state bleeding into the next session. Stopwatch mode needed an open-ended upward count, formatted in HH:MM:SS, that could run for multiple hours without drift or memory accumulation.

Getting both modes to coexist in a single lightweight script — with a GUI that stayed on top without stealing focus, and SetTimer loops that didn't create CPU overhead — required solving problems I hadn't anticipated when I started.

The modulo mathematics for time formatting alone caused six failures:

Converting raw elapsed seconds into a clean MM:SS display requires dividing seconds by 60, using the remainder for the seconds display, and carrying the quotient to minutes. Simple on paper. In AutoHotkey, getting that calculation to update in real time without flickering or drift took multiple iterations. Attempt 17 had correct formatting but the display flickered every second. Attempt 23 ran smoothly but the Pomodoro countdown would occasionally freeze at 00:01 without triggering the completion alert.

Attempt 31 was almost right. The timer ran perfectly — but the GUI wouldn't drag to reposition on screen. I was one fix away.

Attempt 32 worked completely. I dragged it to the corner of my screen, started a Pomodoro session, and watched it count down cleanly to zero. After 32 days of evening scripting sessions, it felt like a significant moment.

What Micro Pomodoro & Billable Timer Actually Does

The Two Core Modes

Pomodoro Mode — starts a 25-minute countdown timer. When it reaches zero, the tool alerts you to take your break. It's visible, persistent, and runs completely offline with no browser involvement. Your RAM stays free for actual work.

Stopwatch Mode — starts an open-ended upward count in HH:MM:SS format for tracking billable freelance hours. It runs until you stop it manually, with no session length limit. Log the number when you finish and put it directly on your invoice.

Features That Go Beyond Basic Timing

• Always-on-top floating display — stays visible over your active windows without blocking your workspace
• Zero browser dependency — runs as a background script with negligible CPU and memory usage
• Drag-to-position — place it in any corner of your screen to fit your workspace layout
• Clean state resets — Stop/Reset clears all timer state completely, no residual variables carrying between sessions
• Offline operation — no internet connection required, no account, no data sent anywhere
• Dual-mode in one window — switch between Pomodoro and Stopwatch without reopening or reconfiguring anything

The Honest Limitations

Micro Pomodoro uses a fixed 25-minute Pomodoro interval. If you prefer longer focus blocks — 50 minutes is popular with some writers — the interval isn't adjustable through the GUI. You'd need to edit the script file directly to change that value, which is a one-line change but requires opening the .ahk file in Notepad.

The billable hour stopwatch also doesn't auto-export or log to a file. It displays your elapsed time, and you record it manually. If you need automatic time logging with client labels and CSV export, you'll want a dedicated time tracking app alongside this tool.

Best suited for: Upwork/Fiverr Freelancers, Developers, Remote Workers, Students

What Changed in My Actual Workflow

I tracked my productivity output and subjective energy levels across four weeks in early 2026 — two weeks without structured breaks, two weeks using Micro Pomodoro consistently.

The output difference was measurable:

In unstructured weeks, I averaged 6.2 publishable article sections per day before my writing quality degraded noticeably. In Pomodoro weeks, that number rose to 8.1 — and I finished with enough mental clarity to do a final editorial pass the same day rather than leaving it for the next morning.

For billing accuracy:

Before using the stopwatch mode, I was estimating hourly project time after the fact, which consistently led to me undercharging by 15–25 minutes per session. Small per session, but across a month of hourly projects it was a meaningful amount of unbilled work. The stopwatch eliminated that entirely.

The bigger shift was psychological. Having a visible countdown running made stopping at 25 minutes feel like completing something rather than quitting. The break became a reward instead of an interruption.

How to Download and Run It (Beginner's Guide)

Everything you need:

1. Step 1 — Install AutoHotkey v2.0: Download the v2.0 installer from autohotkey.com and run it with default settings. One-time setup.
2. Step 2 — Download the Script: Download MicroPomodoroTimer.ahk from my GitHub. Save it anywhere on your machine — Desktop is fine.
3. Step 3 — Launch It: Double-click the .ahk file. The floating timer window appears immediately. A small AutoHotkey icon in your system tray confirms it's running.
4. Step 4 — Activate with the Shortcut: Press Ctrl+Shift+S to show or hide the timer window during your session.
5. Step 5 — Position and Use: Drag the window to your preferred screen corner. Click Pomodoro to start your 25-minute focus session, or Stopwatch to begin tracking billable hours. Click Stop/Reset when done.

Why I'm Giving This Away Free

This tool sells on Gumroad at $24.99 and has found a steady audience among Upwork freelancers and remote developers who needed exactly what it does — a reliable, offline, always-visible timer that doesn't add browser overhead.

I'm sharing it free at rifins.com for the same reason I've released my other tools here:

The AutoHotkey community helped me solve the problems that made this tool possible. The 31 failures I went through were only productive because forum members helped me understand what I was doing wrong. Sharing the finished result freely is a direct continuation of that same dynamic. If you found this post, you're getting the exact tool that others paid for — not a demo, not a lite version, but the complete script I use every working day.

Download it. Set a Pomodoro. Take your break when it goes off.

Frequently Asked Questions