One state machine per record
Every record type has a single authoritative lifecycle. The interface only offers transitions that are legal right now.
construction erp
Run every project from first estimate to handover
bhetierp puts estimating, planning, procurement, change, finance, field, quality and documents on one record. Approve something once and it lands everywhere it matters.
In development · platform core in review
portfolio overview
IllustrativeGood morning, Priya
Active projects6
Contract value$184.6M
Open RFIs37
Pending change orders
Budget vs cost to date
Open items
- RFIs9 overdue37
- Submittals4 overdue22
- Change orders2 overdue
- Inspections due3 overdue18
- Non-conformances5 overdue11
CO-014 approved · budget, BOQ and SOV updated
Portfolio dashboard with illustrative figures. The product’s dashboard is live; change-order approval arrives with contracts and change in phase 6.
built on a full inventory
Nothing left behind. Every capability has a home.
bhetierp was planned against a complete construction ERP. Each of its capabilities is assigned to exactly one bhetierp module, and an automated coverage check fails the build if any go missing.
- product modules
- 98
- 92 in the work sidebar, 6 under administration.
- reference capabilities mapped
- 244
- Each assigned to exactly one module. A coverage check proves nothing is dropped.
- lifecycle groups
- 18
- Navigation follows the order a project is actually built in.
- end-to-end workflows
- 10
- From estimate-to-budget to handover, each with one state machine per record.
Standards on the roadmap
WCAG 2.2 AAAccessibility target for every screen
EN 16931E-invoicing, plus national clearance
BCF · OpenCDEBIM collaboration
IDS · COBieInformation requirements and handover data
one platform
The whole project, one record
Most firms run a construction project across a dozen tools that never agree. bhetierp follows the project the way it is built, from the first estimate to the last retention release, and keeps every stage on the same record.
- 01
Estimate
Cost databases, assemblies and a BOQ editor with markups, snapshots and locking.
- 02
Plan
Gantt and CPM schedules with baselines, lookahead and Last Planner, resources and progress.
- 03
Procure
Requisition to purchase order to goods receipt, subcontractors and commitments.
- 04
Contract & change
Contracts and SOV, progress claims, change orders, variations and claims.
- 05
Control cost
Budgets, invoices and payments, earned value, CVR, cashflow and risk.
- 06
Build
Site diary, field reports, time and payroll, equipment, logistics and forms.
- 07
Inspect
Inspections, NCRs, punch lists, permits, commissioning, safety and ESG.
- 08
Hand over
Closeout packages, the defects liability period and retention release.
workflows
Records that move. Effects that follow.
Each record type has one state machine, and each transition has consequences in other modules. Pick a workflow and watch a record reach its next state.
A locked estimate becomes the budget
Price the BOQ from cost databases and assemblies. Locking it generates budget lines through the cost model, so finance starts from the number you bid.
BOQ-0042Draft
Structure & envelope
Riverside Medical Centre
- Positions
- 1,284
- Priced from
- Cost database · Assemblies
- Total
- €18,420,550.00
Only legal transitions are offeredLock BOQ
Status history
MMarcus LeeCreated as Draft2 days ago
Across modules
Effects land here when BOQ-0042 reaches Final.
- Cost controlBudget lines generated from the locked BOQ
- Bill of quantitiesSnapshot kept; further edits open a revision
modules
98 modules, grouped the way projects run.
Eighteen groups follow the construction lifecycle, from pre-construction to real estate. Switch on the ones your organisation needs. Each module shows the phase that delivers it.
Overview
Live modules are built; the phase shows when the rest ship- DashboardPartly live
Portfolio and project KPIs, open items and recent activity.
Still to come: Configurable widgets, KPI tiles per module and BI dashboards (Phases 6-13).
- ProjectsPartly live
Project register with WBS, milestones, members, status history and regional settings.
Still to come: Delivery models, project handbook and governance settings (Phase 10).
- InboxPartly live
Notifications, pending approvals and items awaiting your response.
Still to come: Deadline tracking and approvals awaiting you (with approval routes, Phase 5).
- TimelineLive
Filterable newest-first feed of significant project events.
- PortfolioP7
Programme tree, capital plans, capacity, cross-project scheduling and WIP.
why it holds up
Built for the arguments before they happen
Disputes on a project come down to who approved what, when, and for how much. bhetierp is designed so the system can always answer.
Decimal money end to end
Decimal arithmetic from database to screen, never floats, with explicit currency and a stored FX rate snapshot.
Every change on the record
Each state change records actor, time, from and to status and the reason. Signed diaries and CDE gates are immutable.
Access that only narrows
Four global roles and {module}.{action} permissions. Project membership decides who sees a project; record visibility and API keys can only restrict further.
Projects with their own rules
Each project carries its own currency, units, calendar, classification standard and members.
Switch on what you use
An explicit module registry shared by the API and the interface. A disabled module is hidden and blocked in one place.
Lists built for real volume
Search, filters, sort, server-side pagination, saved views, bulk actions and PDF or XLSX export on every list.
how it works
Set it up once. Then let the records do the work.
- 01
Set up your organisation
A real multi-tenant boundary. Invite users and give each one of four roles: admin, manager, editor or viewer.
- 02
Create your projects
Set each project’s currency, units, calendar and classification standard, then add its WBS, milestones and members.
- 03
Enable the modules you need
Turn modules on and off with dependency checks. Navigation shows only what your organisation uses.
- 04
Run work through workflows
Records move through their lifecycle, approvals reach the inbox, and every effect lands in the modules downstream.
roadmap
Sixteen phases, each reviewed before the next begins.
The platform comes first, then the most-used commercial flows. Specialised capabilities such as BIM, AI and country packs come last. This is where the build stands today.
- Complete
- Next
- Planned
- Phase 0Complete
Reference analysis
Module inventory, architecture, design system, roadmap
- Phase 1Complete
Monorepo & UI foundation
App shell, brand theme, login, sample-data dashboard, navigation for every module
- Phase 2Built · in review
Platform core
Go API, PostgreSQL, sessions, organisations, roles, projects, audit log, module registry
- Phase 3Next
Estimating & cost data
Cost databases, assemblies, BOQ editor, conceptual estimate, rate build-up, FX
- Phase 4Planned
Planning
Gantt, CPM, baselines, lookahead and Last Planner, resources, progress to EVM
- Phase 5Planned
Documents & collaboration
CDE, submittals, transmittals, correspondence, signing, RFIs, meetings
- Phase 6Planned
Procurement, contracts & change
Requisition to PO to receipt, subcontractors, contracts and SOV, change orders
- Phase 7Planned
Finance & controls
Budgets, invoices and payments, EVM, CVR and cashflow, risk, portfolio
- Phase 8Planned
Field operations
Site diary, field reports, time and payroll, equipment, logistics, inventory
- Phase 9Planned
Quality, safety & compliance
Inspections, NCR, punch list, permits, commissioning, HSE, carbon and ESG
- Phase 10Planned
Pre-construction
CRM, bid/no-bid, tendering and bid management, design management
- Phase 11Planned
Handover, assets & real estate
Closeout, defects liability, assets, service, client portal, leasing
- Phase 12Planned
Takeoff, drawings & BIM
PDF and DWG takeoff, markups, rebar, BIM models, clash, BCF and OpenCDE
- Phase 13Planned
Reporting, intelligence & AI
Report builder, BI dashboards, AI assistant and search, automation
- Phase 14Planned
Regional, tax & integrations
Country packs, e-invoicing (EN 16931), accounting sync, webhooks, MCP
- Phase 15Planned
Desktop
Tauri shell over the web UI, file-system access, offline cache, auto-update
faq
Questions, answered plainly.
Something not covered here? Request early access and ask us directly.
Not in production yet. Phases 0 and 1 are complete, and phase 2, the platform core, is built and in review: the Go API and PostgreSQL database, sign-in and sessions, organisations, users and roles, a permission matrix, module toggles, projects with WBS and milestones, contacts, notifications, an audit log and a live dashboard. Estimating and cost data come next. Request early access to follow each phase as it ships.
The whole construction project lifecycle: estimating and cost data, planning, procurement, contracts and change, finance and controls, field operations, quality and safety, documents and collaboration, and handover. That is 98 modules in 18 groups.
The platform comes first, then the most-used commercial flows: estimating, planning, documents, procurement and change, then finance. Specialised and heavy capabilities such as BIM and CAD, AI and country packs come last. Every phase is reviewed and approved before the next one starts.
No. Modules are enabled or disabled per organisation, with dependency checks. A disabled module is hidden in the interface and blocked in the API, from one shared registry.
With decimal arithmetic end to end, never floating point. Every amount carries an explicit currency, and FX rates are stored as snapshots, so a converted figure can always be traced back.
Four global roles (admin, manager, editor, viewer) and permissions per module and action, each with a minimum role that admins can change. Project membership controls who sees a project, record-level visibility can only restrict further, and API keys can only narrow their owner’s rights.
Yes. Every state change records who made it, when, the status it moved from and to, and the reason. Signed records such as site diaries and CDE gates are immutable.
It is web first and responsive from 390 px wide, in light and dark themes, built to WCAG 2.2 AA. A desktop app built with Tauri reuses the web interface and adds file-system access, an offline cache and auto-update.
early access
Build your next project on one record
bhetierp is being built in the open, one reviewed phase at a time. Leave your email and we’ll tell you as each phase ships, next with estimating and cost data.