For most of my career I believed I was building products but looking back, I was mostly building org charts.
Every real scaling problem I hit — Weedmaps from 30 to 300+ engineers, ShopKeep through a $550M acquisition, BuildOps to a unicorn — eventually resolved to the same thing. Not a hard technical problem but a deep coordination problem: who owns this, who hands off to whom, where the context lives. what happens between the functions.
The features were almost never the bottleneck but the seams between teams were!
What actually reaches the customer
Here’s the thing founders under-weight: the customer never experiences your product but they experience the coordinated output of your entire company.
The signup flow is product, but the billing dispute is finance, and the outage note is comms, the contract redline is legal. The “can you build us X” is sales making a promise engineering has to keep! By the time value reaches a customer, it has passed through six functions that had to agree on what they were doing.
That coordinated output is the product, and the software is just one input to it.
And the machine that produces the coordinated output is the org chart. The place where the shared context lives so the handoffs don’t drop.
We just never called it the product, because we had no way to build it some we could only staff it.
Conway’s Law, and the trap inside it
Conway’s Law says systems come to mirror the communication structure of the organization that builds them. You ship your org chart, the saying goes.
Most people treat that as a warning: watch out, your architecture will inherit your dysfunction but there’s a bigger implication hiding in it.
If the system mirrors the org, then the org is the higher-order design surface. The org chart isn’t a constraint on the product. The org chart is the upstream product… the one that generates the one your customers see.
For all of tech history that upstream product could only be built out of people. You wanted a new capability, you hired a function. You wanted faster coordination, you reorganized. Reorgs, in my experience, shipped more customer value than most feature sprints but they just never showed up in the roadmap. That was the cognitive overhead tax made org-shaped: the non-product surface area that eats a company alive, rendered as headcount and meetings.
You couldn’t compile an org, since you could only grow one, slowly, at the cost of the thing you were actually trying to build.
What changes when the org chart is software
The AI era isn’t interesting because models answer questions better. It’s interesting because coordination is now something you can build instead of staff.
Decompose a goal into steps, sequence them by dependency, execute across functions, hold context across weeks without dropping it on a handoff. That’s an org chart you can run in software and the coordination layer that used to require a floor of people to operate.
Which flips Conway’s Law from a warning into a design tool. If the system mirrors the org, and you can now build the org directly as a coordination layer, then you design the org you want and let the product fall out of it. The org chart stops being the thing that slowly accretes around your product. It becomes the first thing you build.
The coordination layer is the product and everything else is a module you plug into it.
Why I’m building at this layer
This is the whole reason Aqen exists. You bring the idea and Aqen brings everything else — legal, finance, marketing, ops, product — coordinated across every function against your actual goals, with a shared memory every teammate reads from and writes to.
Read that back with this post in mind. It is not a pile of features. That’s an org chart rendered as software! A cofounder-shaped coordination layer that produces the coordinated output a company used to need forty people to produce I’m now convinced it was the actual product all along and that for the first time it’s something you can build instead of staff.
If you’ve ever watched a reorg unblock more value than a quarter of feature work, you already know what I mean. That instinct was right. We just finally have a way to build the thing the instinct was pointing at.
If you’re building at this layer too, or trying to, I want to compare notes.