Service · Web development

Software built around the way you work.

Custom software development for organisations that have outgrown off-the-shelf packages. We build web applications, mobile apps, backend platforms and integration layers — vendor-independent, with code ownership for you and a senior team based in Amsterdam.

Vendor-independentCode ownershipSenior teamEU data residency

Software isn't a product, it's the way your organisation works.

Companies rarely build custom software out of preference. More often it's out of necessity: an off-the-shelf package that is reaching its limits, a process that can't be forced into a SaaS template, or a commercial opportunity that depends on a digital product that doesn't exist yet. Choosing custom is then a rational decision — not an ambitious one.

We build software for mid-market SMEs, scale-ups and specialty organisations in sectors where off-the-shelf packages are too narrow: healthcare, financial services, logistics, industry and the public sector. Our position is deliberately mid-market: more pragmatic than a Big-4 consultancy, more senior than a freelance collective, and without the lock-in of a low-code platform. You keep the code, and we make sure it works — and keeps working.

On this page, the definition of "building custom software" stretches a long way. It could be an internal web application for your operations team, a customer portal that is part of your service, a mobile app for your field staff, or a platform your entire proposition runs on. It could be a new product that sits alongside existing systems, or a migration in which you replace a legacy system step by step. What all of these projects share: they can't be squeezed into a standard template, and you want to stay in control of what gets built.

On this page you can read about the kind of software we build, the tech stack we use, what our process looks like and how we differ from the alternatives. For a conversation about your specific situation, you can get in touch directly; for a broader overview of what we do, our services page is a good starting point, and for enterprise-scale projects we refer you to our page on enterprise software development.

This page is about custom software in general. Are you looking specifically for a web application, such as a portal or dashboard in the browser? Then see custom web application development. For a mobile app for iOS and Android: custom app development.

What falls under custom software development.

Three main directions in which most projects fall. A project often combines elements from several of them — a web application with a mobile companion, or a platform with a separate integration layer.

Web & mobile applications

Applications that work the way your people work

Custom web applications and mobile apps for processes that can't be forced into an off-the-shelf package. From customer portals and vendor portals to field-service apps, planning software and internal tools for operations. We build them as a single-page web app, native mobile, or a combination of both with a shared backend.

React / Vue / AstroReact Native / FlutterNative iOS / AndroidPWA
Backend platforms & APIs

The system everything runs on

The backend layer where your data, business logic and integrations live. Multi-tenant SaaS platforms, enterprise software serving multiple applications, customer portals, and the API layer that connects front-ends and external systems to the same source. Architecture that scales with your organisation — modular, observable and free of vendor lock-in.

Node.js / Spring BootPython / Django / FastAPILaravel / .NET / GoPostgreSQL / MongoDB
Integration, data & AI

The layers that hold your IT landscape together

An integration layer to ERP, CRM, accounting software and industry-specific systems. Data platforms for analysis, reporting or regulator reporting. AI integration where it adds business value — not as a gimmick, but as part of a workflow. And migrations: legacy systems that you phase out step by step without halting your operations. We often combine these layers with our software development projects into one coherent whole.

REST & GraphQLEvent-drivenAnthropic / OpenAILegacy migration

What you get at the end of a project.

No black box that only Appfront can look into, and no loose code without context. You get a working product plus everything you need to understand it yourself, manage it and — if it ever comes to that — have another party develop it further.

Code ownership isn't a marketing phrase for us, it's contractual. You own what we build for you, you get the repository under your own control, and we don't impose a mandatory maintenance contract that locks you in.

  • Production-ready softwareA working application with production and staging environments. Runs in your cloud (AWS, Azure, GCP) or hosted by us — your choice, no lock-in.
  • Complete codebase + documentationSource code in your own Git repository, with an architecture overview, build instructions and API documentation. No keys held by Appfront.
  • Test suite + CI/CD pipelineAutomated tests on the key flows and a deployment pipeline that lets your IT team release without us.
  • Admin & end-user manualsPractical runbooks for your administrators, short tutorials for end users — written for people, not for compliance tick-boxes.
  • Security & compliance auditPen test in the final sprint, a DPIA where the GDPR requires one, and compliance documentation for NEN 7510, ISO 27001 or DORA/NIS2 where relevant.
  • Maintenance & further development (optional)Monitoring, security patches and functional extensions at a transparent monthly rate — or you take it over with your own team.

