Pricing
Two taps and a slider. Then one picture of what the paperwork costs you now, and what it costs with FieldPE on it.
What do you build?sets the size of a typical change
Who chases the paperwork today?decides what we compare against
How many jobs are running?you only pay for the ones switched on
One change event nobody wrote up. It never shows as a mistake — it shows as a job that came in thin.
A typical unpriced change on : . Put your own number in.
What you get
Each one reads your Procore project, cites what it drafted from, and waits for a person before anything files.
A sub emails a question. FieldPE reads it, finds the drawing sheet and spec section it actually concerns, and drafts the RFI with the passages it relied on shown beside it.
“Which detail governs at grid line 7?” becomes a filed RFI, cited, in about a minute.
Reviewed line by line against the spec section it belongs to, with the findings written out — what conforms, what deviates, and exactly where the spec says so.
Catches the substitution buried on page 40 of a product data package.
Change events opened, pricing requested from the right subs, replies read as they land, and the change order assembled. Plus a watcher that flags an RFI answer carrying a cost.
The answer that says “provide additional blocking” becomes a change event, not a surprise.
Trade scopes drafted from the project's own drawings and specs, in your standard provisions and your language, ready to attach to a subcontract.
Twenty trades, drafted from the set, in an afternoon rather than a fortnight.
Pricing
Unlimited people on every tier. Switch a job off when it closes and it stops billing.
How billing works
A job you have switched on in FieldPE. One you have under contract but have not switched on costs nothing.
It stops billing from the next period. Construction is lumpy; the invoice should be too.
The PM, the assistant PE, the intern chasing submittals. Adding somebody is never a decision you have to make.
No setup fee, no annual lock. Cancel whenever, and your records stay exportable either way.
On every plan
Grounding, human approval and tenant isolation are how the product works, not a tier. The cheapest plan is not the risky one.
Every draft cites the drawing sheet or spec section it came from, so a reviewer can check it in seconds instead of taking it on faith.
FieldPE drafts straight into Procore; issuing it to the architect, owner or sub is a person's decision on every tier.
Never used to train a model. Isolated per company at the database level. Exportable and deletable on request.
Questions
The fastest way to judge this is to point it at a live project and read what it drafts.