Who I work with

Whatever you're building, the people using it are the priority. I work with teams of all kinds. What matters is that the outcome actually helps them.

You do not need a technical background to work with me. You know your work and where it keeps getting stuck, and that is exactly what I need to hear. I ask the questions and explain what I build without jargon, so you can decide with the full picture in front of you.

You need software that fits how your team actually works. Not the other way around.

Usually there is one process that costs your team more time than it should, often a spreadsheet or a long chain of emails. I start there, with the people who do that work every day, and build around how they already do it.

You deal with me throughout, not with a sales team first and someone else later. Your team sees the work early, says what gets in the way, and I change it before anything is set in stone.

Your mission matters. Budget shouldn't be a reason for bad tools. Special rates apply.

When you get in touch, mention that you are a nonprofit or social enterprise. I look at what you already use and keep what works, so the money goes where it actually helps, not into replacing things that were fine.

People come and go, volunteers especially, so what I build has to be easy to pick up without long training. The code and the documentation belong to you, and the system stays yours when your team changes.

Your online presence should feel like your work, not a template.

I start with your work, not with a layout. We look at what people should see first and how your pieces want to be shown, and then I design the site around that.

Afterwards you add new work, texts and images yourself, without code. The site loads quickly, so your images get seen instead of keeping people waiting, and it looks right on a phone, where many people will find you first.

Complex data, unusual requirements, precision. That kind of problem is exactly what I enjoy.

Research projects rarely fit standard software. Before I suggest anything, I take the time to understand your data and your method, and I keep asking until the edge cases are clear.

The code is auditable and documented, so you can explain in a paper or a report exactly what the software does. It runs on open-source technology, so once the project ends it depends neither on me nor on a licence.