A client paying $65 a serve reads fine right up until the third attempt, the bad address that needs skip tracing, and the 20-mile round trip come out of it. This free calculator finds real net profit for one job, then lets you compare two or three clients' fee schedules by what they actually pay per hour — not their headline base fee.
Price one job
Your job inputs above are saved locally in this browser so you don't retype them next time. A shareable link puts the same numbers in the URL fragment — nothing is uploaded. Your client comparison rows below are never saved.
Profit for this job
$0.00
Gross revenue
Extra-attempt revenue
Rush + skip-trace revenue
Mileage revenue
Vehicle cost
Profit margin
Break-even base fee
This is a planning floor from the numbers you typed, not an audited statement. It does not determine whether service was validly effected, whether you are licensed or bonded to serve process in a jurisdiction, or whether an affidavit of service will hold up in court.
Compare clients
For each client's fee schedule, run the same job through the calculator above with that client's numbers and enter the resulting net profit here. Blank or zero rows are ignored. Nothing you type here is saved or uploaded — refreshing the page clears it.
Client / firm
Net profit ($)
Clients compared
Best client
Worst client
Spread between them
Private by default
Everything on this page runs in your browser and nothing is ever uploaded. Your job inputs (attempts, rush/skip-trace flags, mileage, time, costs) are saved locally on this device so you don't retype them next time — Reset to defaults clears them, and Copy shareable link puts them in a URL fragment your browser never sends anywhere. Your client comparison rows are a different promise: they are never saved anywhere, and closing or refreshing the tab clears them. There is no account. We count only anonymous local feature events (job-priced, clients-compared, link-copied, reset) so we can tell whether the calculator gets used — no client names, fees, or job figures are recorded, and Do Not Track / Global Privacy Control turn it off automatically.
Fee looks fine on paper — is it actually worth it?
Why does a flat per-serve fee not tell me whether a job is worth taking?
Because the flat fee is priced for the ordinary case -- a good address, one or two attempts, a short drive. A defendant who is hard to find adds attempts and time the base fee never covered, a bad address can mean skip tracing before you can even attempt service, and a long drive burns real fuel and vehicle wear whether or not the client's mileage add-on covers all of it. The same headline fee can be a great job or a losing one depending on those four things.
Does this tool tell me whether service was properly effected or how to serve someone who is avoiding service?
No. This calculator only prices your own job economics from numbers you supply. It does not determine whether service was validly effected under any state's rules of civil procedure, whether you are licensed, bonded, or registered to serve process in a given jurisdiction, or whether an affidavit of service will hold up in court -- verify all of that independently.
Why does vehicle cost count for every mile driven, but mileage revenue only for miles beyond what is included?
Because that is what actually happens on the job: fuel and wear cost you money for every mile you drive, but a client's mileage add-on typically only pays once you are past the miles their base fee already covers. Counting only the billed miles as a cost is the most common way a job's real profit gets overstated.
Does anything about my job or client fee schedules get uploaded?
No. Every field on this page runs in your browser only. Nothing is sent to a server, there is no account, and the client fee-schedule rows you type into the comparison table are never saved anywhere -- they exist only in the page while it is open. The job inputs above are different: those are saved locally on this device, so you don't retype them, and a shareable link can carry them to another device. Usage counting only tallies anonymous feature events, and you can turn it off with the button above.