Software developer in Amersfoort.

For many national organisations, Amersfoort is the logical head office: centrally located in the Netherlands, geographically at its heart. The city is home to a substantial insurance ecosystem around Achmea, a strong healthcare cluster with Meander Medisch Centrum and GGZ Centraal, a construction and installation sector including TBI, an ABN AMRO distribution site, and of course the Amersfoort municipality and the province of Utrecht. Software that has to run in that context, with heavy compliance requirements, integrations with legacy policy systems, long contracts and internal IT architects with their own preferences, calls for a developer who works across all three layers: web, backend and mobile.

At Appfront, we build custom software for clients in Utrecht and the Amersfoort region. Web platforms for the insurance cluster, client portals for healthcare, integration layers on construction ERP and planning tools, dashboards for municipalities and, where it fits best, apps for field service or the shop floor. Strategy, design, code, infrastructure and release management come from one team, so advice and delivery never drift apart.

Whether you are an insurer needing a claims platform, a healthcare provider with a records portal, an Amersfoort contractor looking to digitise its work and planning processes, or a mid-sized business ready to move away from an outdated ERP add-on, we adapt our role to what you need. A sounding board in the first phase, a builder in delivery, or both throughout the project.

Software in production is more than a nice interface. We build platforms that keep working when a legacy system misbehaves, when the internet connection on the building site drops, and when an audit team gets to look through everything. In practice, all web platforms get a rigorously tested layer in which business logic, integrations and data flows can be tested and scaled separately. For insurance workflows, EHR records or site work orders, that isn't a luxury but a requirement.

For integrations, we work with APIs on top of your existing systems: policy systems, EHRs, CRM, ERP, project management or identity providers such as Azure AD and iWelcome. We build either a direct integration or a lightweight middleware if your source systems aren't stable enough for direct calls. For authentication, we choose standards (OAuth 2, OpenID Connect, SAML, eHerkenning where needed) rather than proprietary solutions.

Everything that goes into production is equipped with observability: logging, performance monitoring, usage analytics that do not compromise end users' privacy, and alerting on the backend. That way you spot problems before your users do, which in an insurance, care or government environment makes the difference between trust and frustration. For GDPR and EU data residency, we work as standard with EU data centres and clearly structured processing registers.

A software engagement starts with an introductory call: half an hour to an hour in which we talk through the problem you want to tackle, the systems in place, and what is expected from management, IT and the people on the operational side. That conversation is free and without obligation. It often concludes that: this can be handled with an existing SaaS product, or: there is a simpler solution that we can achieve through a few integrations, or: this is exactly the kind of use case where a custom platform adds real value.

If there is a suitable use case, we schedule a discovery phase. This is a short phase in which we work out the solution at the level of architecture and interaction: web, mobile or both, which integrations, which data flows, which compliance requirements, and what the release pipeline looks like. We deliver a concrete plan with scope, timeline and budget, so you can make an internal decision rather than having only a vague direction.

Then comes the build, in sprints. At the end of each sprint, something working runs on a staging environment: first limited, then increasingly complete. This helps to discover early what doesn't work in the design for the eventual user, to adjust priorities, and to bring stakeholders along. We work in your own repository, with code review, automated tests and a release process that fits your IT organisation.

After go-live comes maintenance and optimisation. Software needs upkeep: security patches, new versions of external APIs, performance tuning, user feedback and further development. We offer ongoing support or hand over cleanly to your own team, depending on what suits you. For some clients in the insurance and healthcare sectors, we have remained the long-term software partner; for others, we deliver and provide support on request.