Contact
If there is a problem to describe, I would rather hear it first
Before writing a proposal I want to understand what is going on. An email is enough — no phone tag, no meeting to schedule.
What to put in the email
-
Which systems you run
Logo Tiger, another ERP, an e-commerce platform, your own software — whichever it is.
-
What is not working
Be concrete: “stock does not match”, “reports take days”, “nobody finds us in search”.
-
Who it affects
One person, a department, your customers? That is what sets the urgency.
-
What has already been tried
Knowing what failed keeps me from walking down the same road again.
What happens next
- 01
I read it
I read the situation and look at whether anything can genuinely be done.
- 02
I ask questions
A few more questions are usually needed. Nothing is committed at this stage.
- 03
An assessment
I write back what can be done, what cannot, and why.
- 04
I say so if it is not a fit
Not every job suits me. Saying so early saves both of us time.
Whichever field you write from
Questions
Questions about this page
How do I get in touch? Is there a form to fill in?
There is no form — an email is enough: [email protected]. No phone tag, no meeting to schedule. Four things help in that email: which systems you run (Logo Tiger, another ERP, an e-commerce platform, your own software), what is not working, who it affects, and what has already been tried.
What happens after I send the email?
Four steps: (1) the situation is read and assessed for whether anything can genuinely be done; (2) a few more questions usually follow — nothing is committed at this stage; (3) a written assessment comes back saying what can be done, what cannot, and why; (4) if the work is not a fit, that is said plainly.
Why are there no prices on this site?
No figure is discussed before the scope is seen. Two jobs described in the same sentence can turn out very differently depending on the state of the existing system. For the same reason no delivery-time commitment is given; the timeline follows the scope.