Instead of Jobpac Connect
Stop renting Jobpac Connect for your job record. Own how your contracts are costed and claimed.
Enterprise DNA builds your version around your contract types, cost codes and subcontract terms, brings your Jobpac Connect jobs across, and runs it for you. Payroll and the ledger stay where they are.
Jobpac Connect publishes no price. It is quoted privately after an enquiry and a demo.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the quote covers
An ERP priced behind a demo, for a job record that is mostly plain rows
BuildingPoint's page for Jobpac Connect lists forecasting, margin monitoring, cash flow, dashboards and mobile timesheets, and the only way to a price is Enquire Now or Get My Demo. Strip away the accounting and payroll, and what a contractor uses every week is ordinary: jobs, cost codes, budgets, orders, costs, variations, claims, subcontractors, retentions and a diary.
A price you only hear on a call
No plans, no figures on the vendor's page. You find out what the software costs after a demo, without a public number to hold it against.
One suite carrying everything at once
Accounting, payroll, HR, forecasting and project control are sold as one integrated system. The job record your project managers use daily rides along with modules the site team never opens.
Dashboards set up for each role
Role-based landing pages and clickable dashboards show what was configured for that role. The question a director asks on a Thursday, about one job or one subcontractor, still means finding the right report.
Claims handled in another product
Subcontract claims can be run through a separate claims tool connected to Jobpac Connect, with the approved invoice posted back in. That is a second system to pay for and keep in step.
Changes inside someone else's product
A new field, a different approval rule or a report in your own layout is configuration work inside someone else's product. In your own system it is a sentence to Claude and a change you can read.
Years of contracts behind a login
Defects, disputes and retention releases arrive long after practical completion. If every job's history lives in the vendor's system, reaching it depends on your licence. In your own database it is simply there.
What you get instead
The project side of the ERP, on a record your company keeps
Margin
Cost to complete that counts what is already ordered
Each job's budget sits by cost code, every order holds money against its line the day it is raised, and costs land against the same lines.
- check Committed orders count against the budget straight away, so no line looks healthy while an invoice is still to come
- check A line that goes over shows the overrun at once, and you record whether it was scope, rate or waste
- check Every job ranked by forecast margin, weakest first, using contract plus approved variations against cost and commitments
- check Ask which contract type or client has made money across every job you have run, a question no role dashboard was set up for
Head contract
Progress claims held to the contract value
Each claim carries an amount and a due date, and the system checks it before it goes anywhere.
- check A claim that would take the job past the contract plus approved variations is refused, and there is no way to override it
- check Unpaid claims rise to the top of the morning list with the days overdue, and a firm chaser is drafted for a person to send
- check Claim paperwork renders in your brand with the position to date and every approved variation listed
- check A job where cost keeps landing with nothing claimed for 30 days is called out before it strains cash flow
Subcontractors
Variations in writing, cover checked, retentions tracked
The shortcuts that end in a dispute are refused, and each refusal explains itself.
- check No variation work is started or claimed until it is approved in writing, with the name of who approved it
- check A subcontractor whose public liability has expired cannot be put on a job, and cover expiring soon is flagged
- check Retention held past completion is listed job by job, so a release is decided on purpose, not forgotten
- check The site diary is one sentence to add, and in a dispute it is the dated record of instructions and delays
Ownership
Your job record, beside the payroll and ledger you keep
Payroll, timesheets for pay runs and the general ledger stay in the systems that handle them. The job record moves to a database you own, and works through Claude Code and other AI assistants.
- check Your Jobpac Connect jobs, budgets and subcontractors are mapped across by Enterprise DNA, with a test run first
- check The first load is also an audit: larger jobs with no signed contract date and costs with no budget behind them are flagged
- check The rules it enforces sit in a plain file you can read and change to match your subcontract terms
- check Open source and yours: back it up, report on it from anything, and keep every job's history for as long as you need
Make it yours
Design your own Jobpac Connect replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Jobpac Connect. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Jobpac Connect data across and run it for you.
Switching
How to switch from Jobpac Connect
The move involves exporting the job records you want to keep, mapping Jobpac Connect’s fields and rules, then checking the imported data before you switch over.
- 1
Export the job record
Export the records your Jobpac Connect account allows, and check with Jobpac Connect if you are unsure what is available. Focus on the job record you are moving: clients, jobs, budgets, costs, commitments, variations, claims, subcontractors and retentions. Decide how much history to bring across. Payroll and the general ledger stay in the systems you use for them.
- 2
Map the Jobpac fields
Do not assume Jobpac Connect’s export columns match the new database. The free version's import is built for Buildxact's exports, so Jobpac records need mapping before they can be loaded. Map your jobs, budgets, costs and subcontractors, along with the contract types, cost codes, approval levels and subcontract terms your team uses.
- 3
Load a test copy
Load the mapped records as a test before using them for live work. Keep Jobpac Connect unchanged while you do this. If Enterprise DNA is handling the move, the mapping and test run are part of that work. If you are preparing the data yourself, check that it is in a format the importer accepts before loading it.
- 4
Check the import results
Review anything the import flags, then compare the imported records and totals with Jobpac Connect before making a change. Check that jobs, budgets, costs and subcontractors have landed in the right places, and investigate missing or mismatched information. Resolve issues in the mapping or source data and repeat the test if needed. Do not treat a completed import as proof that the records are correct.
- 5
Run both systems briefly
Once the checks are satisfactory, keep Jobpac Connect and the new job record running side by side for a short period. Use the new system for the job information you have moved and compare it with Jobpac Connect as work continues. Keep payroll and the general ledger in their existing systems. When the job records agree and your team is ready, switch off Jobpac Connect for the work you have moved.
Where the real effort goes
The main work is usually mapping your own Jobpac fields, contract types, cost codes, approval levels and subcontract terms, then deciding how much history to bring across. Different columns mean you should not assume an export will load unchanged. If Enterprise DNA runs the system for you, it handles the mapping and test run, with totals checked against Jobpac Connect before you change over.
Not ready for a call?
Get your Jobpac Connect switch plan by email
We will send you the step-by-step plan for moving your business off Jobpac Connect, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Jobpac Connect switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to run it
Try the free version, or have yours built and run
Open source
Run it yourself
Free
- 1 Clone the repo
- 2 npm run demo, then open the folder in Claude Code
- 3 Type /attention
- 4 Map your Jobpac Connect exports to the import and point it at your own database
Omni by Enterprise DNA
Have Enterprise DNA build and run your version
One setup fee, then a monthly retainer
- check We bring your Jobpac Connect jobs, cost codes, budgets and subcontractors across, checked against the old system
- check We set it up around your head contracts, subcontract terms, claim cycles and retention rules
- check A site screen, a subcontractor claim view or a link to your accounts and payroll, built where it earns its keep
- check It runs inside Omni, our managed Command Centre, beside the rest of your business
Questions
Instead of Jobpac Connect, answered
Jobpac Connect runs our payroll and accounts too. Does this replace all of it? expand_more
No, and it does not try to. Payroll and the general ledger are regulated, specialist work and stay in a system built for them. What moves is the job record: budgets, commitments, variations, claims, subcontractors and retentions. Enterprise DNA connects your version to the payroll and accounting system you choose to keep.
Is this built for a contractor our size? expand_more
The free version was built for builders running jobs from quote to handover. For a larger contractor, Enterprise DNA shapes your version to your own contract types, cost codes, approval levels and subcontract terms, on a database sized for the whole company.
Can we bring our history out of Jobpac Connect? expand_more
Yes, but be clear on how. The free version imports Buildxact's export format, and Jobpac Connect's data has different columns. Mapping your jobs, budgets, costs and subcontractors across is part of what Enterprise DNA does, with a test run first and the totals checked against Jobpac Connect before you change anything.
What about subcontractor claims and security of payment? expand_more
The free version refuses a claim past the contract plus approved variations, refuses unapproved variation work, tracks retention held and flags expired cover. The payment rules in your state or country, and your own subcontract terms, are set up in your version, and a person still sends every claim and schedule.
What does the version Enterprise DNA builds include? expand_more
Your Jobpac Connect data carried across, your contracts, cost codes and approval rules set up, your claim and variation paperwork in your brand, your team shown how to ask it for what they need, and someone to call in week one. It runs alongside everything else Enterprise DNA runs for you.
Own the record your projects run on
30 minutes with Sam. We look at what your construction ERP costs you, which parts your project team actually uses, and what your own version of the job record would look like. If it is a fit, we build it. If it is not, take the free version and run it yourself.
Builders for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Jobpac Connect?
Get your version built