We are a small studio that writes software for companies
Much of our work started in rental, fleet management and logistics, where one wrong piece of data turns into an unpaid fine or a car returned without a handover report. Today we also work for companies that make things, sell or offer services, and the method has stayed the same.
We are small on purpose. The person who asks you questions on the first call is the same person who writes the code and answers you when something goes wrong.
How we think
- We tell you when you don't need it
- If the problem can be solved with a better spreadsheet or a program that already exists, we tell you. We earn less today, but you call us again next time.
- A price, not a range
- The quote comes after we have seen the work, with one amount and one date. If the requirements change, the quote changes too, and you decide that up front instead of finding out at the end of the month.
- The code is yours
- The program's code, documentation and access stay with your company. You can carry on with us or with anyone you like, without rewriting anything.
- We measure afterwards too
- Before we start, we pick two or three numbers to keep an eye on, such as the hours spent on a task or the errors per month. After delivery we look at them again together.
How we work, week by week
From first contact to software in use. For each stage you see what we do, what you get and how much of your time we need.
First callDay 1
- What happens
- You tell us about the process that wastes the most time. We tell you honestly whether it's worth automating.
- What you get
- A clear answer: yes, no or not yet.
- Your time
- 15 minutes on the phone
Process analysisWeek 1
- What happens
- We look at how you work today, measure the hours lost and agree together on the numbers to keep an eye on.
- What you get
- A detailed quote, a timeline and the numbers we agreed on.
- Your time
- A couple of hours with the people who do the work
PrototypeWeek 2
- What happens
- We design a clickable prototype with your data, before writing the final code.
- What you get
- A prototype to try out with your team.
- Your time
- One hour to tell us what to change
DevelopmentWeeks 3–7
- What happens
- We build in two-week cycles: at the end of each one we show you what's ready and you try it.
- What you get
- A trial version you can use whenever you like, and progress you can always see.
- Your time
- Half an hour every two weeks
LaunchWeek 8
- What happens
- We get the software running, move your data over and train the people who'll use it every day.
- What you get
- Software in use, documentation and user guide.
- Your time
- Half a day of training
SupportFrom week 9
- What happens
- We look at the numbers set at the start together, fix what isn't working and add what everyday use brings up.
- What you get
- Regular reports on hours saved and errors avoided.
- Your time
- One call a month
Indicative timings for a medium-complexity project. Simple projects: 2–4 weeks. Complex projects: 2–3 months.
Let's see if we can help
Fifteen minutes on the phone: you describe the process and we tell you plainly whether it's worth working on.