No more counting use cases — everything is a use case now. Alex Lieberman's viral list of 30 features of an AI-native company gets the full feature-by-feature treatment: what NLW agrees with, where he quibbles, and what his enterprise work adds — plus the missing 31st feature the comments surfaced: someone still has to own the result.
AI-native finally has substance — and it's not bolting agents onto old processes.
A year ago companies bragged about how many AI use cases they had. Now the agentic transition has actually begun, and the hallmarks of companies redesigned from the ground up are coming into focus: context as code, skills over prompts, loops over prompting, governance as unlock, autonomy that's earned. The through-line across all thirty features: don't constrain agents to mimic your old workflows — build the systems, metrics, and guardrails that let them find better ones.
A year ago companies were still talking about how many use cases they had for AI. Now everything is a use case, the long-awaited agentic transition actually began in 2026, and the question has shifted to what companies are transforming into.
Mapping how work actually gets done unlocks the tribal knowledge trapped in people's heads and Slack side-chats, and that context is enormously valuable. But the hidden assumption that agents will do things the way humans did is very likely wrong — in many cases the better approach is giving agents the goal and the guardrails and letting them figure out the how.
Nine months ago 'daily driver' meant access to a frontier model; now it means a work harness like GrokBot, Claude Cowork, or ChatGPT@work — an environment built for advanced knowledge work and coding, where you manage context, skills, and tool access. Expect more companies to roll their own on open-source foundations for flexibility, rather than risk investing in a tool like Cursor only to lose model access when it's sold.
Aggregating structured and unstructured data, documents, and business logic into a queryable source of truth is the feature the rest of the list is built on. For the biggest organizations, though, a lattice of sources of truth that agents can traverse and reconcile may be more realistic than a single layer.
Model routing is right, but it's part of a larger architecture designed to match task difficulty to model capability. Done well, divisions of labor like heavy planning on higher-effort models and execution on cheaper, faster ones fall naturally out of that design.
Keep architecture docs and conventions updated and make diligent upfront planning an operating discipline. The subtle shift: context isn't background info — it's the actual foundation agents build on, and that's as much mindset as process.
Be willing to throw away everything you've built every three months and reimagine workflows from first principles. Whatever the actual cadence, don't get attached to the clever thing you figured out two months ago — if the AI companies do their jobs, there will be an easier or more powerful way soon.
AI-native organizations use skills distribution systems to manage agent behavior and improve token efficiency across workflows. It's emblematic of a bigger shift: agent management is becoming a discipline, and improving and sharing skills across the org — not siloed in individuals — is part of it.
Keep technical implementation apart from high-level specs so non-technical staff can contribute in formats agents turn into implementation plans. The signal: when Claude Tag launched, Anthropic's technical team said a striking share of their building — the number that sticks is something like 60% — now starts from shared spaces, which naturally opens those conversations to more contributors.
We're at the very beginning of figuring out the key metrics of agentic delivery, but whatever we land on likely includes some sense of completeness — and cost per completeness — so model-harness combos can be compared apples to apples.
Agent-native development — fleets of coding agents that plan, write, test, review, and ship while humans set intent and acceptance criteria — is far less controversial than a year ago. Many organizations still run traditional processes, but the shift looks inevitable.
CLI tools that parse metadata in markdown files and traverse dependency relationships let agents be precise about input tokens — progressive disclosure for company knowledge. This is where the list gets usefully granular: put the metadata an agent needs to judge relevance at the top of knowledge files so it doesn't burn context window on things it doesn't need.
Accounting and record-keeping move toward continuous processes with forecasts reset on a much tighter cadence — OpenAI CFO Sarah Friar recently wrote about doing exactly this inside OpenAI and the mindset and technical discipline it required. The next step: giving the rest of the agentic operating system access to those financial models so cost logic informs strategy and tactics.
Non-technical employees take solutions from idea to production with the company's governance, access, versioning, and software conventions built in. It's not about replacing software engineering — it's about making the things non-engineers build contiguous with how the engineering organization actually works.
Loops give agents a goal and bumpers and let them iterate until they hit a verifiable, objective success metric — 'hit X% on this test' works; 'the interface should look good' doesn't. AI-native organizations get good at defining those metrics even for knowledge work that lacks them natively, because without evals as core infrastructure, the loops simply don't work.
Alex's version runs experimental, scaling, and optimization phases with bets across infrastructure, innovation, and efficiency. Whatever your phases, the big recommendation is an ROI architecture sophisticated enough to recognize that different efforts have different goals — while still judging them all within one framework.
Agent swarms deploying hundreds or thousands of creative variations before scaling ad spend still looks inevitable; what was underestimated was how short-term compute constraints would delay it, and as good-enough models get vanishingly cheaper over the next six months, the experimentation normalizes. Expect a barbell: crazy agentic swarms on one end, utter number-denying human taste for brand on the other — machines on one side, Rick Rubin on the other, and somehow it'll work. The same collapsed content costs make weekly SEO/AEO experimentation-and-measurement loops worth running too.
After the past several months, agentic cybersecurity systems defending against AI-powered threats look absolutely necessary. But exactly what capabilities legitimate defenders get access to, and how they're provisioned, is one of the most important near-term design and policy questions for AI companies and governments now that critical cyber thresholds have been crossed.
Near-frontier open-weights models that can be post-trained on first-party data open real opportunities for high-volume processes that need state-of-the-art performance at reasonable cost. Not every organization will roll its own models — but if you have the technical capability, it's a place to find an edge right now.
People on either side of the work sandwich is wholeheartedly right, though the right human intervention points in the middle of processes are still unknown. Meanwhile, autonomy must be earned: agents climb a ladder from observation to suggestion to acting with approval to acting alone — an ounce of prevention worth a pound of cure.
Not every knowledge worker becomes a full-time manager of agents, but the capacity to build — to use code to prototype, ship, and solve your own problems — is now a critical capability. Products will abstract the technical details away over time, but that won't make people less of builders, and the implications for how enterprises organize themselves are big.
Record everything worth learning from — the twin of process blueprinting, and much to the delight of the 75 meeting note-takers now in every Zoom. Then trace every output to its prompt, model, data, and approver, so human feedback attaches to something specific rather than a vague sense that something is off.
People don't talk about this enough: AI-native organizations treat governance as a way to unlock innovation, with legal, HR, and IT working in lockstep with the owners of the AI agenda. The technical twin is guardrails before features — agents inherit the permissions of whoever is asking, enforced in the data layer, so nothing has to be relitigated every time. This may be a key hallmark separating truly AI-native companies from AI-bolted-on ones.
The bias toward self-disruption cuts beyond how you do current work to what work you should be doing at all. Much of AI's big transformation won't be efficiency on today's tasks but the orthogonal, adjacent opportunities AI now makes it possible to pursue.
The best addition from the comments: every AI workflow needs a clear owner, a measurable goal, and someone responsible when things go wrong — the best AI-native companies won't just ask 'can AI do this?' but 'who owns the result?' That's nothing short of a new management discipline, and it applies to everyone, because everyone is becoming a manager of agents as well as an implementer of their own work.