The problem with homegrown agent platforms is not that they are bad. They are often quite good — for the first year. The problem is that they are built by people who have other jobs.
The engineer who built your internal agentic coding platform is not going to maintain it forever. They will get promoted, get poached, or move to a more interesting project. When they do, their system becomes a liability. The Shopify Slack agent gained traction organically and is now getting a team built around it. That is the best case. It is still fragile.
The firehose of internal AI tools at these companies is, by one insider's account, "out of control." A lot of these tools are built not because they are the highest-leverage work, but because developers want to practice agentic workflows and build portfolio pieces in case the next round of layoffs comes. A lot of engineering energy producing tools with a bus factor of one.
These platforms go into disrepair. They stay feature-poor because no one has the mandate to invest in them continuously. They are desktop-grade tools when the organization needs a cloud-grade system with autoscaling, proper sandboxing, audit trails, and the reliability production workloads demand.
I have seen this movie before. At Astronomer, we built the commercial Kubernetes-based Airflow platform. Our customers were companies that had outgrown a single-machine Airflow deployment some data engineer stood up as a POC and accidentally promoted to production. The pattern is identical now. I've argued the real product is what replaces homegrown — and the trigger for that replacement is almost always the day the maintainer leaves.
Sources
Related Essays
The Real Product Is What Replaces Homegrown
Do not compete with what Shopify is building internally. Build the system that replaces every homegrown agent platform when the engineer who built it moves on.
What the Build-vs-Buy Data Actually Shows
From Stripe to a five-person startup, the agent stack is mostly blue — built in-house. The harness is bought. The middle of the stack is built. The opportunity sits in turning blue dots green.
The Gap Is Infrastructure, Not Intelligence
The distance between an AI demo and an AI deployment is not a model gap or a harness gap. It is the absence of composable primitives for the boring parts of operationalization.
Key takeaways
- The problem with homegrown platforms is not that they are bad. They are often quite good — for the first year. They are built by people who have other jobs.
- When the maintainer gets promoted, poached, or moves to a more interesting project, the system becomes a liability with a bus factor of one.
- These platforms stay feature-poor and run desktop-grade infrastructure when production workloads need cloud-grade reliability, audit trails, and autoscaling.
FAQ
Why do homegrown agent platforms decay?
They are built by ambitious individuals as side projects. When those engineers leave or move teams, no one has the mandate or context to keep investing. The platform stays at v1 while the surrounding world keeps changing.
What is the typical bus factor?
One. A single staff or principal engineer holds the system together. When they get promoted or poached, the institutional knowledge leaves with them and the platform begins to rot.