Skip to main content

Product

One proposal for everything on the lot.

The customer sees one proposal at one price. Each crew sees its own part, in order, and the margin rolls up by trade at year's end.

One proposal

Paving, curb, sealcoat and striping on one proposal.

The property manager wants one number for the lot. One proposal carries every trade at one contract price, and one invoice comes back. Behind it, each trade is its own part of the job with its own crew, its own work order and its own daily log.

The jobs board: the sales stages left to right with a card for each job, ending at the Won column.

In order

The striping waits on the paving. Nobody has to remember.

The order the work has to happen in is set for you when the customer signs: striping waits until the paving is done; sealcoat waits until new asphalt has cured, 30 days by default; striping over sealcoat waits for the sealcoat. Change the wait or set the cure to zero on a lot where it doesn't apply. A change order on the paving pauses only the paving crew's part until the customer signs.

  • Each crew sees its own part of the job on the board and on the phone
  • Subs confirm their day from a link in their email, without an account

The schedule board

The sealcoating pipeline in settings: its stages, one with a checklist item that blocks and the wait on striping.

Comparing tools? Pavr vs PavementSoft covers this part of the job side by side, with a source and a date on every claim, and the rest of the comparisons are next to it.

One proposal, one invoice

A lot that needs milling, an overlay, new curb along the entrance, sealcoat on the back half and a restripe is one sale. In Pavr it's one proposal at one contract price, and one invoice at the end. The paving crew, the concrete crew and the striping sub each see their own part of the job with their own work order, schedule and daily log, and a change order on one trade pauses only that trade's part until the customer signs.

The order is set for you

When the customer signs, the waits between trades are already there:

  • Striping waits until the paving is done.
  • Sealcoat waits until new asphalt has cured: 30 days by default. Sealcoat over an existing lot doesn't wait.
  • Striping over sealcoat waits until the sealcoat is done.

Remove a wait or set the cure to zero on a lot where it doesn't apply. The board won't let the striping crew be dispatched ahead of the paving without someone deciding to.

Subs on the job

The milling sub or the striping sub gets an email with a link to confirm their day. They don't need an account or a seat. Their invoice posts against the job's costs like any other sub invoice, and their insurance certificate gets a reminder at 30 days, 7 days and expiry.

Who's running it

Every job has a team of four: the salesperson, the project manager, the superintendent and the foreman. One person fills each, and one person can hold several. They show in a strip under the job's name, and a tap on a name picks someone else. Set a default person for each once, under Settings, Team and roles, and new jobs start with them.

What Pavr tells people follows the team. A signed change order goes to the project manager, a rescheduled visit to the superintendent, a dispatched work order to the foreman, and a proposal nobody has signed in a week to the salesperson. If nobody holds that role on the job, the notice goes to the next one down the line: foreman, then superintendent, then project manager, then salesperson, and to the owners if nobody on that line can see the job. Nothing important goes to nobody. The job team routes the news; it never lets anyone see or do more than their role does.

Put one real job through it.

Draw a lot you priced last month, price it with your own numbers, and see what it would have made. Fourteen days, no credit card.

Try it free for 14 days See what it costs