groflex
Risk-free validation

Your own data. Our platform. 1 to 3 days. Then we delete everything.

Before you spend anything, see what your execution gap cost you last year, measured on your own history rather than on a benchmark.

How it works

One file in. One report out. Nothing left behind.

  1. You send one historical export01

    CSV or Excel. 12 to 24 months of sales, inventory and decisions. Anonymised if you prefer, the analysis does not need to know who your counterparties are.

  2. We replay it through Groflex02

    The report shows the decisions that took days, what deciding them in 30 minutes was worth, and your decision-latency baseline against your own margins.

  3. The report is yours. The data is not kept03

    Source data is deleted on delivery and the deletion is confirmed to you in writing. Nothing is retained, and nothing trains a shared model.

What you get back

Your decisions, replayed against the clock.

Backtest reportDelivered

Groflex · Backtest report

Food distribution operator

24 months replayed through the platform. What the decisions cost at the speed they were actually made, against the same decisions made in under 30 minutes.

Backtest outcomes, before and after
MeasureBeforeAfterChange
Decision latency51 h24 min−99.2%
Stockouts146101−31%
Inventory accuracy87%96%+9 pts

Illustrative · modelled on typical industry inputs · your figures come from your own data

Range · 2024-06 to 2026-05Source data deleted on delivery · 2026-06-07
What we do with the file

The shortest data-handling section you will read this quarter.

No integration
Nothing is installed and nothing connects to your systems. You send a file.
No system access
No credentials, no VPN, no read access to your ERP.
No retained data
Deleted on delivery, confirmed in writing.
NDA on request
Mutual NDA before any data moves, if you want one in place first.

Groflex is designing for EU AI Act Article 12 and FSMA 204. Those programmes are in progress and Groflex is not certified against any standard. Deletion on delivery is not a compliance claim, it is what happens to your file.

The backtest is how the pilot decision makes itself.