Who builds it

Built by an operator, for operators.

Every feature was built inside a working store, on real order days.

The two of us

The operatorCo-founder · 1 of 2
Tyler, co-founder of Operator Lens

Tyler

Behind the counter since age ten. About six years running stores.

Around Dairy Queen since age ten, and about six years running and operating stores. Tyler knows the weekly truck order the way only an operator can: what flies out on a hot Friday, what sits in the freezer, and what both cost when the order is wrong. Two stores now order with Operator Lens every week, and every feature on this site proved itself on those order days first.

The builderCo-founder · 2 of 2
William presenting AI research at an academic conference

William

AI researcher. Builds the engine behind the order.

An AI researcher preparing for a PhD, William has presented research on how AI agents model one another and coordinate at an academic conference, and brings the same rigor to the truck order. William builds everything behind Operator Lens: the import that reads your invoices and sales, the math that writes the suggested order, and the app your manager counts and approves in. When a store's numbers move, the math moves with them.

Why it works

The perfect match.

Most ordering software is built in an office; Operator Lens was built at the back counter.

From Tyler

  • How a real order day runs, from the count to the truck
  • What every item really costs when it runs out, or sits
  • The calls only an experienced manager knows to make

From William

  • Math built on each store's own invoices and sales
  • Every change tested on months of real orders before it ships
  • Software that does the math in seconds, so your manager doesn't have to

Together: the order an experienced operator would write, done in minutes and approved by you.

Comes standard

Built for a real order day.

Operator Lens has run inside a working store since May 2026, and every safeguard below comes standard on yours.

  1. 01

    Full history first

    Your invoices load before the first order, so it starts from what you actually buy.

  2. 02

    A shelf for every item

    Every ingredient gets a shelf before the first count, so the count sheet follows the way you walk the store.

  3. 03

    One line per ingredient

    Several distributor products can feed one ingredient, and you count it once. No double counting.

  4. 04

    Checks before you submit

    A near-empty count or a missed fast mover is caught before it reaches the order.

  5. 05

    Your decisions stick

    Approve or reject an item once and it stays that way, through every re-upload.

  6. 06

    Counts dated right

    A count taken at close is dated the next morning, so a same-day truck is counted once.

  7. 07

    A quick count of your fast movers

    A ten-minute count the night before order day keeps the items that drive the order accurate.

  8. 08

    Every order approved and checked

    Approving saves every change your manager makes, with a reason, so every order can be checked after the truck.

Principles

Four rules we hold ourselves to.

  1. 01

    You approve every order.

    We suggest the order; your manager changes what they know better and approves it. Nothing is ordered without your OK.

  2. 02

    Fix the cause.

    When a line runs short, we fix what caused it: a count, a recipe, the sales we learn from. So the order keeps matching what you use, week after week.

  3. 03

    Results you can check.

    We check every order line by line at the store after the truck. You get the same report card for your own stores, every week.

  4. 04

    We run our own stores on it.

    Tyler orders for his own two stores with Operator Lens every week, so it is built for a real order day, not a demo.

See real results

Talk to us.

Tell us about your stores and we'll show you what your first two weeks look like.