One jobsite. One estimate. Every building type it actually has.
PieceWrk turns takeoff quantities into a hierarchy: building types, floors, units, and rooms, each carrying its own count. Every line prices itself off your own rate table, and the whole tree rolls up into one master estimate for the jobsite.
How it works
From counted quantities to one priced total.
- 01
One jobsite, one master estimate
Every jobsite carries exactly one master estimate. Start a second project at that same jobsite and it links to the existing estimate instead of spinning up a new one, so pricing never forks.
- 02
Build the hierarchy the job actually has
Building types, floors, and units come in from the takeoff, each with its own quantity. A floor that repeats three times multiplies everything under it by three, without anyone retyping the floor.
- 03
Price every line off your own rate table
A line item prices itself the moment it’s created, against your company’s service rate, not a generic price book. Override any line by hand when a job calls for it.
- 04
Roll it up into one total
Line items sum into their node, nodes sum into their parent, all the way to one labor total, one material total, and one grand total, markup and contingency included.
Multi-building jobs
A root in the hierarchy is a building type. Quantity is how many get built.
Multifamily and built-to-suit work rarely means one building. The top level of PieceWrk’s estimate hierarchy is a building type, and the quantity on it is the building count, not a floor count or a room count. One estimate can carry as many building types as the job has, each pricing its own floors and units.
That’s different from software built around one building per estimate, where a second building type means faking it with duplicate line items or a second estimate that has to be kept in sync by hand.
What one estimate can hold
- Building Type A×14
- Building Type B×6
- Building Type C×3
Twenty-three buildings, three layouts, one jobsite, one estimate. Each type prices its own floors and units, and the estimate total is the sum of all of them.
Pricing
The number that prices the job is the number that pays the crew.
Line items pull their price from your own service rate table the moment they’re created. That’s the same rate table PieceWrk uses to figure what the crew earns on the same piece of work, so a bid and a payroll run were never two different numbers to begin with.
Once the jobsite’s estimate is priced, it becomes the source for a proposal: markup and contingency get layered on top when it’s time to put a number in front of the customer.
Common questions
- What if my estimate has more than one building?
- That’s the normal case for multifamily and built-to-suit work, not an exception. The top of the hierarchy is a building type, not a single building, and its quantity is how many of that type actually get built. One estimate can carry as many building types as the job has, each with its own floors and units underneath it.
- Does every project need its own estimate?
- No. A jobsite carries exactly one master estimate, and every project at that jobsite prices off it. A second project starting at an address that already has a master estimate links to that estimate instead of getting a new one.
- Where do the prices on each line come from?
- Your own service rate table, not a generic price book. A line item prices itself against your company’s rate the moment it’s created, and you can override any line by hand when a job calls for it.
- What happens to the estimate once it’s priced?
- It becomes the source for a proposal. Markup and contingency get applied on top of the estimate total when it’s time to put a number in front of the customer, and the estimate itself stays the record of what the work actually costs to build.
Bring us a jobsite with more than one building type.
That’s the fastest way to see whether the hierarchy holds together against a job like yours, not just the tidy single-building example.