An intelligence layer for the operation you already run.

TrueFlo connects each order to the documents, deadlines, rules and decisions around it. It checks new information against that record, flags what needs attention, and prepares the work that follows.

Short load on 417
Maya OkaforTuesday 4:12pm

@logistics The short-load flag on 417. What does it change, and what do I have to decide before the document deadline?

Reading order 417 sources Worked for 3 seconds
  • Read the loading confirmation, page 1
  • Compared it against the sales order and the draft invoice
  • Checked the certificate request quantity

18 of 20 pallets loaded, 1,800 of 2,000 cartons. The draft invoice still bills 2,000 and the certificate was requested at 2,000, so both have to change. 48 hours to the document deadline. Three things are ready. One decision is yours: the 200 open cartons.

  • Customer note in the drafts folderDraftedwaits on the trader
  • Draft invoice quantity 2,000 → 1,800waits on the controller
  • Hold on the invoice until the certificate matchesStagedwaits on the documentation desk

One shape of operation, as an example. Kestrel Coast Produce, the order and its numbers are made up, and the arithmetic is consistent so you can check it.

How it works

Incoming documents, checked against your orders and your team's rules.

The confirmation is in the inbox, the order is in the ERP, the deadline is on the booking. Your team is left to compare them by hand.

01 · Reads

It reads both sides.

A forwarding rule sends the mail you already receive. A scheduled export sends your orders. One record holds what you agreed and what actually happened.

02 · Checks

It checks the moment something lands.

Each arrival and each advancing clock re-checks the order against what was ordered, the rules for that destination and commodity, and the deadlines.

03 · Routes

It routes the result to a person.

What does not match goes to whoever owns it, citing the page it came from, with the draft already written. Sending, writing and the commercial calls wait for a person.

Who this is for

Built for operations that run on other people's paperwork.

If the documents that decide whether an order ships, clears and gets paid come from outside your company, this is the shape TrueFlo is built for.

Exporters

Did the container load what was sold, and will the documents clear at the other end?

Booking confirmation · loading confirmation · certificate · bill of lading

Importers

Does the entry match the invoice, and is anything holding up the release?

Purchase order · commercial invoice · customs entry · arrival notice

Distributors

Did what arrived match what was ordered, and what is the deduction for?

Purchase order · advance ship notice · receiving report · chargeback

Different documents. The same shape: an order, the paperwork that arrives around it, and the moment two of them disagree.

See everything it reads

Keep your systems. Cut the duplicate work.

The layer reads your systems where they are and leaves them there, and you choose what it can see before it sees anything.

  • Gmail
  • Outlook
  • Google Drive
  • Google Sheets
  • Microsoft Excel
  • NetSuite
  • QuickBooks
  • Xero
  • Salesforce
  • HubSpot
  • Shopify
  • Slack
  • Microsoft Teams
  • Notion
  • Stripe
  • DocuSign

Read through forwarded email, scheduled exports and shared folders. No native connector is required to start.

One order, as the layer holds it

A short load is found the day it loads, not the day it lands.

One example. The loading confirmation said 1,800, the order and the invoice said 2,000. Twelve minutes later, this was waiting.

See the whole trace
Prepared, not sentProposed Tuesday 4:12pm
Draft invoice quantity: 2,000 → 1,800ERP · invoice 417 · quantity, cartonsStaged
Note to the customer: 18 of 20 pallets loaded, revised invoice to followDrafts folder · the trader · not sentDrafted
Hold on the draft invoice until the certificate matches 1,800ERP · invoice 417 · hold proposed, with reasonStaged
Certificate: requested at 2,000 → must match 1,800Order record · documents · the documentation deskStaged
Open: 200 cartons remain on the order. Ship on Thursday's load or close short?A decision, not a correction · the traderQuestion
Waiting on the controllerNothing leaves the drafts folder and nothing changes in your systems until it is signed off
Awaiting sign-off
What your team sees

How your team uses TrueFlo.

In the first deployment

Ask the record

Anyone on the team asks a question and gets the answer from the record, with the documents it came from. It never sends, writes or decides.

See an order traced
In the first deployment

Your team's know-how, written down

We write down the rules each desk uses, test them against real orders, and keep them current with the people who own them. Every check reads them.

How skills work
Once it has earned trust

One email per person

A morning email with only what is theirs and what needs attention next. Every line cites its document. Nothing to click, and it is refreshed each morning.

See every workflow
When you turn writes on

The gate

Every proposed change shows the field, the current value, the proposed value and who proposed it. Every note is a draft until someone presses send. There is no setting that turns this off.

How the gate works
Working with us

Start small. See everything. Then decide.

We learn how your operation actually runs, then build against what we find. TrueFlo is configured around your operation and run for you, starting with one workflow.

01 · Map · Start here

The Operations Map

1-2 weeks · Defines the first workflow

We sit at the desk where the work happens and map how it actually gets done - every document, every handoff, every hour. It starts after the first call with a model of your own orders, before you commit to a build.

  • Yours to keep, build with us or not
02 · Prove

The First Workflow

Weeks, not quarters · Read-only

We build the workflow for the job your team most resents doing by hand, read-only, alongside them on real orders. You see every catch and every miss first.

  • A baseline measured before it turns on
03 · Run

Run and grow

Ongoing · Monthly run fee

We keep the layer running, keep the rules current, and add the next workflow against the same record. Every month you get the numbers, even when they are bad.

  • Agreed maintenance and rule changes included in the monthly run fee

The map ends with a defined workflow, scope and quote. You decide whether to proceed.

The full engagement, step by step

Zach Louie, founder of TrueFlo
From the founder

You'll talk to Zach.

TrueFlo started at my own desk, retyping information between systems at a tax-recovery startup until I built the system that did it for me. I still sit at the desk where the work happens before anything gets built.

How I work
Let's talk

Bring one order that went wrong last month.

We will trace it in front of you and name the first workflow worth testing.

Book a call

Nothing gets connected on the call and nothing is ever sent without you. Prefer email? zach@trueflo.net