Book a review
Field notes

What we learn, written down.

Notes from the work: the arithmetic, the arguments and the things that turn out to matter. Written for operators who would rather make the next decision than admire another dashboard.

Voice
3 minute read

The real cost of an unanswered call.

Most owners have never done the arithmetic on a ringing phone nobody picked up.

A missed call is easy to dismiss as a moment. Across locations, departments and weeks, it becomes an operating number. The useful first step is not buying technology. It is calculating the possible exposure with your own call volume, missed-call rate and average gross, then measuring what is actually happening before anything gets built.

Read the note
Data
3 minute read

Why your systems disagree on the numbers.

The CRM, the ad platform and the spreadsheet each report a different number, and none of them is technically wrong.

Different systems count different events at different moments. The problem is not necessarily that one number is broken. It is that the business has not agreed which system answers which question, or what happens when the systems disagree. Until it does, every reporting meeting begins with reconciliation instead of decisions.

Read the note
Margin
3 minute read

Rank your catalog by contribution, not revenue.

Revenue tells you what sold. Contribution tells you what was actually worth selling.

A high-revenue product can still be a poor product for the business once its real costs are visible. Ranking a catalog by contribution changes what gets purchased, promoted and replenished. But first, the unit-cost data has to be honest enough to support the decision.

Read the note
Operations
5 minute read

How an AI daily operations brief drives system improvement.

One AI helps the retailer run today. Another investigates the system behind tomorrow's brief, with human approval at the boundary.

A useful daily brief does more than summarize data. It reconciles orders, shipments, carrier events and client history into a prioritized action queue. When the automation itself needs attention, a separate systems AI receives the issue, investigates the cause and improves the operating layer without confusing maintenance work with customer service.

Read the note

These notes are drawn from systems running in production. Client details are anonymized by policy, and figures are generalized from measured implementations unless marked illustrative.