Workflow systems database
I build software for workflows that used to live in spreadsheets, inboxes, and someone's head.
The real work sits in workflows, review steps, imports, and the admin surfaces that make a system safe to operate after launch. Most of that gets underbuilt because it is invisible in the demo. That is where problems accumulate. That is where I focus.
I build admin systems that show operators what changed, what needs review, and what is safe to publish.
Working philosophy
The hard part is rarely writing the code. It is understanding the real workflow before you write it: what people currently do, where mistakes happen, what must be reviewed, and what should never be silently overwritten.
Good fit
Legacy rebuilds, admin tooling, and workflow systems with operational risk.
I am usually most useful when a team has outgrown spreadsheet workflows, inherited a brittle CMS or PHP system, or needs imports, approvals, publishing states, and operator visibility to stop living in guesswork.
The visible interface was never the hard part.
These projects look different on the surface, but they all depended on getting the structure underneath right first: workflow rules, data shape, operator paths, or information architecture. The part people click on only holds up when the model behind it does.
SELECT * FROM `projects`;
Skills and stack
Backend systems, legacy rebuilds, and enough frontend to own what ships.
I work close to the operational details: imports, approval paths, admin edge cases, data corrections, and the parts that become painful after launch if they are skipped.
If you need help untangling a messy workflow or rebuilding an aging system, let's talk.
If your team is operating a system they are afraid to touch, running workflows through spreadsheets they have outgrown, or facing a rebuild they do not know how to scope safely, that is the work I do. Email me what you are trying to fix. I will be straight with you about whether I can help.
Based in Utrecht. Backend systems since 2012, which is long enough to have seen what happens to the ones that skipped the hard parts.
I came up through the kind of systems that accumulate history: old CMS installs, custom ecommerce builds, SQL-heavy workflows, IIS-hosted sites, Linux boxes managed by hand, and admin panels that mattered more than the marketing pages. That is why I pay attention to the operational layer, not just the launch layer.
I tend to enjoy systems with edge cases, operational constraints, and rules that only become visible once people rely on them daily.