Construction Project ERP for Anademir

A construction project exists twice. On site, it is concrete, materials and deadlines. In the office, it is a calculated quote, a list of requested materials, a progress billing and a payment plan. Both sides describe the same undertaking.

The second side is the one that gets scattered. Cost estimation, material requirements, billing, payment plan and project records can live in different tools, each of which works on its own. What’s missing then isn’t order, but a shared point of reference — the place where all of it talks about the same project.

Starting in 2021, Batunet developed a platform for Anademir that brings this second half together in one system: structured around the company’s business areas, with the project as the shared reference.

Separate business areas need a common denominator; otherwise they are just programs placed side by side. In this platform, that denominator is the project.

A project is created from a quote and keeps that origin. Attached to it are its line items, the site’s material requests, the progress billings, the assigned incoming payments, the recorded project receipts with the material consumption derived from them, the documents and the notes.

These areas aren’t connected by an end-to-end automation, but by the shared data model: they reference the same record. A shared reference is easier to achieve than an integration and lasts longer than any interface between two tools.

It starts with a cost estimate, not a price. A quote consists of line items, and each line item carries the purchase price and the resulting margin alongside the sales price. The quote totals are therefore a result, not an input.

When the quote turns into an order, the project is created in a single operation: header data and all line items are carried over, the project receives its own system number, and the link to the quote is preserved. The operation is wrapped in a transaction — it either succeeds completely or leaves nothing behind. A half-created project with half of its line items would be worse than none.

Every carried-over line item remains identifiable as carried over. Anything added to the project later can thus be distinguished from what was originally quoted — the prerequisite for being able to compare quote and execution at all.

Up to this point, the system could be many things. This is where it becomes a construction system.

In construction, a progress billing isn’t a special case of an invoice but a document type of its own: the work billed for a period, performed by a specific company, on a specific project. That is exactly how it is modeled — as a dedicated request type with its own form for company, amount, document number, date and attachments, its own list, its own area on the project and its own total. The status model distinguishes planning approval from accounting approval and provides a separate state for disputed billings. Anyone who has ever negotiated a progress payment knows why this third state in particular isn’t an edge case. It is a status model that the people involved maintain, not an enforced workflow engine.

Alongside it is the payment plan. It is created on the quote, moves into the project and consists of planned installments with due dates. Incoming payments are assigned to these installments, and the degree of fulfillment results from comparing the planned amount with the payment received.

Calculations are done in two currencies, Turkish lira and US dollars. When a quote, payment plan, invoice or project receipt is saved, the Turkish central bank’s daily rate is recorded on the document, so it remains traceable which rate was used. The reports keep lira and dollars as separate series.

The first version of the platform ran on Laravel 9 with server-rendered tables and forms. In March 2023, the technical foundation was rebuilt: since then, Laravel 10 has provided a JSON API, and the interface is a standalone Vue 3 application whose modules mirror the same business areas as the backend.

Technically, this was a rebuild; functionally, it wasn’t. Quote, project, material request, progress billing and payment plan remained the areas in which the company worked, and the platform continued to be maintained afterward — with exports, corrections to reports and bug fixes.

This includes things you can’t see in an interface: server-side filtering, search and sorting of large tables, separate number ranges per document type, file attachments on projects and requests, and a change log with before and after values alongside a log of business events.