I'm the non-engineer who accidentally built an orchestration thing. Tell me what I broke

Two weeks ago I stood in this room and begged you all to stop using big words like "orchestration."

This week I "accidentally" built one. La ironía.

Quick reminder of who's talking: I'm not a coder. Built my company on Excel, faith, and the kind of stubbornness my pregnant wife tolerates because I bring snacks to bed at 1 AM. In a room full of software engineers, I'm the guy who snuck into Harvard on a clerical error. So grade this on a curve.

Here's the thing I built. I'm calling it the 8 SIGNAL Operating System (my fancy words for 8 SIGNAL's implementation of ICM).

If you've been around in the community long enough, you know the drill. It's one place where my whole team and I work alongside AI. Not a chatbot in the corner. Not eleven different tools nobody remembers to open. One environment, and every department lives inside it. Marketing. Client work. Accounting. This week, legal.

The part that still makes me a little dizzy: it routes itself.

--- Hand it a legal document and it walks itself to the legal corner of the OS, does the work there, and still carries the context of the whole company with it.

--- This morning, mid leadership meeting, I fed it notes on a job candidate. Never told it where to look. It went and found the job descriptions on its own and started scoring the fit while I was still talking.

--- It's tool-agnostic. Whatever model is best in that moment, Claude, Gemini, Codex, it's supposed to reach for that one. I'm not married to a vendor. I'm married to the result. (I should probably test this out for myself, but I'm taking Jake's word on this one.)

And the boring win I love most:

every week somebody on my team used to pull our accounts receivable and payable out of QuickBooks by hand and type them into a task before our leadership meeting. Tedious. Easy to forget. As of last week, the system reads it, organizes the numbers the way my team likes to see them, drops them in the right place (Asana task description) on its own, and moves last week's data to a new place (Asana comments on that same task). Nobody touches it. Three months ago I could not have built that. I learned how by building it.

So back to the big word.

You all kept saying "orchestration" and I kept nodding like I knew. Turns out an orchestrator is just the mall map that says you are here, legal is over there, please proceed in an orderly fashion. I built the map. I still don't love the word. But I get it now, and that only happened because the people in this room kept saying it until it stuck.

One thing I keep thinking about. I'd been reading about how Fortune 500s are spending millions trying to deploy AI across a whole company in a unified way, and still getting stuck. Some of you work for companies that are throwing away the opportunity to let you save them money by implementing AI in your departments the smart way. Meanwhile my five-person shop did it in an afternoon. The giants have to turn an aircraft carrier. I just had to point. That advantage is real and it's ours, and I don't think enough of the small builders in here know they're holding it.

A big chunk of why I could build any of this is Jake and his team. The folder-and-context way of thinking I keep using came straight out of his videos and conversations with others in this community. Cheapest professional development on my calendar, like I said last time (I tend to repeat myself. I'm working on it).

Now the actual reason I'm posting. I am, statistically-probabilistically-not-so-elastically-deterministically, the least technical person who has built one of these. So I want the engineers to poke holes. Where does this fall apart at scale? What am I doing that's going to bite me in three months that I can't see yet because I don't have the training to see it? What would you have done differently?

Talk down to me. We've established I can take it.

Still stalking, still learning,

Ruben

P.S. Yes, I noticed I opened a post about hating the word "orchestration" by announcing I built an orchestrator. Character development. It's my story arc :D

26 comments