"Retainer Invoices That Remind You to Bill (Instead of Billing Themselves)"

#The retainer I forgot three times

I had a client on a monthly retainer, the kind that should be the easiest invoice of the month. Same hours, same rate, same client, same fifteenth of the month. No scope to estimate. No new line items to negotiate. A rubber stamp with a date on it.

I forgot to invoice them three months in a row.

Not because I did not care. Because the retainer invoice lived in a different part of my brain than the project work. The project work had a timer and a deadline and a client checking in. The retainer was background noise, a thing I would "get to at month end," and month end always had something louder in it. By the time I remembered, it was the twentieth, the client was politely confused, and I was apologizing for my own disorganization on a task that should have taken thirty seconds.

I am telling you this because it happens to almost every consultant I talk to. Retainers are the most reliable income a small agency has, and they are also the invoice everyone forgets, because there is nothing to trigger the memory. No new project kicks off. No estimate gets approved. The work just happens, month after month, and the invoice quietly does not.

#What the honest fix looks like

I want to be straight with you about what owntime does here and what it does not, because this is the kind of feature that is easy to oversell.

Here is the workflow that actually works: you track the retainer's hours through the month the same way you track any other time. At month end, you open the invoice view, select the unbilled entries for that client, group them by project or day, add your tax, and export a PDF with your letterhead and terms. The invoice is built from your tracked time, not from a guess. That part is real, and it takes about a minute.

What makes the retainer case better is a recurring template. You set up a retainer as a recurring line: the client, the expected amount, the cadence (usually monthly), and the next run date. That template lives in your Recurring Invoices view. It does not generate a draft by itself. What it does is give you a visible schedule of what is supposed to bill and when, so "did I invoice Acme this month?" stops being a memory question and starts being a glance at a list.

I am telling you this plainly because I could have written a post called "retainers that bill themselves." The honest version is "retainers that remind you to bill." The reminder is real. The billing still needs you.

#Why I did not build auto-billing

I thought about building a retainer that generates and sends its own invoice on a date. I decided not for a reason that matters: I have been the client on the receiving end of a machine-sent invoice that had a mistake in it, and the experience is degrading. The wrong amount, the wrong date, the wrong line items, all arriving in your inbox with no human having looked at it. It erodes trust faster than a late invoice.

So the line I drew is this: the app reminds you, and the human sends. The recurring template tells you what should bill and when. You open the invoice view, you confirm the numbers against your tracked time, and you press send. The send step is the last honest checkpoint, and I am keeping it.

I will also admit a practical reason. Building a reliable auto-scheduler means building a daemon or a background process, and a background process means a server or at least a running service, and that is the exact architecture I am trying to avoid. The recurring template works with the app you already open. It does not need anything running while you sleep. That constraint is the whole product.

#The monthly retainer workflow, step by step

If you have a retainer client, here is the honest workflow in owntime.

1. Track the work normally. Log hours against the retainer's client and project through the month. The timer and the manual entries work the same as for any other work.
2. Set up a recurring template. In the Recurring Invoices view, add a template for that client with the expected amount, the cadence, and the next run date. This is your reminder, not your invoice.
3. When the run date arrives, open the invoice view. Select the unbilled entries for that client. Group them by project or day. Add tax. The draft PDF has your letterhead, your invoice number, your terms.
4. Confirm and send. Check the total against what you expected. If the hours came in high or low, you see it before the client does. Press send.

That is the whole flow. The recurring template makes Step 3 happen on time instead of three weeks late. The human makes sure Step 4 goes out right.

#The honest limits

A recurring retainer template in owntime is a flat amount you expect to bill, on a cadence you set, with a next run date. It is not a live calculation of tracked hours, and it is not a draft that generates itself. If you bill by the hour and your retainer hours vary month to month, the template is a reminder to check, and the invoice view is where you see what you actually tracked.

The template is also not a contract. It does not enforce the retainer, it does not notify the client, and it does not do anything you do not open the app to see. It is a schedule you can trust, and that is the right amount of automation for a job that should have a human on the send side.

#The month-end test

If you have a retainer client, here is the test. Set up a recurring template with the cadence and the next run date. Let the date arrive. Open the Recurring Invoices view and see the template waiting. Then open the invoice view, build the draft from your tracked hours, and send it.

If the template kept you from forgetting, and the invoice view let you build the draft in a minute, you have the whole feature. It is not magic. It is a reminder that works and a draft that is right, and for a monthly retainer that is usually enough.

Try owntime free for 14 days · See pricing, one time · Read the honest feature roadmap