Questions, answered honestly

BuildCore is a modular, multi-tenant SaaS platform purpose-built for construction. It carries one connected, audit-ready project record across documents, communications, quality, HSE, contracts, commercial and finance, procurement, stores, construction delivery, close-out, people, assets and analytics — so information isn't scattered across email, spreadsheets and disconnected tools.

By module. Every module across the Axontrix suite — the seventeen construction-focused BuildCore modules plus the independent Learning & Assessment (LMS, Examinations) and Retail & Commerce lines, twenty in all — is licensed independently, so you can start with one capability area and add more over time. The platform layer — multi-tenant, RBAC, audit trails, letterhead PDFs, notifications and deployment on your own servers — is included with every plan. Use the Build your plan configurator to assemble a module mix; pricing is tailored, so we quote against your mix, users and deployment.

Not as firm figures. Pricing depends on your module mix, number of users and projects, and deployment needs. The packaging shown on the pricing page is clearly labelled indicative, and the value estimator there is an illustrative model — not a quote. Contact us for tailored pricing.

Yes. BuildCore runs on .NET 8 and SQL Server on your own Windows or Linux servers, so project data stays inside the environment you control. Its interface libraries ship with it rather than loading from the internet, and AI can run on a local model. Email needs your own mail server, and licensing can use an offline licence file. See the Trust Centre for how deployment, isolation and access control work.

Access is governed by role-based access control with custom roles per organisation, down to the module, the project and the individual document. Audit records capture who did what, when and from which IP address, with before-and-after values, and are hash-chained so tampering is detectable — and each tenant's data is isolated. Formal outputs render as professional PDFs on your letterhead for the official record.

Construction-specific. The workflows model how construction projects really run — transmittals, RFIs, NCRs raised from rejected materials, permits-to-work, interim payment certificates, variation orders, man-hours with TRIR/LTIFR, and more — rather than a generic system bent to fit.

Yes. Contract administration, change orders, variations and interim payment certificates reflect how FIDIC-based projects are administered, and the Contract Management module tracks FIDIC claims against their Clause 20 time bars, alongside variation orders, EOT requests and joint ventures.

Primavera P6 planning and email are live today, and the platform includes webhooks and notifications. Other integrations are on a clearly-marked roadmap — see the Integrations page, where planned items are labelled as planned, not live.

Whichever solves your most painful gap first — because modules are licensed independently, there's no need to adopt everything at once. Many teams begin with Document Management and Communications, or with the module their role centres on (Quality for QA/QC, HSE for safety, Commercial & Finance for QS). The Solutions page maps common roles to modules.

No. In Communications, AI helps when a user asks it to — risk-scoring a letter, summarising a thread or drafting a reply — so time-critical letters are triaged and answered before deadlines. People review, edit and decide. It's assistance, not automation of the decision.