For one month I put a stopwatch on every minute I spent on invoicing. Not just making invoices. Everything around them too: writing them, fixing a wrong one, sending them, checking who had paid, and chasing the people who had not. I run 11pixels Design Studio, I send a normal number of invoices, and I had a hunch that the real cost of billing was hidden somewhere I was not looking. It was.
The total came to about 5 hours across the month. That part did not shock me. What the 5 hours was made of did.
Here is the headline: across those 9 invoices, only about 7% of my invoicing time went to creating invoices. The other 93% went to tracking payments and chasing late ones.
The breakdown
I sent 9 invoices that month. Here is where the time actually went.
| What I did | Time |
|---|---|
| Creating and sending invoices | 22 min |
| Checking payment status, matching UPI and bank credits | 95 min |
| Following up on late payments | 130 min |
| Fixing and reissuing two invoices | 18 min |
| Digging up old invoices for a client and my CA | 40 min |
| Total | ~5 hours |
Read that top row again. Out of roughly 305 minutes, the actual act of creating invoices took 22 of them. Around 7 percent. The other 93 percent was everything that happens after the invoice exists: tracking it, reconciling it, and chasing it.
Why this surprised me
I had spent two years assuming invoicing was a creation problem. The story in my head was the one most freelancers tell themselves: "I hate making invoices, they take forever." So I built a way to make them in 30 seconds, and I genuinely thought I had solved my own problem.
The stopwatch said otherwise. Creation was never the expensive part. It felt expensive because it was annoying and I procrastinated on it, which is a real thing, just look at why freelancers procrastinate on invoicing. But measured in minutes, creation is cheap. The expensive part is the admin tail: was I paid, by whom, how much is still pending, who do I nudge, and where is that invoice from March the client is now asking about.
That admin tail does not feel like work in the moment. It is 4 minutes here, 7 minutes there, a scroll through PhonePe to confirm a credit, a re-read of a WhatsApp thread to find an amount. None of it lands on your calendar. All of it adds up to most of your invoicing time.
What 5 hours a month actually means
Five hours a month is 60 hours a year. That is more than a full working week, every year, spent not on design, not on clients, but on the bookkeeping around getting paid. At even a modest ₹1,000 an hour of billable time, that is ₹60,000 of time a year. For one freelancer. Most of it invisible.
And that is in a good month. The number spikes the moment a payment goes properly late, because late payments do not cost you one follow-up. They cost you the follow-up, the re-check three days later, the awkward second message, the mental load of remembering all of it. The real cost of sending an invoice late compounds on the receiving end too.
What I changed after the month
Three things cut the number down, and none of them were about creating invoices faster.
First, one place to see status. The single biggest time sink was reconciling payments across UPI apps, bank SMS, and memory. Moving every invoice into one view where paid, pending, and overdue are just visible killed most of the 95 minutes.
Second, I stopped drafting follow-ups from scratch. A late-payment nudge does not need to be written fresh every time. I keep a short set of scripts now, the same ones in the late payment follow-up guide, and sending one takes seconds instead of the five minutes I used to spend wording it so it did not sound rude.
Third, I stopped letting reminders depend on me remembering. A due-date reminder that fires on its own removes the entire "did I forget to chase this" loop, which was quietly eating attention all month.
This is exactly the gap I keep building Riffit toward. Creating the invoice from a WhatsApp message is the 30-second part, and that matters. But the reason I track payment status and send automated reminders inside the same tool is that the stopwatch proved where the hours really hide. If you have never measured your own, I would recommend it. Pick a month, note the minutes, and you will probably find your invoicing problem is not the one you think it is. Most of the fixes are downstream of the patterns in the 5 invoicing mistakes Indian freelancers make.
FAQ
In my own one-month tracking experiment, invoicing took about 5 hours across 9 invoices, which works out to roughly 60 hours a year. The striking part was the split: only about 22 minutes went to actually creating invoices, and the remaining 93 percent went to tracking payments, reconciling credits, and following up on late ones.
Written by
Aaqil · Founder, Riffit
Runs 11pixels Design Studio in Bangalore. Built Riffit because invoicing from a laptop in traffic wasn't an option. Writes about invoicing, freelancing, and running a solo business in India.