Does Appfront work as a software developer in Haarlem?
Yes. Our office is on the Westerdoksdijk in Amsterdam, about an 18-minute drive from Haarlem via the N200. We work for clients across North Holland — Haarlem, Heemstede, Bloemendaal, Hoofddorp, Beverwijk and the wider Kennemerland region. Most of our work is remote-first; for strategy sessions, kick-offs and user testing we're happy to come to you.
Which sectors in Haarlem do you build software for?
We work for media and publishers (Haarlem's graphic-industry DNA lives on), retail (the city centre and a region facing a retail surplus), education (Hogeschool Inholland and arts education such as the Bavinck cluster), healthcare (the Spaarne Gasthuis catchment area, care chains and practices), tourism (cultural institutions, attractions, hospitality) and the growing digital scene. We're versatile but not tied to any one industry — a good architect looks at the whole chain first, then at the sector-specific details.
What is the difference between building software and building an app?
Software is the broader term: web applications, back-ends, integrations, DevOps and, where relevant, apps too. An app is usually a mobile application specifically. For most Haarlem clients, a mobile app is just one component of a wider software landscape, alongside a webshop, a back office and integrations with existing systems. For purely mobile questions, see our
app page for Haarlem.
What does a software project cost?
That depends on scope (a single application or a whole suite), the number of integrations, compliance requirements and the degree of customisation. We work with sprint budgets and, after a short discovery phase, give you a concrete plan with a price for the whole project or for the first phase. You will usually get a first indication in the introductory call. We don't work with fixed price lists because no two projects are the same.
How long does a software project take?
That varies a great deal. A simple integration or a small web app takes a few sprints; a complete custom suite with several modules and integrations takes many sprints in succession. We work iteratively, so there is something working at the end of every sprint and you can adjust scope and planning early on.
Will you come to Haarlem for sessions?
For longer projects, we schedule on-site sessions in Haarlem as standard: kick-off, design review, user testing and stakeholder meetings. For one-off questions or short updates, we work via video sessions. The journey from Amsterdam-Westerdoksdijk to Haarlem city centre takes about 18 minutes by car or half an hour by train, so it fits easily into a working day.
What about GDPR, ISO and NEN 7510?
From sprint one, we build with the right compliance in mind. GDPR is relevant to every application, including data minimisation, data processing agreements and data residency. For healthcare software, NEN 7510 applies on top of that, and sometimes MDR considerations. For financial applications, DORA and PSD2 come into play. We build in documentation, logging and privacy by design from the start, rather than treating compliance as a separate phase afterwards.
Which tech stack do you use?
We choose what fits per project. Back-end is usually TypeScript/Node.js, Python or .NET. Front-end is React or Vue. The database is PostgreSQL by default, or something else where needed. Hosting is on AWS, Azure or a Dutch cloud provider with EU residency. CI/CD runs via GitHub Actions, with infrastructure as code via Terraform. For mobile: Swift, Kotlin, React Native or Flutter. We consistently work with open standards, with no low-code platforms and no vendor lock-in.
What happens after go-live, and who maintains the software?
Software needs ongoing maintenance: libraries receive security updates, security issues come up and users raise new questions. After go-live, you choose between an ongoing maintenance contract with us, a hybrid model in which your own team is responsible for most things and we handle the more complex matters, or a complete handover to your internal team after a short handover period.
How does a project with Appfront begin?
With a free, half-hour
introductory call in which we go through the problem you want to solve, which users will use the software, and what a suitable first step would be. This is followed by a paid discovery phase of a few days with a concrete plan and budget, or straight away by a first build sprint if the use case is clear.