Give your project team one brain for contracts, subs, and change orders.
The Prana Brain reads your contracts, specs, sub files, and change-order history, and answers from those documents with the source cited. Project management tools and the ERP stay connected. A PM or controller approves every draft before anything is sent or posted.
The problem
The job file, the project tools, and the ERP do not share one memory.
Contracts and change orders live in folders and email. Status lives in the project tools. Cost codes live in the ERP. The next write-up still starts from scratch.
What slows the job
- The last similar change order is a search through email and shared drives.
- Sub files and specs are not next to the draft a PM is writing.
- Cost codes in the ERP do not match the code on the paperwork.
- Routine follow-ups get retyped because the last reply is hard to find.
What this closes
- The Brain answers from the company's documents and cites the source file.
- Change order, RFI, and sub follow-up drafts wait for a person.
- Project tools show status. The ERP stays the system of record.
- An API built in the integration lets the Brain read past jobs and cost codes.
What we build
The Brain, the project tools, and the ERP, scoped as one integration.
We connect what you already run. The Brain is the project memory. The ERP API is part of the build, not a connector we already ship.
What the build includes
2-week discovery
We name the documents and the approval gate before we write a workflow.
The audit is a map of this stack: the files, the project tools, the ERP, and the drafts a person still writes by hand.
Inventory
We list the project management tools, the ERP, and the document sets the team already keeps. We name who owns each login and each file share.
Trace
We walk one change order from the request to the signed file and the cost code. We mark every place a person retypes or hunts for the last similar job.
Cite
We name the documents the Brain may answer from, and the citation the answer must carry. We write which drafts stop for a PM or controller before anything is sent or posted.
Find
We name the first workflow to build, including any ERP API the lookback needs. We write what stays in the project tools and the ERP.
Proof
One change order, as an example.
A PM asks how a similar change was priced on a past job. The Brain answers from that company's change-order files and cites the document. It drafts the write-up. Nothing is sent until the PM approves it.
The integration includes an API against the contractor's ERP so the Brain can look at past jobs and cost codes, compare the new change to similar work, and flag a mismatch. A weekly job-cost pack is a custom build on top of that, not a product feature already in the catalog. The ERP stays the system of record.
FAQ
Common questions
Two weeks. We inventory the project management tools, the ERP, and the document sets, then trace one change order from the request to the cost code. You get the map and the build plan for your stack.
Project management tools and the ERP you already run, plus the contracts, specs, and change-order files the team keeps. Discovery names which ones are in scope. We do not ask you to replace the ERP.
No. It drafts change order write-ups, RFI replies, and subcontractor follow-ups. A PM or controller approves every draft before anything is sent or posted.
Least-privilege access. Credentials stay in your control. We sign an NDA and work inside your IT requirements. We do not copy production logins into a shared vault we own.
No. The ERP stays the system of record. If the Brain needs past jobs and cost codes, we build an API against your ERP as part of the integration. That API is not a connector we already ship.
Other use cases
What else we build
Ready to map the project memory?
Book a call. We will walk the documents, the project tools, and the ERP, and name the first build.
Book a call See platform trustAn example build on the hosted Prana IQ platform.