From the first introduction to live software and ongoing maintenance. No six-month waterfall method without a demo, and no vague 'agile' talk; instead, short sprints with real deliverables, open communication, shared access from day one and code ownership for your organisation. On this page we explain the seven phases, what we pay particular attention to and what we deliberately do not do.
We work in short sprints with a fixed rhythm of planning, building, demo and retrospective. Every sprint delivers something that works: no surprise launch after half a year of silence, and no 200-page report without any code. We put your goals first and tell you straight if an approach won't work or a feature isn't worth the effort. That is where the value of a senior team lies: you get people who dare to think along with you, not just carry out instructions.
From day one, you have access to the repository, the project board and the design files. We are vendor-independent: no reseller deals with platform providers, and no disguised lock-in through a proprietary platform that only we can operate. What we build belongs to you. If you want to continue with a different team tomorrow, you can do so without a migration headache. That attitude runs through every phase: in the choice of stack, in how we document, and in which dependencies we do or don't bring in.
What you won't get from us: secondments with juniors learning on your budget, no-code wonder promises for situations where no-code is not the answer, or upfront time and price guarantees without us knowing the context. What you will get is a senior team that takes responsibility for what goes live, with an ongoing security baseline and compliance as a standard layer under every project, not as an extra line item on the invoice afterwards.
The page below walks you through all seven phases: from a no-obligation introductory conversation, through discovery and design, to building in sprints, testing and the pilot, the rollout and the ongoing management afterwards. We then explain what sets us apart, what we deliberately don't do, which tools we work with, and how we handle compliance and confidentiality. If, after reading, you have questions that aren't covered in the FAQ, the easiest way to reach us is a short introductory call: no intermediate step, no sales layer.
A short first call, free and non-binding, at an unhurried pace. You tell us about the challenge and we ask questions to properly understand the context. No sales pressure, no quote form, no sales tricks. Together we establish whether there is a fit in terms of sector, complexity and approach. If it doesn't click, we will say so honestly and, where possible, point you in the right direction. The next step is a discovery project, or no step at all.
A workshop with your team to get clarity on pain points, business goals and stakeholders. We map the technical, data and IT landscape and, where useful, speak with end users or the service desk. This is followed by MoSCoW prioritisation, in which must, should, could and won't items are explicitly recorded. The result: a scope document, a target architecture and an honest quote with assumptions per phase.
UX research, wireframes and interactive Figma prototypes: you review and steer before a single line of production code is written. In parallel we work on the technical architecture: services, data models, integration patterns and a security baseline. The compliance overlay (GDPR, sector-specific where needed) runs through this from the start, not as a separate step at the end. The result: design files and an architecture document.
We build in short sprints with sprint planning, sprint review and retrospective at fixed moments. Every sprint includes a demo of working software in your own repository, with no waiting for the final delivery. Pair programming and code review are standard, with test-driven development where it makes sense. Communication runs via Slack or Teams with a weekly stand-up; questions are answered quickly and decisions are recorded openly.
A test suite of unit, integration and end-to-end tests that evolves alongside the code, rather than being a separate step at the end. Performance measurement with Lighthouse, k6 or JMeter, and security scans via SAST, DAST and dependency checks built into the pipeline. First a beta with your own team, then a pilot with a group of end users, and a bug-fix loop for the issues that only surface in real-world use. The result: production-ready software with a candid overview of what has and hasn't been tested.
A rollout plan suited to your situation, whether big-bang or phased, depending on risk and your organisation. Data migration where needed, training for your team, a roll-back plan worked out in advance and clear responsibilities during go-live. We stand by during the first hours and days live, with a direct line to the people who wrote the code. You won't go live alone: we remain on standby until the system runs stably and operations can be handed over to your team.
Optional managed services with a bug-fix SLA, 24/7 monitoring where required, and alerting through your own channels. For ongoing development, a fixed feature velocity per sprint, monthly reviews with your stakeholders, and always the option of a phased handover to your own team. No contract lock-in and no mandatory minimum monthly commitment: you pay for what you use and can scale up or down whenever the business requires it.
An honest overview of where our value lies and where other parties are a better fit. We aren't the right partner for everyone, and we're upfront about that from the outset so you don't lose time to a mismatch.
No reseller deals with Mendix, OutSystems or SAP. We recommend what fits, not what earns us a commission; the choice of platform or stack is your decision, with our reasoning alongside it.
All code in your own GitHub or GitLab from the very first commit. No black box, no exit fee if you choose to leave, and no hidden licences on 'proprietary frameworks'.
We don't send a junior along to learn on your budget. The people you meet during the introduction are the ones who actually build the system with you.
Working software over thick reports. We write documentation where it helps, for onboarding, security reviews or handover, rather than to fill hours.
We build as well. A report without working code isn't a deliverable in our book; pure strategy consultancy is a different discipline, and other firms are better at it.
We are a development team, not a staffing agency. Don't expect a junior wandering around with your badge and sending you a monthly timesheet without context or direction.
No-code has its place for simple internal tools. It isn't the answer for a complex domain with integrations, strict security requirements or large user numbers.
We don't give hard week or month guarantees without understanding the context. First a discovery phase, then an honest plan per phase with assumptions we state openly.
Daily contact via Slack or Teams: no ticketing system for simple questions, and no email chain for decisions that can be made in five minutes. One fifteen-minute weekly stand-up and a sprint review with a demo at the end of every sprint. The backlog is visible to everyone in Jira or Linear, and decisions are recorded openly so that colleagues who join later can follow what was chosen and why.
GitHub or GitLab with your organisation as the owner of the repository. Figma with your team as editors, not just viewers. Sentry or Datadog for monitoring and alerting through your own channels. You have access to everything from day one: no detour via us, no queue for a password reset. We work in your environment, not the other way round.
We work in line with the GDPR and, where relevant to the sector, NEN 7510 or ISO 27001 practices, with attention to data classification, access control and logging from the first sprint. Penetration testing on critical components, client audit rights written into the contract, and dependency scans as a fixed part of the CI pipeline. For us, compliance is a design layer, not an audit exercise after the fact.
A half-hour introductory conversation in which we go through where you are now, what you want to achieve and whether our approach suits your situation. No sales pitch, no obligation, no pre-cooked proposal, just an honest conversation in which we take the time to understand your context. If it's a good fit, we'll look together at a discovery project; if not, we'll say so and help you on your way.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
