All case studies & publications

Construction & Infrastructure · Logistics & Supply Chain

ERM Platform for Road Construction

Anonymised engagement
Client
Road-construction group · Bulgaria · ~300 staff, €100M+ revenue, own asphalt, concrete and fuel sites
Industry
Construction & Infrastructure
Department
Operations
Region
Bulgaria

A road builder with 300 people, 180 trucks and machines, its own asphalt, concrete and fuel sites and €100M+ a year in public contracts was running on paper, Excel and the accountants' memory. Every figure was typed three times, management saw the month three to four weeks late, and insurance and inspection deadlines lived in one person's spreadsheet. We designed the platform that runs the whole operation from one place.

A working model of the approach on sample data. It plays on its own and pauses when scrolled away; nothing here touches a live system.

The results

< 1 day
management reporting, down from 30 Projected
Projected, on live data.
180
vehicles, machines and plants in one system
Every expiry date tracked.
20+
document types processed automatically Projected
Manual entry from 100% to under 10-20%, projected.

The challenge

Our client is a Bulgarian road-construction group of around 300 people and more than €100M in annual revenue, building and rehabilitating roads, motorways, bridges and tunnels on public contracts. It runs its own asphalt and concrete plants, stone crushing, quarries and fuel stations across several sites, and a fleet of about 180 assets: cars, vans, heavy trucks, road machines and production plants.

The mechanisation, technical operations and procurement departments ran on paper and Excel. Finance was the only place the company's data came together, so everything else waited for accounting.

What it was costing them

  • Triple entry. Every figure captured on paper, again in Excel, and again by the accountants: 40-100+ hours a month lost, and one to two weeks every month just to consolidate.
  • Management flying blind. Reports ran 21-30 days behind reality, with no live cost view per site or per motorway lot.
  • Compliance exposure across 180 assets. Insurance, technical inspection, vignette and tachograph dates tracked by hand in a spreadsheet. One lapse means an uninsured truck or a stopped machine on a public contract.
  • Driver paperwork at scale. The law requires a waybill for every vehicle every day: about 2,000 a month on paper, kept for years.
  • Informal approvals. Repair and purchase approvals over messaging apps, with no audit trail.
  • Key-person risk. Fleet knowledge concentrated in one person.
One figure's journey today
  • Captured on paper
  • Typed into Excel
  • Typed again by accountants
  • Management: 3-4 weeks late

The approach

We took the engagement from "the paper is killing us" to a specified, prototyped and costed platform: process discovery across three departments, a full specification, a working interface prototype, the architecture and a contract-grade delivery plan.

An Enterprise Resource Management platform, not a generic ERP

Document-driven and built on three pillars, document AI, one central register and automated workflows, with its own web and mobile interface, integrated with the accounting software finance already uses.

Documents in, data out: 20+ types

Documents are captured by upload, email or phone, then split, classified and extracted automatically. The action centre shows the original document beside the extracted fields with the source highlighted, supports batch approval, and can undo every change a document triggered.

AreaDocument types
FinanceIncoming invoices, fuel invoices, bills of quantities, acceptance protocols
FleetDriver waybills, vehicle log books, fuel limit cards, registration papers, inspection certificates, insurance policies, service documents
Site operationsDaily work records, weighbridge tickets, bills of lading, construction acts, permits, accident reports
People and contractsEmployment contracts, health cards, powers of attorney, rental contracts, calibration certificates, customs declarations

17 modules across the operation

  • Transport and mechanisation. A full file for every vehicle and machine; fuel cards and own fuel-station balances; fuel reconciliation against supplier statements; GPS routes; waybills exported in the traffic-police format for statutory retention; service requests with approval thresholds by amount.
  • Compliance calendar. Every expiring document, insurance, inspection, vignette, tachograph and licences, with reminders at 30, 15 and 5 days.
  • Projects and costs. Projects, sub-sites and cost categories; invoices split by project; live cost per site and lot.
  • Procurement, employees and assets. Requests and purchasing, employee files with licence categories, fixed assets and depreciation.
  • Management dashboards on live data instead of a month-old report.
  • Accounting integration. Two-way sync with Microinvest and Plus-Minus through self-hosted n8n and our own Microinvest connectors: invoices out; payroll, clients and depreciation in. Finance keeps its software and the third round of typing disappears.
  • Bulk import of 14 source formats, from fuel statements and GPS routes to payroll and insurance.
  • Security. Role by module by action permissions, two-factor authentication and a full audit log. Responsive down to phone size, so drivers upload waybills from the cab.
The action centre
  • Original beside extracted fields
  • Source highlighted per field
  • Batch approval
  • Undo any change a document made
One heavy truck, one file
  • Insurance and inspection dates
  • Vignette and tachograph dates
  • Reminders at 30, 15 and 5 days
  • All expiry dates in one calendar

A prototype the departments could walk through

Every key screen was designed and built as an interactive prototype, so mechanisation, operations and procurement could walk their own workflows and react to them before a line of production code existed. That is where most requirements are actually discovered.

A delivery plan that can be executed

PhaseScope
1 FoundationDocument AI and automation server, infrastructure, authentication
2 CoreTransport and mechanisation, document core, employees, administration
3 BusinessProcurement, technical operations, reports, dashboard, accounting integration
4 DataImport, export, security and performance
5 Go-liveQA, DevOps, acceptance

Five phases over 30-36 weeks and about 3,800 hours of build, with written sign-off per phase, acceptance criteria per deliverable, a defect severity model with resolution times, and a support model with uptime commitments.

Technology

LayerWhat we designed with
Front endReact, TypeScript, Vite, Tailwind CSS, shadcn/ui
Back endNode.js, PostgreSQL, Redis and BullMQ, S3-compatible storage
Automation and AISelf-hosted n8n, Google Document AI splitter and custom extractors
IntegrationsMicroinvest (our connectors), Plus-Minus, GPS tracking, fuel-card data
OperationsDocker, nginx, GitHub Actions, Sentry, EU hosting

The outcome

All figures below are projected from the discovery and the specification.

TodayWith the platform (projected)
Manual data entry100%, three times overUnder 10-20%
Management reporting21-30 days lateUnder a day, live
Expired insurance or inspectionFound by chanceReminders at 30, 15 and 5 days
Document processingBy hand60-90% faster, ~80% fewer errors
ApprovalsMessaging appsThresholds, audit log
  • One platform for fleet, plants, sites, procurement, people and reporting across a 300-person, 180-asset company.
  • 20+ document types processed automatically.
  • 100+ hours a month returned, and the pressure taken off accounting.
  • Payback in under 18 months, at roughly a fifth of the cost of a comparable ERP rollout.
  • A specification and prototype that stand on their own. Every symptom the client came with, triple entry, the reporting lag, invisible compliance dates, is traced to the module that removes it.

The risk most teams miss

An off-the-shelf ERP does not know Bulgarian waybills or your plants. Unless documents flow in automatically, teams drift back to Excel within a quarter and the investment sits unused.

Next step

Start the same conversation

Tell us the process that keeps breaking. We will come back with what it would take to fix it, what it would cost, and what we would measure.

Or write to us directly: •••••@•••••••.•••

  • A reply from a partner within one business day
  • Fixed scope and fixed fee, agreed before we start
  • The maps and the backlog are yours either way