Let’s talk.

Some problems keep growing as long as you ignore them. If yours is one of them, or you simply want to find out whether I am the right fit: tell me what it is about. You are writing to me, Tim Rutte, Cloud & Software Architect, not to an agency.

  • 24 his how long a reply takes, usually less
  • 1:1straight to me, no agency in between
  • 30 minfirst call, no pitch, no obligation
Book a call

Helpful: which system, what prompted it, and by when it needs to run. Confidential details can wait until later.

This site is protected by reCAPTCHA. Google’s Privacy Policy and Terms of Service apply.

Thank you! I will get back to you shortly.
Oops! Something went wrong while sending.

A shorter way

If you already know what you need.

Each of these has its own short form asking exactly what decides the scope. That saves a round of questions, and you get a date instead of an estimate.

Before the first call

Questions that often come up first.

How quickly will you respond?

Usually within 24 hours. If your system is down or an acute security issue is open, put that in the first sentence so I can prioritize the request accordingly.

How do you handle confidentiality?

You do not need to put confidential details in the first form. Before access, architecture documents or internal data are exchanged, we can sign a mutual non-disclosure agreement.

Do you work at a fixed price or by time spent?

Both, to suit the project and the model you prefer. The problem gets understood and the scope clarified first; the model follows from that. Clearly bounded work gets a fixed price, longer or more open-ended work is billed by time spent. Analyses and reviews carry fixed prices, listed on the service pages beforehand.

Can we have a short call first?

Yes. The first call takes 30 minutes and is there to clarify the starting point, the objective and the next sensible step. There is no pitch and no obligation to commission work afterwards.