A short, honest description of what working with I mean IT looks like – from the first email to the final handover. No buzzwords, no surprises.
1. Intake call (free, 30 minutes)
Everything starts with a conversation. We hop on a video call or meet in person if you're nearby in Twente. You tell me what you're working with, what's broken or missing, and what success would look like. I ask questions to understand the technical reality and the business context.
I don't try to sell you anything on this call. The goal is to figure out whether what you need is something I can genuinely help with – and if it isn't, I'll tell you and point you toward someone who can.
You walk away with: a clearer picture of the problem, and an honest opinion on whether external help makes sense at all.
2. Scoped quote
If we agree there's a project worth doing, I send you a written quote within a few days. The quote includes:
- A clear description of what I'll deliver
- A list of what's explicitly not included (so there are no surprises)
- An hours estimate or fixed price
- A proposed timeline
- Payment terms
If anything is unclear or needs adjusting, we iterate until we're both comfortable. Quotes are valid for 30 days.
3. Agreement
Once you accept the quote, I send you a short Overeenkomst van Opdracht based on the standard Belastingdienst model agreement for freelance work without employer authority. We both sign it digitally before any work starts.
This protects both of us – you get clear deliverables, I get clear scope and payment terms.
4. Kickoff
We schedule a kickoff call. You give me access to the systems involved, I confirm I have everything I need to start, and we agree on a communication rhythm – usually a short weekly check-in plus async updates when I hit milestones.
5. The work
I work independently and report progress regularly. You can reach me by email or chat for questions, and I'll always tell you if something is going slower or differently than planned – I don't believe in last-minute surprises. Code, configs, and documentation go into version control from day one, so you have full visibility into what's been done and full ownership of the result.
6. Delivery and handover
When the work is done, I deliver everything in writing: the technical artifacts (scripts, configs, infrastructure changes), the documentation explaining how it all fits together, and a runbook for whoever will operate it after I'm gone. We do a walkthrough together so your team knows where everything lives.
I include 14 days of post-delivery support for any issues that come up while you're settling in.
7. Invoice and aftercare
I invoice on completion of fixed-price projects, or monthly for ongoing engagements. Payment terms are 30 days unless we agree otherwise.
After the project is done, I'm always reachable for questions. If you want to bring me back for related work later, we just pick up where we left off.
What you can expect throughout
Honest communication. If something is harder than expected, you hear about it. If something turns out to be unnecessary, I'll tell you and reduce scope rather than pad hours.
Clean handover. Everything I build is documented well enough that someone else – including future-you – can understand and maintain it. No black boxes.
No vendor lock-in to me. Your infrastructure should run fine without me. That's the whole point.
Reasonable response times. Emails and messages during weekdays get a response within one business day, usually faster.
Ready to talk? [email protected] or +31 6 16 89 33 68.