Enterprise DNA

Instead of Procore

Stop renting Procore. Own your project records.

We build your version around how you run projects and subcontracts, bring your Procore projects across and run it for you. The deadlines that cost head contractors money are counted for you, and the records are yours.

Procore publishes no price. Its own pricing page says it charges an upfront annual fee by product, based on your Annual Construction Volume, and quotes each builder privately.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What you are paying for

Procore is priced by your turnover. Underneath, it is fourteen kinds of record

Procore does not publish a price. Its pricing page says the fee is set each year by product and by your Annual Construction Volume, the dollar value of the work across your projects. Win a bigger job and the bill for looking at your own records goes up. What a head contractor holds is ordinary: projects, cost lines, subcontracts, claims both ways, variations, RFIs, submittals, delays, defects and a site diary.

paid

A fee that follows your turnover

Procore charges an upfront annual fee based on the value of the work you build. Grow, and it grows, whether or not anyone uses more of it. The records underneath do not get more expensive to hold because the project got bigger.

lock

Priced tool by tool

Project management, financials and quality are separate products on the same annual quote. The cost report and the commitments your commercial manager lives in sit in the financial products, on top of the project tools.

schedule

Deadlines you still count yourself

A subcontractor claim lands and the payment schedule clock starts: 20 working days in New Zealand unless the contract says less, 10 business days in NSW, 15 in Queensland, with each Act skipping a different Christmas period. Miss it and the full claim is payable. Here the deadline is counted the day the claim is recorded.

dashboard

Reports that answer the vendor's questions

Logs, dashboards and report builders chart what the vendor chose. The Monday question, which schedules are due this week and which RFIs are holding steel, is a sentence here, not a report hunt across three tools.

extension

An implementation before it earns its keep

A project system that big needs configuring, training and templates before the first project runs on it. Here the first hour is you asking for your own fields, your subcontract terms and your public holidays in plain words.

layers

Your record behind their login

Years of subcontracts, claims, variations and RFIs live inside the vendor's system, reachable one tool export at a time. Here it is a database you own, kept for the whole liability period, with nothing to leave behind when you change tools.

What you get instead

The same projects, over a database you own, with the deadlines counted and the gates kept sharp

The payment clock

Every subcontractor claim answered before the Act's deadline

Record a claim the day it lands and the payment schedule deadline is worked out in working days for the project's state, then it climbs the attention list as the days run out.

  • check New Zealand, New South Wales and Queensland periods built in, each skipping its own Christmas period and your public holidays
  • check A schedule for less than the claim will not go out without the reasons the Acts require, and there is no way to override that
  • check A missed deadline sits at the top of the morning list in plain words: the full amount is now payable, call your adviser
  • check The payment schedule renders in your brand with the claim, the amount, the retention and the reasons, ready for a person to serve

The money

A cost report that counts what you have already promised

The tender becomes the cost plan by cost code. Subcontracts, their approved variations and direct costs land on lines, and forecast final never flatters you.

  • check Committed, pending, actual and forecast final by cost code, with the lines doing the damage named
  • check Instructed variations never priced to the client are valued and aged, loudly, because that is work you may never be paid for
  • check A progress claim stops at the contract plus approved variations, and on an NSW project it will not go without the supporting statement
  • check Forecast margin by project, worst first, at today's numbers

The programme

RFIs, submittals and delays joined up, with the time bar counted

An overdue RFI that holds work is the start of an extension of time claim. The system knows that, and dates the notice the moment the delay is logged.

  • check Every RFI has a due date and a holder, and the ones holding work are flagged
  • check Shop drawings are tracked against the date approval is needed for the order to go in, not just the reviewer's turnaround
  • check Each delay gets its notice date from your head contract's time bar, in working days, and the notice renders with the site diary attached
  • check A compliance check finds any overdue RFI holding work that has no delay logged against it yet

Your data

A database you own, any assistant, and an import that audits as it lands

Runs on a laptop with nothing to set up, or on your own database for the whole company. Works with Claude Code and other AI assistants: the database is what matters, the assistant is just the way in.

  • check Bring each project's commitments, RFIs and submittals across from Procore's own spreadsheet exports, with a test run first
  • check The import is the first audit: subcontractors with no insurance on record and RFIs already overdue are loud the moment it finishes
  • check A subcontractor with expired public liability cannot be signed to a subcontract
  • check Ten compliance rules with their sources written out, from the security of payment Acts to retention trust money, which you can read and change

