TELOS Framework
Create enough structural leverage to focus on high-agency work, meaningful relationships, and long-arc thinking -- without sacrificing health or presence to get there. The point isn't AI. It's autonomy.
"I believe capable people lose to friction they shouldn't have to fight, which is why I'm building AI systems that give small operators the infrastructure that used to require enterprise budgets."
World Problems
The fundamental issues driving my work.
Small operators are structurally disadvantaged
the gap isn't talent, it's tooling.
Most people live reactively inside invisible systems they can't see or redesign.
AI is being consumed passively instead of architected intentionally.
Goals
Priority-weighted — each roughly half as important as the one above.
Revenue Without Heroics
stable monthly baseline where core income runs from systems, not constant intervention.
Operational Autonomy
most repetitive execution handled before it hits him. Steps in for design and direction, not maintenance.
Cognitive Clarity
clean schedule, deep work blocks protected, less context switching, no background stress.
Physical & Relational Alignment
strong body, stable energy, present partner. Ambition that doesn't erode connection.
Challenges
Life-Level:
C0: Over-engineering before revenue is stabilized -- disappearing into architecture that feels productive but delays direct execution that moves cash and clarity faster.
C1: Cognitive overload from parallel tracks -- juggling infrastructure, clients, optimization, research, and personal upgrades erodes sharpness through context switching.
C2: Energy inconsistency -- when sleep, stress, diet, or emotional bandwidth slip, everything downstream degrades.
Strategic:
Research without shipping is a STRONG pattern (6+ sessions). The system excels at analysis but repeatedly defers execution.
Learning loop is "sometimes," not mandatory -- the critical feedback step of measuring whether promoted patterns improve outcomes is missing.
Success rate measurement absent -- cannot yet prove the system is learning with a number.
Strategies
S0: Infrastructure Before Intensity -- build the system first (data flows, feedback loops, leverage points), then scale effort on top of it. Stability compounds. Chaos doesn't.
S1: Remove Friction Before Adding Force -- if something requires constant willpower, it's poorly designed. Redesign environments so the right action is easier than the wrong one.
S2: Leverage Small Inputs Into Compounding Outputs -- code once, reuse everywhere. Capture insight once, structure it, redeploy it. Solve at the root so every downstream layer benefits.
Playbook: Architect smarter, then apply pressure where it multiplies.
TELOS is a living framework that evolves as I learn and build. It's not rigid adherence to a plan — it's a north star for decisions and actions.