If your question isn't covered here, send a message and I'll answer directly.
With a short conversation, by email or video call, where you describe what you're trying to do. I'll come back with a rough idea of scope, approach, and a budget range. If we both want to move forward, we agree a small first milestone before committing to the rest.
Both, depending on the work. For well-scoped pieces (a new feature, a migration, a clearly defined integration) I prefer a fixed price per milestone. For exploratory or maintenance work I bill hourly with a weekly cap so there are no surprises.
Most projects I take on run between two weeks and three months. Larger pieces are usually broken into several milestones rather than one big delivery, so we can re-plan as we go.
Yes. A mutual NDA before sharing anything sensitive is fine, just send the version you want to use. I can also work under your master services agreement.
Yes. A good chunk of my work involves joining an existing engineering team for a defined piece of work, or making careful, well-tested changes to a codebase someone else built. I'm comfortable with code review, pull-request workflows, and the usual collaboration tooling.
I'm based in the Netherlands (CET / CEST) and work remotely worldwide. I overlap comfortably with Europe and the eastern half of North America. For Pacific or Asia-Pacific clients, async-first works best, with one or two scheduled calls per week.
Yes. After a project ships, most clients keep me on a small monthly retainer for bug fixes, dependency updates, and minor changes. If you'd rather hand it off entirely, I'll make sure the codebase is documented well enough for the next engineer to take over.
Send a message anyway. The list covers the common shapes of work, but a lot of interesting projects don't fit a single bucket. If it's outside what I can do well, I'll say so.
Happy to answer anything else over email.
Get in touch