An app project starts with an introductory meeting: half an hour to an hour in which we go through the problem you want to tackle, the systems in place, and the expectations of management, IT and users in the barn, on the lorry or in the shop. That conversation is non-binding. Often the outcome is: this can also be done with a progressive web app, or: an existing SaaS product is more suitable here, or: this is exactly the use case where a custom app adds value for your agri, transport or SME operation.
If there is a suitable use case, we plan a discovery. This is a short phase in which we work out the solution at architecture and interaction level: native or cross-platform, which integrations (TMS, ERP, farm management system, POS, KringloopWijzer, I&R), which data flows, which compliance requirements (GDPR, supply chain sector requirements, audit trails), and what the release pipeline looks like. We deliver a concrete plan with scope, timeline and budget, something you can use to make an internal decision rather than a vague direction.
Then comes the build in sprints. At the end of every sprint, something working runs on real devices. That helps to discover early on what in the design doesn't work for the dairy farmer, the driver, the engineer or the shop assistant, to adjust priorities, and to bring stakeholders along. 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: ongoing support or a clean handover to your own team, depending on what fits.