Make it yours

Design your own Procore replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Procore. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Procore replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Procore data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real runs on a fictional Hamilton head contractor with a distribution centre, a school science block, an office refurbishment in its defects period and a retail tender, and a month going wrong.

forum

Construction Projects for Claude Code

Connected to your own database

What needs a decision across our projects this morning?

Needs a decision (18)

Schedule missed

Record
SCL-703
Who
Voltline Electrical
Where
PRJ-201 Te Rapa Distributio...
Days
1
Detail
96,300 claimed 2026-08-29, schedule was due 2026-09-26 and none went out: the full amou...

Schedule due

Record
SCL-702
Who
Waikato Steel Erectors
Where
PRJ-201 Te Rapa Distributio...
Days
2
Detail
214,600 claimed, payment schedule due 2026-09-29 (2 days): assess it and issue the sche...

Delay notice

Record
EOT-901
Where
PRJ-201 Te Rapa Distributio...
Days
4
Detail
Steel erection held at gridlines E to G awaiting RFI-401: notice due 2026-10-01, 4 days...

Delay notice

Record
EOT-903
Where
PRJ-202 Hillcrest College S...
Days
-12
Detail
Uncharted stormwater main found under the east footings: notice was due 2026-09-15, 12 ...

Claim overdue

Record
PC-604
Who
Te Rapa Logistics Pro...
Where
PRJ-201 Te Rapa Distributio...
Days
6
Detail
935,750 due 2026-09-21, 6 days overdue. The Act gives you remedies; use them

Variation unsubmitted

Record
VAR-502
Who
Te Rapa Logistics Pro...
Where
PRJ-201 Te Rapa Distributio...
Days
34
Detail
Relocate dock leveller pits, instructed 2026-08-24, about 48,500 and never priced to th...

Rfi overdue

Record
RFI-401
Who
Structura Consulting ...
Where
PRJ-201 Te Rapa Distributio...
Days
12
Detail
Mezzanine connection detail at gridline F: answer was due 2026-09-15. It is holding wor...

Rfi overdue

Record
RFI-404
Who
Arcline Architects
Where
PRJ-202 Hillcrest College S...
Days
3
Detail
Fume cupboard exhaust route through level 2 slab: answer was due 2026-09-24

Submittal late

Record
SUB-801
Who
Arcline Architects
Where
PRJ-201 Te Rapa Distributio...
Days
5
Detail
Sprinkler shop drawings, zones A and B: approval was needed by 2026-09-22 for procureme...

Insurance expired

Record
Kaimai Roof...
Who
roofing and cladding
Where
PRJ-201 Te Rapa Distributio...
Days
9
Detail
public liability expired 2026-09-18 on a live subcontract (SC-303): an incident today i...

Ask it anything

Ten questions Procore cannot answer

The free version answers each of these on the demo contractor today. Your version answers them on your projects, and any others you think of.

chat_bubble Which subcontractor claims have a payment schedule due this week, in working days for their state, and which deadline did we already miss?
chat_bubble How much instructed variation work are we carrying that has never been priced to the client, by project and by age?
chat_bubble Which overdue RFIs are holding work on site, and which of those have no delay notice logged against them yet?
chat_bubble Which delay notices are inside their time bar right now, and how many working days are left on each?
chat_bubble Which subcontractors are on a live subcontract today with expired public liability?
chat_bubble Which cost lines are forecast over budget because of subcontract variations we approved but have not recovered from the client?
chat_bubble How much retention are we holding from subcontractors on each New Zealand project, and is there a trust account on record for it?
chat_bubble Which payment schedules did we issue for less than the claim without recording why?
chat_bubble Across every project, what is the client holding in retention from us, and when does each defects period end?
chat_bubble Which projects have gone more than three days without a site diary entry while a delay claim is open on them?

Switching

How to switch from Procore

