The site gets a paper trail.
Not a folder of paper.
Built for how construction actually runs in Bulgaria — every quantity, every certificate, every signature has an author, a timestamp, and proof.
02
The site and the office run on different truths.
Quantities live in one file, invoices in another, certificates in a folder, and site photos on someone’s phone. Every reconciliation is manual, and every discrepancy surfaces late — usually at payment.
Excel as a system
It works until someone changes, or a file gets overwritten by another version.
Certificates live on paper
Who signed, when, and based on what — reconstructed from memory.
Overspend shows up at the end
A line-item overrun surfaces after it happened, not while it’s happening.
03
One record for everything that happens on site.
Everything in Arcon is a record — a delivery, a certificate, an incident, an inspection, a request. Every record carries an author, a timestamp, a state, and proof. The modules work on top of these records.
What it is
- — The system of truth for the site
- — Approvals and certificates as data, not files
- — An audit trail by default, not by request
- — Works offline, on site
What it isn’t
- — Not an accounting package
- — Not a design tool
- — Not an AI that decides for you
- — Not a pre-loaded price catalog
04
The contractor proves. The client verifies.
The same records, read two ways — so the dispute is settled on data, not on memory.
Contractor
Proves what got done
- — Certificates assemble themselves from the underlying records
- — Photo evidence is required, not optional
- — Availability and cost are visible per line item
- — Disputes close with an audit trail
Client
Verifies what got paid
- — Budget control by site and by line item
- — Certificate of works checked against quantities installed
- — Readiness for handover is visible, not promised
- — Own crews and subcontractors in one place
05
A record passes through a gate. The gate demands proof.
Approvals and checks aren’t a screen someone can skip — they’re a condition in the data. A record with an unmet condition doesn’t move forward.
Record
Delivery, inspection, incident, request
Gate
Condition: photo, weather, role, prior certificate
Signature
Who, when, on what — for every record type
Certificate
Assembled from records already proven
Result: the chain of accountability exists for every record type — not just the documents someone remembered to sign.
06
Conditions get checked before the work, not after the incident.
H&S
Weather-gated work permits
A permit isn’t issued under unsafe conditions. Weather data comes from MeteoAlarm, Open-Meteo, and the Bulgarian meteorological institute — the decision stays on record with the time and values it was made from.
Incidents
Reports require a photo
A report doesn’t close without photo evidence. Evidence lives in a shared gallery, reachable from every linked record.
Quality
Signed, chained inspections
Every inspection carries an author and a timestamp. Signatures attach to any record type, so accountability tracks across the whole site.
07
The regulatory framework is designed in, not bolted on.
Generic ERPs ask you to adapt to their model. Arcon’s data model starts from Bulgarian construction law and tax reporting — Act 12/14/15/16/19 certificates, ДНСК and РИОСВ requirements, qualified e-signing via eIDAS providers (Evrotrust, B-Trust), counterparty lookups by EIK, and the SAF-T reporting standard the platform is being built toward.
Act 12Act 14Act 15Act 16Act 19ДНСКРИОСВeIDAS · EvrotrustB-TrustSAF-TEIK lookupsТАРИК / KH8
Signing for legally-binding documents runs through a qualified e-signature provider. Everything else in the chain stays cryptographically signed.
08
Certificates get checked against numbers, not against an AI’s opinion.
The check is deterministic and explainable. Every result traces back to the specific numbers that produced it — that’s the difference between an argument and a guess.
Materials
Consumption norms balanced against what was actually installed
Labor
Time norms balanced against logged hours
Deliveries
Cross-checked against third-party delivery notes
Chain
Gates at every certificate, double-measured by procedure
09
Pricing, built from your own numbers
The catalog fills from your invoices — not someone else’s price list.
Arcon doesn’t ship a price catalog. You enter an invoice — the item, the supplier, the real price go into the system. From there, the bill of quantities is priced on your own terms, not a market average.
Pack factor — raw quantity vs. the packaging you order in
Dual pricing — the invoiced price and its derived unit cost
Parametric norms — consumption rate × parameter
10
The database is yours. We hold the key, not the data.
Every client gets their own database and their own file storage. If you leave tomorrow, your data was never ours to begin with.
Control plane
Client registry, database provisioning, an access vault encrypted with AES-256-GCM.
Data plane · your infrastructure
- — A separate database per client
- — Your own Postgres, your own S3 storage
- — No mixing of data between companies
- — Export on demand, no negotiation required
11
The project timeline, live.
This is the real product, not a mockup — the same Gantt and Kanban views a site manager works from every day.
12
We’re building this with a small number of real sites, on purpose.
Bring a real site and real requirements. We build the parts you need next, in the order you need them — not in the order that’s convenient for us.
What you get
- — Priority on which modules we build next
- — Implementation shaped by your process, not our assumptions
- — Your own database, exportable at any time
- — Early-access terms, agreed individually
What we ask
- — One real site, not a test environment
- — Access to the people entering the data
- — Feedback every two weeks
- — Patience for a working, evolving product
Next step
Show us how you run a site today.
We’ll tell you exactly what Arcon covers now.
And what’s still ahead, and roughly when.