We translate your words. We never translate your prices.

If you have used AI for anything, you already know it will make something up and sound completely sure about it.

Now picture that writing a bill with your name at the top.

That is a fair thing to be nervous about. So instead of telling you we take accuracy seriously, we are going to tell you exactly where the AI is in this product and exactly where it is fenced out.

The AI does two jobs

One. It turns what you said into English.

Two. It reads that English and works out which items on your price book you are talking about, and how many of each.

That is the list. Everything else you might expect AI to do here, it does not do.

It never picks a price

Rates come off your price book. Nowhere else.

Your price book is built out of invoices you have already sent, so the rate on the line is a number you charged a real customer for real work. The model does not get to nudge it because the job sounded big. It does not get to look up what pavers go for around here. It cannot type a dollar figure into a rate field at all. That field gets filled by looking your rate up, the way a cashier scans a barcode.

It never does the math

The model hands back two things for each line: which item, and how many. Rate times quantity, the subtotal, the tax, the total, all of that is done by ordinary code in our software. Boring code that does the same thing every time and that we can check.

There is a reason for that. A language model is a guessing machine, and it is very good at producing an answer that looks right. Arithmetic does not want a guess, so it never gets to do any.

A dollar sign in a sentence is not a price

Real invoices have money talked about in them that nobody is charging for. You have written lines like this:

Recommended replacing the main panel, roughly $3,200. Customer declined for now.

If software reads a description and grabs whatever number has a dollar sign in front of it, that customer just got billed $3,200 for a conversation you had in their driveway.

So a dollar figure sitting inside a description is never treated as a rate. Not once, not under any conditions. It is words, and it stays words.

When it does not know, it stops

This is the part that matters most and it is the least impressive to look at.

If the software cannot tell how many loads you hauled, it leaves the number blank. A blank. Not a zero, and not a reasonable sounding two. On the invoice it shows up as an empty ruled line, so you can spot the hole from across the room.

While there is a hole in it, the invoice will not send. The button is off. You fill the number in yourself, and you typing it is the confirmation. Nothing to approve, no popup asking if you are sure. It was your call from the start.

Where translation can still go wrong

We should be straight about this, because putting a translation step in front of an invoice adds a risk that ordinary invoicing software does not have.

It can mishear you. Sixteen and sixty sound close in a lot of languages, and they sound closer with a saw running behind you. It can also match your words to the wrong item, especially if you have two similar things on your price book.

Neither of those invents a price out of thin air, which is the failure we cared most about closing. But either one can put a wrong quantity or a wrong item in front of you. So the whole invoice is on your screen before it goes anywhere. Read it. It has your name on it, your license number, and your customer.

The one rule

Everything above comes out of a single sentence we build against: the software never invents a number that changes what your customer pays.

Plenty of companies could write that sentence on a website. The blank line that will not let you hit send is what it costs to actually mean it.