PieceWrkPieceWrk
Private beta

One offer, however many jobsites it takes.

A proposal draws one or more jobsite estimates into a single priced offer. A house is the one-jobsite case; a multi-building deal for the same customer is the same offer with more jobsites in it. Accept it and the offer freezes into a contract.

How it works

From estimate to signed contract.

  1. 01

    Draw in the jobsite estimate

    Start from one jobsite’s master estimate. When a plan set covers more than one building for the same customer, add its sibling jobsites into the same proposal instead of writing a second one.

  2. 02

    Set the offer’s markup and contingency

    Percentages seed from the estimate’s own defaults and stay editable while the proposal is still a draft, then lock the moment it goes out.

  3. 03

    Send it, or hand it over yourself

    Email it through the portal link when your company has customer email turned on, or mark it delivered yourself and keep the same record either way.

  4. 04

    A signature mints the contract

    Accepting freezes the offer into a contract, writes its schedule of values, and locks the source estimate so the numbers can’t move under a signed deal.

The seam

Jobsites combine in exactly one place.

A takeoff, a plan set, and a master estimate all belong to one jobsite each. The proposal is the only step where more than one jobsite comes together: pick the primary jobsite’s estimate, then add any sibling jobsites for the same customer that the same offer covers.

Accept the proposal and the contract spans the exact same jobsites it was built from, nothing more. Jobsites never fan out on their own: if a single plan set genuinely covers more than one building, splitting it into separate jobsites is a call for a person to make, not something the system decides for you.

Single-family isn’t a special case

  • One jobsite in, one jobsite out. A single house proposal works exactly the way a bigger deal does, just with a list of one.
  • Add a sibling jobsite and the offer recalculates as one priced total, not a stitched-together set of separate documents.
  • The markup and contingency you set apply to the whole offer, across every jobsite it spans.

However many jobsites a deal touches, it is still one proposal, one accept, and one contract.

Sending it

What actually happens when you hit send.

The line items were already frozen onto the proposal the moment it was built. Sending mints (or reuses) a token-gated customer portal link for that proposal as it stands, no account or password required on their end. Whether that link goes out by email depends on a company-level setting.

Customer email turned on

The proposal emails from a connected mailbox with the portal link inside it, and the send is logged with who it went to and when. Resending, or sending to a second recipient, keeps adding to that same log without moving the proposal backward.

Customer email off (today’s default)

Outbound customer email is off by default for every company until it’s deliberately turned on. Trying to send is refused with the reason why, nothing is emailed. You hand the proposal over yourself, then mark it delivered so the status and the delivery record still move forward.

The customer’s side

Two moments: accepting the deal, and signing it.

A homeowner holding the portal link can approve the proposal there, typed name and timestamp recorded, which is what mints the contract. From there they can also execute the contract itself: a typed or drawn signature, an ESIGN/UETA consent record, and a SHA-256 hash of the exact PDF they signed, with the IP address and timestamp captured to an audit trail alongside it.

When your customer is a builder or GC instead of a homeowner, that same link lets them view the offer, but signing authority stays with you: you record the acceptance the same way you would a signature taken on paper.

Common questions

Does a single-family job work differently from a multi-building deal?
No. A proposal always draws from one or more jobsite estimates. A single house is the everyday case where there happens to be one jobsite, not a separate mode. A four-building deal for the same customer adds three more jobsites into that same offer.
What actually happens when I hit send?
PieceWrk mints (or reuses) a token-gated customer portal link for the proposal and emails it, only if your company has turned on outbound customer email. That is off by default. If it is not on yet, sending is refused with the reason why, and you can hand the proposal over yourself and mark it delivered so the record still advances.
Does my customer need an account to accept it?
No. The portal link needs no login. A homeowner can approve the proposal there, which mints the contract, and can go on to sign it with a typed or drawn signature captured under an ESIGN/UETA consent record with a hash of the exact document. When your customer is a builder or GC rather than a homeowner, that link lets them view the offer, but signing goes through you, the same as a paper signature taken in person.
Where does a change order’s price come from?
A change order raised against a signed contract is priced the same way the original offer was: its own line items, its own markup and contingency, not a bare cost delta. It gets the contract’s next stable number, and when it is raised off a revised plan set it cites the exact revision it came from.

After signature

A change order carries the same discipline.

Once a contract exists for a jobsite, a change order against it is its own small proposal: its own line items, its own markup and contingency, priced the way the original offer was rather than a bare add or subtract. It gets the contract’s next stable number, so it reads as CO #1, CO #2, and on, in the order they were raised.

Raise a change order off a revised plan set and it cites the exact revision it came from, so a dispute over whether something was in the original drawings has a document to point at instead of a memory of a conversation. That citation travels with change orders raised this way, through the proposal against a signed contract.

Private beta

Bring us a deal that spans more than one jobsite.

That’s the one where seeing your estimates come together into a single offer matters most.