Let the system do what is now done by hand
I learn how your processes work, take the manual labour out of them and make the technical decisions that now sit waiting. One process at a time, and something goes live every month.
- Too much happens by hand
- Nobody leads the technology
- AI was promised, not delivered
- now
- The schedule is retyped into the hours module by hand every day.
- then
- The schedule writes the hours itself; the employee only confirms.
- yields
- Three quarters of an hour a day and no more typing errors in the invoices.
- way back
- Runs alongside the current process and reverts with one click.
Examples for a fictional company.
Three documents that carry the rhythm
| action | how often | costs |
|---|---|---|
| Retyping hours from the schedule | daily | ± 45 min |
| Assembling quotes in Word | weekly | ± 3 hours |
| Checking invoices for travel hours | monthly | ± 4 hours |
| Answering customer questions by e-mail | daily | ± 30 min |
Candidate list
The result of month one: which actions cost time, how often and how long, ranked by what automating them yields.
- now
- The schedule is retyped into the hours module by hand every day.
- then
- The schedule writes the hours itself; the employee only confirms.
- yields
- Three quarters of an hour a day and no more typing errors in the invoices.
- way back
- Runs alongside the current process and reverts with one click.
Proposal per initiative
One page per process: what happens now, what the system will do, what it yields and how we roll back.
- Hours from the schedule are now ready automatically; you only confirm.
- A quote becomes a branded PDF with one click.
- Searching customers is faster and also matches on postcode.
Release note per delivery
Your users hear in their own words what is new. A message you can forward.
Examples for a fictional company. Yours will hold your processes and your numbers.
From shadowing to measurable
I bring the proposals, with what they yield attached. You decide which go ahead; you never have to steer on technology.
-
Shadow and measure
month 1I record where the time leaks away: which action, how often, how long. At the end there is a candidate list.
-
First process live
month 2We pick one, I build it, and it goes live alongside the existing process. You see the difference against the measurement.
-
Rhythm
month 3 onwardsA next process every month, plus maintenance of what already runs. Each process goes live on its own and rolls back on its own.
One fixed monthly fee
No timesheets, no reconciliation. The fee scales with what there is to do, the rhythm does not.
per month, excluding VAT
- Contact every week, something live every month
- Building, maintenance and further development in one
- Technical decisions, not just execution
- Minimum of 3 months, monthly notice after that
When I can start
I take on a limited number of partnerships at a time. This is what is free per week, updated by hand.
Next start: Jan 2027, 3 days a week.
Updated 25 August 2026Nothing to build and your software mostly has to keep running? Then maintenance with a support desk is the cheaper shape. See maintenance with a support desk
One person, with a mandate and without an agency
I am Mathijs Oggel, and for ten years I have built and led software platforms, from first idea to product with real users. Code, data and documentation are in your name, and at the start we agree who takes over if I am out for longer.
Book a thirty-minute call
No obligation. In thirty minutes you know whether this model fits you. If not, I will say so.
Loading the calendar_