How much time you spend on proposals that never get paid

26 September 2026 · 6 min read

Every hour you spend on a proposal that does not land is paid for by the projects that do. Most freelancers never see that number, because proposal work is scattered across an inquiry email, a call, a draft, a revised estimate and three follow-ups. To find it, measure one month: keep a list of every proposal, note the time each one took using a record of your Mac day, then divide the total by the proposals you won.

Why proposal time hides

Proposal work has no client to bill, so nothing forces you to record it. It also rarely happens in one sitting. You read an inquiry between two billable tasks, reply with questions, take a call two days later, write a draft on Thursday evening and send a revised version the following week.

Each piece is short and feels like admin. Added together, a proposal for a mid-sized project can take most of a working day, and you might write several a month. If you never measure it, it quietly lowers your real hourly rate.

What counts as proposal time

Draw the line clearly before you measure, or the number will mean nothing. Count everything from the first inquiry to the signed agreement:

Reading the inquiry and writing the first reply.
Discovery calls and the notes after them.
Research on the client, their current site or product, and their competitors.
Estimating hours and building the price.
Writing, formatting and proofreading the proposal itself.
Revisions, follow-up emails and contract back-and-forth before signing.

Once the agreement is signed, the time belongs to the project. If the proposal is declined or the client goes quiet, the time belongs to your overhead.

Measuring a month of it on a Mac

You do not need to start a timer for every inquiry, and you will not keep it up if you try. An automatic record of the day works better.

Punchcard is a Mac menu bar app that notices which app is in front during your day, by app name only, and at the closing time you set it prints a receipt: the top five apps with time per line, the rest as MISC, and a day total. It needs no macOS permissions to do this.

A method for one month:

Keep a list of proposals: client, date of inquiry, date sent, outcome. A spreadsheet is fine.
On any day with proposal work, glance at the receipt when it prints. If you wrote the proposal in Pages that evening and Pages shows 1h 20m, write 80 minutes next to that proposal.
On days where proposal writing and client work used the same app, export the CSV. It has one row per session, with start and end times, so you can pick out the evening session that was the proposal.
Add calls and meetings from your calendar, since time away from the Mac does not appear on the record.
At the end of the month, total the minutes per proposal.

Punchcard cannot do the sorting for you. It has no per-project or per-client tracking, and it never records document names or window titles, so it cannot tell a proposal from a project report in the same app. It gives you the when and the which app. You bring the what.

Doing the math

With a month of proposals, three numbers matter: total proposal hours, proposals sent, and proposals won.

Proposal hours per win is total proposal hours divided by wins. As an illustration with round numbers: if you spent 14 hours on six proposals and won two, each project you won carried seven hours of unpaid work behind it.

Effective rate is what you actually earn per hour once that time is included. If a won project bills 40 hours, it really took 47 hours of your time. Your effective rate is your hourly rate multiplied by 40 and divided by 47.

That second number is the one to bring to your next pricing decision. Freelancers: the difference between hours open and hours billed covers the wider gap between time worked and time invoiced, and the time audit to do before raising your rates shows how to use numbers like these in a rate conversation.

Spending less time without winning less

Once you can see the number, you can change it. Some approaches that do not depend on writing better proposals:

Qualify before you write. A short list of questions, or a fifteen-minute call, filters out inquiries with no budget or no real start date before you invest an evening.
Build a template. Your process, terms, timeline format and past work do not change between proposals. Only the scope and price do.
Match effort to size. A small job deserves a one-page reply, not a twelve-page document.
Charge for discovery on large projects. When scoping itself is substantial work, offering it as a paid first phase turns unpaid hours into billable ones.
Cap revisions before signing. One revised proposal is reasonable. A third usually means the scope is not settled, and more writing will not settle it.

Measure a second month after changing something. If the hours per win drop and the win count holds, the change worked.

Questions

Should proposal time be built into my hourly rate? It already is, whether you planned it or not: it comes out of the hours you bill. Measuring it tells you how much, so you can price with the real figure instead of absorbing it.

Can Punchcard tag time as proposal work? No. It has no projects, tags or timers. Use the receipt and CSV to find the sessions, and keep the labels in your own list.

What about proposals I write on my phone? Punchcard records your Mac only and has no iPhone app. Add phone and in-person time from your calendar or messages.