# Marcus Terlouw, Head of Compliance & Sourcing at Brimfield Foods BV — read of Pesticide Compliance Verifier, June 2026

> "14 years moving specialty produce and spices into the EU. Currently managing three labs on contract, one customs agent who texts me at 6am, and a spreadsheet I built in 2019 that I'm embarrassed to describe."

## How I got here

Searched "EU MRL compliance software importers" sometime in March after our third SGS rejection in a row on paprika from a new Turkish supplier. A LinkedIn post from someone in a Dutch trade group linked to this page. I bookmarked it, forgot it, found it again last week cleaning out my browser tabs. Classic.

## What I clicked first

The hero stopped me: "Verify compliance in hours, not weeks." That is the actual problem. We wait 12 to 18 days on standard lab turnaround for EU MRL checks. When a container is sitting on demurrage, that sentence is magnetic. I read it twice.

Then I looked for the "how" and hit: "Submit Data -- Provide product origin, growing region, batch codes, and prior test results." That gave me pause. It's asking for prior test results. So... you're cross-referencing results I already have? Or are you doing something to help me before I have results?

## Where I paused

The compliance standards list is genuinely the most credible block on the page. EU Regulation 396/2005, FDA FSMA, Japan/Korea/Singapore national registries, Tesco and Sainsbury's private label thresholds -- that is a real list. Someone who knows this space wrote it. That made me slow down and read more carefully instead of closing the tab.

## What I distrusted

Two things, and one of them is a wall.

First: "99.2% Detection Accuracy. Trained on 10+ years of regulatory refusal data." Trained on refusal *data* is not the same as detecting contamination. I've been in this industry long enough to know that pesticide detection is a wet chemistry problem -- you can't software your way around an LCMS. If what you're actually doing is cross-referencing known residue flags against known MRL thresholds using submitted test data, that is a compliance *matching* tool, not a detection tool. Say that. The word "detect" is doing a lot of heavy lifting it doesn't earn.

Second, and this one killed it for me: buried at the bottom, in a section I almost missed, it says "Honest disclosure: we don't have live customers on this idea yet." But earlier the page claims "50+ importers already reducing regulatory risk" and "$12K average cost saved per rejected shipment." Those two things cannot both be true. If you have 50+ importers using it, you have customers. If you have no live customers, you don't have 50+ importers. That is not a minor inconsistency.

## What would convince me

A single, named case. Not "a European importer of produce." Give me a company name, a country of origin for their shipment, what pesticide flag came up, and what they did with the result. One real case with a paper trail would do more than every stat on this page.

And I need clarity on the core mechanics: does your system cross-reference test results I already have against MRL databases, or does it do something I don't yet have? If it's the former, I need to understand why I'd pay for this versus a well-maintained MRL database subscription like PesticidesDB or the EU's own EFSA portal. What is your edge?

## What I'd ask in an email reply

1. The page says "prior test results" are an input -- does that mean I need lab results in hand before your system is useful, or can I submit a shipment for pre-clearance risk scoring before testing?
2. The "50+ importers" claim and the "no live customers yet" disclosure are contradictory. Which is accurate, and if it's zero customers, what are those statistics based on?
3. What is the actual data source for your MRL cross-reference engine -- is it pulling live from EFSA and FDA, or is there a refresh cycle I should know about?

## Verdict: on-the-fence

The problem is real, the compliance standards list shows real domain knowledge, and the hero line hit the actual pain. But the detection-vs-matching confusion and the flatly contradictory customer claims make me unwilling to book a demo until someone explains them. If a founder replied to those three questions with straight answers, I'd get on the call.

---
*Memo by skeptic persona, generated 2026-06-09. Studio breaks own self-grading loop.*