Who we work for.

We build for organisations that need custom software because the standard market doesn't cover their problem. Four patterns we often come across.

Mid-market SMEs

Outgrown standard SaaS

Your organisation is hitting the limits of an off-the-shelf package: workflows that don't fit, integrations that don't exist, user numbers that make the pricing unsustainable. A platform of your own is then often cheaper and more flexible in the long run. We help you work out whether custom software is genuinely the right route in your situation.

Scale-ups

A product that is part of the proposition

You're not a software company by origin, but your customers expect a digital experience that sets you apart from the competition. You'd rather build that yourself than depend on a third-party SaaS. We think along at product level, not just at execution level.

Enterprise

Specific custom components

You have a large IT landscape with serious packages such as SAP or Salesforce, but one or two processes need something that doesn't fit into them. We build that custom layer, usually around an existing package rather than replacing it. Alignment with your architecture board and security requirements is standard.

Agencies & cooperatives

White-label or industry-specific

For agencies that want to deliver their own tool under their own brand, or for trade associations building a shared platform for their members. We deliver under your flag and you keep the client relationship. NDA and non-compete up front, and no mention in our portfolio without your explicit permission.

Specialist & regulated

Healthcare, finance, public sector, critical infrastructure

Sectors with sector-specific legislation: NEN 7510 in healthcare, DORA and NIS2 in finance, NIS2 for critical infrastructure, and e-government standards in the public sector. We build those requirements in from the design stage rather than bolting them on afterwards.

Migration projects

Legacy systems you're phasing out

An outdated system that has been building up technical debt for years and that nobody dares to replace. We do strangler-fig migrations: a new platform grows alongside the old one, takes over functionality step by step, and eventually the legacy system is switched off. No big bang, no panic-filled weekend.

The tech stack we work with every day.

We're not loyal to any one framework. The stack is chosen based on your situation: the IT landscape you already have, the people who will have to maintain it, and the demands the software itself makes. Below are the languages, frameworks and platforms our team is senior in.

Backend & API

Robust server-side foundations

For the backend we use Node.js (TypeScript) as our general workhorse, Spring Boot for Java-oriented organisations, .NET for Microsoft shops, Python (Django, FastAPI) where AI or data processing is central, Go for performance-critical services and Laravel where PHP expertise is already in place. APIs are REST or GraphQL, and event-driven where that fits. The choice isn't based on technology preference but on your situation: which languages your team masters, which ecosystem fits your existing integrations, and which skills are available on the Dutch labour market for future maintenance.

Node.js / TypeScriptSpring Boot.NETPython / Django / FastAPIGoLaravel
Frontend & mobile

Interfaces users keep coming back to

React and Vue are our most commonly used frontend frameworks, with Astro for content-heavy sites and Svelte where bundle size is critical. For mobile apps we work with React Native or Flutter when cross-platform is the right trade-off, and native (Swift for iOS, Kotlin for Android) when platform-specific performance or integrations call for it. Our app developers work with these every day.

ReactVueAstroReact NativeFlutterSwift / Kotlin
Data, cloud & DevOps

A platform you can manage

Databases: PostgreSQL is our default, MySQL where it fits, MongoDB for document-heavy models, Redis for caching and queuing, ClickHouse for analytics. Cloud: AWS, Azure or GCP — or Hetzner or a private cloud where EU sovereignty is a requirement. DevOps: Docker, Kubernetes where scale demands it, Terraform for infrastructure as code, GitHub Actions for CI/CD. AI integrations via Anthropic, OpenAI or open-source models (Llama, Mistral), depending on privacy requirements and use case. We have no reseller interest in any particular cloud or model provider, so our advice is based on what fits, not on margins.

PostgreSQL / MongoDBAWS / Azure / GCPDocker / KubernetesTerraformAnthropic / OpenAI

How we compare to the alternatives.