The move is done project by project: you export three logs from Procore, test the import before anything is written, work through what the import flags, then run the new records alongside Procore for a while before you close the account.

  1. 1

    Export your Procore records

    Procore exports each tool's log per project from its Export menu. Pull the Commitments list, the RFIs log and the Submittals log as CSV, one project at a time, in whatever format your account allows, usually CSV or Excel. If your setup differs, check with Procore support on what your account can export before you start.

  2. 2

    Run a test import first

    Before anything is written to your records, run the import as a test. It reads your three files and shows you what would come across without changing anything. Look over the result, fix anything that looks wrong in the files, and only then run the real import for that project.

  3. 3

    Check what the import flags

    The import doubles as an audit. The moment it finishes, it calls out subcontractors with no insurance on record, commitments with no cost line behind them, and open RFIs already past due. Work through that list before you trust the project. These are gaps Procore was carrying quietly, not something the move created.

  4. 4

    Run both systems side by side

    Keep Procore live for a short period while you work from the new records day to day. Check that claims, RFIs and submittals match what Procore shows for the same project. This is where you catch anything the export missed or the import misread, before Procore is the only place with the true version.

  5. 5

    Switch off Procore

    Once every live project has been brought across, checked against the import flags, and run side by side without surprises, cancel the account. Your records now live in plain database tables you own, readable by any tool, with no export request needed and no annual fee tied to your construction volume.

construction

Where the real effort goes

The three exports only carry commitments, RFIs and submittals. The real work is deciding what else moves, which closed projects' history is worth bringing in, and setting your own payment schedule periods, public holidays and head contract time bars on each project so the clock is right from day one. Enterprise DNA does this mapping and entry when they run the installed version for you.

Not ready for a call?

Get your Procore switch plan by email

We will send you the step-by-step plan for moving your business off Procore, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm run demo, then try /attention and /sub-claims
  3. 3 Use Claude Code, Codex, OpenCode or Cursor on the same records
  4. 4 Test-import a project's Procore commitments, RFIs and submittals, then point it at your own database
Get the free version

Built around your business

We customise it

Scoped to your business

  • check Your cost codes, subcontract terms, schedule periods and public holidays
  • check Your Procore projects brought across and checked against your last cost report
  • check A site screen for your site managers, or a subcontractor claim inbox, if you want one
  • check A different setup when it suits you, such as liquidated damages exposure per project
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with access and backups set up for your team
  • check Your live claims, variations, RFIs and delays entered so the clocks are right from day one
  • check Payment schedule deadlines and delay notices watched for you every morning
  • check Run through Omni by Enterprise DNA, with someone responsible for keeping it working
Talk to Sam

Questions

Instead of Procore, answered

Is it really free? expand_more

Yes. The free version is open source under the MIT licence. Run it anywhere and change anything, with no account with us. Your AI assistant subscription and your own time are separate.

What about drawings and photos? expand_more

The free version does not hold drawings, markups or photos. Keep them where they live today. It holds the questions and decisions about them: the RFI, the answer, the variation it caused and the delay it held. When Enterprise DNA builds your version, a drawings register or photo links can be added.

Does it work out the payment schedule deadline for Australian projects? expand_more

Yes, for New South Wales and Queensland today, alongside New Zealand. Each project records its state, and the deadline is counted in that Act's business days, skipping its Christmas period and the public holidays you enter. Other states can be added in your version. The system counts the days and enforces the gates; whether a particular schedule meets the Act is your call and your adviser's.

Can my site managers use it on site? expand_more

The free version runs where your AI assistant runs, usually a laptop. A site manager can write the diary, raise a defect or log a delay by saying it in plain words. A phone screen for the site team is something Enterprise DNA builds into your version when it earns its keep.

What does the installed version add? expand_more

Your Procore projects brought across, your live claims and delays entered so every deadline is right, your subcontract terms and head contract time bars set per project, your paperwork in your brand, your team shown the commands that matter, and someone to call. It runs alongside everything else Enterprise DNA runs for you.

Stop paying more for your records every time you win bigger work

Spend 30 minutes with Sam on what your project software costs a year, what your team actually uses it for, and which deadlines have cost you money. If it is a fit, we build your version. If not, take the free version and run it yourself.

Construction Projects for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Procore?

Get your version built