For most of the history of software and marketing, the expensive part was producing the load-bearing writing: the code that has to run, the content that has to ship, the report someone acts on. That's the part that took skill and time.
AI is collapsing that cost. Not to zero, but close enough that the bottleneck moves. When producing a working function, a campaign, or a migration stops being the hard part, the hard part becomes everything around it: wiring the output into real data, keeping it honest, guarding what it can touch, and getting a team to actually run it.
That operational layer is the opportunity. Anyone can get a model to write something. The value is in the plumbing, the guardrails, and the adoption — turning a capability into something an organization runs every day and trusts. That is the work this firm does. But the payoff for crossing that layer is bigger than efficiency, and it's worth being precise about why.
Metal
When code was expensive, the only way to afford it was to spread the cost across the whole market. That's what SaaS is: one company builds a workflow once and sells it to ten thousand businesses, each of whom bends their operations to fit it. It worked, but it meant your operations ended up looking like everyone else's. The software defined the workflow; the business didn't. Data, processes, and workflows had to be rigid, because reshaping them meant paying full freight for custom code, so almost nobody did. You worked in metal: expensive to shape, painful to change, so you left it alone.
Clay
When the cost of code collapses, workflows stop being metal and turn to clay. You can shape them to how your business actually runs, reshape them when it changes, and build the thing that fits instead of the thing the market sold to everyone. Operational creativity, locked down for a generation by the economics of software, opens back up.
That's the real prize, and it isn't doing the same work cheaper. It's that a business can now own sovereign, custom operational infrastructure, built from the ground up around how it actually operates. That infrastructure becomes a source of separation from competitors who are all still running the same off-the-shelf workflows. The collapse of code cost, once you operationalize it, is how a company stops looking like the market and starts operating like nobody else.
A note on where compute lives
Default to cloud. For most teams, most of the time, that's the right answer: elastic, managed, cheapest to start. But deployment should be a function of data sensitivity, and that means being able to reason across cloud, hybrid, and on-premise honestly.
We can reason about it because we've done it. We run local models in real systems — a research engine that routes most of its work to a local Qwen model for cost, on a workstation built around an NVIDIA 5090. For a data-sensitive business, where "the data never leaves the building" is a hard requirement, a dedicated on-prem box that slots into existing IT as just another endpoint is a legitimate option. It's one delivery mode among several, chosen by the audit.
Why this matters
The companies that win the next few years won't be the ones with access to the best model. Everyone has that. They'll be the ones who operationalized it: who built the clean data, powered up their people, connected their departments, and managed the whole thing like a system instead of a demo. The ones who used cheap code to build operational infrastructure shaped to them, and stopped running the same workflows as everyone else. That's the work.