What Seems To Be Driving Scott Right Now
This version uses both telemetry and voice. Specifically: 5 full days of Cowork activity plus 1,764 Superwhisper recordings from the last 144 hours, around 144,441 transcript words, and the behavior patterns from typing, switching, browser surfaces, and clipboard use.
The strongest conclusion is that the bottleneck is not intelligence, not effort, and not classic distraction. The bottleneck is closure under pressure. Scott is carrying a stacked threat model at the same time: cash flow, payroll/client reliability risk, custody/family pressure, product-story ambiguity, and too many open strategic lanes.
What is stressing him out? Money, daughter/custody pressure, investor credibility, and product reliability touching payroll.
What is he avoiding? Narrowing to the few painful closures that would actually reduce that stress.
Is IQ the issue? No. If forced to guess from this data alone: probably high enough that raw cognition is not remotely the bottleneck, roughly 135 +/- 10. The exact number is mostly bullshit.
Generated 2026-03-24 11:31 PDT
Typed characters landing inside Claude, Codex, or OpenWork. This is not someone who thinks privately first and tool-uses second.
Median time to snap back into build mode after communication. Interruption hurts less than ambiguity.
`need to` 418, `have to` 301, `should` 646 across the voice corpus. The mind is obligation-heavy.
The Pressure Hierarchy
This is the hottest layer. The language gets most urgent when production instability touches time tracking, payroll, or client retention. The stress is not abstract. It is “this could cost us hundreds of thousands” and “people panic because they think their time isn’t tracking.”
This is the deepest emotional layer in the dataset. It is not constant in every clip, but when it surfaces it clearly reorganizes the meaning of the money pressure. Money is not just runway. It is tied to getting his daughter back.
He knows there is something real and valuable here, but the packaging still feels slippery: RAG versus real workflow intelligence, software versus consulting, founder-led pilot versus scalable product, personal brand versus company GTM.
The voice data is saturated with “we need to,” “we should,” “I have to,” videos, articles, landing pages, investor prep, Katie, Xavier, Andy, April, outages, SEO, product collateral, MCP content, side hustle, and lead-gen. This is not laziness. It is overload plus unsolved closure architecture.
What He Is Probably Avoiding
- Not work itself. He is obviously working constantly.
- He is avoiding painful narrowing. Killing options hurts him more than generating them.
- He is avoiding choosing one brutally simple GTM story and shipping it without further committeeing.
- He is avoiding direct confrontation with the most humiliating version of the money problem: “we may need cash now in ways that do not match the founder/product self-image.”
- He is avoiding the human follow-through items that crystallize commitment: investor prep, send-the-video, reach Andy, do Xavier, close the story, ask for the money, ship the thing.
- He is also avoiding trusting half-built systems. When tools lie, misclassify, or drift, he responds by reopening control loops himself.
Psychological Profile, Harder Version
- Very high systems intelligence. He compresses abstractions quickly, moves between product, GTM, architecture, and operator detail without much friction, and spots bad framing fast.
- Identity is “conductor,” not “specialist.” He wants many top-tier minds in parallel, then wants the best synthesis, not ego ownership.
- Low tolerance for fake rigor. He hates roleplay debate, caricatured AI personas, shallow SEO, and tools that act confident while missing the point.
- Uses profanity partly as compression and partly as force application. It punches through ambiguity and helps him keep momentum. It is often a control tool, not just anger.
- Trust is fragile around memory loss, context drift, wrong dates, or “I did the thing” when the thing was not actually done. That is when frustration spikes.
- He wants challenge, not comfort. Multiple clips explicitly ask for honest disagreement and not to make him feel better.
- The morning self-image is probably wrong. The actual high-output self arrives in the afternoon and evening.
If I Had To Stupidly Guess
I would not treat this as psychometrics, but if you force the question from transcript + telemetry alone, the safest answer is:
Scott probably sits somewhere around 135 +/- 10 in the kind of general reasoning people casually mean by IQ. The data supports “well above average, likely very high.” It does not support pretending we can nail an exact number. The much more important truth is that his constraint is not horsepower. It is closure bandwidth, emotional load, and strategic overextension.
Why that range? Fast analogical reasoning, unusually high thread juggling, strong abstraction, high verbal compression, and the ability to translate technical primitives for non-technical users without losing the underlying architecture.
Why I’m Saying This
“I’m on like five projects at once and I do need to get a fucking landing page up relatively soon.”Voice transcript, 2026-03-18 11:38
“I’m trying to get money in and I’m still feeling good about money coming in one day… it’s fucking taking forever.”Voice transcript, 2026-03-18 18:06
“I’m going to need this money to get my kid back.”Voice transcript, 2026-03-19 02:26
“We’re fucking cash fucked like we do not have money like we don’t payroll for fucking April.”Voice transcript, 2026-03-23 14:33
“I have a really big investor call in about three hours on Tuesday and I could get a check today if it happens.”Voice transcript, 2026-03-24 07:20
“This is connected to people’s time tracking… they panic because they think their time’s not fucking tracking.”Voice transcript, 2026-03-24 09:04
What He Most Needs To Do
- Stabilize the payroll / time-tracker / production reliability lane. That is the most acute credibility threat.
- Do the investor / cash conversation and related prep before more meta-work. This is the leverage event closest to reducing the deepest pressure.
- Ship the few overdue human-facing artifacts with revenue or trust impact: Katie, Xavier, Andy, core GTM/video deliverables.
- Choose one brutally simple SMB story and stop widening it for a day: what it does, for whom, why now, what happens on the first call.
- Stop opening new content/SEO/article lanes until the above are done or clearly delegated.
Blunt version: the thing he most needs is not another smart idea. It is a ruthless closure layer.
One Thing I’m Not Ignoring
There was one explicit “I want to kill myself” line inside a money-pressure clip on 2026-03-18. In context, it reads like overloaded frustration rhetoric, not a literal plan. I am still not going to hand-wave it away. If that is current and not just language, the right move is to tell a real person now and get immediate support.
This report uses Scott’s own local voice + telemetry data and intentionally allows personal inference. It is still an inference report, not diagnosis.