For us, a project starts with an introductory meeting: a short session in which we go through the problem you want to tackle, for which users, and which systems are already in place. That conversation is free and non-binding. Sometimes the outcome is: this doesn't need a custom build, an existing package or an inexpensive SaaS solution is enough. Other times: a custom app really is the right answer here — and then we talk about scope, integrations and compliance.
If there's a suitable use case, we plan a discovery. This is a short phase in which we sharpen the solution: which platforms (iOS, Android or both), which modules, which integrations, which compliance requirements and which user roles. For Schiphol-related projects we look at customs integrations, cargo data protocols and existing integrations; for finance, at SSO, DORA and PSD2 requirements and core banking; for field service, at MDM, offline flows and the existing ERP layer. We deliver a concrete plan with scope, timeline and budget — not a vague deck, but something you can base internal decisions on.
Then comes the build, in sprints. At the end of every sprint, something working is running in TestFlight or the Play Console, even if it's limited at first. This helps us test design choices early, adjust priorities and bring stakeholders along. We work in your own repository, with code review, automated tests and a staging environment you can use to test with real users — for example with a handful of engineers or agents on site in Badhoevedorp or Schiphol-Noord.
After go-live comes maintenance and further development. An app needs upkeep: iOS and Android versions are updated every year, libraries receive security patches and integrations get new API versions. We offer ongoing support or hand everything over cleanly to your own team.