Way of working · Sprint-based

Our process.

From first meeting to live software and ongoing maintenance. No six-month waterfall without a demo, no vague 'agile' story. 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 extra attention to and what we deliberately don't do.

TypeSprint-based project
First callFree & no obligation
Sprint cadenceShort & iterative
DemoEvery sprint
CodeIn your repo
Lock-inNone

Client first, honest about what works.

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 six months of silence, no 200-page report without code. We put your goals first and tell you when an approach doesn't work or a feature isn't worth the effort. That is also where the value of a senior team lies: you get people who dare to think along with you, not just carry out instructions.

You get access to the repository, project board and design files from day one. We are vendor-independent — no reseller deals with platform vendors, no disguised lock-in through a proprietary platform that only we can access. What we build is yours; if you want to continue with another team tomorrow, you can do so without migration drama. That attitude runs through every phase: in the stack we choose, how we document, and which dependencies we do or don't bring in.

What you won't get from us: secondments of juniors who learn at your expense, no-code miracle promises for situations where no-code is not the answer, or up-front time and price guarantees before we know the context. What you will get: a senior team that takes responsibility for what goes live, with a continuous security baseline and compliance as a standard layer under every project — not as an extra invoice line afterwards.

The page below walks through all seven phases — from a no-obligation introduction, through discovery and design, to building in sprints, testing and the pilot, the rollout and the ongoing support 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 you have questions after reading that aren't covered in the FAQ, the easiest way to reach us is a short introductory call — no intermediate step, no sales layer.

7
Phases: from introduction to further development
Sprint-based
Fixed rhythm of planning, demo and retro
Senior
No school where juniors learn at your expense
Your own repo
You own the code, no lock-in

The first four phases.

01
Phase 1 — Introduction

A conversation without obligation

A short first call — free and non-binding, at an unhurried pace. You tell us about the challenge, and we ask questions to understand the context properly. No sales pressure, no quote form, no sales tricks. Together we decide whether there is a fit in terms of sector, complexity and approach. If it doesn't click, we'll say so honestly and point you elsewhere where possible. The next step is a discovery phase — or no step at all.

02
Phase 2 — Discovery

Workshop, pain points and scoping

A workshop with your team to get pain points, business goals and stakeholders clear. We map the tech, data and IT landscape and speak (where useful) with end users or the service field. This is followed by a MoSCoW prioritisation in which must/should/could/won't are explicitly recorded. Result: a scope document, target architecture and an honest quote with assumptions per phase.

03
Phase 3 — Design

From wireframe to architecture

UX research, wireframes and interactive Figma prototypes — you look on and steer along before a single line of production code is written. In parallel, we work on the tech architecture: services, data models, integration patterns and a security baseline. The compliance overlay (GDPR, sector-specific where needed) runs through it from here on, not as a separate step at the end. Result: design files and an architecture document.

04
Phase 4 — Build

Short sprints with demo and review

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 — no waiting for the final delivery. Pair programming and code review are standard, test-driven where it makes sense. Communication runs via Slack or Teams with a weekly stand-up; questions are answered quickly, decisions recorded openly.

Testing, rollout and further development.

Phase 05

Testing & pilot

A test suite with unit, integration and E2E tests that evolves alongside the code rather than being bolted on as a separate step afterwards. Performance measurement with Lighthouse, k6 or JMeter, and security scans via SAST, DAST and dependency checks in the pipeline. First a beta with your own team, then a pilot with a subset of end users and a bug-fix loop for the issues that only surface in real-world use. The result: production-ready software with an honest overview of what has and hasn't been tested.

Phase 06

Rollout & go-live

A rollout plan that fits your situation: 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're on hand during the first live hours and days, with a direct line to the people who wrote the code. You don't go live alone; we stay on standby until everything is running stably and operations can be handed over to your team.

Phase 07

Maintenance & further development

Optional managed services with a bug-fix SLA, 24/7 monitoring where needed and alerting through your own channels. For ongoing development, a fixed feature velocity per sprint, a monthly review with your stakeholders and always the option to hand over to your own team in phases. No contract lock-in, no mandatory monthly minimum: you pay for what you use and can scale up or down whenever the business requires it.

What sets us apart, and what we don't do.

An honest overview of where we add value and where other providers are a better fit. We're not the right partner for everyone, and we're upfront about that so you don't lose time on a mismatch.

Vendor-independent

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.

