fluctor

Every milestone invoiced. Every delay seen before it costs.

Marren Engineering is an example of a plant engineering firm. Its project leads make the calls, its agents watch milestones, suppliers and hours.

Wind turbines in a field at sunset

How one case runs.

A milestone accepted by the client and never invoiced. Here is what fluctor does with it, step by step.

  1. 1Noticed

    On 25 September Helen Quirke of Ormond Foods signs off milestone 3 and emails the acceptance certificate. Twenty-four days later nobody has invoiced it. fluctor raises the signal: €372,000, with her email as its source.

  2. 2Traced

    Explore opens milestone 3 of project P-2418, the Ormond Foods cooling plant, read from the signed acceptance certificate. Linked to it are the acceptance email and clause 8.3 of the contract, which allows the invoice on the day of signature. The accounting record lists the milestone, and next to it there is no invoice.

  3. 3Automated

    One click on Automate this opens the chat. The agent is described in a sentence: when a milestone is accepted but not invoiced, draft the partial invoice and send it with the acceptance certificate to the client’s accounts address.

  4. 4Approved

    The first run stops before anything is sent. Invoice 2641 and the acceptance certificate are in the draft; one click on Approve this run sends this one. With Always allow for this agent, the next ones go out on their own; otherwise each run is approved separately.

  5. 5Tracked

    A sentence in the chat builds the dashboard of open milestones by project. €230,500 is still unbilled across two projects, and Ormond Foods shows as invoiced.

See it work, start to finish.

One milestone, accepted by the client and never invoiced. Watch fluctor notice it, trace it, hand it to an agent and keep watch on all the others.

Two more agents for every project.

Deadlines and penalties

The problem
A supplier slips, and the penalty lands on your milestone.
It starts when
A supplier writes that a delivery will be late
The result
Project lead briefed, 39 days ahead
The agent “Deadlines and penalties” opened in the agent list: last run 19.10.2026, 06:00. Two dates were found, milestone 4 and the Kilbride delivery. Both went to the project lead.

Hours against budget

The problem
A work package runs over, and it shows in the final account.
It starts when
Every week, against the timesheets
The result
340 hours over, flagged the same week
The agent “Hours against budget” opened in the agent list: last run 19.10.2026, 07:30. Eleven work packages were checked, one is above its budget.

What project leads ask.

Every answer comes with the file it was read from.

  • No. Helen Quirke signed the acceptance for milestone 3 on 25 September. There is no invoice on file. €372,000 is outstanding.

    Source: acceptance_M3.jpg

  • On 27 November 2026, in 39 days. If it is late through our side, the contract charges €9,300 for each full week, up to €93,000. The control cabinets from Kilbride are 12 days late.

    Source: contract_P-2418.docx

  • At the project meeting on 8 October: a second heat exchanger on line B and extra pipework in hall 2, agreed at €38,400, invoiced separately.

    Source: minutes_08-10.docx

Your data stays yours.

Contracts, acceptance certificates and timesheets stay in-house: hosted in the EU or entirely on your own servers.

Security
  • EU hosting
  • Your own servers
  • GDPR & DPA
  • No training on your data
  • Every answer with its source
  • Activity log

See fluctor on your own documents.

A demo on your own projects, with your real inbox and files, not on slides.