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 conversation
No migrations

It 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.

How it looks today

Three moments you'll recognise

  1. 01

    The packet sits on a desk for two weeks, and procurement waits on it.

  2. 02

    The same declarations of performance are hunted down from scratch on every project.

  3. 03

    When the back-office person who knew it all leaves, the process leaves with them.

How it looks in the system

In the order of the real site workflow

  1. 01

    The material approval packet - runs itself

    Generated from the product library, not rewritten.

  2. 02

    The third-party approval flow - visible any time

    Status per item and per approver.

  3. 03

    The document library - fills up once

    Declarations of performance and technical agreements reused across all projects.

  4. 04

    The as-built file - written as you go

    Not reconstructed at handover.

  5. 05

    Quoting - starts from the bill of quantities

    Not from scratch.

−70%

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 conversation

NDA → mapping → prototype on your process → pilot on one workflow, fixed price, success criterion set together.