Custom software for agri and food.
For growers, exporters and food companies who work between climate computer, ERP, auction and export papers.
No obligation · six questions · reply within one to two working days
Who we build for
- Greenhouse horticulture
- Floriculture export and wholesale
- Fruit and vegetable trade
- Food production
What is happening.
What is changing in agri and food.
- 01
Requirements per country
You apply for export certificates through CLIENT Export, and each country sets its own requirements per shipment. If a detail is missing, the shipment waits.
- 02
Evidence per lot
Retail audits under HACCP, BRC and IFS ask for evidence per lot. With a complaint, you need to know at once which grower, lot and customer are involved.
- 03
CO₂ levy in greenhouse horticulture
Since 1 January 2025, greenhouse horticulture has been subject to a CO₂ levy. You track energy and emissions per business, alongside your growing data.
- 04
Seasonal peak with temporary staff
At the peak, many temporary workers are on site. Hours, handling and lots must then add up, without anyone checking everything by hand.
Where it can be better.
Six processes from day-to-day operations in horticulture, trade and food production.
- How it works now
- For each shipment: check the country requirements, schedule inspections and apply for the certificate.
- What could be better
- Certificates right first time, so shipments are not rejected.
Demo company
- Shipments
- Country requirements
- Inspections
- Certificates
- Documents
Demo company › Export
- This week
- Awaiting inspection
- Deviation
- Issued
- Shipments this week
- 14
- Awaiting inspection
- 3
- Country requirement not met
- 1
Roses to Japan: the country requires an additional declaration, and the application lacks it. Inspection with declaration proposed for Friday.The export officer decides on the application.
Schedule inspectionAdjustRoses to Japan: the country requires an additional declaration, and the application lacks it. Inspection with declaration proposed for Friday.The export officer decides on the application.
Schedule inspectionAdjustExample. Demo company; names and figures are fictitious.
All processesThe system proposes. You decide.
The system reads, checks and prepares. A person decides what happens.
| Process | What the system does | Who decides |
|---|---|---|
| Export certification | What the system does: Country requirements checked per shipment in advance. The CLIENT Export application is ready from the order. | Who decides: The export officer decides on the application. |
| Auction and Floriday | What the system does: Clock, clock pre-sales (KVV) and direct trade in one overview. With the purchase profiles and limits from Floriday. | Who decides: The buyer decides on profile and limit. |
| Crop recording | What the system does: Weekly measurements per crop next to the climate computer data. With no Excel in between. | Who decides: The cultivation manager decides on the adjustment. |
| Traceability and recall | What the system does: For each lot, where it came from and where it went. In a recall, the full picture at once. | Who decides: Quality decides on release and recall. |
| Returnables and logistics | What the system does: Containers and trolleys per customer and carrier. Return slips read and booked, so the balances add up. | Who decides: The returnables controller decides on the booking. |
| Audits | What the system does: Evidence per lot and per period, gathered during the work. The file is ready before the audit. | Who decides: The quality manager decides what counts as evidence. |
Compliance you can prove.
What the rules in horticulture and food production ask, and what the system records.
| Rule | The inspector asks | The system records |
|---|---|---|
| Plant Health RegulationPlant passport and registration when trading plant material within the EU. | Plant passport and registration | Passport per batch |
| NVWA export certificationPhytosanitary certificates through CLIENT Export, with different requirements per country. | Requirements per destination country | Certificate per shipment |
| CO₂ levy for greenhouse horticultureSince 1 January 2025. | Emissions per business | Gas consumption per period |
| HACCP, BRC and IFSFood safety and audits by retailers. | Proof for retail audits | Measurements, nonconformities and actions |
| For every sector | ||
| GDPR | Who processes personal data, and where | Data processing agreement, EU hosting with ISO 27001-certified partners |
| AI Act | Human oversight of AI | Every proposal with who approved it |
Start here.
One process, one prototype. Then you decide.
Start with export certification per shipment, or with traceability per lot.
- Step 01
Conversation
A process map
- Step 02
Prototype
A prototype
- Step 03
Build
A go or no-go per phase
- Step 04
In operation
Your code, your data
Systems you may already use
- Floriday
- CLIENT Export
- Priva
- Hoogendoorn
- LetsGrow
- Florisoft
- Axerrio
- Agrovision
We connect to what is there, or build alongside it where the package is too heavy or too rigid.
Where we are not the right fit
Cooperatives and multinationals with long procurement processes are not our focus. We build for family businesses where the managing director decides.
Questions.
About costs, time, integrations and ownership.
What does it cost?
Most systems we build cost between €10,000 and €40,000, one-off. Support is about 3 to 5% of that, per month. After the prototype you get a fixed price, before you sign anything.
How long does it take?
We set that after the prototype, per phase. We do not give a timeframe before then.
How much of our time does it take?
One owner who makes the decisions, and a few users who review and test during the build. We agree the exact amount per project.
Does it connect to our ERP and Microsoft?
Yes. Users sign in with their own Microsoft account and MFA. We set out in the proposal which ERP and file integrations are included.
Who owns the software?
You do. The rights transfer per phase, once that phase is paid. No licence.
Where is it hosted?
In the EU, encrypted: EU hosting with ISO 27001-certified partners.
Who maintains it?
We do, under an SLA. Or you do: the documentation is written for that.
People
You talk to the people who build it: Jelle, Mike and Jeroen. No account manager, no middleman.
About usShow us one process that could be lighter.
No obligation · six questions · reply within one to two working days. Or get in touch