Bill rate calculator

Zero or negative billable hours make the rate undefined, so the task fails with invalid_input and is not billed.

How the hourly bill rate is computed from costs, hours, and margin

Start with annual_costs: salary or owner draw, payroll taxes, benefits, rent, software, insurance, contractors, and every other operating line you must recover from client work. Pair that total with billable_hours — the hours you can actually put on an invoice, not the hours you sit at a desk. The third input is profit_margin, a percent of required revenue, not a fraction and not a markup on cost.

Input contract, response shape, and error behaviour

Example: eighty thousand of annual costs, twelve hundred billable hours, and a twenty-five percent margin yield a required revenue of one hundred six thousand six hundred sixty-six point six seven, a profit amount of twenty-six thousand six hundred sixty-six point six seven, a break-even rate of sixty-six point six seven, and an hourly bill rate of eighty-eight point eight nine. POST a JSON body with three required finite numbers. annual_costs is the yearly cost stack to recover, in one currency unit; aliases costs, annual_cost, and overhead map to the same field. billable_hours is the count of hours you can invoice in that same year; aliases hours and billable are accepted so a utilization sheet can keep its column names. profit_margin is the desired profit margin as a percent of required revenue — twenty-five means twenty-five percent, not zero point two five — and aliases margin and margin_percent are accepted. Each numeric field may arrive as a JSON number or a numeric string. Missing fields, empty strings, and non-finite values fail with invalid_input naming the field. If annual_costs is negative the request fails. If profit_margin is negative or is greater than or equal to one hundred the request fails, because a one-hundred-percent margin would divide by zero. Those failures are not billed. On success the body echoes annual_costs, billable_hours, and profit_margin, then reports required_revenue, profit_amount, break_even_rate, and hourly_rate, all money figures rounded half-up to cents. Pair the JSON with your own utilization model if you need to derive billable hours from a roster; this endpoint prices a given hour count, it does not forecast utilization.

Where a bill rate calculator earns its keep

Independent consultants use a bill rate calculator at the start of a year to turn a cost stack and an honest billable-hour forecast into a floor they can quote without underpricing the calendar. Agencies and studios re-run the same three fields when utilization slips or overhead jumps, then publish a new shop rate before proposals go out below cost. Failed validation does not consume balance. Finance partners drop annual_costs from the budget, billable_hours from the staffing plan, and profit_margin from the target, and they pin hourly_rate in a pricing sheet so every estimator shares one number. This is a different search and a different job from converting a salary into an equivalent wage: salary-to-hourly divides pay by scheduled hours, while a bill rate lifts costs by a profit margin and divides by invoiceable hours. Keep billable_hours strictly positive, keep profit_margin below one hundred, pin the rounded currency fields in tests, and you get a reproducible hourly bill rate for rate cards, LMS plugins, and edge workers without standing up a professional-services engine of your own.