Sometimes you don't need software but a clear answer: which way do you want to go, what is the actual problem, and what does it cost to leave it as it is?
Often the question isn't for a new system but for a decision.
Which stack fits this scale, why won't system A work with system B, is this still maintainable, and what is better left alone? I come from both the factory floor and the software side, so I look at what is actually workable in practice, not only at what is technically possible. I don't sell licences and have no stake in any vendor.
What's going on, who is affected by it, and what has already been tried?
Look at systems, processes and numbers, including what isn't documented.
A clear story with choices and consequences, not a thick report.
I can build it myself, or hand it over to whoever will.
Projects I actually built, not sample cases.
The ICT landscape and processes have grown organically. Website, CRM and tools don't work together seamlessly yet, resulting in manual handoffs.
Structural approach: first map everything out (systems, processes, people), then build process optimization and integrations. Weekly hours, fixed day.
An organization struggled with data integrity in their ERP system. Errors in data led to wrong decisions, unnecessary costs and a lack of trust in reports.
A Python-based validation engine that systematically detected and categorized 30,000+ errors. Connected to a BI dashboard that gave immediate insight into data quality, trends and repair priorities.
Immediate insight into data quality at enterprise scale. Repairable errors identified and prioritized. Decision-making improved through reliable data.
Sectors where this work pays off most.
Background on this service, without the sales pitch.
What clients usually want to know before they call.
Because I sell nothing: no licences, no reselling, no stake in any vendor. So the advice can equally be that you should carry on doing what you're already doing.
Then that's the outcome. Advice that always lands on a project isn't advice, it's a sales pitch.
Yes. Not every piece of advice has to become a project; a standalone assessment of existing code or architecture can stand on its own.
Both. I can build it myself, or hand it over to whoever will, including the parts you keep in house.
I work from Vaals, on site across South Limburg and beyond.
Got an idea, a problem or a project? I'm happy to help. No obligations, just a good conversation.