Why I built
SENTINEL MAN.
I was making decisions in the wrong conditions.
Not bad decisions, exactly. The decisions a man running a business has to make every day — hire this contractor, fund that initiative, push back on this client, hold the line on that commitment. The hundred-and-ten micro-decisions that compound into the year you actually have, versus the year you thought you were going to have.
What I noticed, over enough years to have evidence rather than a theory, was that the quality of those decisions had almost nothing to do with how much I cared, how much I had thought about them, or how experienced I was. It tracked something else. Something physiological, situational, and almost completely invisible to me at the moment of choice.
I made my best decisions in roughly the same window. Mid-morning. Sleep above seven hours. Physical load low. Network warm. Calendar uncluttered. I made my worst decisions in conditions I could now describe in equally specific terms — but at the time I had no language for them at all. They just felt like normal Tuesday afternoons.
The problem with this is that the world does not present significant decisions inside your peak window. It presents them when they arrive. The phone rings, the email lands, the contractor wants an answer by the end of the day. You are 4pm on five hours of sleep and the decision is in front of you regardless.
The tools didn't help.
I tried what was available. Therapy was offered, and I attended. The therapist was capable. The framework was clinical — psychological history, emotional processing, the architecture of feeling. None of which was wrong. None of which addressed the question I was actually asking.
The question was: was Tuesday morning, on five hours of sleep, the right time to finalise a $300,000 contract?
That is not a therapeutic question. It is an operational one. And there was no operational tool. There were wellness apps that asked me to journal my feelings. There were productivity apps that tracked tasks. There were sleep trackers that scored last night and forgot it by lunchtime. There was nothing that would tell me, at 8am on a Tuesday, that today was the wrong day to make the call I was about to make.
So I built it for myself.
Not as a product. As a personal governance stack. A daily document I wrote each morning before opening my inbox. Five inputs — mood, sleep, physical state, mental clarity, network condition. A score I gave myself, calibrated against weeks of self-observation. A short brief I wrote to myself describing the day's conditions in operational language.
And, eventually, a set of Operating Principles — five sentences that captured how I had decided to make decisions. Every significant decision was checked against those principles before it was made. If a decision violated a principle, it had to either be revised or the principle had to be revised. The principle was not allowed to silently bend.
I did this for a long time. The patterns became visible. I learned things about my own decision-making that no therapist could have told me, because they were patterns in my data — things that only emerged when there were 90 days of evidence to look at.
Some of them were obvious in retrospect. Some of them were not. The most useful pattern I ever surfaced was that my decision quality dropped catastrophically on days following heavy physical load combined with sub-baseline sleep, and that this was the condition under which I tended to receive decisions from others — because the world, again, does not present decisions on your terms.
Knowing that pattern changed how I structured my week. Then it changed how I structured my month. Then it changed how I made decisions in the conditions where decisions arrive — which is to say, all the time.
I knew other men needed this.
This is the part of the founder story that is both true and slightly embarrassing. I knew it because the men I respected — operators, founders, partners, the men actually running things — kept describing the same problem to me, in different language, without realising they were all describing the same problem.
"I can't tell when I'm being smart and when I'm just being tired."
"I make my worst calls in the afternoon and I never figure out how to stop doing it."
"My wife says I'm a different person on Sundays. I don't know what she means but I know she's right."
None of these men were going to open a wellness app. None of them were in therapy. Most of them, if you asked, would say they were "fine" — and they were, in the sense that the word means nothing. They were not fine. They were operating without the intelligence layer that any system at scale requires. They were running businesses with no telemetry on the operator.
The product had to be different.
I did not want to build another wellness app. I did not want to ship another version of the thing that men were already not using. The problem was not that the existing tools lacked features. The problem was that the entire framing was wrong for the audience.
So SENTINEL MAN was built around three architectural rules that are not negotiable.
Performance intelligence, not wellness. The product is framed around operational output, decision quality, and cognitive performance. The clinical work — and there is clinical work, embedded in the methodology — happens invisibly. Men engage with performance. The outcomes are the same. The door is different.
Man-sovereign. The man buys the product. He owns his data. There is no employer layer, no HR involvement, no institutional visibility. This is not corporate wellbeing. This is a private intelligence system that happens to be available to anyone who wants it.
Adversarial intelligence in the loop. The Decision Advisor — the engine that analyses significant decisions — runs four AI models in parallel, and one of them is explicitly built to attack the obvious choice. To find the kill shots. To identify what you are not seeing because you are inside the decision. Most AI products agree with the user. SENTINEL MAN deliberately includes a model whose job is to disagree.
The 90-day arc.
The product is structured around a deliberate 90-day arc, because that is roughly how long it took me, in my own use of the original system, to build a model of myself that was actually predictive. The arc is not a marketing fiction. It is the actual minimum viable timeframe in which the system can produce intelligence that is recognisably yours rather than recognisably generic.
Day 7 is when the first confirmed pattern appears. Day 14 is when the Decision Advisor activates. Day 30 is when the system delivers a structured assessment of your operating profile — patterns confirmed, principles tested, peak windows established. Day 90 is when the system steps back and asks one question, and waits for ten seconds before doing anything else, because the answer matters more than the answer's speed.
I designed each of these milestones from the inside. I know what it feels like to receive Day 30 because I delivered Day 30 to myself. The arc is built on lived experience, not theorised user journeys.
Why now.
I held this system for years before turning it into a product. Two things changed.
The first is that AI got good enough to deliver the methodology at scale, in the operational language it needs to be delivered in. The four-lane Decision Advisor that takes 26 seconds was not technically possible three years ago. Today it costs less than a dollar a month per user to run. That changes everything about whether this is a product or a private practice.
The second is that the men I respected kept asking me what I was using to operate the way I was operating. After enough of those conversations, it became clear that keeping the system to myself was a choice — and not an obviously correct one.
What this is, in one sentence.
SENTINEL MAN is the operational intelligence system I built for my own use, made accessible to the men who would have benefited from it but were never offered anything that fit them.
It is not therapy. It is not coaching. It is not a chat app. It is a system that tracks how you operate, surfaces the patterns that govern your decision quality, and gives you better intelligence about your own state than you have ever had.
If that sounds like something you would use, the door is at sentinelman.com. Seven-day trial. No credit card. The system starts building from Day 1.
If it sounds like something you would not use — fair. It was not built for everyone, and that was deliberate. It was built for the man who has been running on his own internal estimates for too long, and who is ready to hand part of that work to a system that does it more rigorously than he ever could on his own.
That is who I built this for. That is who it is for now.
— Nick Lord