Skip to content

03 / HOW I WORK

Diagnosis first. Then the build. Then the number.

  1. 01HOW I WORK

    Diagnosis before build

    I build nothing before I know what is actually stuck.

    A reported interface problem was a master-data problem: 59 of 62 invoices already carried the discount.

  2. 02HOW I WORK

    Draft or diagnosis first

    Before the offer comes proof, not a pitch.

    One page of diagnosis or one draft, free. Then you decide.

  3. 03HOW I WORK

    Back-test before live

    Every rule runs against the inventory before it is armed.

    The watchdogs in the invoice intake were tested against 505 and 1,074 real invoices before they were switched on.

  4. 04HOW I WORK

    Operation with watchdogs

    A system that runs reports when it stops running.

    After a standstill of 5.9 days there is now a watchdog that alerts after 72 hours without a booking.

  5. 05HOW I WORK

    AI builds with me, I am liable

    AI does the manual work here. What goes out has been decided and checked by me.

    I check the result against its intended use before handing it over.

  6. 06HOW I WORK

    Numbers instead of adjectives

    What I cannot measure, I do not claim.

    Every number on this site has a source and a date. A test breaks the build when a number without a source appears.

You work directly with me, from the first conversation through implementation.

Background

  1. Bachelor in business administration.
  2. Then camera, photography and film.
  3. Then head of content at a Berlin e-commerce startup.
  4. Since 2025 I build systems.

German and English. Ho Chi Minh City, remote.

Contact

What is stuck on your end?

One paragraph is enough. I answer with one page: what is stuck, what I would build and what I would not. It costs you nothing.

Show me what is stuck