A project with us begins with an introductory call: a short session in which we go through which problem you want to solve, for which users, and which systems are already in place. That conversation is free and non-binding. Sometimes it turns out this doesn't need to be a custom build: an existing package or an affordable SaaS solution will do. Sometimes a custom app really is the right answer, and then we talk about scope, integrations and compliance.
If there is a suitable use case, we schedule a discovery phase. This is a short phase in which we sharpen the solution: which platforms (iOS, Android or both), which modules, which integrations, which compliance requirements, 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 take internal decisions on.
Then comes the build in sprints. At the end of each sprint, something working is running in TestFlight or the Play Console, even if it's initially limited. This helps you test design choices early, adjust priorities and bring stakeholders along. We work in your own repository, with code review, automated testing 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 annually, libraries receive security patches, and integrations need updating to new API versions. We offer ongoing support or hand over cleanly to your own team.