Health
-20kg This Year
Proven capability. You did 108kg in 18 months. This is maintenance-mode ambition, not a stretch goal. The system just needs to not get in the way.
Target: ~1.7kg/month. Track weekly, act monthly.
Primary Revenue
InfraGuys Sales
Build. Deploy. Automate. AWS-first. $1,500 deployment tier as the entry offer. The goal is first paying clients, then pipeline rhythm, then scale.
Output metric: 3 meaningful conversations per week minimum.
Background Project
MenTool
You believe in it, you use it, you built it for yourself first. That's the strongest possible foundation. This simmers while InfraGuys gets heat.
Time budget: max 3hrs/week. No feature creep.
The 50-Project Problem
You have built an extraordinary amount. That is both an asset and a current liability. The framework below treats everything except InfraGuys as frozen until you have revenue. Not forever. Just now.
-
InfraGuys
All primary sales energy lives here. The $1,500 deploy offer is your sharpest entry point because it's specific, deliverable, and priced for a fast yes. AWS-first builds are the upsell pathway. This is where your calendar, your Focusmate sessions, and your VeebaOS pipeline attention go.
-
Health Systems
Bali actually helps here. The food environment, the movement culture, the climate. Set it up structurally in week 1 and let it run. It should not compete with sales energy, it should support it.
-
MenTool
3 hours per week maximum. Protected time, capped time. No more. The constraint is the feature, not the bug, as it forces prioritisation within the project itself.
-
Everything Else
Frozen. Logged in VeebaOS. Will still be there in 90 days. The 50 projects are not going anywhere. Attention is the scarce resource, not the projects.
AUDHD Design Principle
No hour-by-hour schedule. Three containers per day, in order. The container type is fixed. The exact time is flexible. All three must happen before the day closes.
Container A
Deep Work
90 minutes max. Single task only. Phone in another room or on Do Not Disturb. Focusmate session booked in advance. InfraGuys work primarily.
Container B
Admin + Comms
Pipeline touchpoints via VeebaOS. The 3-2-1 ritual lives here. Emails, DMs, proposals. All reactive work is quarantined to this block.
Container C
Open + Recharge
Protected. Not optional. No guilt attached. This is not wasted time. For ND brains this block is what makes the other two sustainable.
The Ignition Problem
Your nervous system needs a consistent on-ramp. In Bali, with a new environment, this matters more not less. The anchor ritual is the most important item in this entire document.
01
The Anchor
Same action, same order, every single morning. One thing only. Coffee, walk, specific music, whatever is yours. This is the ignition switch. Pick it in week 1 in Bali and do not change it.
Anchor
02
Focusmate Session
Book the session the night before, not in the morning. Morning booking is an activation energy trap. The social contract is what fires your brain's engagement system.
Output
03
The 3-2-1 Pipeline Touch
Move 3 deals forward in VeebaOS. Reach out to 2 people. Follow up on 1 existing conversation. 15 minutes max. This lives in Container B, every day without exception.
Output
04
Movement + Eating
Non-negotiable as a structural block, not a willpower decision. Bali makes this easy. Set the container, let the environment do the work. Track weight weekly not daily to avoid noise.
Health
05
Night Before Prep
60 seconds. Write one sentence: what is the single thing that makes tomorrow a win? Book your Focusmate. Close all tabs. This is the system that makes the morning possible.
Reset
3
Move 3 deals forward in VeebaOS pipeline
2
Reach out to 2 people in your Rolodex or new contacts
1
Follow up on 1 existing open conversation or proposal
Why Activity Not Outcomes
Outcomes lag by weeks or months and give your AUDHD brain nothing to fire off. Activity is immediate, controllable, and gives you a daily win signal. The deals will follow the activity. Trust the system, not the mood.
The InfraGuys Entry Offer
$
$1,500 Deployment-Ready Package
Containerise, deploy to AWS, basic DevOps, basic backup. As long as it is deployment-ready you take it on. This is the sharpest, most specific offer you have. Lead with this in outreach. Everything else is an upsell from here.
Primary
^^
Build + Automation Services
Lambda, Fargate, ELK stack, AWS-native builds. Automation scoping. These are the upsell and repeat-client territory. Introduce after trust is established via the deployment offer.
Upsell
The Anti-Drift Protocol
This is the single highest-leverage habit in the entire framework. Without it, the ND drift kicks in and three weeks disappear. 20 minutes, every Friday or Sunday, non-negotiable.
- What actually moved forward this week? Name one thing in each goal area: InfraGuys, health, MenTool.
- What is stuck and why? Is it a task problem, an energy problem, or an activation problem? The answer determines the fix.
- What is the single domino for next week? One thing that, if it happens, makes everything else easier or irrelevant.
The System Survives Because You Planned for the Floor
Bad days happen. Dysregulation happens. Sensory overload happens. The framework does not break on those days because you have pre-decided what counts as surviving. If you hit the floor protocol, the day is not a failure. It is a hold.
🍽
One real meal.
Not negotiable.
⚡
10 minutes of forward motion on anything that matters.
🛡
No self-destruction. No catastrophising the day.
📓
One sentence: what triggered this? Mine it for pattern data.
You already named the biggest one.
The AUDHD novelty trap. You know it exists. Naming it gives you power over it. Below are the specific versions most likely to hit you.
-
!
The Bali Honeymoon. The new environment will feel like it is doing the work in weeks 1 and 2. It is not. The systems have to be in place before the novelty wears off, which it will by week 3.
-
!
Project Bleeding. You have 50 projects. One will start whispering to you that now is the time. It is not the time. Log the idea, freeze the project, return to InfraGuys.
-
!
VeebaOS Feature Creep. Your own product will tempt you to build rather than sell. A new feature on VeebaOS is not InfraGuys revenue. Treat it like any other frozen project during sales hours.
-
!
Research as Progress. Reading about systems, watching productivity videos, planning the framework. None of that is the 3-2-1. The doing has to outweigh the meta-work at a ratio of at least 4:1.
-
!
Perfect Week or Nothing. Missing one day does not break the system. Missing three in a row might. The weekly reset exists to catch drift before it becomes an identity story about failure.
If the whole framework feels overwhelming, run just these five.
Everything else is optimisation on top.
1
The Anchor Ritual
Pick it in week 1. Never change it.
Daily
2
Focusmate
Booked the night before. Every working day.
Daily
3
The 3-2-1 in VeebaOS
15 minutes. InfraGuys pipeline only.
Daily
4
Weekly Reset
Three questions. 20 minutes. Friday or Sunday.
Weekly
5
The Floor Protocol
Pre-decided. No improvisation on bad days.
Emergency