Question 1

What's the catch?

Accepted Answer

There is a condition rather than a catch. We only take on work where the volume makes the per-document revenue worth a day of building. If your volume is low we will tell you on the call, instead of building something that does neither of us any good.

Question 2

What does it actually cost?

Accepted Answer

A prepaid package priced per document, valid for a calendar year. The rate depends on the document type and your monthly volume, so we send it after the call. There is no subscription, no per-seat charge and no setup fee at any volume.

Question 3

How long until it is running?

Accepted Answer

Usually one business day from the moment we have your sample documents. Setting up the API takes none of your team's time, because we do all of it. The only thing we need from you afterwards is somebody to look at the output and tell us whether it is right.

Question 4

What if the accuracy is not good enough?

Accepted Answer

Then you do not pay, because nothing went into production. We either keep working on it or we tell you plainly that your documents are a poor fit for this. Either way it has cost you nothing but the call.

Question 5

Do we have to move our team into your platform?

Accepted Answer

No. The extraction runs behind the systems you already use. At Blitz, the 300 people using it every day work inside their own contract application and never see anything of ours.

Question 6

What happens if Catalin is unavailable?

Accepted Answer

Once it is built, it runs on its own. The extraction at Blitz has been processing about 2,500 documents a month since 2022 without anyone touching it, through four years of holidays and busy weeks. Catalin is personally involved in the build and in anything that changes afterwards.

Question 7

Is it safe to send you our documents?

Accepted Answer

We do not store them and they never train anything. Fragments are kept only if you turn on data lineage for auditability, and those are encrypted. We will sign an NDA if you want one, and redacted samples work fine for the build.

Real results from real teams