From bottleneck to prototype in 10 working days.
I come to you for the first day to see how one of your processes really runs. The rest we do by video: we measure how long it takes today, and your team tests a prototype with real cases. At a fixed price, with a clear result. And if it isn’t worth it, I’ll tell you.
Does one of these sound familiar?
“Writing a quote takes us days.”
“We retype data from one system into another.”
“Only two colleagues know how it works.”
“Our legacy system won’t last much longer.”
“We pay for software that only half fits us.”
Ten working days, one clear result.
One day on site, the rest by video and screen sharing. On-site work in the Ruhr area and North Rhine-Westphalia is included; elsewhere we agree travel costs in advance.
- Before
Preparation
You name a process and a person who knows it. There is nothing else to prepare.
- Day 1
I watch
on siteA day on site, next to the people who do the work.
- Day 2
We measure
by videoHow long does it take today, and where do errors happen?
- Day 3
We choose
by videoOne step that pays off first. And honestly: whether it pays off at all.
- Days 4–5
We write down how to tell it’s finished
by videoA simple list you can check. It belongs to you.
- Days 6–9
Prototype
by videoYour team tests it with 5 to 10 real cases, by video and screen sharing. The software does the work, your people check and approve.
- Day 10
Results meeting
on site recommended, video possibleWhat it costs, what it brings, how to continue. Or that it isn’t worth it.
Afterwards: if you go ahead, I build the solution in stages you sign off one by one, then run it: hosted in Germany, with backups, updates and monitoring. Just like our own products.
Short answers.
I describe the method behind the sprint in my (German-language) book “SaS – Ein ‚a‘ weniger”.