PieceWrk for builders & gcs
For builders who are tired of chasing finishes.
Finish decisions and allowance overruns are where custom jobs lose their schedule and their margin. PieceWrk keeps selections, contracts, change orders, and the customer conversation on one record, without putting your numbers in front of the wrong people.
The problem
Where custom builds go sideways
- Selections living across email threads, a shared spreadsheet, and three showroom quotes nobody can reconcile.
- Allowance overruns discovered at closeout instead of the week they happened.
- Change orders argued from memory because nothing records which plan revision the original price assumed.
- Not being able to put the homeowner, the sub, and the supplier in one system without exposing your markup.
What PieceWrk does about it
What changes
Selections your customer can actually use
One token-gated link (no account, no password) carrying the live selection list, the allowance-versus-spent position, the schedule, and progress photos.
Your margin stays yours
The supplier order, the install labour, your markup, and the customer price are separate values on the same record. Each party is served only what they’re entitled to, enforced in the database.
Contracts signed in the browser
Accepted proposals become a contract signed on the spot: ESIGN/UETA consent, a hash of the signed document, IP and timestamp on an audit trail. No separate e-sign subscription.
Change orders that cite the plans
A change raised off a revised plan set cites the specific revision it came from, so the conversation is about the document rather than about who remembers what.
Every capability above is running in production today. See the full list, including what isn’t built yet.
The job to bring us is the one with the messy allowance schedule. That’s where the difference shows up fastest.
Also built for