The question
Administration that passes through hands costs time that could have gone to customers. Kwakkel BV wanted to know whether that work could be automated, and did not want to take a report’s word for it. They wanted to see it.
What was there after six days
- A working prototype that processes administrative steps automatically, on Kwakkel BV’s own data
- A demo for the people who do the work today, so they could say what was still missing
- A business case on one page: what a full build costs, what it returns and when it pays back
How we approached it
We started with the people who do the administration, not with the technology. Which steps come back every day, where it goes wrong, what data already exists. Then we built the prototype in a six-day sprint, connected it to the real data and let it run alongside the current work.
On real data
No demo with invented examples. From day four the prototype processed Kwakkel BV’s actual administration.
Human in the loop
Every automated step can be traced and corrected. What the system is not sure about, it hands to an employee.
Business case first
Before any build decision, Kwakkel BV knew what the full version costs and what it returns.
Owned by Kwakkel BV
Source code, documentation and data model of the prototype belong to the client, even if the build does not go ahead.
The result
This is the way of working we have since called the start sprint: one week, fixed fee, a working prototype or build plan, always with the business case. Kwakkel BV was the first organisation where the current team did it this way.
About Kwakkel BV
Kwakkel BV is a Dutch SME whose administration grew with the organisation, and was therefore due for less manual work.
Want something like this built?
A start sprint is the first step: one week, fixed fee, a working prototype or build plan. Always with the business case included.
Plan a start sprint →
