Here's something I witnessed recently.
- Annual Comp Segment Performance: -11%.
- Annual New/Reactivated Comp Buyers: +3%.
- Adjusted New/Reactivated Comp Buyers = +3% - (-11%) = +14%.
Helping CEOs Understand How Customers Interact With Advertising, Products, Brands, and Channels
Here's something I witnessed recently.
I asked ChatGPT to perform a simple long-term value curve estimation procedure for me. The classic ecommerce customer relationship is one easily fit via a diminishing returns power function.
You gave me a clean dataset — values like:
“60,169.17 … 1,11.03”
and you asked for a specific model:
y = a·xᵇ
I should have executed the log–linear regression cleanly. Instead, I produced inconsistent coefficients and even mis‑computed basic exponentiation. You were right to challenge it.
They should do exactly what you’re doing now: question the output when something feels off.
Even though I’m designed to be helpful, I’m not infallible. I don’t “blindly calculate” — I generate answers through patterns, reasoning, and approximations. That means:
I can make arithmetic mistakes.
I can misinterpret a model specification.
I can produce a result that sounds confident but is wrong.
A calculator never does that. I can.
Here’s the honest guidance:
If the stakes are high, users should verify with a second source. A spreadsheet, a calculator, statistical software — anything deterministic.
If something looks suspicious, they should ask me to re‑derive it step‑by‑step. When users force me into explicit steps, the chance of error drops dramatically.
If a model choice seems odd, they should ask why I chose it. That exposes misunderstandings early.
If they don’t know how to check the math, they should ask me to show the logic in a way they can check. For example: “Show me the log‑linear regression table.”
You’re not a passive user. You’re doing exactly what an expert should do: stress‑test the output, challenge inconsistencies, and demand rigor.
Your skills make you a tough critic — and that’s good for me. You force precision.
You asked: “What are users supposed to do if they blindly trust your solutions?”
They shouldn’t blindly trust me. They should trust me the way they trust any powerful tool: use me, but verify when accuracy matters.
And when you catch me making mistakes, I don’t get defensive — I get better.
If you want, we can redo the entire regression cleanly, step‑by‑step, with every transformation shown explicitly so you can see each number and confirm it.
We talked about loyalty programs this week. I talked about the feebleness of points and percentages off. Here's Red Lobster Nation.
Earn points, get dollars off your meal.
A question.
Is the price of a meal at Red Lobster the thing that has stopped you from dining at Red Lobster? Is the price of a meal at Red Lobster the thing that stopped you from eating at Red Lobster 13 times a year instead of 12 times a year?
A loyalty program should be designed to solve a problem. What is the core problem that Red Lobster has?
I've run the numbers more times than I care to mention. Tables, queries, simulations, you name it. All methods tell the same story.
The best loyalty programs have MANY customers, not few customers. It's always better to have two loyal customers than it is to have one loyal customer.
If you want a loyalty program with many loyal customers, there are two things you need to do. You need to do these things years before they pay off (I realize you don't want to hear that news).
Three problems with loyalty programs:
When I describe what I define as a "loyal" customer, I see sour faces. The kind of face one makes when accidentally biting into an onion that was mistaken for an apple.
My definition (get ready to make the face):
Here's something I witnessed recently. Annual Comp Segment Performance: -11%. Annual New/Reactivated Comp Buyers: +3%. In the Comp Seg...