Conresti Construct
Five job sites, two people in the back office. The system keeps up, they can't.
Material approval (MAF), procurement and the as-built file, digitised on your site process. For MEP contractors and general contractors running 5+ sites at once.
Book a conversationIt works with what you already have - Charisma, BITSoftware or just Excel and email. You migrate nothing, you change nothing in accounting.
Material approval, procurement and the as-built file, on your process
Submittals that run themselves
Material approval is generated from the product library, not rewritten.
Procurement without bottlenecks
The status of every item, visible at any time.
Documentation that writes itself
The as-built file is ready at handover, not reconstructed.
See how it works
How a material approval file is generated and how it moves through the approval circuit
Three flows from Conresti Construct, on demo data: build the MAF file from the product library, submit it for approval and track the decision, then turn the bill of quantities into a list of files. Click, type, use ⌘K.
| MAF | Discipline | Components | AI | Status | Package | With client | Date |
|---|---|---|---|---|---|---|---|
| ECT 015Car park distribution board | ECT | 3 | 7 analysed | Generated | — | — | 15 Aug |
| ECT 014Outdoor luminaires | ECT | 2 | 5 analysed | Generated | — | — | 13 Aug |
| ECT 013Emergency lighting | ECT | 1 | 2 analysed | Draft | — | — | 10 Aug |
| ECT 012LED office luminaires | ECT | 3 | 8 analysed | Documents received | — | — | 29 Jul |
| ECT 011N2XH 5×16 cable | ECT | 2 | 5 analysed | Rejected | P1 | — | 19 Jul |
| ECT 010Main distribution board | ECT | 3 | 8 analysed | Approved | P1 | — | 9 Jul |
How it looks today
Three moments you'll recognise
Material approval, the document library and the as-built file are one process, done by hand by two people in the back office. This is what it looks like when the volume grows.
- 01
The material approval file sits on a desk for two weeks
The MAF is assembled by hand from data sheets, declarations of performance and technical approvals, then waits at the site supervisor and the designer. Procurement waits for it, and the site waits for procurement.
- 02
The same documents are searched from scratch on every project
Declarations of performance, CE certificates and technical approvals already exist in the company, but not in a document library: they are requested again from suppliers, for every file, on every site.
- 03
When the back-office person leaves, the process leaves with them
The as-built file is reconstructed at handover from e-mails and folders. The person who knew where every approval and every revision was has left, and the history of the files left with them.
How it looks in the system
In the order of the real site workflow
The material approval file is generated from the product library: data sheets, declarations of performance and technical approvals are analysed with AI and go into the MAF without being rewritten. The third-party approval circuit is visible at any time, with a status per item and per approver; a rejection becomes a revision with the same number.
The document library fills up once and is reused across all projects, and the as-built file is written as you go, not reconstructed at handover. Quoting starts from the bill of quantities, not from scratch.
processing time on material approval packets, at an MEP contractor with over 100 employees.
Objections
What you tell us in the first five minutes
"We already have an ERP" / "We don't have an ERP"
We hold the process between the office and the site; accounting stays where it is, whether that's Charisma or a simple program.
"Our processes are chaotic"
Mapping the process is the first stage of the implementation, not a precondition.
"We don't have an IT person"
You don't need one; the system is run by the back-office people already working in it.
“It’s worked fine for 15 years”
Yes - at today’s volume. At the next site, “it works fine” needs one more back-office hire. Whom the market no longer has.
"How much does it cost"
Fixed price per scope, set after mapping. No per-user licences.
It's for
- General contractors who approve submittals and coordinate dozens of subcontractors.
- Specialist contractors - MEP, façades, structure - with 5+ concurrent sites and 2-3 back-office people.
- Niche subcontractors losing contracts on quoting speed.
Not for
- Firms with 1-2 job sites a year.
- Property developers and owners.
- Anyone looking for an ERP.
Start from the workflow that hurts most.
Book a conversationNDA → mapping → prototype on your process → pilot on one workflow, fixed price, success criterion set together.