See which jobs made money.

Trades

Same shop OS. Your jobs.

Pricebook presets and a scorecard for the work you actually bid — not a dispatch board.

• See which plumbing jobs made money.

  Water heater swaps and drain jobs look fine on the invoice. The shop OS shows whether the hours and fittings left anything on the truck.

• See which HVAC jobs made money.

  The bid felt right on the driveway. CostPerJob puts bid, refrigerant, and hours on one card after you close the job.

• See which electrical jobs made money.

  A panel upgrade that ran long still looks like revenue. The shop OS shows the labor burden and material ticket against the bid.

• See which handyman jobs made money.

  A day of small tickets is easy to underprice. The shop OS logs each job so you stop bidding the next deck the same way if this one lost money.

A shop OS built for margin, not for dispatch.

v1 is the money loop: pricebook → estimate → costs → scorecard → history. More shop modules only if they stay anti-dispatch.

Most tools help you get the job and get paid. CostPerJob helps you see if the job made money — without a field-service stack.

1. 01

   Shop OS for jobs and money

   Pricebook, estimates, job costs, scorecards, and history in one system. Not a dispatch board.

2. 02

   Scorecard at the center

   Bid vs actual, margin $, margin %, hours over/under. Not a buried report on a higher plan.

3. 03

   Costing at Free / $29

   See if a job paid without climbing a $149+ field-service ladder.

4. 04

   Closes the invoice-app hole

   Getting paid is solved elsewhere. We close the learning loop: estimate vs actual on the same job.

5. 05

   Anti-bloat

   No scheduling, outbound SMS, payments, or AI estimator in v1. You bid it, you log it, you learn.

6. 06

   Beats the spreadsheet

   Estimate and costs stay on one job so variance isn’t a Sunday-night formula.

7. 07

   Trade-ready presets

   Plumbing, HVAC, electrical, handyman starters.

8. 08

   Honest scope

   We say what we don’t do. Fewer surprises than “everything to run your business.”

Busy shops don’t need another field-service platform. They need a shop OS that shows which jobs made money.

Kit vs platform

A thin scorecard kit — not a field-service platform.

Field-service platforms run the day. Estimate apps get you paid. Spreadsheets work until you’re busy. CostPerJob is the thin shop OS for margin.

Kit vs platform

After the job

Getting the job isn’t the same as knowing if it made money

Tools and apps that help you win work and get paid stop at the invoice. CostPerJob starts where they leave off: bid vs actual, margin $, margin %, hours over/under — on the same job — so the next bid isn’t a guess.

What problem does CostPerJob solve?

Most tools help you get the job and get paid. CostPerJob helps you see if the job made money. That is the shop OS: bid, log costs, read the scorecard before you bid the next one the same way.

What is a shop OS?

A shop OS is the operating system for the shop’s jobs and money. Most tools help you get the job and get paid. CostPerJob helps you see if the job made money. The loop is pricebook, estimate, open job (materials and hours), scorecard, and margin history — for a solo shop or a 1–2 truck crew.

How is a shop OS different from a field-service OS?

Field-service OS runs the day — schedule, SMS, CRM, sometimes payments. Shop OS runs jobs and money — the scorecard. Most tools help you get the job and get paid. CostPerJob helps you see if the job made money. We do not schedule, dispatch, route crews, or send outbound SMS.

What is in v1?

The money loop only: pricebook → estimate (PDF or link) → open job → log materials and hours → scorecard and history. Free includes 3 open jobs. Pro is $29/mo for unlimited. Estimate PDFs may carry a watermark on Free.