Software developer Duivendrecht.

A software developer builds the digital infrastructure your organisation runs on, usually a set of connected components rather than a single closed product. For a financial services provider along the Holterbergweg or in the Bullewijk cluster, that typically means a client portal that talks to a policy administration or core banking system, with audit logging, MFA and strict authorisation. For a logistics player with a depot or cross-dock in Duivendrecht, it means a dashboard that brings WMS, TMS and EDI integrations together into one operational view. For a retail fulfilment organisation, it means a back office that consolidates orders from multiple channels and connects to the warehouse stack. For a SaaS provider, it means a multi-tenant platform with tenant isolation, billing and API access for customers.

At Appfront, we cover the full landscape: web applications, custom back-ends, integrations, client portals and the related DevOps. We are a building agency, not a pure strategy consultancy and not a loose freelance layer, with a senior Dutch team that writes the code, deploys it to production and maintains it themselves. No body-shopping, no offshore cascade.

Duivendrecht is physically close to our Amsterdam office and sits on the financial, data and distribution backbone of the south-eastern flank. In practice, this means we can easily join stakeholder sessions, user testing or architecture reviews. You can find the full range of services on the locations hub; the neighbouring Amsterdam mobile page is at app developer Amsterdam.

Software in production is more than an attractive front end. It has to work during peak traffic on a claims portal after a hailstorm, during the monthly batch run that rolls out a TMS update, and at the first serious marketplace peak for your fulfilment stack. We work per project with a suitable stack: TypeScript/Node.js or Python for back ends, .NET where the Microsoft ecosystem leads (for many financial clients, that is the starting point), React or Vue for front ends, and PostgreSQL as the standard database. For mobile components: Swift, Kotlin, React Native or Flutter.

Hosting on AWS, Azure or Dutch cloud with EU data residency. CI/CD via GitHub Actions or Azure DevOps, infrastructure as code via Terraform or Bicep, and monitoring tuned to your scale and compliance context. An insurer with DORA requirements has a different stack question than a SaaS scale-up, so we make those choices explicit and document the reasoning in writing.

For AI systems, such as a claims classifier, a document processor, a copilot for advisers or agents, we work with retrieval-augmented generation on your own content, with evaluations and consent built in from sprint one. For financial clients we pay attention to DORA and EBA guidelines, for logistics to EDI standards, and for multi-tenant SaaS to the familiar isolation and billing questions. Documentation, audit trails and privacy by design are handled from the outset.

A project starts with an introductory meeting: half an hour in which we go through the problem you want to solve, for which users, and which systems are already in place. The conversation is free and without obligation. Sometimes the outcome is that an existing package or a supplier portal extension is enough. Sometimes it is that custom really is the right answer, for example because no standard package covers the audit and authorisation requirements of your claims flow, or because your fulfilment orchestration across multiple marketplaces is so specific that standard middleware cannot provide a suitable mapping.

For a suitable use case, we plan a discovery: a short phase in which we sharpen the solution. That covers which modules, which integrations (policy administration, core banking, ERP, WMS, TMS, EDI, EHR, marketplace APIs), which compliance requirements (DORA, GDPR, NEN 7510, ISAE 3402), and which user roles and authorisation matrix. We deliver a concrete plan with scope, timeline and budget so you can make an internal decision.

Next comes the build, carried out in sprints. At the end of each sprint, something working is running, starting limited and becoming more complete over time. This helps us discover early what doesn't work in the design for the adviser behind the portal, the planner in the distribution centre, or the customer opening their policy overview on a mobile phone. We work in your own repository, with code review, automated testing and a staging environment you can use yourself.

After go-live comes maintenance and further development. Software requires ongoing care: security updates, user questions, new requests and audit reporting. You choose: continued support from us, a hybrid model, or handover to your own team. Some financial and logistics clients have remained our long-term software partners; for others, we deliver and provide support on request.