Where Should You Start With OSLO? The Most-Asked Question, Answered

Not with the 285 skills. Start with the 3-minute assessment: it walks your business through Offers, Sales, Leads, and Operations in order and names the first domain that fails. That domain is your starting point. You work it — with agents carrying the executable volume — until it passes, then re-run the walk. That's the whole on-ramp.

This is the question founders ask most before committing, and it usually hides a worry: "this looks like a lot — a whole taxonomy, four domains, hundreds of skills. What's the actual first move, and how much of my life does it eat?" Fair worry. Here's the straight answer, including the parts that tell you not to do things.

Why not start by studying the framework?

Because OSLO is a diagnostic, not a curriculum, and studying a diagnostic instead of running it is a category error. The skills library exists so you don't have to become an expert in all four domains — each skill is a markdown file that makes an agent the practitioner, with escalation to you built in. Reading all 285 before acting would itself be a sequencing mistake: comfortable preparation standing in for constraint work. You'll genuinely need maybe a handful of skills in month one — the ones mapped to your failing domain. The rest sit ready for later cycles.

What does the first 30 days actually look like?

1. Day 1 — run the assessment. Three minutes. Out the other side comes the thing most founders haven't had in years: a single named priority with causal reasoning behind it.
2. Week 1 — verify the diagnosis with your numbers. Informed-prospect conversion for Offers; close rate without you in the room for Sales; qualified pipeline per week for Leads; delivery headroom for Operations. The bottleneck guide covers each reading. If the numbers contradict your gut, trust the numbers.
3. Weeks 2–4 — work the one failing domain. Pull the skills mapped to it and put agents on the executable parts — drafting, research, templates, follow-ups — while you make the calls only the architect can make: pricing, positioning, what to promise. Refuse downstream work for the month. All of it.
4. Day 30 — re-run the walk. If the domain passes now, the next constraint surfaces and the loop continues. If it doesn't, you've at least spent a month on the right problem — which beats a year on the wrong ones.

How long until the loop pays?

Honest answer: the first cycle is the slowest, and the framework says so itself. Early on, most of your energy still goes to learning — the site's own gears metaphor calls the pre-OSLO state "walking," where 95%+ of effort is wasted figuring out what works, and the first loop "a bike in low gear": still inefficient, but for the first time the wheels turn. What compresses is everything after. Each cycle, the sequence is a habit instead of a discovery, the skills are tuned to your business, and the bottleneck resolves in days instead of months. The payoff curve is back-loaded — which is exactly why the expensive move is delaying the first loop, as the cost breakdown makes explicit.

What does starting cost?

The assessment is free, the sequence and its logic are public on the site, and the guides here spell out the method in enough detail to run a loop yourself. There's no implementer to hire and no certification between you and the framework. If you want the built version — the agent and skill infrastructure stood up around your specific business, inside the broader Optimus stack — that path starts with an application at buildwithoptimus.com. But the diagnostic works before any of that, which is the correct order anyway: diagnose first, then decide how much machinery the fix deserves.

The three wrong starting points, for the record

• Starting with Leads because demand feels like growth. If the offer or sales process is the constraint, more demand burns prospects you can't get back.
• Starting with tooling — agents, automations, a new stack — before the sequence has named a target. Capacity pointed at nothing in particular produces faster nothing.
• Starting everywhere at once. Four simultaneous initiatives means the constraint gets a quarter of your attention. One failing domain gets the architect; the rest runs on agents and team.

If you've read this far, you already suspect which domain of yours is failing. The assessment either confirms it in three minutes or saves you a quarter by proving your gut wrong. Both outcomes are worth more than the three minutes.

FAQ

Where do I start with the OSLO framework?

Start with the 3-minute assessment on osloframework.com. It walks your business through the four domains — Offers, Sales, Leads, Operations — and names the first one that fails. That failing domain is your starting point; ignore the other three until it passes.

Do I need to read all 285 skills first?

No — that would be a sequencing mistake in itself. The skills are an execution library, not a curriculum. You pull the handful mapped to your failing domain when the diagnostic names it, and agents run them. The other domains' skills sit ready for later cycles.

How long does the first OSLO loop take?

It varies with the domain and the business — the honest framing from the framework itself is that early cycles are slow because most of your energy still goes to learning, and later cycles compress. The first loop is about wiring up all four domains completely, not about speed.

Does OSLO cost anything to start?

The assessment is free and the framework — the sequence and its logic — is public on the site. The paid path beyond that is working with Optimus to build the agent and skill infrastructure around your business, which starts with an application at buildwithoptimus.com.