From tender to invoice.In one motion.

A mid-sized general contractor runs eight to ten projects at once, with twenty to thirty subcontractors per project. Per subcontractor: a contract, amendments, performance certificates, deductions, retention and warranty obligations. That product runs into the thousands — and typically lives in a shared folder, a dozen spreadsheets and a few thousand e-mails. ATMOS keeps that chain in one place: project delivery works from the same data as finance, so nothing is entered twice.

It starts with the tender. Requests for quotation go out to the selected subcontractors, incoming bids are comparable against identical technical content, the decision and its rationale are recorded, and the winning bid becomes a contract in one click. Contracts are generated from parameterised templates — civil law, public procurement or reverse-charge VAT — versioned, and signable by magic link without paper.

The performance certificate is not a separate spreadsheet: it is built from contract line items, runs through the approval round, is generated and archived as a document once signed, and then becomes an invoice. Variations are settled on a separate track so they never blur into the contracted scope, while advance recovery and retention are part of the formula rather than someone’s memory.

Who is it for? Typically the general contractor who has outgrown spreadsheets: above three or four parallel projects, tracking contracts and certificates starts to live inside one person’s head, and that becomes an operational risk. Here a construction ERP is not a luxury — it is the reason summer holidays do not stop invoicing. Rollout is not a months-long project either: the core chain of tender, contract, certificate and invoice is in place from day one, because the system was built for it.