The method

How an engagement runs

Four to eight weeks. One fixed price, agreed before anything starts. No hourly meter, and no discovery phase that quietly becomes the project.

01

Scope and access

Week 0

We agree in writing what is in scope and what is excluded, and get read-only credentials to the systems that matter. Excluded folders and tables are named here, not discovered later.

What we need from you: Someone who can approve access, and an hour to walk us through the systems.

02

Index in place

Weeks 1–2

Your business system is read through a read-only connection. Your files are indexed where they sit. Nothing is copied off-site, and nothing is written back into the system of record.

What we need from you: We'll be exploring your data, applications and code. Several light demos and exploratory conversations with you on how you use your systems.

03

First real answers

Weeks 3–4

You sit down with it and ask your own questions. Not a scripted demo — questions we did not pick, from the person who can tell when an answer is wrong.

What we need from you: The operating expert. Estimating, planning, scheduling or service — whoever actually knows.

04

Handover and rollout

Weeks 5–8

Three to five core users are trained properly. The engine runs against live data, and your people run it.

What we need from you: The core users, and an owner-level decision on how widely it goes.

Why there is no price on this page

What an engine costs depends on how many systems, how much history, and how much of it is in a shape anyone can read. Publishing a number would mean publishing a number that is wrong for most of the people reading it.

What we will commit to in public: it is a fixed price, you see it before the work starts, and it does not move unless you change the scope. The first conversation is free and usually tells us both whether there is a fit.

What “done” means

A working assistant over your real data, demonstrated live, answering questions your people wrote.