Services

Scan, build, hand over.

Most work runs in this order. You can also stop after the scan. Each part is priced to the job, agreed before it starts.

1. 01

   Knowledge scan

   Where knowledge sits, which process costs time, and whether AI is the right tool. You leave with scope and a number.

   Conversations with the people who do the work, and a look at the systems that already hold the truth. Sometimes the outcome is that building is not useful yet. Martijn says so.

   Scoped to the job

2. 02

   Build and integrate

   The system itself, on your documents and tools. Tested with real questions from the company.

   A source on every answer. Permissions per role. No demo on fake data. If a connection cannot be made safely, it does not go in.

   Scoped to the job

3. 03

   Handover

   Your team learns to use it and keep it current. After that you can continue without DroidBender.

   Documentation, a working session with the people who will use it, and an agreement on what must stay current. Staying on after go-live is a separate agreement, also scoped.

   Scoped to the job