Engagements and rates
How I work,
and what it costs.
I scope the work and then build it. Once it is running, I can keep running it. Most firms do one part of that and hand you a phone number for the rest.
Research institutes, university labs, non‑profits and small platform teams, mostly. They call when something works on one machine and now has to serve a hundred people, or when the person who built it has left.
I work in the open by default, so what I build for you is yours under a licence your community can use.
Rates
| Engagement | Basis | Rate |
|---|---|---|
| Consulting and engineering | Hourly | €125 / $150 |
| Academic, non-profit or open-source work | Hourly | Reduced |
| Retainers, hosting and fixed-scope work | Per project | Quoted on request |
| First contact | No charge |
Anything beyond hourly work is quoted per project, once I know what it involves. Cloud spend on a hosting arrangement is passed through at cost, on your account wherever that is possible.
How an engagement runs
You can stop at the end of any step and keep everything produced up to that point. That is deliberate.
First contact
Email me what you have. I read it properly and tell you whether I am the right person and roughly how big the job is. No charge, and a call only if it helps.
Written proposal
Short. Scope, milestones, an estimate, what is explicitly out of scope, and what I need from your side to start.
Delivery in checkpoints
Work lands in reviewable pieces, in your repositories, with the tests that prove it.
Handover
Documentation aimed at the team who will run it, and a working session with them before I leave.
Get in touch
Write me a paragraph about what you are trying to build, or what you need kept running. That is enough to start, and scoping it costs nothing.
- Reply
- Within two working days