Services
What I can build or fix for you.
Find the problem that sounds like yours. Each kind of work starts with a small first step you can say yes to, and I do the work myself. Small jobs are welcome.
-
Someone spends hours every week copying data, rebuilding reports or babysitting a script.
Python automation and internal tools
Turn a manual or fragile process into software that runs on its own, logs what it did and tells a person when something needs attention.For example A weekly spreadsheet routine, or data copied between two tools by hand, replaced by a small service with checks, history and alerts.
First step A short call, then a written proposal with a fixed price for a defined first piece.
Evidence
- Alerting, licensing and integration services (client work, trading)
- Obsidian Text Transformer (open source)
-
You want AI in a real workflow, but it can’t be allowed to guess, invent data or act without approval.
AI systems with the checks in code
Add AI to a real workflow or product where it actually helps: it chooses from options your system has checked, and a person approves anything that cannot be undone.For example An assistant that reads incoming requests, looks up the details in your systems and drafts the reply or action, then waits for your approval.
First step A small pilot on your real cases, measured, with an honest verdict on whether it is good enough.
Evidence
- IntentSQL (open source, public alpha)
- Decision Lab (open source, experimental)
-
Releases are stressful, nobody is sure who can access what, and outages are noticed by customers first.
Kubernetes and OpenShift
Releases from Git that are routine and reversible, clear answers to who can access what, and monitoring that tells you first.For example An application containerised and deployed by Argo CD from Git, with commit-pinned images, TLS, hardened pods and a dashboard, plus the notes to run it.
First step A written review of your current setup with a prioritised list, or a scoped setup project.
Evidence
- Red Hat EX280 and EX180 (certified, 2026)
- Aim Duel platform (own project, live)
- Lineage (open source, early v1)
-
Software your business depends on keeps breaking, and the person who wrote it has moved on.
Fixes and ongoing care
The software you already depend on gets someone who fixes it, watches it and keeps it working, month after month.For example A script, bot or small service that breaks every few weeks gets diagnosed, fixed, monitored and written down, so it stops depending on luck.
First step A paid review of the system: what is fragile, what to fix first and what it would cost to look after.
Evidence
- Supporting client systems in live markets since 2017 (client work, trading)
- Monitoring as code on Aim Duel (own project, live)
-
You trade with MetaTrader 5 and need a system built, changed, or kept running.
Trading software for MetaTrader 5
Changes to the systems you already use, new builds, alerts when something stops, and dashboards across accounts.
First step A short call about your rules or existing system, then a fixed quote.
Evidence
- My client work since 2017
-
Your team needs an extra developer for a while.
An extra developer for your team
I join on a contract for Python, automation, AI integration or platform work, inside your process and your repositories.
First step A short call about the work, your team and how long you need help.
Evidence
- Long-term client delivery (client work)
- 5 merged fixes to the Kubernetes docs, through upstream review (open source)
How pricing works
Every project starts with a written proposal: scope, approach, price and timing. Defined work gets a fixed price; open-ended work is time-based. When scope is unclear, I suggest starting small.
A small first step
A paid review, a short pilot or one defined fix. Useful when the scope is unclear, and a good way to find out whether we work well together.
A defined project
Something built end to end for a fixed price, delivered with tests, documentation and a handover.
Ongoing work
Continued development, fixes and care for systems that keep changing, usually monthly or time-based.
What moves the price
- How clearly the work is defined. Clear scope means a fixed price.
- What it connects to: each outside system adds testing and failure handling.
- How it has to run: unattended, monitored, with what kind of support afterwards.
Who I work well with
A good fit
- Small businesses with a process that eats hours every week.
- Founders who need an AI feature that behaves predictably.
- Teams that need an extra developer for Python or platform work, remotely and on contract.
Probably not a fit
- Work that needs a large team or a guaranteed 24/7 on-call rota.
- Terraform or AWS projects (no work to show yet).
- Trading tools sold on profit promises.
Common questions
I am not sure what I need. Is that a problem?
No. Describe the problem in plain words. Working out whether it needs AI, plain automation or neither is part of the first conversation.
Who owns the code?
You do. Work is delivered into your repositories and accounts, documented so your team or anyone else can maintain it.