Code ownership

All code in your own GitHub or GitLab from the first commit. No black box, no exit fee if you want to leave, no hidden licences on 'proprietary frameworks'.

Senior team

We don't send a junior along to learn at your expense. The people you meet during the introduction are the ones who actually help build the system.

Pragmatic

Working software over hefty reports. We write documentation where it helps, for onboarding, security reviews or handover, not to pad out hours.

Not advisory only

We build as well. A report without working code isn't a deliverable to us; pure strategy consultancy is a different trade, and other firms are better at it.

No secondment in disguise

We're a development team, not a staffing agency. Don't expect a junior walking around with your badge who sends you a monthly timesheet without context or direction.

No no-code miracle

No-code has its place for simple internal tools. Not as a solution for a complex domain with integrations, strict security requirements or large numbers of users.

No blind promises on timing

We don't give hard week or month guarantees without knowing the context. First a discovery, then an honest plan per phase, with assumptions we state openly.

Communication, tools and guarantees.

Communication

Slack, Teams and a weekly stand-up

Daily contact via Slack or Teams: no ticket system for simple questions, no email merry-go-round for decisions that take 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.

Tools & access

Code in your repo, design in your Figma

GitHub or GitLab with your organisation as the owner of the repository. Figma with your team as editors, not spectators. Sentry or Datadog for monitoring, with alerting through your own channels. You have access to everything from day one: no detour via us, no waiting for a password reset. We work in your environment, not the other way around.

Compliance

GDPR, NEN 7510 and ISO 27001 approach

We work in line with the GDPR and (where relevant to the sector) NEN 7510 or an ISO 27001 approach, with attention to data classification, access management and logging from the very first sprint. Penetration testing on critical components, customer audit rights in 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.

Frequently asked questions.

How long does an average project take?
That depends heavily on scope, integrations and the level of compliance required. A first working version can be live after a few sprints; a full enterprise project runs over several sprints, followed by ongoing development. After the discovery phase we give you an honest plan per phase, and not before. We deliberately don't make blind promises on timing before we know the context; in our experience that has more often led to disappointment than to a healthy project.
What determines the cost?
Scope, complexity, number of integrations, security requirements and sprint cadence together determine the budget. We work with a fixed sprint budget so you can adjust per sprint: smaller if the business calls for it, larger around a go-live moment. After the discovery phase you receive a concrete quote with scope and assumptions per phase. No open-ended commitments, no surprises along the way and no hidden extra-work tricks.
Which tools do you use?
Slack or Teams for day-to-day contact, Jira or Linear for the backlog, GitHub or GitLab for code, Figma for design and Sentry or Datadog for monitoring. The application stack itself depends on the project, often TypeScript with Node or Python, with PostgreSQL or a comparable database. We never push a specific platform vendor on you for commercial reasons; we choose what fits your context and team.
Will we have full ownership of the code?
Yes, always. The code lives in your own GitHub or GitLab organisation, and you are the owner from the first commit. We don't build anything on a platform that you can only access through us: no lock-in, no exit fee, no disguised licensing structure. If you want to continue with another team after delivery, you can do so without migration drama; all documentation lives in the repo, not in our heads.
Can you work with our internal team?
Yes, and we often do. Pair programming, shared code reviews, joint sprint planning and a phased handover to your own team are a standard part of many projects. We're not afraid of making ourselves redundant; in fact, a successful project often ends with a team on your side that can carry on independently. Between one extreme and the other, we adapt to your situation.
What about confidentiality and data?
We sign an NDA as standard before the discovery phase begins. Employees and freelancers work under a confidentiality clause that continues after the project ends. Customer data stays in your environment; we only get access to what is strictly necessary and only for the duration of the project. In sensitive sectors (healthcare, finance, government) we work with separate test data, masked production copies or synthetic datasets.
How do we get started?
The easiest way is an introductory call: half an hour, free, no obligation. We listen to the challenge and decide together whether a discovery phase makes sense. Schedule a call via the contact form or email Fabian directly. You'll get a reply within one working day, and if it turns out we're not the right party, we'll say so.

Talk to us about your project.

A half-hour introduction in which we go through where you stand now, what you want to achieve and whether our approach fits 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 fits, we'll look at a discovery phase together; if it doesn't, we'll say so and help you on your way.

Reply within 1 working day
No-obligation conversation
Westerdoksdijk 599, Amsterdam

Edit content