Building custom software is not your only route. It's a choice between four or five categories of supplier, each with a different profile. Here's how we position ourselves against each one.

vs standard SaaS

Salesforce, HubSpot, ServiceNow

We don't replace commodity software. What standardised SaaS does well, such as CRM, marketing automation and helpdesk, we don't rebuild. But the custom layer around it, the integrations and the specific workflows that don't fit the standard package: that's where we add value.

vs low-code

OutSystems, Mendix, Power Apps

Low-code is excellent for relatively simple internal tools. We build pro-code where low-code becomes too limiting: when you have complex business logic, unusual integrations, or demanding scale and performance requirements. No platform lock-in, and no seat licences that grow with your success.

vs offshore

India, Eastern Europe, Vietnam

Offshore rates are attractive; the real costs lie in coordination, time zones, language differences and the lack of EU jurisdiction. We work in the same time zone, speak Dutch with your stakeholders and fall under the same GDPR and liability regime as you.

vs Big 4 / freelance

Consultancy or secondment

The Big 4 deliver process and methodology at enterprise rates; we are more pragmatic and fit mid-market budgets. Freelance teams are flexible but fragile: if one senior leaves, your knowledge walks out the door. We provide team continuity at senior level.

How a project with us works.

We work in seven phases, from first introduction to ongoing maintenance. The phases are not strictly waterfall — building and testing overlap — but this is the order in which a project unfolds. You'll find a fuller explanation on our process page.

1

Introduction

A no-obligation conversation in which we learn what you want to build, why, and what your situation is. No pitch, no sales funnel — we look at whether there's a match and whether we can add value.

2

Discovery & scoping

