Brewer Strategies · AI

The life of
one invoice.

One piece of software. One job. Follow a single supplier invoice from the inbox to posted — the whole machine is three parts and one written rule, and you can watch it happen.

01 arrives

Nobody chose this moment.

A supplier invoice lands in the inbox before six in the morning. No one asked for it, no one is awake, and until something reads it, it is one more PDF waiting for a Friday afternoon that nobody wants.

a siding supplier · received

  • item
  • qty
  • unit price

not read yet

illustration · the mechanism, not a client document

02 read

Every line lifted off the paper.

The tool does not read the way a person reads. It takes each line off the page — the item, the quantity, the unit price — and turns it into numbers it can compare. That is the only clever part of the whole thing, and it happens once, before anyone opens the file.

  • itemmatched to the agreement
  • qtya number
  • unit pricea number

illustration · what comes off one line

03 the rule

One written rule, agreed in advance.

Now it meets the only instruction it has. Compare every line to the price we agreed. The rule is the client's, written in the client's words, and it is the entire brain of the tool. There is no judgement in here — that is the point, and it is why the answer is the same every time.

  1. Compare every line to the agreed price.
  2. Inside tolerance — post it.
  3. Over — stop, and say by how much.

the rule, in plain language

04 the fork

This is where the story turns.

One invoice, one rule, and from here two different mornings. Both of these came out of the same run.

inside tolerance

+1.0%

It posted itself. No one opened it, no one approved it, no one remembers it. This is the outcome the tool exists for.

over

+9.7%

It went to a person — with the invoiced price and the agreed price already side by side. This is the outcome a person is still for.

two outcomes from one run · measured

05 settled

Done before the owner's day starts.

By the time the office opens, the invoices that were fine are posted, and the ones that were not are sitting in one short list with the reason attached. Nobody spent a Friday afternoon on it. Here is what that was, measured, over seven and a half weeks of a working contractor's accounts payable.

  • $1.6Mchecked
  • $1,924overpayment caught, weekly average
  • $2,424supplier credits recovered
  • 421invoices checked
  • 115cleared with nobody touching them
  • 45flagged, with the reason attached

measured · production ledger, 26 Aug – 17 Oct 2026

06 the fleet

Same three parts. A different rule.

Read something. Apply one written rule. Hand back a decision. Change the rule and you change the tool — that is the entire catalogue. None of these is a platform, and none of them took a department to run.

newsletter engine

The Plug

reads
the week's drops and restocks
rule
their own voice, their own format
hands back
a drafted issue, for a person to approve

starts November

knowledge portal

Insurance industry · Client: FMO

reads
the firm's own documents
rule
answer only from those, cite the source
hands back
an answer with the passage attached

in build

invoice check

Roofing & exteriors contractor

reads
supplier invoices
rule
every line against the agreed price
hands back
posted, or flagged with the reason

running · the one we just followed

quote tool

Gregg Shields Custom Home Painting

reads
the measurements and the scope
rule
their own pricing sheet
hands back
a quote and a deposit request

demo built

trips desk

Brewer Strategies · in house

reads
a client's request and their balances
rule
transfer partners first, portal last
hands back
finalists for a human to confirm

running

proof

The tool in beat four, running.

The figures above come out of the production ledger. The screen here is the working build driving on seeded data, so nothing on it belongs to a real supplier or a real client account.

working build · seeded demo data, not client invoices

start

Which job would you hand over first?

Not a demo request and not a discovery call. Name the one job you would rather never do again, and I will tell you whether it is three parts and a written rule — or whether it isn't, which is just as useful to know.

This opens your own mail app with the message written. Nothing is stored here. Or write straight to max@brewerstrategies.com.