Stop retyping: one simple program instead of loose lists.
Do you type the same data into two systems, or has your spreadsheet grown so big nobody dares touch it? There is usually a small program that can take the work over, without turning your whole business upside down. I build it. With AI assistants there is a working proof of concept to review within days, checked and tested by me.
- Based in
- Enschede, NL
- Works in
- Netherlands and Belgium, remote. On site in Twente
- Approach
- The chore that costs the most time, first
- First step
- A 20-minute intro call
Manual work a computer does better.
Many businesses run on an accounting package, a web shop, a planner and a handful of spreadsheets that all stand apart. Someone retypes the data, and now and then something goes wrong.
I first look at what happens now and which chore costs the most time. I solve that one first, so you notice the difference quickly. You need no technical knowledge, I explain everything in plain words.
A simple program for the way you work.
It is usually one of these four things.
A link instead of retyping
Your web shop, accounting and planner talk to each other, so data is entered only once.
A spreadsheet that got too big
What started as a spreadsheet becomes a simple program with a login, a clear overview and fewer mistakes.
A tool for one chore
A registration, a request form or an overview for your team, exactly the way you work.
A program of your own instead of a package
If you only use a small part of a big package, I build just what you need.
AI as a working method.
I work with AI assistants, but I do not sell them as a service. They take over the routine work, so a working prototype of the most important part can be running within days. I decide how it is put together and read and test every line myself. A proof of concept is not a finished product: real use still needs testing, security and review.
Tracker, my own tool for tracking work and bugs, had login by emailed code and data import and export on day one, and was live. I built a registration app for a school the same way.
Look first, then build.
Four steps, without technical talk.
Intro call
A 20-minute call: what do you do by hand now, and what costs the most time?
Look together
I look at how the work goes now and suggest what to replace first.
First version
Within days a working prototype you can try yourself.
Start using it
I explain how it works and your team uses it. After that you can let it grow or leave it as it is.
Simple programs with one purpose.
Two examples of programs I built for a clearly bounded purpose.
A registration app for a school
An app for a school in which data is registered. Built with AI-assisted development, checked and tested by me.
Tracker
A program of my own for keeping track of work and bugs, just the way I work. Built for one purpose, with public source code.
Work that could go faster?
Tell me what is done by hand now. I will say honestly whether a program is worth it, and I usually reply within one business day.