A web app engagement starts with an introductory meeting: half an hour to an hour in which we go through the problem you want to tackle, the systems already in place, and the expectations of management, IT, users and — depending on the sector — compliance, security or audit. That conversation is free and non-binding. Often the outcome is: this can also be done in an existing portal, or: a SaaS product is cheaper here, or: this is exactly the use case where a custom web app adds value.
If there is a suitable use case, we plan a discovery. This is a short phase in which we work out the solution at the level of architecture and interaction: which front-end stack, which backend, which integrations with core systems, which data flows, which compliance requirements, 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 each sprint, something working is running in a test or acceptance environment — limited at first, then increasingly complete. This helps to discover early on what doesn't work on the shop floor in the design, adjust priorities, and bring stakeholders along. We work in your own repository, with code review, automated tests and a release process that also stands up to an external audit.
After go-live comes maintenance and optimisation. Web apps need maintenance: dependency updates, security patches, performance tuning, user feedback. We offer ongoing support or hand it over cleanly to your own team — whichever suits you. For some clients in finance and healthcare we have remained the permanent web app partner; for others we deliver and provide support on request.