How I work

Five steps, no surprises

  1. 01up to 30 minutes

    Free consultation

    Online or in person, up to 30 minutes. We go through what slows you down and I tell you whether it can be automated. Within three working days I send a proposal with an indicative price, or a quote straight away.

  2. 02

    Analysis and price

    I go through your operation and you get a document: what will be done, what it will cost and when it will be finished. I then hold to that price.

  3. 03

    Build

    I build the solution and test it on your real data, so that it fits your operation exactly.

  4. 04

    Handover

    I put the solution into service, hand it over with plain documentation and show you how it works.

  5. 0530 days notice

    Support

    Optional. For a monthly fee I watch that everything runs and handle changes, for instance when a tool ships an update. The notice period is 30 days; I do not tie you into a fixed term.

A smaller automation goes live within a few weeks; for a more complex one, count on a month.Source: common questions, rollout time. The individual steps are not measured yet.

How I prove it

I do not promise it will work. I show you.

Every project goes through the same set of checks and the result is written down. You will not get the sentence “it is fine” from me, you will get a document with a line for every point saying what proves it. Where a point has no evidence, I treat it as unmet, not as a detail.

What I do not guarantee: that nothing will ever break. Nobody can honestly promise you that. What I guarantee is that it gets checked by the same procedure every time, that the result is written down, and that if you keep me on support it goes through this check again, not only once at handover.

Handover checklist5 checks on every project

  1. A security review before handover

    I look for access credentials left in the code, places where nobody checks who asked for the data, and paid services with no ceiling. A finding marked “must be fixed” means it does not get handed over. Not that it gets handed over with a note.

    What you get: A completed checklist, with the evidence next to every line

  2. Written down: what can go wrong

    Before I build, I write down what is worth anything in the solution, which routes lead into it from outside, and what I am knowingly not addressing because it would cost more than the damage. That last part matters: anyone claiming to cover everything is either not doing it or charging you for it.

    What you get: A document you can hand to whoever takes the system over after me

  3. Accounts in your name

    Every account behind what I build for you is in your name and you pay for it directly. I have a role on it that you can remove at any time. When we stop working together, there is nothing to take over from me.

    What you get: The list of accounts in the handover protocol, with the owner of each

  4. When there is AI inside, it says so

    Since 2 August 2026 an EU rule requires that a person knows they are talking to a machine. On every project with AI I determine who carries the obligation under the regulation and write it straight into the quote. A bot admits it is a bot, always. Even if you would rather it did not.

    What you get: An AI checklist and clearly written roles in the quote

  5. Numbers, not impressions

    Page speed, text contrast and screen reader legibility can all be measured. So I measure them and write the numbers down, instead of writing “fast and accessible”.

    What you get: Measured values, not adjectives

    You can see how it looks at bikested.com

Common questions

Common questions about automation, price and timing

All eight questions and answers

Do I have to be technical to use it?
No. I set it up so that it runs on its own and hand you a plain set of instructions. You just do your work; the technology is my part.
How long does a rollout take?
A smaller automation usually goes live within a few weeks; for a more complex one, count on a month. Sometimes longer, when we are waiting for access or for data from your side. You get the exact deadline from the analysis, not as a guess over the phone.
Will my data stay safe?
I take it seriously. The data stays in your systems, I do not copy it to myself, and the automation can be switched off at any time. Where a task genuinely requires sending part of the data to a supplier, typically an AI model, I say so in advance, we go through exactly what, and I choose a supplier that does not train on your data. All of it in line with the GDPR.