What people actually ask us.

No. We put one module into service, your teams actually use it, then we move to the next. That is our method, not a concession: a system delivered all at once is never adopted all at once.

We say so, and explain why. Then we do as you decide. You know your trade better than we do; we know the consequences of a technical choice better than you do. Both are useful.

Yes, in your teams' own language and on your own screens — not on a demo dataset. After go-live, someone answers.

Because a published figure would be wrong for almost everyone: the cost depends on the modules you keep, the number of sites and people, and how much of your existing data has to be brought forward. Tell us your size and what you want covered, and you leave the first conversation with a figure — not a brochure.

Yes. Many start with a single sore point — worker attendance, or intake at the packhouse — and add the rest season after season. A single farm is as much a customer as a group of three.

They do not start again from nothing. We bring the existing data forward and it becomes searchable inside the new system. That is a step in our method, not an option billed separately.

The interface is in French, Arabic and English. Each person picks their own: the accountant can stay in French while the crew leader reads Arabic.

An ordinary phone is enough: entry in the field, at intake and on the dock all happen on it, by QR or barcode. The exact hardware is decided with you, looking at your real conditions — damp, cold, pace.

Entry carries on on the phone with no connection, and goes up when the signal comes back. Here that is the normal case, not an exception: a large share of plots has no reliable coverage.

Yes, and it is the heart of the system: from a carton number you go back to the pallet, the quality check, the intake lot, the crew that harvested, the treatment applied and the plot. The Traceability page shows it in twelve steps, on sample data.

Yes. Every treatment records the product, the dose, the date, the plot and the worker who applied it. The pre-harvest interval is carried from the product sheet and compared with the harvest date, so an overrun shows up before shipping rather than during an inspection.

No, and nobody can be certified in your place: certification covers your farm, not a piece of software. What we do comes earlier — keeping the records an auditor asks for (treatments, quality checks, non-conformities, carton-to-plot traceability) so that audit day is a matter of looking things up rather than reconstructing them.

Yes, and the correction leaves a trail: who, when, and the value before. Nothing disappears quietly. That is what makes a figure defensible in front of a customer, an auditor or the authorities.

With you, or wherever you decide. This is not a paid option: it is the rule. Your production, payroll and margin figures are not a bargaining chip.

Yes, with no conditions and no fee. Data exports to a spreadsheet from the screens themselves, and the database stays yours. A vendor who holds your data hostage is not keeping you, they are trapping you — and that is not the same thing.

Rights are set screen by screen, and money is a boundary of its own: a crop manager can follow their plots without seeing costs or wages. That is often the condition for the field to actually enter its data.