Billable sessions in, invoice-ready decimals out. Add up your tracked time and convert it without a spreadsheet.
Invoices want 6.75 hours; your notes say 6h 45m. That conversion - and adding up a week of scattered sessions - is exactly where billing errors creep in. TCalc sums real durations and flips the total to decimal in one tap.
No project-management suite needed: type your sessions as an expression and bill the result.
Freelance billing has one recurring failure: time is tracked in scattered fragments and invoiced as a single number, and the addition happens by hand at the end of the month when attention is lowest. Forty minutes here and two hours ten there add up to a figure that is easy to get wrong by a quarter-hour, and a quarter-hour every week is roughly a day of unbilled work a year.
Adding the fragments as real durations and converting the total to decimal hours at the end gives a number that reconciles against a rate without a second step. The conversion is minutes over sixty - 6h 20m is 6.33 hours, not 6.20 - and getting that wrong biases every invoice in the same direction.
A day assembled from four tracked fragments.
The same total in decimal hours for the invoice line.
A month of tracked time, ready to multiply by a rate.
Day rates and hourly rates are not interchangeable without a stated day length. A day rate quoted against eight hours is a different deal from the same rate against ten, and the difference only shows up once the work overruns. Converting between the two explicitly - dividing the day rate by the agreed hours - makes the comparison honest before the contract is signed rather than after.
The same arithmetic sizes a fixed-price quote. Estimate the effort in hours, convert to days at your agreed day length, and you have both the price and the delivery window, which are the two things the client is going to ask about anyway.
A full week at an eight-hour day - the baseline a day rate should be quoted against.
A sixty-four-hour project as eight billable days.
Eight working days from now, as a date to put in the proposal.
A freelance year is not 2,080 hours of billable capacity. Take out leave, public holidays, admin, sales and the gaps between engagements and the honest figure is substantially lower - and it is that lower figure a rate has to cover. Running the subtraction once a year is the difference between a rate that sustains the business and one that merely looks competitive.
The same logic applies at the week level. If sixty per cent utilisation is realistic, a forty-hour week yields twenty-four billable hours, and any plan built on forty is going to fail quietly rather than loudly.
A nominal year less twenty leave days and ten public holidays.
A realistic billable week at sixty per cent utilisation.
Six calls at 45 minutes - multiply instead of adding six times.
Tracked time → invoice decimal, one tap.
Morning session plus afternoon session.
A project phase converted to total billable hours.
Divide the minutes by 60: 6h 45m = 6.75 hours. TCalc does it with one tap on the output format - enter the duration, switch to hours, invoice the number.
Chain them in one expression: 2h 45m + 1h 30m + 45m... TCalc carries minutes into hours correctly, and cloud sync keeps the history on all your devices.
Yes - Pro custom buttons let you define e.g. Call = 45m or Sprint = 2h 30m, so a day of work is a few taps.