Operations Management & Systems

Endless Management is the shared operations layer for a holding company managing multiple food businesses at different stages — active locations, new openings, and acquisitions in progress.

Team size: ~5–10 people

Day-to-day work depended heavily on the owner for context, decisions, and follow-ups. Processes lived in people’s heads, Looms were long and messy, and async work was hard — especially with team members outside the PST time zone.

If the owner wasn’t available, work slowed down or stopped.

I supported daily operations while building systems that could eventually run without me.

My focus was not just “getting things done,” but removing the owner (and myself) as bottlenecks so the team could work independently and async.

SOPs from scratch for core operational workflows

A clear SOP template + instructions to turn messy Looms into usable documentation

A prompt-based workflow so the team could create SOPs consistently (without depending on me)

ClickUp structures that tied:

Clear rules for task statuses, reviews, and handoffs

Immediate drop in repetitive questions and back-and-forth

Work could move async across time zones without waiting for the owner

SOPs were actively used (not just stored):

Bookkeeping and other sensitive processes were documented and handed off cleanly

Both the owner and I were freed from constant clarification and follow-ups

Not everything needs to be over-documented. Some technical or tool-specific details didn’t stick — and that was okay.

The real win was building a shared culture of documentation and ownership, not making ops depend on one person (or one role).

ClickUp (tasks, docs, SOPs)

Loom (input → structured documentation)

Lightweight templates & prompts for repeatability

In short: This project was about keeping operations running while building systems that made me less necessary over time.