An app project starts with an introductory meeting: half an hour to an hour in which we go through which problem you want to tackle, which systems are in place, and what expectations management, IT and users on the work floor, the farm or in the shop have. That conversation is free and non-binding. Often the outcome is: this can also be done with a progressive web app, or: an existing SaaS product is cheaper here, or: this is exactly the use case where a custom app adds value.
If there is a suitable use case, we plan a discovery: a short phase in which we work out the solution at architecture and interaction level. That covers native or cross-platform, which integrations (MDM, GS1, ERP, MES, agri ERP, POS), which data flows, which compliance requirements (HACCP, allergens, traceability, GDPR), and what the release pipeline looks like. We deliver a concrete plan with scope and timeline, something you can use to make a decision internally.
Then comes the build, in sprints. At the end of each sprint, something working runs on real devices, so you see early on what does and doesn't work for the operator, grower, engineer or shop assistant. We work in your own repository, with code review, automated tests and a release process for both stores. After go-live comes maintenance and optimisation, either ongoing or handed over to your own team. For web or ERP follow-up questions, we continue with our software colleagues for Purmerend.