Two to four workshops with your team and relevant stakeholders. We map out flows, integrations and risks, prioritise using MoSCoW (must / should / could / won't), and finish with a concrete scope, a phasing plan and a well-founded estimate.

3

Design: UX and architecture

A parallel track: a UX designer works on screen flows and interaction, while a tech lead works on the architecture and data models. By the end of this phase, the key screens are a clickable prototype and the technical blueprint is fixed.

4

Building in sprints

Two-week sprints, with a working build at the end of each one. You test along with us, and end users are involved early. We iterate on what actually matters most now, not on a list from a year ago.

5

Testing & pilot

A pilot phase with a limited group of real users, running in parallel with the final build sprints. We measure where people get stuck, fix what's needed and run a security pen test before go-live.

6

Rollout & go-live

A phased rollout — first one team, then one department, then the whole organisation — with monitoring from day one. Training sessions for key users and a runbook for your IT operations.

7

Maintenance & further development

After go-live: monitoring, security patches and functional extensions. Optionally through an ongoing contract with us, or you take it over with your own team — we arrange the handover in advance.

Who you'll speak to

Mies Brons

Your first conversation is with Mies Brons, business developer. Mies listens to what you want to build and why, and asks the questions needed to see whether custom software is right for you.

From discovery onwards, you work with the team that builds the software: a tech lead for the architecture and a UX designer for the screens, as in the phases above.

Book an introductory call with Mies →

Compliance & security: taken seriously, not a box-ticking exercise.

For the sectors we work in — healthcare, financial services, the public sector, critical infrastructure — compliance is not a formality. We build legal and sector-specific requirements into the design from the start, rather than adding them as a sticker at the end.

For enterprise projects, we contractually agree audit rights: you can audit (or have audited) our code, our processes and our infrastructure. EU data residency is standard — your data does not leave the EU unless you choose otherwise.

We shape compliance project by project, together with you and your data protection officer, legal adviser or sector regulator. We don't present a standard checklist that is identical for every client — that would mean not taking the regulations seriously. For healthcare, financial services and the public sector, we know the specific points of attention; for less regulated sectors, we limit ourselves to what is genuinely needed rather than what sounds good in marketing material.

  • GDPRDPIA where required, data minimisation, data processing agreement, right to erasure implemented technically.
  • NEN 7510 (healthcare)For healthcare organisations, we build in information security controls from the design stage, with audit trails on patient data.
  • ISO 27001 & SOC 2For enterprise clients running their own ISO/SOC programme, we deliver a compliant software chain, including evidence for your auditor.
  • DORA & NIS2For financial institutions and critical infrastructure organisations: incident reporting, ICT risk management and third-party risk built in from the design stage.
  • EU AI ActFor AI components: risk classification, transparency requirements, logging and human oversight built in.
  • EU data residencyData and backups in EU regions, under EU jurisdiction. No US subprocessors without an explicit assessment.

Frequently asked questions.

What clients ask before we start on a project.

What exactly falls under custom software development?
Quite a lot: custom web applications, mobile apps, backend platforms, customer and vendor portals, multi-tenant SaaS, integration layers between existing systems, data platforms, AI integrations, and migration of legacy software to modern stacks. Often a combination of several — for example, a web app with a mobile companion and an API layer connecting to your existing systems.
Do you replace standard SaaS such as Salesforce or HubSpot?
Not for commodity functionality. We wouldn't rebuild a good CRM or marketing automation tool from scratch — that would be a waste of your money. What we do build is the custom layer around it: workflows that don't fit the standard product, integrations with your industry-specific systems, and tailored user interfaces for your roles.
What is the difference compared with low-code platforms such as OutSystems or Mendix?
Low-code is fast and well suited to relatively simple internal tools. Pro-code (what we do) is suited to more complex logic, unusual integrations, external users, and anything where performance, scalability or platform freedom matters. There is also the lock-in: with low-code you are tied to the platform and its licence costs. With us, you own the code and pay no per-seat licences.
What determines the cost of a custom project?
The biggest factors are scope (how much functionality), integration complexity (one external system or five), compliance requirements (healthcare or financial services is different from an internal tool), and the scale you need (internal for 50 users or public for 50,000). In the introductory and discovery phase, we combine these factors into a well-founded estimate with a phased plan — not an open-ended budget.
How long does a project usually take?
That depends heavily on the scope. A first working version is often ready after a few sprints; a production-ready platform with integrations and compliance requirements takes a programme of several sprints. We deliberately work iteratively: you get a working build after every sprint, so there is always something to show, test and use to decide where the priorities lie.
How is the team put together?
A typical project has a product owner / business analyst, a tech lead, one or more engineers (depending on scope), a UX designer where relevant, and a QA role. All are senior or mid-level — no juniors learning to code on your project. The team is a fixed group; we offer team continuity, not secondment.
What does vendor independence mean in practice?
We are not a reseller or partner of Mendix, OutSystems, SAP or any other specific platform, which means our advice isn't driven by licence discounts or partner quotas. We choose the stack based on your situation, not on what suits us commercially. The same goes for cloud providers: AWS, Azure, GCP or an EU provider, depending on what fits.
What if we ever want to continue with another party?
That should be possible without any hassle. You own the code from day one, the repository is under your control, and we provide documentation and runbooks that allow another party to take over. We have no commercial interest in locking you in. If the match is no longer right, we'll arrange a clean handover.
Do you only build software, or do you also provide maintenance?
Both, and you choose. Many clients take out a maintenance agreement after go-live for monitoring, security patches and functional development. Other clients maintain it themselves with their own team and only call us for larger extensions. We don't make a maintenance contract a condition of the build.
Do you also work with our internal IT or dev department?
Almost always. We transfer knowledge throughout the entire project, not just at the end, so that your team builds along, reviews along and can ultimately maintain it themselves. For enterprise clients that often means a joint team; for SMEs a lighter version with handover sessions and pair programming on critical parts.

Talk to us about your software challenge.

A no-obligation half-hour conversation. We listen to what you want to build, ask questions where things could be sharper, and offer direction where we have it. No pressure for a quote, no sales funnel.

Would you like to look at this challenge from the custom software angle? On applatenmaken.com you'll find a write-up on building custom software.

Want to start a project?

We'd love to hear from you.

Long story, or would you otherwise have emailed it? Choose Detailed briefing: headings and bullet lists, images in the text and attached files.

Mies

Contact Mies

Business Developer

Contact Martijn

Founder of Appfront

Martijn

Your message has been sent

Thanks for your interest! We'll get back to you as soon as possible, usually within 1 working day.

Edit content