FABRX

We build your document processing and connect it to what you already use.

Send us a few sample invoices, contracts or IDs. We build the extraction, wire it into Make, your ERP or your own application, and hand it back working. Usually within one business day, and it costs you nothing until it runs on your real documents.

Catalin Crisan

Catalin Crisan, founderTwelve years building data pipelines. He runs every build himself.

You pay per document, once it is live. Nothing before that.
supplier "Supabase Pte. Ltd."number "SCLWGF-00016"vat_id "RO47771958"date "2026-07-27"due "2026-07-27"currency "USD"total 44.03pages 2

Running in production at

  • Blitz
  • USMLEX
  • Cicada Technologies
  • Tap Point
  • MakeIT Future
  • Solo
  • Premium Advisors

Before you pay anything

The build is on us. Here is what that covers.

Everything below happens before any money changes hands, and almost none of it needs your time.

  1. 01

    We talk for 30 minutes

    What documents you handle, what you need out of them, and where that data has to end up. If it is not a fit, we will say so on the call rather than after.

    30 minutes

  2. 02

    You send a few representative documents

    Whatever actually comes in. We need to see the scans that arrive crooked and the supplier who formats their invoices differently to everyone else.

    We sign an NDA if you want one, and redacted samples are fine. Your documents never train anything, and we do not keep them.

  3. 03

    We build it

    The extraction, the output structure, the validation, and the connection into Make, your ERP or your own API. That part is ours to do.

    Usually one business day

  4. 04

    You look at the output

    Your documents, your fields, your team checking whether the values are right. That is the only part that asks anything of you, and it is reading results rather than setting anything up.

    Zero hours of setup on your side

  5. 05

    It goes live, and only then does it cost anything

    You pay per document processed. Nothing before that point, and nothing else after it.

The arrangement

Why we do not charge for the build.

We get paid per document. If what we build never ends up processing anything, we have spent a day for nothing, and that is our problem rather than yours.

It is also why we turn work down. If your volume is small, the metered revenue will not cover the build, and we would rather tell you that on the call than take the project and hope.

Most tools in this space charge you a subscription first and let you discover afterwards whether they cope with your documents. We would rather find out first, at our expense.

We are putting a day of work against your document volume. If the accuracy is not good enough for you to run it, we have lost the day.

Catalin Crisan

Catalin CrisanFounder, Fabrx

Before Fabrx, twelve years of data engineering.

Pipelines
ETL and ELT frameworks at ING, Rabobank, APG and Paddy Power Betfair, moving data from source systems into warehouses people report off.
Scale
Redshift warehouses past 10TB, and ingestion running at thousands of records a second.
Regulated
IFRS9, AnaCredit and COREP reporting, the kind banks get audited on, plus EU AI Act Annex IV documentation.

Connecting an extraction to your ERP, your warehouse or your database is the routine half of this work.

Four years in production

Blitz turned a two-minute contract into a ten-second one.

Over 300 field agents scan an ID and a completed contract comes back, inside Blitz's own application rather than ours.

Blitz, field sales

We built ID extraction into their existing contract generation app. It has been running there since 2022.

12×
Faster contracts, from about 2 minutes to 10 seconds
300+
Field agents using it every working day
~2,500
Documents processed every month
4 yrs
In production, on the same workflow
We have been using Fabrx.ai for over 4 years to automatically extract data from identity documents within an internal contract generation application used by more than 300 users. The implementation was straightforward, and the extracted data has been consistently accurate.
Rebeca Dogaru, Business Analyst, Blitz
It reduces the time spent filling out contracts from approximately 2 minutes to 10 seconds. It's a secure way of entering data because it eliminates human error associated with manual input.
Bogdan Lucaciu, Regional BD Manager, Blitz

Read the full story

What customers say

Most of it is about how we work rather than what we built.

Responsive

What really sets them apart is their communication. It's rare to find a partner that is both technically capable and so personally invested in their clients' success. If you need efficient document processing and a team that actually picks up the phone, I highly recommend Fabrx.ai.
Craig Sullivan
Founder, USMLEX

90% time saved

The system has proven to be reliable and efficient, which has helped us automate processes that previously consumed a lot of time. Cătălin is flexible, responds quickly, and finds practical solutions for any situation encountered along the way. For us, this type of partnership matters just as much as the technology itself.
Bogdan Rus
CEO, Cicada Technologies

Integration

It lands where your data already lives.

You do not adopt a new tool or move your team into somebody else's dashboard. The extraction runs behind whatever you already use.

What we connect to

  • Make
  • Your own app, over our API
  • Your ERP

Where documents arrive from

  • An email inbox
  • A shared drive
  • An upload in your own interface
  • A scanner or a phone camera

What comes back

  • Structured fields, same shape every time
  • A webhook on every result
  • An exception when a value cannot be read

Data handling

Your documents stay yours.

We do not store them
Documents pass through and are gone. Fragments are kept only if you switch on data lineage, and that is your choice to make.
Never used for training
Your documents and the data we pull out of them never train a model, ours or anybody else's.
GDPR
PII detection and audit trails are part of the service rather than something we sell you separately.

Pricing

You buy documents, not seats.

A prepaid package of documents, valid for a calendar year, drawn down as you process. We send your rate after the call, once we have seen what your documents actually take, because before that we would only be guessing.

What you pay for

  • Documents processed, counted one at a time
  • A prepaid package, valid twelve months
  • A better rate as your volume grows

What you never pay for

  • The build, the integration or the tuning
  • A monthly subscription or platform fee
  • Per-seat licences, however many people use it
  • Compliance, audit trails or observability

Not ready for a call? Send me pricing by email.

The small print, in plain words

Since the build is free, you should know how it ends.

What we own
The extraction logic and the schema we build stay ours. You have access to them for as long as you are a customer.
What it costs later
A package holds its price for the calendar year. We rarely change rates, and when we have to you get at least a month's notice first.
If you leave
One month's notice. There is nothing of yours for us to hand back, because your documents were never ours to keep.

Questions

The ones people actually ask.

What's the catch?

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.

What does it actually cost?

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.

How long until it is running?

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.

What if the accuracy is not good enough?

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.

Do we have to move our team into your platform?

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.

What happens if Catalin is unavailable?

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.

Is it safe to send you our documents?

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.

Tell us which documents are eating your week. We will tell you on the call whether we can fix it.

Catalin Crisan

You will be talking to CatalinEvery call goes straight to the founder.

12+ years · 150+ clients · over a million documents processed