Every number comes with the line it was read from.

Basaltflow builds document automation for small teams. Every value it reads comes with the line it was quoted from, and that quote has to be found in your file before anything gets posted. Test it on your own document before you spend a dollar.

Delivery note reader Three ways a value comes back
Lieferschein-Nr. LS-2026-4471 quote found in the document
Document number LS-2026-4471
Silikat-Innenfarbe naturweiss 12,5 L quote found in the document
Line 1, item Silikat-Innenfarbe
Dichtring EPDM 40 x 3 mm        Stk covered on the page, nothing guessed
Line 3, quantity not read

Word for word from two saved runs you can click in the reader: a clean paint delivery, and a photo with a smudge over one quantity.Open it and try to make it invent a number.

The problem

Where the week actually goes.

Not the skilled work. The typing, sorting and chasing around it. Three moments most owners know:

FRI 6:40 PM

The callback pile

Four missed calls from today. Two of them already booked someone else.

SUN 9:15 PM

The invoice stack

Ninety minutes of typing numbers a machine can read on its own.

MON 8:02 AM

The shared inbox

Everyone can see it. Nobody owns it. The urgent one sits under spam.

Each of these has a tool you can try right now. See the demos

This one was off by twenty five dollars.

Four line items, a total, and a number that does not add up. Nobody catches that at eleven at night on the ninth invoice. The check runs in code, so it catches it every time. Other document AI hands you a confidence score instead, which is the same model grading its own guess, and an invented line item can arrive at 95 percent.

An invoice next to the fields that were read from it. The total says 1,284.00 while the line items add up to 1,309.00, and the difference is flagged. An invoice next to the fields that were read from it. The total says 1,284.00 while the line items add up to 1,309.00, and the difference is flagged.

Real output from the invoice demo. The vendor and the amounts are made up, the arithmetic is not.

Try it on your own invoice

The demos

Six tools you can test right now.

Every one of them is live and takes your own file. Open one and try to make it say something wrong.

Simulated data · Real engineering

Not mockups. These are the demos above, mid-run.

An invoice from Sterling Hardware is shown next to the fields the model read. A red flag reads: total 1284.00 does not match the line items, which add up to 1309.00.
It catches the $25 that does not add up, and refuses to book it.
A question about a liability cap is answered with the exact clause, cited as Service-Agreement.pdf page 6, with the passage highlighted in the source document.
Every answer names the file and the page, and shows the passage.
One profit and loss table for eight clients built from three read-only exports. A traffic light sits next to each client and a line above reads: 2 of 8 clients need attention.
Three exports, one P&L, and the two clients worth a phone call.

Go ahead

Open any of them and try to break it. Nothing is stored, nothing is billed, and no sign-up stands in the way.

Back to the demos

Process

How it works

Four steps. No discovery phase, no workshop, no deck about your deck.

01

You describe the busywork

A short call or an email about what eats your week. No prep, no spec document.

02

You get a working demo

Built on your real examples, usually inside a week. You test it before you pay.

03

We tighten the edge cases

You try to break it. We fix what you find, until it holds up on a bad day.

04

It goes live, documented

Plain-English docs, a named contact, and no lock-in. You own what was built.

Who it's for

Built for businesses like yours.

Trust

Built to be trusted, not just impressive.

It shows its sources

Answers cite the exact file and page they came from, so you can check the work yourself.

It knows its limits

When the documents do not support an answer, it says "not in the documents" instead of guessing.

Everything in writing

Scope, price, and what happens if something breaks. Agreed on paper before work starts.

Money-back

If it isn't live, you don't pay.

Support

Written reply within one day.

Your data

Your build is hosted in the region you pick.

Contact

A named contact on every build.

Pricing

One flat price. In writing.

No hourly billing and no subscription you forget to cancel. After the free automation check, you get a fixed written quote for the whole build.

The build

A flat project price, quoted before work starts.

Running it

Optional care plan for updates and support. Cancel any month.

The guarantee

If it never goes live, you pay nothing.

Questions

Fair questions, straight answers.

Something here not covered? Write one sentence and you get a written reply within one day.

Ask us directly
Do we need to change the software we use?+

No. These tools plug into what you already have: your phone number, your inbox, your web form, your accounting export.

What happens when the AI is not sure?+

It stops and hands the case to a person. You can watch this happen in the demos. Uncertainty gets routed, never guessed.

Where does our data live?+

For a customer build you pick the region and it goes in the contract. This demo site is separate: it runs on a server in Madrid and sends demo inputs to Google for processing, which can mean the US. Nothing is ever sold or used to train public models, and you can ask for deletion at any time.

How long until it works?+

Most demos are ready inside a week. Going live usually takes two to four, depending on your systems.

Will this replace anyone on my team?+

It takes the repetitive part, not the job. Your team keeps the judgment calls.

Free automation check

Tell us what you want to automate.

One sentence about the busywork is enough. You get a written reply within one day.

Sending failed. Please try again in a minute.

Thanks. You will get a written reply within one day.

No newsletter. No call unless you ask for one.