Workday Is the Friend Graph
What a16z's System of Intelligence thesis looks like when you apply it to where the data actually lives.
On May 14, three partners at a16z, Gio Ahern, Stephenie Zhang, and Alex Immerman, published a piece arguing that the most valuable layer of GTM software is no longer the database. It's the layer that reads the database, reasons across it, and acts. They called this the System of Intelligence, and they used the CRM as their example.
The argument is more true in talent than it is in sales. They picked the more competitive battleground.
Their metaphor is Facebook's friend graph and news feed. The friend graph was supposed to be undisruptable. Then the news feed showed up, and the graph became one of many inputs feeding it. The graph never went away. It just stopped being where users went.
Now apply that to talent.
The HRIS is the friend graph. Workday, UKG, and Oracle HCM hold employee records. The ATS is also part of the graph. Greenhouse, iCIMS, and Lever hold candidate records. These systems remain authoritative for the data they manage.
A CHRO or VP of Talent still has to connect what those systems show. A record in one system does not by itself explain the relationship between a hiring decision and the post-hire outcome stored elsewhere.
The System of Intelligence in talent is the layer that reads across approved Systems of Record, reasons over them, and surfaces a prioritized list of decisions for a named human. Where the evidence supports it, each item can carry the cost of action, the cost of inaction, and a drafted cross-system workflow. The human approves, edits, or declines before the system acts.
The Systems of Record are still where the data lives. The System of Intelligence is where the work happens.
What the morning looks like
a16z walked through the morning of an account executive in 2027. The AE opens her laptop to a research agent already done reading the prospect's 10-K, a dialer already coached on the recurring objections, and notes from yesterday's call already structured back into Salesforce. The CRM is still authoritative. She just doesn't go there anymore.
An illustrative morning for a VP of Talent looks similar, with one difference. Each item in her feed is a drafted workflow rather than a notification. The production evidence today is limited to insurance talent. Mobility, succession, retention, operations, and revenue workflows begin with read-only historical replay and separate validation.
She opens her laptop to a prioritized feed.
At the top: several new hires in the producer cohort need an early-ramp review. Each case shows the evidence, the modeled cost of delay, and a proposed response waiting for the responsible manager. Nothing is sent until that person approves or edits it.
Underneath: candidates in the active pipeline display evidence historically associated with the defined production outcome. Each case carries uncertainty and counterexamples. A named human reviews the evidence, edits the proposed workflow if needed, and makes the final call.
Underneath: an internal-mobility replay has surfaced employees whose stated preferences may align with an open role. That workflow remains illustrative until the customer's historical replay, validation, and approvals are complete.
Underneath that: a prior applicant may now align with a current opening. If the customer's retention, consent, and outreach policies permit reuse, the system can draft a proposed next step for a recruiter to review.
She does not log into Workday. She does not log into Greenhouse. She does not log into Salesforce. The approved data remains in those systems while the intelligence layer turns connected context into ranked evidence and drafted workflows.
She approves what she wants to approve. She edits what she wants to edit. She sends back what doesn't look right.
This is the news feed. It is the valuable layer now.
Three is the floor
Talent has more than one System of Record, and the decision often depends on relationships across them.
The three primary ones are the CRM, the HRIS, and the ATS. The CRM holds field context. The HRIS holds post-hire outcomes. The ATS holds the candidate record. Each system provides one part of the decision record.
The broader architecture may also include assessment, performance management, compensation, learning, engagement, mobility, background-check, and scheduling systems. Ten to fifteen systems is a useful planning range. The exact sources and permissions vary by customer.
The full context is difficult for one person to assemble during a live decision. It can span a resume in the ATS, assessment scores, interview records, post-hire outcomes in the HRIS, and field context in the CRM. The intelligence layer connects those records while preserving their source and time.
An agent does.
This is the orchestration problem a16z described, applied to talent. The relevant Systems of Record can have different schemas, identifiers, access rules, and owners. The intelligence layer has to reconcile those differences without guessing at uncertain mappings.
The agents do not wait
Many AI hiring tools are reactive. A recruiter types a query, the system answers, and the recruiter decides what to do next.
This is not a System of Intelligence. This is a search engine with a costume.
The System of Intelligence can work in the other direction. Within the customer's approved operating envelope, agents inspect connected evidence and draft workflows that may deserve attention. Outside the validated insurance hiring workflow, those patterns begin as historical replay. They do not become production recommendations until the customer validates and promotes them.
Inside a validated workflow, the agents do more than log a notification. They can brainstorm the response, draft the cross-system workflow, and present it with evidence for approval. A named human can approve, edit, or decline it.
At runtime, the product surface is thirteen agents driving sixteen decisions across three pillars: Hire & Develop, Operate & Run, and Sell & Grow. An orchestrator coordinates them, and all thirteen run against one calibrated model. Insurance talent is the current production proof. The other decisions begin with read-only historical replay and their own validation path.
The recruiter does not see the orchestration. The recruiter sees a feed. The work happens behind the feed.
When every applicant looks the same
Applicant volume and AI-assisted resumes make surface-level screening less informative for many roles. Applicants with different abilities can arrive looking similar on paper. Keyword density and bullet structure are weak substitutes for a measured post-hire outcome.
From the recruiter's seat, evaluation time remains constrained while resume signal can flatten. Tighter keyword filters and mandatory experience floors may remove people who would have reached the employer's defined outcome.
Instead of filtering blindly, Nodes treats measured outcomes as governed evidence with uncertainty, never categorical truth or proof of an individual's success. Human decisions provide context, and a named human makes the final call. Calibration or production promotion requires validation. The 10,765 agents describe the historical study cohort rather than product throughput. Enterprise talent at one Fortune 500 insurance carrier is the sole current production proof. Underwriting, lending, and admissions remain illustrative and would begin with read-only historical replay.
The recruiter still makes the final call. The goal is to widen review where rigid filters would have excluded evidence worth inspecting.
The governed outcome evidence
a16z argues that a System of Intelligence can preserve operational context that would otherwise be difficult to hand to a successor. They called it institutional memory you can ship.
We call it the governed outcome evidence.
When an experienced producer exits, much of the working context may leave with them. A handoff rarely captures every decision, exception, and field pattern. Governed records can preserve parts of that context for a successor without treating one employee as the template for another.
In capturing this knowledge, human choices remain contextual evidence. Governed measured outcomes provide the evaluation target, and any later calibration candidate requires validation and named-human promotion.
This governed evidence avoids universal or cross-domain scores. It prevents automatic adverse decisions by refusing to treat a single employee as a template, ensuring a named human always decides.
At one Fortune 500 carrier, ramp moved from 8 to 12 months to six weeks. This is an observed deployment result and does not isolate one feature as the cause. On that carrier's production record, a 30-day reduction corresponds to $1,357 per agent per year. That modeled constant should not be transferred to another employer without its own data.
Enterprise talent at one Fortune 500 insurance carrier is the sole current production proof. Underwriting, lending, and admissions remain illustrative. Each would begin with read-only historical replay, followed by separate validation and named-human approval before production.
Where the thesis breaks
a16z's piece is precise about what the System of Intelligence does and approximate about how it should be built. The approximation is where the thesis hits the wall of regulated enterprise.
One common architecture is a multi-tenant cloud platform that ingests data from customer Systems of Record via API, reasons over it in a shared inference layer, and writes back. A data-sensitive talent buyer has to inspect whether that boundary is allowed for the records involved.
Performance data is sensitive. Compensation data is sensitive. PII on candidates and employees is sensitive. At the anchor carrier, review required a deployment control that kept data inside the customer's environment.
The carrier rejected six AI hiring vendors on architecture in eighteen months before Nodes reached production. The customer-required boundary kept the data inside its environment.
The System of Intelligence in talent has to deploy in the customer's environment. Single-tenant. VPC-resident. Model weights owned by the customer. Zero customer production-data egress.
The architecture is the product.
A vendor built around external data movement may need substantial architectural work to meet a customer-controlled VPC boundary.
This is the gap in the thesis as written. The thesis is clear about what the value layer does and quiet about where it runs. For regulated enterprise, the deployment boundary is a decisive part of the evaluation.
The production record
The argument so far is theoretical. The reason to take it seriously is that the production data already exists.
At a Fortune 500 insurance carrier, we deployed the System of Intelligence inside the carrier's VPC, integrated with their ATS, HRIS, and CRM. Over four years, this historical study cohort covered 10,765 agents.
The study parsed 8,181 unique skills from four years of applicant data and tested 3,597 against the first production milestone. After Bonferroni correction, zero predicted the milestone and 30 were anti-predictive. In the n=50 subset of milestone achievers with parseable ATS skills text, the industry-experience filter would have excluded 80%, and the cumulative funnel would have excluded 98%.
In the smaller subset with personality data, full fusion reached AUC 0.735. That result comes from an evaluable n=229 small sample in one-carrier research. It measures ranked separation within that sample, not certainty about any person or universal production accuracy. Keyword screening was evaluated separately at AUC 0.558. In the live deployment, requisition-to-hire time moved from 127 days to 38 days, and median contract-to-production time moved from 109 days to 62 days. These observed one-carrier results do not establish causation or promise the same outcome elsewhere.
The methodology, including the adversarial review protocol and the decision-trace logging, is published on arXiv: Decision Traces. The paper explores this thesis. The observed association at the customer's production environment supports the approach, though outcomes depend on specific contexts. The companion argument, why the layer that assembles this context holds its value while models commoditize, is in Model quality stopped being the bottleneck. The context layer is.
What is being built
The next decade of enterprise talent software is being built at this layer. Not at the ATS layer, where the database vendors will continue to compete on integrations and pricing. Not at the HRIS layer, where Workday will continue to be Workday. At the layer above both, where an AI-native System of Intelligence reads from the existing Systems of Record, reasons across them, and surfaces decisions worth making, with quantified costs and pre-built workflows.
A credible system at this layer should make three things inspectable: where it runs, who owns the data and weights, and how it works with existing Systems of Record. Nodes answers those questions with a VPC-resident, single-tenant deployment, customer-owned weights, and zero customer production-data egress.
a16z's piece is the framework. This is the implementation.
Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises. Methodology: Decision Traces.