One senior operator, moving in tight loops

Who you're working with

Oodaloli is run by one person: Jason Dunn, a senior operator who has run sales, marketing, and operations — not watched them from a strategy deck. That background changes what gets built. When the question is "should this lead get a same-hour reply or a nurture track," we've owned that quota. When it's "will the ops team actually adopt this," we've been the ops team.

This is deliberately not an agency. There is no bench of juniors your engagement gets handed to after the kickoff, no account manager translating between you and the person doing the work. The one on the call writes the code, wires the integrations, and shows up to the weekly demo. That caps how many clients we take at once, and we think that's the right tradeoff.

Consulting on a loop

The practice runs on John Boyd's OODA loop: observe, orient, decide, act — then go around again, faster than the problem changes shape. Applied to consulting, that means we don't open with a 40-page assessment. We watch the work happen, orient around the two or three friction points that cost the most, decide on the smallest build that removes one, and ship it. Then we look at what actually happened and adjust.

Ship small, observe, adjust. A working automation in week 2 teaches more than a roadmap in month 3, because the automation generates evidence and the roadmap generates meetings. Every engagement shape we offer — Sprint, Project, Embedded — is just this loop run at a different scale.

About the name

Oodaloli (pronounced OO-da-LO-lee) is two ideas welded together. Half is "oo-de-lally," the unreasonably cheerful refrain from Disney's Robin Hood (1973) — the sound of a day going your way. Half is the OODA loop, a fighter pilot's model for out-iterating an opponent.

Together they describe how the work should feel and how it should move. Oo-de-lally is the feel: this stuff should make Tuesday lighter, not add another system to babysit. OODA is the speed: notice a problem, ship something against it, and be back with a better version before a traditional engagement would have finished discovery. If either half goes missing — the work turns heavy, or it turns slow — something is wrong.

Operating principles

• Your stack, not ours. We build in your accounts and your tools. No proprietary platform, nothing to migrate away from later.
• Approval gates on anything customer-facing. A human signs off before an automation touches someone who pays you.
• Audit logs on anything autonomous. If it acts on its own, you can see what it did and why.
• Documentation so you can fire us. Every handoff includes runbooks your team can operate without us on retainer.
• Numbers we can defend. ROI claims come from your data, not from adjectives.