Which Business Framework Should You Start With?
Start with the framework that matches your current constraint — and for most founders, that's OSLO, the prioritization framework, because every other framework assumes you're already working on the right thing. If your calendar is the constraint, start with LEAD. If you don't yet believe the shift is real, start with ARMS. The wrong answer is starting with whichever framework sounds most impressive.
The Optimus system is eight interlocking frameworks, and "interlocking" cuts both ways: they compound when you run them together, but each one owns a single decision and works standalone. That means the entry-point question has a real answer — it depends on which decision is currently costing you the most.
What is each framework actually for?
One line each, so the diagnosis below makes sense:
- ARMS (Agents, Robots, Materials Science) — the technology thesis: where the world is going, in three horizons.
- OSLO (Offers, Sales, Leads, Operations) — what to work on, in what order.
- FAST (Factory of Agents with Skills and Tools) — how you build AI agent systems.
- CORE (Capture, Optimize, Roll-up, Exit) — how you build wealth on the engine.
- AIMS (AI Materials Science) — the research frontier; what's coming next.
- LEAD (Eliminate, Automate, Delegate, Liberate) — how a leader frees their time.
- RICE (Reach, Impact, Confidence, Effort) — how ties get broken when the team disagrees.
- FUSE (Food, Utilities, Shelter, Education) — why any of it matters.
How do you diagnose your constraint?
Match the symptom to the entry point:
| Your loudest symptom | Start with | Why |
|---|---|---|
| "We're busy but the needle isn't moving" | OSLO | You have an ordering problem. Offers → Sales → Leads → Operations tells you what deserves attention first. |
| "My calendar is wall-to-wall; I am the bottleneck" | LEAD | Eliminate before you automate. You can't architect anything from inside a packed calendar. |
| "We tried AI and it didn't stick" | OSLO, then FAST | Failed adoptions are sequencing failures first, engine failures second — see why adoption fails without a framework. |
| "I want to build agent systems now" | FAST | Agents × skills × tools, multiplicative. But keep OSLO open in the other tab, or you'll build a brilliant engine pointed at the wrong work. |
| "I'm acquiring / rolling up / positioning to exit" | CORE | Capture, Optimize, Roll-up, Exit is the wealth-creation strategy — the playbook lives at corewealth.ai. |
| "My team argues about priorities constantly" | RICE | (Reach × Impact × Confidence) ÷ Effort. A scoring model ends debates that charisma was winning. |
| "I'm not convinced this AI wave is different" | ARMS | Skeptics shouldn't start with tactics. Read the thesis; the rest only makes sense if you buy the direction. |
Why is OSLO the default answer?
Because prioritization failure is upstream of everything else. A founder who adopts FAST before OSLO builds automation for whatever was already on the to-do list — and the to-do list is usually Operations-heavy, because ops is what nags. OSLO's core claim is that the order matters: Offers first, because a sharper offer multiplies every sales conversation; Sales second, because conversion multiplies every lead; Leads third, because volume only pays into a working machine; Operations fourth, on purpose, even though it screams loudest.
OSLO is also where the system's 300+ portable skills live, organized across those four domains — so starting there hands you the map and the tools for the territory.
How do the frameworks hand off to each other?
The natural progression looks like this: OSLO points you at the right work. Doing that work at leverage requires an engine — that's FAST, and the rollout sequence is OSLO and FAST run together. A working engine raises the strategic question of what it's all for — that's CORE if the answer is wealth creation. LEAD and RICE run continuously alongside, keeping the leader's time and the team's decisions clean. And FUSE sits underneath as the reason: food, utilities, shelter, education — raising the floor so people stop surviving and start creating.
Don't collect frameworks. Run one until it creates the need for the next.
FAQ
Which Optimus framework should a founder learn first?
OSLO, for most founders. It's the prioritization framework — Offers, Sales, Leads, Operations, in that order — and every other framework assumes you're already pointed at the right work. The main exceptions: if you're drowning in your own calendar, run LEAD first; if you don't yet believe the technology shift is real, read ARMS first.
Do I need all eight frameworks to get value?
No. Each framework owns one decision and works standalone — OSLO alone will reorder your quarter; LEAD alone will return hours. The compounding comes from the interlock: OSLO tells you what to work on, FAST builds the engine that does it, CORE turns the engine into wealth, LEAD and RICE keep the leader operating at the right altitude. Add them as the earlier one creates the need for the next.
What's the difference between OSLO and RICE?
OSLO is strategic sequence — which category of work matters first (Offers → Sales → Leads → Operations). RICE is a tactical tiebreaker within a category — score competing ideas by (Reach × Impact × Confidence) ÷ Effort when the team disagrees. OSLO decides the battlefield; RICE settles skirmishes. RICE was originally developed by Sean McBride at Intercom.
When should CORE come before the others?
When your goal is acquisition-driven — buying a business, optimizing it with AI, rolling up several, or positioning for exit. CORE (Capture, Optimize, Roll-up, Exit) is the wealth-creation strategy that runs on the FAST engine, so even acquisition-first founders end up needing OSLO and FAST inside each company they touch.