Does Appfront work as a software developer in Haarlem?
Yes. Our office is on the Westerdoksdijk in Amsterdam, about 18 minutes' drive from Haarlem via the N200. We work with clients across North Holland, including Haarlem, Heemstede, Bloemendaal, Hoofddorp, Beverwijk and the wider Kennemerland region. Most of our work is remote-first; for strategic sessions, kick-offs and user testing, we are happy to visit you in person.
Which sectors in Haarlem do you build software for?
We work with media and publishers (Haarlem's graphic heritage is still very much alive), retail (the city centre and region, facing the challenge of a retail surplus), education (Hogeschool Inholland and arts education such as the Bavinck cluster), healthcare (the Spaarne Gasthuis catchment area, chains and practices), tourism (cultural institutions, attractions, hospitality) and the growing digital sector. We are broadly applicable but not tied to a single industry: a good architect first looks at the value chain, then at the sector-specific requirements.
What is the difference between building software and building an app?
Software is the broader term: web applications, back-ends, integrations, DevOps and, where needed, apps. An app is typically a mobile application specifically. For most Haarlem clients a mobile app is only one component of a wider software landscape, alongside a webshop, a back office and integrations with existing systems. For questions about mobile alone, see our
app page for Haarlem.
How much does a software project cost?
It depends on scope (a single application or a full suite), the number of integrations, compliance requirements and the degree of customisation. We work with sprint-based budgets and, after a short discovery phase, provide a concrete plan with a price for the whole project or the first phase. You will usually get an initial indication during the introductory conversation. We do not use fixed price lists, as no two projects are the same.
How long does a software project take?
This varies considerably. A simple integration or a small web app is a project of a few sprints; a complete custom suite with multiple modules and integrations takes several sprints back to back. We work iteratively, so at the end of each sprint there is something working, allowing you to steer scope and planning early on.
Do you come to Haarlem for sessions?
For longer projects, we schedule on-site sessions in Haarlem as standard — kick-off, design reviews, user testing and stakeholder meetings. For quick questions or short updates, we work through video calls. The journey from our Westerdoksdijk office in Amsterdam to Haarlem city centre takes about 18 minutes by car or half an hour by train, so it is practical to combine with a working day.
What about GDPR, ISO and NEN 7510?
From sprint one, we keep the right compliance in mind. GDPR is relevant to every application — think data minimisation, processor 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 documentation, logging and privacy by design into the work — not as a separate compliance phase at the end.
Which tech stack do you use?
We choose what suits each project. Back-end is usually TypeScript/Node.js, Python or .NET. Front-end is React or Vue. Database is PostgreSQL by default, otherwise wherever needed. Hosting on AWS, Azure or a Dutch cloud provider with EU residency. CI/CD via GitHub Actions, infrastructure-as-code via Terraform. For mobile: Swift, Kotlin, React Native or Flutter. We consistently work with open standards — no low-code platforms with vendor lock-in.
What happens after go-live — who maintains the software?
Software needs ongoing maintenance: libraries receive security updates, security issues arise, and users ask new questions. After go-live, you choose: an ongoing maintenance contract with us, a hybrid model in which your own team handles most things and we handle the more complex matters, or a complete handover to your internal team with a short transition period.
How does a project with Appfront begin?
With a
introductory call of half an hour (free) in which we discuss which problem you want to solve, which users will be using the software, and what a suitable first step is. This is followed by a paid discovery phase of a few days with a concrete plan and budget, or straight into a first build sprint if the use case is clear.