A "harness" is framed as all the infrastructure, interfaces, context, and state that wrap a stateless large language model so it can actually produce work. SaaS businesses will follow a trajectory from traditional human-built software to engineers and other functions pairing with agents, to agents running core tasks with humans in review roles, to proactive background agents orchestrating humans. As that happens the company itself becomes a harness: the product becomes model output plus the company’s integrations, context, permissions, and review interfaces, while humans shift into "taste-holder" roles that supply judgment and selective oversight.
That shift changes what matters strategically and operationally. A good harness routes human attention to the highest-value moments (e.g., agents synthesize customer feedback for a product lead, escalate feature proposals to an engineering taste-holder, or present top UI variants to a designer). Differentiation will come from how harnesses learn, watch, interface, and integrate, so many firms will build top-level harnesses in-house and plug third-party components for specific workflows. If any vendor can run an entire business harness end-to-end, that business becomes commoditized. Expect increased in-house harness building, orgs redesigned around harness roles, AI-native entrants winning in harness-able domains, and more headless software to enable outer-loop automation.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.