# Revolv: Agentic Relationship Intelligence (Full Content) > Revolv is an iOS app that helps you build the relationships that move you forward. It understands the context behind your relationships, discovers who matters next, and helps you take the right next step. It's the relationship intelligence platform, the CRM alternative, for people who build relationships, not pipelines. # Updated: 2026-08-15 ## What is Revolv? Revolv is agentic relationship intelligence for professionals: AI-powered, on-device, and private. It captures context from every conversation, then proactively surfaces the relationships going quiet, the warm introduction paths you'd have missed, and the right moment to reach out. From day one, using only your calendar and contacts, it shows who in your network is slipping away. ## Key Features - **Smart Bump**: Exchange contacts with a tap using UWB proximity - **AI Follow-Up Reminders**: Never miss a follow-up with intelligent timing - **Connection Intelligence**: Relationship insights powered by on-device AI - **Travel Mode**: Networking tools optimized for on-the-go professionals - **Conversation Memory**: Every context, every detail, every follow-up, remembered - **Privacy-First**: On-device processing, no data sold, your network stays yours ## Who Is It For? Revolv is built for relationship-driven professionals: - Founders building partnerships that compound - Executives managing stakeholder relationships - Sales leaders turning conversations into deals - Investors managing portfolio relationships at scale ## Company - **Founded by**: Jon Chu (see https://www.therevolv.com/about for founder details) - **Headquarters**: United States - **Category**: Business / Productivity / Relationship Intelligence / Agentic AI - **Platform**: iOS (iPhone) - **Status**: Pre-launch, early cohort forming ## Key Pages - Homepage: https://www.therevolv.com (waitlist signup, brand home) - Platform: https://www.therevolv.com/platform (product features, on-device AI architecture, privacy model) - Agora: https://www.therevolv.com/agora. Revolv's invitation-only dinner series for founders, operators, and investors; a curated table of ~two dozen people put together by hand and informed by Revolv's relationship intelligence, hosted in New York, San Francisco, and Hong Kong. Request a seat (submit your deck to Revolv) to be considered. - Apply to Revolv: https://www.therevolv.com/dealrooms. Founders submit a pitch deck (link or PDF); Revolv reads it, maps it against the investor relationship graph, and surfaces warm introduction paths and investor timing signals instead of cold outreach. Every submission is reviewed by a human; free to submit. - Advisory: https://www.therevolv.com/advisory (APEX Framework strategic advisory for teams of 5-500) - About: https://www.therevolv.com/about (company overview, founder, mission) - Signal: https://www.therevolv.com/signal. Essays by Jon Chu on the people you already know, why the ones who matter drift out of view, and what it takes to notice in time. - FAQ: https://www.therevolv.com/faq (common questions about the product and waitlist) - Contact: https://www.therevolv.com/contact (hello@therevolv.com) - Privacy Policy: https://www.therevolv.com/privacy - Terms of Service: https://www.therevolv.com/terms # Signal Articles (full text) ## A Weak Tie Is Not a Weak Relationship - **Canonical URL**: https://www.therevolv.com/signal/weak-ties-are-not-weak-relationships - **Author**: Jon Chu | **Published**: September 2, 2026 | **Reading Time**: 7 min - **Tags**: Relationship Intelligence, Networking, Strategy In 2022, LinkedIn ran an experiment on twenty million people. Most of them never knew they were in it. For five years, the "People You May Know" algorithm quietly varied its suggestions. Some users were nudged toward close connections, others toward distant ones. Two billion new ties and six hundred thousand new jobs later, the researchers were settling a fifty-year-old argument about where opportunity actually comes from, and the results ran in *Science*. [1] The distant connections won. But not the most distant ones. The effect peaked at a specific distance: moderately weak ties, around ten mutual connections. They moved more careers than close friends, and more than near-strangers. Past that peak, more distance stopped helping. That is the finding that should bother you. If the rule were simply *the more distant the better*, you could follow it. There is no such rule. The value sits at one particular distance, and nothing you own tells you which of your ties are standing at it. --- ## The Argument LinkedIn Settled You already know the claim. Granovetter, 1973: opportunity travels through acquaintances, because your close ties live in your world and hear the same news you do. [2] By the time something reaches them, it has usually reached you. Strong ties give you trust. Weak ties give you news. But fifty years of retelling flattened the sharp part, and the sharp part is this: > A weak tie is not a weak relationship. It is a measure of distance. Its value has nothing to do with how rarely you talk. It comes from how much of their world you have never seen. And that value is not fixed. It moves whenever the far side moves: a job change, a new city, a market entry, a fundraise. --- ## What It Costs You You sat next to her at a dinner two years ago. Good conversation, traded numbers, you even wrote a note afterward. Then nothing, because nothing needed to happen. Last month she took a senior role at a company entering your market. You found out the way a stranger finds out: from an announcement, days late. A mutual friend, one seat over at that same dinner, had known for weeks. Nothing about the relationship changed. Everything about its value did. She was a weak tie in the only sense that matters: her world was not yours. She was a bridge you forgot you owned, and the stale date next to her name was measuring the one axis that does not matter. What you needed was not a reminder to follow up. It was a notice that something on the far side had moved: ```revolv-card { "label": "Revolv · Why this surfaced", "stamp": "Aug 19", "name": "Maya Okonkwo", "role": "VP Partnerships, Arcadia Health · new", "rows": [ { "label": "Came from", "value": "Director of BD, Telos Systems, 4 years" }, { "label": "Distance", "value": "9 mutual · nothing in common with your current work" }, { "label": "Your tie", "value": "Agora dinner, New York, Nov 2024 · one note, March" } ], "why": "Arcadia moved into claims automation on Aug 19. That is the category in your March note on Telos, the company Maya just left. She is your only tie inside it.", "action": "Open your March note →", "caption": "A composed illustration of the notice, not a screenshot. What matters is which line does the work: not “you have not spoken in 21 months”, which was true the whole time and meant nothing, but the change on the far side." } ``` The hard part is not finding out that Arcadia entered claims automation. That is public the morning it happens, and a feed will hand it to you along with four hundred other things. The hard part is that the announcement means nothing on its own. It becomes yours only when something connects it to a note you wrote in March, about a company you have not thought about since, belonging to a person whose name you would never have thought to search. Knowing the world moved is cheap. Knowing which movement is yours is the work. Some version of this has happened to you this year. The unsettling part is that you cannot know which tie it was. --- ## You Will Not Fix This With Discipline The instinct is to follow up more. Be better. The research says that will not save you either. A 2011 study in *Organization Science* had executives reconnect with dormant ties, people they had not spoken to in years. [3] Those conversations delivered more novel information than their active relationships did, and the executives had expected less from them than they got. They had been avoiding the one kind of outreach that helped them most, because silence makes a call feel awkward and closeness feels safe. So the deck is stacked twice. Your instincts point at the nearest ten people, and your tools agree with your instincts. Memory sorts by closeness, phones by recency, both toward people whose information you already have. What a network actually needs is two dimensions, and the second one moves. How strong the tie is, and how much world it bridges. Trust lives on the first axis and holds still. Discovery lives on the second and changes without telling you. Every product you can buy, and every instinct you carry, measures the axis that does not move. The interesting question about a network was never "who have I talked to lately?" It is "whose position just changed in a way that changes mine?" Nobody holds that question open across two hundred quiet ties. The executives in the study could not manage a handful. --- ## The Room You Cannot Build Alone Noticing is only half of it. The second axis has two moves, and instinct is bad at both. The first is seeing the bridges you already own. The second is acquiring bridges you do not have yet, and that is where most people quietly give up, because the rooms available to them are the wrong rooms. Your industry's annual conference. The company offsite. Alumni drinks. Every one of them is assembled around the thing you already have in common, which is another way of saying a room with no distance in it. You will leave with names. You will not leave with news, because nobody in that room knows anything you were not going to hear anyway. Now read the dinner again. You did not engineer that meeting. Somebody sat you next to a person whose world did not overlap yours, and two years later that accident turned out to be the only tie you had inside a market you cared about. The accident is the product. Distance does not accumulate on its own, and it does not survive a room that assembled itself. It gets built one table at a time, by someone choosing every seat. That is the problem I am working on with [Revolv](/platform). Not another place to store contacts. An answer to the second axis in both directions: the quiet tie whose far side just moved, and the table where the next quiet tie gets made. Granovetter has been right for fifty years. LinkedIn proved it on twenty million people who never agreed to be proved on. And almost nothing about how anyone keeps a network has changed since, because both moves that follow from it are things a person cannot do alone. So the question is not who you should call this week. It is how many bridges you have already forgotten you own, what changed on the far side of them this month, and who you have still never met because every room you ever walked into agreed with you. --- ## Sources 1. Rajkumar, K., Saint-Jacques, G., Bojinov, I., Brynjolfsson, E., & Aral, S. (2022). A causal test of the strength of weak ties. *Science*, 377(6612), 1304-1310. [doi.org/10.1126/science.abl4476](https://doi.org/10.1126/science.abl4476). The inverted-U finding, moderately weak ties as the most productive channel with diminishing returns to further weakness, is the paper's own refinement of Granovetter. The effect was strongest in industries where work has moved online. 2. Granovetter, M. S. (1973). The strength of weak ties. *American Journal of Sociology*, 78(6), 1360-1380. [doi.org/10.1086/225469](https://doi.org/10.1086/225469). 3. Levin, D. Z., Walter, J., & Murnighan, J. K. (2011). Dormant ties: The value of reconnecting. *Organization Science*, 22(4), 923-939. [doi.org/10.1287/orsc.1100.0576](https://doi.org/10.1287/orsc.1100.0576). --- ## The System of Record for the System Itself - **Canonical URL**: https://www.therevolv.com/signal/systems-thinking-needs-a-system-of-record - **Author**: Jon Chu | **Published**: July 20, 2026 | **Reading Time**: 4 min - **Tags**: Strategy, Relationship Intelligence Netflix CPTO Elizabeth Stone says the most important skill she hires for is no longer deep specialization. It is systems thinking. She is right. And it surfaces a question that rarely gets asked. If seeing the system is the scarcest skill in the AI era, where is the system written down? --- ## The Missing System of Record Walk through any company's software stack. - CRM holds the customers. - ERP holds the money. - HRIS holds the employees. - Jira holds the work. - The wiki holds the knowledge. > Every company has a system of record for everything except the system itself. How decisions actually get made. Who trusts whom, and how much. Which relationships carry the business and which are quietly going cold. Where influence really flows, whatever the org chart says. That layer runs the company, and it is recorded nowhere. It lives in people's heads, and it walks out the door with every departure, every reorg, every acquisition. For decades that was survivable. The only intelligence reading your company was human, and humans fill gaps with judgment and hallway context. A new VP spends her first ninety days rebuilding the picture: who to ask, who to convince, which approval is a formality and which one is the real decision. The company pays for that reconstruction over and over, and calls it onboarding. Agents can't do the reconstruction at all. --- ## What AI Sees, and What It Misses Point AI at your documents and it understands your documents. It does not understand your organization. It cannot tell that a renewal is safe because of a ten-year relationship, or that a deal died because trust did, or that the fastest path to a decision runs through someone three boxes away from the official owner. The most consequential layer of the enterprise is invisible to the systems we are now asking machines to reason over. This is the argument I keep coming back to in Signal. Greatness comes from systems, not heroics ([Stop Chasing Greatness. Start Building the System.](/signal/stop-chasing-greatness)). AI transformation starts with making the organization understandable to AI ([AI Doesn't Replace Human Intelligence. It Runs on It.](/signal/ai-runs-on-human-intelligence)). The ontology work in that second piece covers the operational layer: objects, properties, links, actions. But there is a layer underneath the operating model that the ontology conversation usually skips. The human one. Relationships, trust, influence, and the informal decision paths that determine whether anything in the official process actually moves. Stone is describing the org-design side of the same shift: hire the people who can see the system. But a hire is not infrastructure. The map a systems thinker builds lives in their head, and it leaves when they do. The missing piece is a system of record for what they see. --- ## A Graph You Can Only Build With Consent That is the problem I am building Revolv against: relationship intelligence, a working model of the human system. Who knows whom. What the history is. Where trust is strong and where it is decaying on a schedule. The obvious way to build that graph is the wrong way. Mine the inboxes, scrape the calendars, infer the relationships from metadata nobody agreed to share. It has been tried, and it fails for a structural reason, not a technical one: a trust graph built on surveillance destroys the thing it claims to measure. The moment people learn the system is watching them, they route around it, and the graph goes dark exactly where it matters most. The only durable version is built from what people choose to capture. The context someone writes down after a meeting because they want to remember it. That is slower. It is also the only version that stays true. --- ## The Next System of Record The last generation of enterprise software recorded transactions. The next one has to record how the organization actually works. Systems thinking is the skill. The relationship graph is the infrastructure. Companies will need both, because the thinkers keep leaving, and the machines are already here. --- *For companies staring at this gap now, this is the work I do hands-on through [Revolv Advisory](/advisory): making how your organization actually works legible, to your people and to your AI, before you ask agents to reason over it.* --- ## AI Doesn't Replace Human Intelligence. It Runs on It. - **Canonical URL**: https://www.therevolv.com/signal/ai-runs-on-human-intelligence - **Author**: Jon Chu | **Published**: July 8, 2026 | **Reading Time**: 7 min - **Tags**: Strategy, AI & Technology Most answers start with technology. Which model? Which vendor? Which platform? But across transformation work in investment banking, asset management, media, and regulatory compliance, I have seen the same failure mode repeatedly: the organization does not fully understand how its own people, knowledge, workflows, and decisions connect. AI agents turn that old organizational problem into a technical constraint. If you want AI to transform an enterprise, you first have to make the enterprise understandable to AI. > Everyone is focused on making AI smarter. The enterprise challenge is making the organization understandable to AI. --- ## The Pattern Behind Every Transformation Every stop in my career taught the same lesson from a different angle. In investment banking, the systems were never the hard part. The hard part was the workflows underneath them: how a trade actually moved through the firm, who touched it, where the exceptions lived. At one asset manager, the entire culture was built on making decision-making criteria explicit, because a decision you cannot articulate is a decision you cannot systematize. In media, the challenge was fragmentation: content and data ecosystems that had grown up separately and had no shared model of what anything meant. In regulatory compliance, every workflow step had an owner, an approval, and a consequence on paper. The risk lived in the gap between the documented process and how the work actually moved. Different industries. Different technology eras. Same failure mode. The organizations that struggled were not short on tools. They were short on a shared understanding of how the business actually operated. The knowledge existed, but it lived in people's heads, in unofficial processes, in the judgment of whoever had been there longest. In every one of those engagements, the deployment was the easy part. What mattered was understanding complex systems, aligning people around outcomes, and using the technology to change how organizations operate. AI does not change that work. It makes the cost of skipping it impossible to hide. What was missing, everywhere, was an explicit model of how the business actually worked. Computer science borrowed a name for that model from philosophy decades ago. It is called an ontology. AI agents are what finally made it urgent. --- ## What an Ontology Actually Is Strip the philosophy away and the concept is simple: - A database tells you what happened. - A knowledge base tells you what people wrote down. - An ontology tells you how the business works. For enterprise AI, the ontology becomes the machine-readable model of how the organization operates: the operating model translated into a structure a machine can reason over. It teaches AI what your business means, not just what your documents say. An ontology has four parts, and each one solves a specific failure of AI systems today. **Objects are the nouns.** Customers, contracts, employees, invoices, support tickets, sales opportunities. Without objects, AI sees "row 12478 in Salesforce." With them, it sees Acme Corp, a Fortune 500 customer, renewal coming in 45 days, owned by Sarah, with three open support issues. Objects give AI a business vocabulary. **Properties are the facts.** Industry, contract value, renewal date, risk score, role, permissions. Ask an AI without properties to "show me risky accounts" and it guesses. With properties, risky account has a definition: renewal inside 60 days, usage down 30 percent, an unresolved P1, negative sentiment on the last three calls. The answer stops being a vibe and starts being a query. **Links are the relationships.** Customer owns contract. Contract includes products. Support ticket affects renewal risk. Sales rep manages account. This is where intelligence emerges, because the AI stops retrieving isolated facts and starts understanding a graph of the company. **Actions are the verbs.** Create the renewal plan. Escalate the ticket. Update the CRM. Trigger the workflow. This is what separates a chatbot from an agent. The ontology tells the agent what exists, how things relate, and what it is allowed to change. What exists, how it connects, what can be done about it. That is the operating system AI needs, and no vendor can ship it to you. Which raises the real question: where does it come from? --- > Enterprise AI is becoming an organizational design problem disguised as a technology problem. ## People Define the Ontology The people closest to the work hold the context that no system of record captures. How decisions actually get made. Which exceptions matter. Which processes are unofficial but load-bearing. Where knowledge actually lives. Who really owns a call, regardless of what the RACI chart says. The org chart does not describe how a company operates. The ontology does. This is why I keep coming back to the foundation layer of the [Apex Pyramid](/signal/most-orgs-arent-built-to-scale): People + Outcomes = Transformation. I wrote there that AI amplifies whatever already exists, and that structure has to precede systems. Ontology is what that foundation layer produces when you take it seriously. Clear ownership of outcomes, explicit decision rights, alignment on what good looks like: those are not soft cultural exercises. They are the raw material of a machine-readable operating model. An organization that has done the people work can write its ontology down. An organization that has not will discover it cannot, and that discovery is worth more than any pilot. --- ## Outcomes Give the Ontology Direction Here is how the first meeting usually opens: "The board keeps asking about our AI strategy. Where should we be deploying agents?" It sounds like a plan. It is a solution looking for a problem. The better question is: what business outcome are we transforming? Cut customer resolution time by 40 percent. Shorten onboarding from months to weeks. Raise compliance accuracy. Compress the sales cycle. The outcome determines which objects matter, which properties need to be precise, which links carry the intelligence, and which actions the agent needs permission to take. An ontology built around outcomes stays lean and useful. An ontology built for completeness becomes a data governance project that ships nothing. The agents are downstream of all of it. The architecture that is emerging looks like this: people define the knowledge, knowledge structures the ontology, the ontology grounds the agents, and the agents drive business outcomes. The model sits in the middle of that chain as the reasoning engine. The model thinks. The ontology tells it what to think about. --- ## The Moat Moved The first wave of enterprise AI was a straight line: user, prompt, model, answer. It produced demos and disappointment in roughly equal measure. The enterprise future runs through structure: user, agent, ontology, business systems, action. And that reordering changes where advantage lives. The frontier models will continue to differentiate. But access to model intelligence is becoming broadly available, and improvements arrive on someone else's schedule. Your organization's understanding does not. Your ontology improves on your schedule, for you alone. It encodes how your company thinks, decides, and changes. No competitor can copy it because no competitor operates exactly the way you do. The models are rented. The context is owned. That is the moat. If a company asks whether AI can automate their entire enterprise, the honest answer is: not without first mapping how decisions happen. You cannot automate what you don't understand. --- ## The Same Problem, One Level Down I see this pattern from both sides now. Advising enterprises, the ontology is the operating model of a company. Building [Revolv](/platform), it is the operating model of something smaller and more personal: a professional network. The objects are people, companies, meetings, and commitments. The properties are trust, recency, and context. The links are who knows whom, and how well, and why. The actions are the intro, the follow-up, the meeting brief. The scale is different. The principle is identical. Intelligence without a model of the underlying system produces answers that sound right and change nothing. Intelligence grounded in how the system actually works is what produces transformation, whether the system is a Fortune 500 operating model or one person's network of relationships. The technology was never the constraint. Understanding was. AI has not changed that. It has just made understanding executable. --- ## What I Learned About Thinking From Ray Dalio (And Why It Shapes How I Build AI) - **Canonical URL**: https://www.therevolv.com/signal/principled-thinking-relationships - **Author**: Jon Chu | **Published**: June 10, 2026 | **Reading Time**: 7 min - **Tags**: AI & Technology, Strategy, Founder Stories Ray Dalio published a piece today called "[Principled Thinking and AI Need to Go Together](https://www.linkedin.com/pulse/principled-thinking-ai-need-go-together-ray-dalio-jo84e)." When I read it, I did not learn anything new. I recognized it. I worked at Bridgewater Associates. The culture there does something to how you think. It forces you to name the criteria behind every decision, to separate instinct from logic, to demand that reasoning be visible. That discipline stayed with me long after I left. It shaped how I evaluated opportunities, how I advised companies, how I thought about what was actually driving outcomes versus what people assumed was driving them. Over the past year, building a relationship intelligence platform, I have started to see just how deeply that way of thinking runs through everything I design. --- ## What Principled Thinking Actually Means Dalio defines principled thinking as "the examination and systemization of one's decision-making criteria rather than just thinking to make decisions." Most people will read that as organized thought. It is sharper than that. That practice rewires how you operate. Once you start naming your decision-making criteria explicitly, you notice how often you were making decisions on instinct dressed up as logic. The instinct might be right. But until you articulate the criteria underneath it, you cannot test it, refine it, or teach it to anyone else. You cannot improve what you cannot see. That is the distinction most people miss. The gap is not between good judgment and bad judgment. It is between judgment you can name and judgment you cannot. --- ## Understanding, Not Data Mining Dalio makes a point in his piece that most AI builders are ignoring. He says principled criteria "are not best derived by looking at what would have worked in the past and assuming that it will work in the future, i.e., data mining, or simply asking an AI what to do. They are based on logical understandings converted into decision-making systems." The default approach in AI is pattern recognition. Feed in enough data. Find correlations. Optimize for what worked before. The problem is that correlation-driven systems break silently. They cannot tell you why they made a decision. They cannot be debated. They cannot adapt when the environment shifts because they never understood the environment in the first place. Dalio describes the alternative: each criterion has a reason attached. "If this happens, do this, because XYZ." The because matters more than the rule. When a principle stops working, you trace back to the causal logic and find where the world changed. You do not throw out the system. You refine your understanding. At Bridgewater, that discipline was cultural. You lived inside it every day. That habit shaped how I think about building intelligence systems. When I sat down to design Revolv, I kept coming back to the same question: are the criteria underneath this system based on a logical understanding of how relationships actually work, or are we just mining patterns and hoping they hold? The Bridgewater instinct was always to demand the former. Dalio tests his principles across time and geography. As far back as possible. Every country. Every type of environment. If a principle only works in certain conditions, it is not a principle. It is a local optimization. I apply the same test to the principles underneath Revolv. Trust builds through consistent follow-through. Context compounds over time. Relationships weaken without reinforcement. People remember being remembered. These hold across industries, roles, and eras. They were true before phones. They will be true after whatever comes next. --- ## The Partner, Not the Oracle The most counterintuitive thing Dalio says is that even the most advanced AI is not good enough to follow blindly. He describes the ideal as a partnership: the system makes moves based on systematic criteria while you make moves based on the criteria in your head, and you compare the two. Most AI products are built on the opposite assumption. Hand off thinking. Accept the answer. Move on. Dalio's framework rejects that entirely. Another line stayed with me even more: "The system always speaks to you, explaining its logic so you can understand each other and align your thinking." Most AI products are silent. They process in the background and surface a result. If you ask why, you get a confidence score or nothing at all. At Bridgewater, the culture demanded that reasoning be visible. You were expected to challenge logic, not defer to it. That friction was the point. The alignment happened through the disagreement. > You are not outsourcing your judgment. You are augmenting your memory. I internalized that years before I built anything. Revolv is built around both principles: the human stays in the loop as a partner, never as a passenger, and the system explains its reasoning so you can challenge it, calibrate against it, and improve alongside it. A relationship intelligence system that cannot explain itself cannot earn trust. And without trust, you either follow blindly or ignore entirely. Neither produces intelligence. --- ## The Domain That Was Missing Dalio writes from investing. He has spent fifty years encoding cause-effect relationships about markets into systematic criteria that partner with human judgment. The framework he describes is proven in that domain. But there is a domain where the same framework applies and nobody has built it yet: relationships. People already have good instincts about their relationships. They know who matters. They know when something feels off. They know when a connection is going cold. What they lack is the systematic memory to act on those instincts at scale. Their judgment is sound. Their bandwidth is not. The insight Dalio surfaced decades ago, that principled thinking bridges human intelligence and computerized intelligence, turns out to be exactly what professional relationships need. Encode cause-effect relationships about people, trust, timing, and context into systematic criteria. Build a system that partners with memory the way Dalio's systems partner with judgment. Make the logic visible so the human can debate with it and improve alongside it. That is what I am building with [Revolv](https://www.therevolv.com/platform). Not a CRM. Not a networking tool. A relationship intelligence platform that applies principled thinking to the domain of human connection, preserving the context that makes professional relationships compound over time rather than decay. --- ## The Line That Connects The same instinct kept showing up across my career: the hardest problems are the ones where human judgment is irreplaceable but human memory is insufficient. That was true in every company I advised, every product I built, every team I watched struggle with decisions that depended on context nobody had written down. I wrote about why [systems thinking is the skill that survives](/signal/the-skills-that-survive-the-talent-shift) when everything else gets automated. This is what I meant. Bridgewater taught me to take that instinct seriously. To build systems around it instead of working around its absence. The criteria should be explicit. The logic should be visible. The human should stay in the loop. The principles should be durable enough to survive whatever technology comes next. That is what I am building toward. And reading Dalio's piece today reminded me where it started. > AI did not make relationships simpler. It made the cost of forgetting impossible to hide. - Jon Chu --- ## The Skills That Survive the Talent Shift - **Canonical URL**: https://www.therevolv.com/signal/the-skills-that-survive-the-talent-shift - **Author**: Jon Chu | **Published**: April 16, 2026 | **Reading Time**: 8 min - **Tags**: AI & Technology, Strategy, Networking I had coffee last month with a director of product, who had just been laid off. She had twelve years of experience. Strong track record. Led teams through two major platform migrations. She was not panicking, but she was confused. "I did everything right," she said. "I shipped. I hit the numbers. I managed well. And they still cut my role." She was not wrong. She had done everything right by the rules that existed three years ago. The rules changed. --- ## What the Data Actually Says About Your Role McKinsey just published what they call an [AI transformation manifesto](https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/the-ai-transformation-manifesto). Twelve themes drawn from studying companies that have actually transformed with AI. The headline numbers are for executives: 20% EBITDA uplift, $3 returned for every one dollar invested. But buried in the data is something that matters far more if you are mid-career, between roles, or watching layoffs ripple through your industry. Here is what they found about talent. As AI agents take on more scheduling, status reporting, and routine decision-making, human roles shift up the value stack. Engineers spend less time writing code and more time designing architecture, workflows, and quality controls. Business leaders spend less time managing tasks and more time setting objectives, defining success metrics, and making trade-offs. Their framework is called the "30-70 shifts." More than 70 percent of talent should be in-house. More than 70 percent should be builders, not coordinators. More than 70 percent should perform at competent or expert level. Read that again. Seventy percent builders, not coordinators. If your job is primarily coordinating other people's work, scheduling, status reporting, aligning stakeholders, routing information between teams, that job is being absorbed. Not next year. Now. The product director I mentioned? Her role had quietly become coordination. She spent most of her time in alignment meetings, writing status updates, and translating between engineering and leadership. The actual product decisions were being made by two senior engineers who understood the domain and used AI to move from insight to prototype in a day. Nobody told her the center of gravity had shifted. --- ## What Actually Becomes More Valuable Here is what I keep seeing, both in the companies I advise and in building Revolv: three capabilities are pulling away from everything else in value. **Domain judgment.** Not domain knowledge. Judgment. The difference is that knowledge can be looked up. Judgment is knowing which question to ask, which tradeoff to accept, which constraint actually matters. It is the instinct that says "this feature looks right but will break the business model in six months." That instinct comes from years of operating inside a specific domain. AI cannot shortcut it because it requires lived pattern recognition, not information retrieval. I wrote about this in "[When AI Makes Software Cheap, Judgment Becomes Expensive](/signal/when-ai-makes-software-cheap)." The argument was about product teams, but it applies to every function. When execution gets cheap, the bottleneck moves to the person who knows what to execute. That person's value goes up, not down. **Systems thinking.** This is the ability to see how a decision in one part of the organization cascades through others. How a pricing change affects support load. How a hiring freeze in engineering shifts the burden to product. How a data architecture choice made today constrains what you can build in two years. Most professionals are trained to optimize their function. Systems thinkers see across functions. That has always been true. It is now essential because AI compresses the distance between decisions and consequences. When you can build and ship faster, the cost of a bad decision shows up faster too. The person who sees second-order effects before they arrive is worth more in a world that moves at AI speed. **Relationship context.** Every career-defining opportunity I have seen, and I have watched hundreds across advisory work, came through a relationship. Not a job board. Not a recruiter. A person who mentioned someone's name in a room they were not in. The professional who had coffee with me? The role she will get next will almost certainly come through her network. Through someone who remembers what she is capable of, who trusts her judgment, who can vouch for her when she is not in the room. AI can write your resume, generate your outreach, and optimize your LinkedIn profile. None of that replicates the trust that comes from someone remembering a conversation you had two years ago and connecting it to an opportunity that just opened up. I explored this in depth in "[The End of Networking: The Rise of Relationship Intelligence](/signal/relationship-intelligence)." The strongest professional signal is no longer who you know. It is how well you remember the people you meet. AI did not change that. It intensified it. --- ## The Coordination Layer Is Disappearing Let me be direct about what is happening. AI agents are absorbing the coordination layer of organizations. Meeting scheduling, status aggregation, cross-team communication, routine analysis, report generation, basic project management. These tasks used to require people. They are being automated faster than most professionals realize. This is not a prediction. McKinsey's manifesto describes it as already happening inside the companies that are winning. "The result is fewer people doing higher-leverage work, with clearer accountability and faster learning loops." Fewer people. That part is real. But the second half of the sentence matters more: higher-leverage work. The question is not whether your role will change. It will. The question is whether you are building the capabilities that sit above the coordination layer. If you spend your day primarily on: - Routing information between people who could talk directly - Summarizing what happened in meetings - Creating slides that repackage someone else's thinking - Managing processes that exist because of organizational friction Those activities are on the automation curve. Not because they are unimportant, but because they are pattern-matchable. AI is very good at pattern-matchable work. If you spend your day on: - Making decisions where the context lives in ten conversations AI never heard - Building trust that took two years of follow-through to earn - Seeing how a pricing change in Q1 becomes a support crisis in Q3 - Teaching someone how to think about the problem, not just how to solve it Those activities are moving up in value. They require the kind of accumulated context that cannot be fed into a prompt. --- ## Memory Is a Career Moat Here is the connection most people miss. The [Apex Pyramid framework](/signal/most-orgs-arent-built-to-scale) I introduced last year was about organizations: how structure, workforce design, and scalable systems determine whether AI transforms a company or stalls at the pilot stage. Only 25 percent of AI initiatives deliver expected ROI. The structural gap is real. But careers have the same architecture. The professionals who compound their context, who carry institutional knowledge from role to role, who maintain relationships with depth and continuity, who remember what they learned and build on it rather than starting over, those professionals become harder to replace with every passing year. The ones who start fresh every job, whose relationships reset when they change companies, whose institutional knowledge lives only in their current Slack workspace, those professionals stay interchangeable. AI makes that interchangeability visible in a way it never was before. Think about what happens when you leave a job. Most of what you learned about how that organization actually works, the informal power structures, the real reasons decisions got made, the relationships you built with people across teams, all of that context evaporates. You start your next role at close to zero. Now multiply that across a career. Every transition is a reset. Every reset means you are competing against your own forgetting. The professional who treats their accumulated context as an asset, who systematically preserves what they learn about the people and organizations they work with, builds a compounding advantage that looks small in year one and enormous by year ten. This is why I built Revolv. Not as a CRM. Not as a networking tool. As an intelligence layer that helps professionals preserve the context that makes their relationships and judgment more valuable over time. The thesis is simple: the people who remember will outperform the people who forget. That was true before AI. AI just raised the stakes. --- ## What She Did Next The product director did not send out 200 applications. She did not sign up for an AI certification. She did not rebrand herself on LinkedIn as an "AI-native leader." She went narrow. She picked the domain she understood best, supply chain operations for mid-market SaaS, and started advising two companies where that specific judgment was scarce. Within six weeks she had a full-time offer from one of them. Not because she applied. Because the CEO had watched her work through a problem he had been stuck on for months and realized she saw connections his team could not. That is the pattern I keep seeing. The professionals who land well after a transition are the ones who go deeper into what they already know rather than wider into what everyone else is learning. McKinsey's data shows the same thing at the company level: the best AI returns come from concentrating on one to three domains, not spreading across dozens. Careers work the same way. AI can be a generalist. You should not try to compete with it on breadth. She also did something most people skip. She went back through her network with intention. Not mass outreach. She reached out to twelve people she had real history with, referenced specific conversations, followed up on commitments she had made months earlier. Three of those conversations led to the introductions that mattered. The career opportunities that count still come through people. They always have. But only if you show up with context when everyone else shows up cold. The skill underneath all of it was something she had been building for years without naming it: the ability to see how pieces fit together across teams, products, and time horizons. Systems thinking. The highest-leverage capability in any organization. It is learnable. It takes practice, not credentials. And it sits permanently above the coordination layer that AI is absorbing. Every decision she made that required understanding tradeoffs, politics, timing, trust, or relationships was an asset appreciating in the background. AI can process information. It cannot sit in the room and know that the CFO's hesitation is not about the budget, it is about what happened in last quarter's board meeting. That kind of judgment is earned. It compounds. And it is about to become the most valuable thing any professional carries. --- ## The Uncomfortable Truth The talent shift McKinsey describes is not coming. It is here. The coordination layer is thinning. Headcounts are dropping in the exact roles that used to define middle management. The ones who thrive will be the ones already building the assets AI cannot touch: deep domain judgment, system-level thinking, and relationships rich with context and trust. That is not comfortable to hear if you are in transition right now. But it is clarifying. Because it tells you exactly where to invest. Not in learning the latest AI tool. Tools change every quarter. Not in adding certifications. Credentials are being commoditized faster than ever. Not in optimizing your LinkedIn profile for algorithms. In the things that compound: what you know deeply, who you know well, and what you remember about both. > AI made execution cheap. It did not make judgment cheap. It did not make trust cheap. It did not make the accumulated context of a career cheap. Those are yours. And they are worth more now than they were a year ago. --- ## Why Most AI Transformations Reset Every Quarter - **Canonical URL**: https://www.therevolv.com/signal/why-most-ai-transformations-reset-every-quarter - **Author**: Jon Chu | **Published**: April 14, 2026 | **Reading Time**: 8 min - **Tags**: AI & Technology, Strategy Every quarter, another company restarts its AI strategy from scratch. New vendor. New use case list. New team. Same lessons relearned. [McKinsey just published data](https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/the-ai-transformation-manifesto) that explains why. They studied 20 companies that actually transformed with AI. The results: 20 percent EBITDA uplift. Three dollars of incremental EBITDA for every one dollar invested. Breakeven in one to two years. Those are not pilot results. That is structural repricing of how a business operates. But here is the part most executives will read past: the advantage did not come from the technology. McKinsey says it directly. The tools are broadly available. The gap between the companies generating those returns and everyone else is not what AI they use. It is how fast they apply it to real problems. How they organize. How they decide. How quickly they close the distance between knowing something and doing something about it. I have been saying this for the past year building Revolv. Technology made execution cheap. The scarce resource is the organizational capacity to know what to execute, learn from what happened, and remember what was learned. McKinsey just gave that argument a dataset. --- ## The Missing Thirteenth Theme The manifesto lists twelve themes. Strategy. Talent. Speed. Platforms. Data. Trust. Adoption. Agentic engineering. Continuous learning. All of them are real. All of them matter. But there is a thirteenth theme hiding underneath the other twelve, and it is the one that explains why the winners keep winning and the losers keep restarting. Organizational memory. Not knowledge management. Not documentation. Not the wiki nobody reads. Memory. The accumulated context that lets an organization make its next decision better than its last one. Consider the pattern. The companies that generated $3 per $1 invested concentrated on one to three business domains. Not a long list of AI use cases. One to three areas where they went deep and stayed deep. Concentration produces those returns because depth builds institutional knowledge. Each deployment teaches the organization something. A model fails in a specific way and the team learns why. A workflow redesign exposes a bottleneck nobody had mapped. A data enrichment effort reveals that the real signal was in a field everyone had been ignoring. That learning informs the next decision. The next decision deepens the context. The context compounds. I introduced the [Apex Pyramid framework](/signal/most-orgs-arent-built-to-scale) last year after seeing this pattern across every advisory engagement. BCG's data told the same story from a different angle: only 25 percent of AI initiatives deliver expected ROI and just 16 percent scale across the enterprise. The framework addressed the structural gap. Alignment. Adaptive workforce. Scalable systems. What I did not name explicitly then was the mechanism underneath all three layers. The thing that makes alignment hold, that lets workforce planning adapt, that keeps systems from becoming shelfware. Memory. The organization's ability to carry what it learned into what it does next. Companies that spread across dozens of use cases never build that depth. Each initiative starts close to zero. Lessons from one deployment do not transfer to the next because the teams are different, the sponsors are different, and the institutional knowledge from round one lives in someone's head or a slide deck that nobody will open again. The organization relearns the same things every quarter. > The winners remember what they learned. The losers keep relearning. That is the gap. Not technology. Memory. --- ## What the Talent Shift Actually Means McKinsey introduces what they call the "30-70 shifts." More than 70 percent of tech talent should be in-house. More than 70 percent should be builders, not coordinators. More than 70 percent should operate at competent or expert level. The implication is compact, high-density teams outperforming large armies of lower-skilled staff. That tracks with what I have seen across every advisory engagement and what became obvious building Revolv. But the manifesto goes further. As AI agents absorb coordination, execution, and routine decision-making, human roles shift up the value stack. Engineers spend less time writing code and more time designing architecture, workflows, constraints, and quality controls. Business leaders spend less time managing tasks and more time setting objectives, defining success metrics, and making trade-offs. Fewer people. Higher-leverage work. Faster learning loops. I wrote about this shift in "[When AI Makes Software Cheap, Judgment Becomes Expensive](/signal/when-ai-makes-software-cheap)." The argument was that as execution gets cheaper, the premium on product sense, systems thinking, and review goes up. McKinsey's data confirms it from the enterprise side. The 20 companies that generated real returns did not just deploy AI. They changed who does what. Business leaders, usually one to three levels below the CEO, became the ones conceptualizing, building, and running the AI systems. Not IT. Not a center of excellence. The people who understand the domain. That is not a reorg chart. That is a different kind of company. And it only works when those leaders have enough context to make informed decisions quickly. Which brings us back to memory. A compact team with deep institutional context will outperform a larger team that has to reconstruct its understanding every cycle. The talent shift McKinsey describes is real, but it has a prerequisite that the manifesto does not name: the organization has to be able to preserve what its best people know, even as the team composition changes. When a key leader leaves and takes three years of deployment context with them, the team that replaces them spends six months relearning decisions that were already made. Nobody got less talented. The system forgot. --- ## Data Enrichment Is the Compounding Asset The same dynamic that makes talent depth compound also applies to data. The manifesto makes a distinction that most companies miss. There is a difference between making data easy to consume and enriching data for sustained advantage. Productized data means teams can discover it, access it, and use it across applications without wrangling. That is necessary. It is also table stakes. Enriched data means the data gets more valuable through use. Quality improves. Context deepens. Uniqueness compounds. As David Baker, the 2024 Nobel laureate in Chemistry, observed: "AI needs masses of high-quality data to be useful." Without enrichment, AI plateaus. The model is only as good as what you feed it, and most organizations are feeding it the same raw inputs they had before the model existed. Consider what happens when a wealth management firm runs every client interaction through its risk model. The first hundred interactions calibrate the baseline. The five hundredth interaction catches a pattern the model could not have seen at one hundred. By the thousandth, the system is detecting life events and portfolio risks before the advisor notices them. The data did not just accumulate. It learned. This is the exact dynamic driving what we build at Revolv. A meeting note becomes a knowledge graph connection. A knowledge graph connection becomes a trust signal. A trust signal surfaces an opportunity. The intelligence layer does not just store data. It enriches it through use. That is what compounding context looks like in practice. Not a bigger database. A smarter one. The same principle applies at the enterprise level. The 20 companies McKinsey studied are not just collecting more data. They are building systems where data quality improves as a byproduct of using the system. Each decision, each deployment, each customer interaction leaves the data layer richer than it found it. That is the moat. Raw data is available to everyone. Enriched, contextual, use-deepened data is not. --- ## Why Agents Widen the Gap The manifesto's most forward-looking theme is agentic engineering. Foundation models capable of sustained, autonomous work. Productivity gains in software development that McKinsey calls astonishing. Companies racing to build repeatable agentic playbooks. But the manifesto includes a warning that deserves more weight than it gets: "The excitement for agentic AI may be getting ahead of companies' ability to manage the more complex risks." I have built a multi-agent system. Six specialized agents with a circuit breaker, a knowledge graph, and a progressive context loader that keeps the whole system under a token budget. The thing I can tell you from inside the build is that agents are powerful when they operate inside a system that already has strong feedback loops, clear accountability, and enriched data to act on. > Agents inside a fragmented organization create more sophisticated confusion. An agent that can reason autonomously is impressive in a demo. In production, it needs to know when it is wrong, how to degrade gracefully, and where to hand off to a human. It needs guardrails that are not bolted on but designed in from the first line of architecture. It needs trust as a design constraint, not a compliance checkbox. McKinsey is right that "Rewired leaders consistently absorb new technologies faster because they have built the underlying capabilities to do so." The inverse is also true. Companies that skipped the organizational fundamentals will find that agentic AI does not help them catch up. It widens the gap. Faster execution on top of fragmented context just produces more wrong answers with more confidence. --- ## The Speed Tax McKinsey frames organizational speed as "the metabolic rate of the organization." Companies win when they redeploy resources faster, empower teams without excessive dependencies, and reduce the latency from insight to decision and decision to action. Here is the part that makes this harder than it sounds. Speed without memory is just churn. Moving fast only helps if the organization retains what it learns along the way. I have watched companies sprint through quarterly AI initiatives, each one starting fresh because nobody documented what the last team discovered. The cycle looks productive from the outside. Internally, it is the same lessons being re-derived by different people in different rooms. This is the adoption gap I described in "[AI Is Everywhere in Business. Its Impact Isn't](/signal/ai-adoption-gap)." Seventy percent of firms using AI. Nine in ten reporting no meaningful change. The gap is not adoption. It is retention. Not of people. Of learning. True organizational speed requires three things working together. The ability to decide quickly. The ability to act on that decision without bureaucratic latency. And the ability to remember the outcome so the next decision starts from a higher baseline. Most organizations have invested in the first two. Almost none have invested in the third. --- ## The Test Pull up your last three AI initiatives. Can you trace a direct line from what the first one learned to how the third one was designed? If the answer is no, you are resetting. The fix is not another initiative. It is the decision to preserve what each one discovers before starting the next. --- ## What This Means McKinsey closes with a line that is easy to skim and hard to argue with: "Companies can accelerate their way through developing capabilities, but they cannot skip over the foundational work." The companies generating $3 per $1 did not start with AI. They started with organizational clarity. Clear ownership. High-density teams. Data treated as a performance asset. Speed embedded in the operating model. AI amplified what was already working. The companies struggling did not fail at AI. They skipped the prerequisite. And the prerequisite that ties all the others together is the one nobody has a line item for: the capacity to learn from what you did and carry that learning into what you do next. Most organizations invest in hiring. They invest in tooling. They invest in AI. They do not invest in preserving and compounding the context that makes all those investments coherent. That is where transformation stalls. The [Apex Pyramid](/signal/most-orgs-arent-built-to-scale) gave teams a structure: align people around outcomes, design workforces that adapt, build systems that multiply execution. This article names what holds that structure together. Without organizational memory, alignment drifts. Adaptive teams lose what they adapted to. Scalable systems scale the wrong lessons. Technology made execution cheap. Judgment got expensive. But the thing that makes judgment improve over time, the thing that separates the $3-per-$1 companies from the ones still running pilots, is not talent alone and not technology alone. It is memory that compounds. The companies that build that layer will pull away. The rest will keep resetting. --- ## When AI Makes Software Cheap, Judgment Becomes Expensive - **Canonical URL**: https://www.therevolv.com/signal/when-ai-makes-software-cheap - **Author**: Jon Chu | **Published**: April 5, 2026 | **Reading Time**: 8 min - **Tags**: AI & Technology, Product, Strategy Fifteen months ago, I wrote a piece for Revolv Signal called "[When AI Speeds Up Engineering](/signal/when-ai-speeds-up-engineering)." The argument was simple: when AI lowers the cost of building, it exposes the parts of product development that were never really about code. After fifteen months building Revolv, I believe that even more strongly now. AI is changing software. That part is obvious. The more important shift is what it is doing to the people, workflows, and decisions around software. Product, engineering, and design are still distinct disciplines. But the old boundaries are under pressure. The old sequence is, too. For years, most teams worked in a familiar pattern. Product defined requirements. Design translated them into interfaces. Engineering implemented the system. The structure made sense because writing production software was expensive, coordination was slow, and mistakes were costly. That logic is weakening fast. Coding agents can now turn an idea into working software in hours. Sometimes minutes. A rough prototype used to require real organizational effort. Now one capable builder can get surprisingly far with a prompt, a component library, and decent judgment. That changes the economics of the work. And when the economics change, the org chart is never far behind. --- ## The Bottleneck Has Moved The hardest part of building Revolv was rarely getting code on the screen. The harder questions showed up earlier and lasted longer. Should this feature exist? Does it solve a real problem or just create activity? How does it fit with the rest of the product? What happens when this decision compounds across ten other decisions? > AI makes first drafts cheap. It does not make judgment cheap. That is the shift. Software teams spent years optimizing around implementation. Today, implementation is getting cheaper while review, coherence, and product judgment are getting more expensive. Teams can generate more options than they can responsibly absorb. Prototypes multiply faster than decisions do. > At first, this feels like speed. Then it starts to feel like load. --- ## PRDs Are Not Dead. Their Job Has Changed. There is a fashionable line right now that PRDs (Product Requirements Documents) are dead. That is directionally true, but incomplete. The old PRD as the center of gravity is fading. A static document no longer needs to sit upstream of every meaningful product decision. Working prototypes now carry more weight because they make the conversation concrete. They show tradeoffs faster. They expose bad assumptions earlier. But intent still has to travel. Review still needs context. Teams still need to know what is deliberate, what is provisional, and what problem the feature is meant to solve. That means some version of a requirements document still matters. It just no longer has the same form or status. In practice, the new artifact may be shorter. Sharper. More executable. It may include prompts, system maps, prototype links, user flows, and a few lines of precise reasoning rather than pages of procedural detail. Long live product requirements. Just in a different form. --- ## The Most Valuable People Are Expanding Their Range One thing became clear while building Revolv: the people with the most leverage are the ones who can move across product, design, and technical execution without waiting for a meeting to translate the problem for them. That does not mean specialization disappears. It means the burden of proof for specialization gets higher. Generalists are becoming more valuable because coordination is now more expensive, relative to execution, than many teams realize. A builder who understands user behavior, has taste in interface decisions, and can work effectively with coding agents can compress days of back and forth into a single cycle of thinking and making. This is one reason the balance of power is shifting. The winners will not be the people who cling hardest to role boundaries. They will be the ones who can hold more of the system in their head. --- ## Product Sense Is Becoming the Scarce Resource In the old model, weak ideas often died from friction. They took too long to spec, too long to design, and too long to build. That protection is gone. Now weak ideas can arrive fully formed. They can look credible. They can even work. Once they exist, they create momentum. Someone says it is already built. Someone else says maybe we should just ship it. A mediocre feature that once would have died quietly now consumes review cycles, design energy, and roadmap attention. That makes product sense the scarcest resource on a modern product team. Not because product managers suddenly matter more than everyone else. They do not. It matters because every function now needs stronger judgment about what deserves to exist. Engineers need it. Designers need it. Founders need it. PMs need a lot more of it than before because the cost of bad judgment is no longer delayed by the cost of implementation. I wrote about this gap between adoption and actual impact in "[AI Is Everywhere in Business. Its Impact Isn't.](/signal/ai-adoption-gap)" The pattern is the same: organizations move faster than their judgment systems can absorb. > Cheap execution raises the price of sloppy thinking. --- ## Two Archetypes Are Emerging Across modern product teams, two archetypes are starting to stand out. The first is the builder. This person can move from idea to prototype quickly. They are comfortable using coding agents. They can reason across user need, workflow, interface, and implementation constraints. They do not need to master every layer, but they do need enough fluency to create momentum. The second is the reviewer. This person sees the second-order effects. They understand architecture, product coherence, usability, scaling, and operational risk. They protect the system from local decisions that look smart in isolation and create problems in aggregate. Most strong teams will need both. But the ratio is changing. AI expands the surface area of what can be built, which means the value of great review rises right alongside the value of fast building. --- ## Where the Leverage Concentrates If I step back from the last fifteen months, three roles look especially central in this next phase. Product thinkers, because someone still has to decide what is worth building and why. Data and intelligence engineers, because AI products are only as strong as the infrastructure, retrieval, orchestration, and data quality underneath them. Creatives and designers, because intelligence without interface is useless. Trust, usability, and adoption live in the experience. These are the three power players because modern software is becoming a three-body problem. Judgment. Intelligence infrastructure. Human experience. And sitting above all three is one capability that matters more with every passing quarter: systems thinking. --- ## Systems Thinking Is the Advantage This was true before AI. It is just much easier to see now. I explored this idea in depth in "[Stop Chasing Greatness. Start Building the System.](/signal/stop-chasing-greatness)" The argument holds: greatness is a system outcome, not an individual act. In engineering, systems thinking means understanding how services, data, dependencies, reliability, and scale fit together. In product, it means understanding how decisions accumulate, how features interact, and where complexity should live. In design, it means understanding how interface choices shape behavior, trust, and comprehension over time. When execution was expensive, organizations could confuse effort for rigor. You could spend weeks building something and mistake the process for quality. That cover is disappearing. AI is stripping the insulation away. It is making it painfully obvious which teams are coherent, which ones are fragmented, and which leaders can actually see the whole board. --- ## What Building Revolv Made Clear Building [Revolv](/signal/why-we-built-revolv) over the last fifteen months has reinforced something I suspected when I wrote "[When AI Speeds Up Engineering](/signal/when-ai-speeds-up-engineering)." The real story is larger than engineering. AI is compressing the distance between idea and software. That sounds like an engineering story. It is really an organizational one. As execution speeds up, companies are forced to confront the parts of product development they used to hide inside process: unclear thinking, weak prioritization, fragmented context, and shallow review. That is where the real pressure is now. This is also why I believe the future belongs to teams that can think across functions instead of defending them. The competitive edge will come from better judgment, tighter feedback loops, stronger architecture, and clearer product sense. Code still matters. Deep craft still matters. But the advantage is moving up the stack. > AI did not remove the hard part. It exposed it. And for product teams, that may be the most important shift of all. --- ## The Moment Steve Jobs Saw the Future - **Canonical URL**: https://www.therevolv.com/signal/steve-jobs-saw-the-future - **Author**: Jon Chu | **Published**: April 3, 2026 | **Reading Time**: 7 min - **Tags**: AI & Technology, Strategy, Founder Stories In 1983, a [28-year-old Steve Jobs stood in front of a room of designers in Aspen](https://www.youtube.com/watch?v=t9HmOz8H0qI) and made a series of claims that sounded detached from reality. Computers would be everywhere. People would spend more time with them than cars. They would become the dominant medium of communication. And design would determine whether humanity embraced them. At the time, almost no one in that room owned a computer. Four decades later, every one of those claims has become baseline reality. The takeaway is not that Jobs predicted the future. He understood how technology becomes part of human life before the market recognizes it. That is the lens worth applying now. Because we are at a similar moment with AI. --- ## A New Medium Is Emerging What Jobs saw in 1983 was not a product shift. It was a medium shift. Computers were moving from specialized machines into everyday objects. Not tools for experts, but environments people would live inside. That distinction matters. When a new medium emerges, it reshapes behavior before it reshapes business models. Electricity changed industry. Television changed culture. Computing changed how we think, create, and communicate. Today, AI is following the same pattern. The mistake most people are making is treating it as a feature. It is not a feature. It is the foundation of a new interaction model. > When a new medium emerges, it reshapes behavior before it reshapes business models. AI is not a feature. It is the foundation of a new interaction model. --- ## The Insight Most People Still Miss Jobs understood that technology adoption is not technical. It is emotional. In that Aspen talk, he made a point that still holds: these machines would be built regardless of how they looked. The question was whether they would be objects people wanted to live with. That was not aesthetic commentary. That was strategy. When technology crosses into the mainstream, design becomes infrastructure. It removes intimidation. It builds trust. It invites participation. The Macintosh proved it. The graphical interface and mouse did not just improve computing. They made it accessible. The same shift is happening again. > Natural language is doing for software what the mouse did for the computer. AI is not powerful because of what it can compute. It is powerful because of how easily humans can interact with it. --- ## The Real Prediction: Computers as a Communication Layer Jobs made another claim that sounded even less plausible. Computers would become the dominant medium of communication. At the time, email barely existed. The internet was not consumer-facing. Most business communication still relied on paper, phones, and fax. Yet today, communication is almost entirely mediated through digital systems. Email. Messaging platforms. Social networks. Digital identity. Jobs saw that computers would not just process information. They would sit between people. They would become the layer through which relationships are formed, maintained, and acted upon. --- ## We Are Crossing That Line Again AI is now pushing computing into its next phase. For the past forty years, software has been something you operate. You open an application. You input information. You execute tasks. Even as systems became connected, the model stayed the same. Humans orchestrated the work. That model is breaking. A new layer is forming above software: agents. --- ## Agents Are the Next Layer of Intelligence Agents change the structure of computing. They do not wait for instructions in the same way traditional software does. They observe context. They interpret intent. They coordinate across systems. They execute actions. Instead of navigating five different tools, the user defines an outcome. The agent handles the workflow. This is not incremental. It is architectural. Software is shifting from tools to intelligence systems that operate on your behalf. In that same 1983 talk, Jobs described something even more prescient. He imagined computers that could capture a person's "underlying spirit," their thought processes and knowledge, and make that intelligence available to interact with others. He was describing, forty-three years ago, what we now call agents: systems that carry your context, understand your intent, and act on your behalf. That is exactly the premise behind what we are building at [Revolv](/advisory). Not another AI tool that automates tasks, but an intelligence layer that understands the relationships and context behind every professional decision. The thesis is simple: the professionals who compound their network intelligence over time will outperform those who just move faster. Jobs saw that computers would sit between people. We believe the next step is building systems that understand what happens between them. The market reflects it. [Gartner predicts](https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025) that 40% of enterprise applications will embed task-specific AI agents by 2026, up from less than 5% in 2025. That is not gradual adoption. That is a medium shift. But here is the part that mirrors the AI adoption gap: [four in five enterprises](https://www.demandsage.com/ai-agents-statistics/) have adopted agents in some form, yet only one in nine runs them in production. The pattern repeats. The technology arrives before the organizational thinking catches up. > Four in five enterprises have adopted AI agents. Only one in nine runs them in production. The technology arrives before the thinking catches up. --- ## The Shift Beneath the Shift When this happens, the center of value moves. Not to better apps. Not to more features. To the intelligence layer that sits above everything else. That layer depends on one thing: context. Not just data. Context. Who you know. What has been said. What matters. What should happen next. Most systems today capture fragments. CRMs capture transactions. Email captures communication. Social platforms capture identity. None capture relationship context in motion. And that is where the next category forms. --- ## Relationship Intelligence If computers became the communication layer, agents become the coordination layer. But coordination requires understanding. Not just of data. Of people. Decisions do not happen in isolation. They happen through networks. Through trust. Through timing. Through context that rarely gets written down. This is the gap. And it is widening as systems become more automated. > Agents that understand workflows will be useful. Agents that understand relationships will be indispensable. --- ## The Pattern Repeats Jobs saw the pattern early. A new medium emerges. The interface changes. Adoption accelerates. Behavior shifts. New categories are built. We are at that same inflection point. AI is not the story. Agents are not the story. The story is what happens when intelligence becomes embedded in how we work, communicate, and make decisions. --- ## What Are You Building the Intelligence Layer Around? The companies that win this era will not be the ones that add AI to existing software. They will be the ones that define what the intelligence layer actually operates on. Most are building it around tasks. Faster summaries, faster code, faster reports. A few are building it around context. The relationships, timing, and trust signals that determine whether a decision lands or stalls. That is the bet we are making with [Revolv](/advisory). Not an AI that does things faster, but an intelligence layer that understands the people and relationships behind every decision. Jobs saw that computers would sit between people. The question now is whether your systems understand what happens between them. Ask yourself: if your most important deal, hire, or partnership depends on a relationship your tools cannot see, what is your AI actually optimizing? --- ## AI Is Everywhere in Business. Its Impact Isn’t. - **Canonical URL**: https://www.therevolv.com/signal/ai-adoption-gap - **Author**: Jon Chu | **Published**: March 28, 2026 | **Reading Time**: 5 min - **Tags**: AI & Technology, Strategy, Founder Stories I sat in an executive meeting last quarter where the answer arrived before the question did. The CEO opened with two slides. The first showed AI tools the company had deployed across six departments. The second was a headcount projection. "If we’re getting this much productivity," he said, "how many people can we cut by Q3?" Nobody in the room had measured the productivity. Nobody had asked what the tools were actually changing. The conversation jumped from adoption to reduction in under ten minutes. I’ve seen this meeting three times now, at three different companies, and it plays out the same way every time. ## Why are companies cutting headcount before measuring impact? They’re not alone. Fiverr’s CEO told employees to ["automate 100 percent"](https://www.businessinsider.com/fiverr-ceo-tells-employees-use-ai-or-get-left-behind-2025) of their work with AI, then cut 250 people a few months later to become an "AI-first company." Klarna replaced 700 customer service employees with an AI chatbot that handled two-thirds of all queries. Quality dropped. Customers revolted. The CEO [later admitted](https://www.wsj.com/articles/klarna-ai-customer-service-chatbot-hiring) they "went too far" and started quietly rehiring humans. Roughly [55,000 jobs were cut](https://layoffs.fyi) in layoffs that companies attributed directly to AI in 2025, more than three times the total in the preceding two years. The pattern is the same everywhere. The solution shows up before the problem is understood. A [recent study from the National Bureau of Economic Research](https://www.nber.org/papers/w32966) surveyed nearly **6,000 executives** across the US, UK, Germany, and Australia. About **70 percent** of their firms are using AI. **Nine in ten** report no meaningful change in employment or productivity. The executives themselves spend an average of **1.5 hours a week** using AI, less than the workers they manage. That’s the gap I keep running into. Not between companies that have AI and companies that don’t. Between companies that adopted AI and companies where AI actually changed something. ## What happens when the bottleneck moves up the stack? Here’s what most people miss. AI has collapsed the cost of execution. Writing code, generating content, summarizing research, building prototypes... all of it is faster and cheaper than it was two years ago. That part is real. But when execution gets cheap, it stops being the bottleneck. The bottleneck moves up the stack, to the decisions, the context, and the organizational thinking that execution depends on. Most companies haven’t noticed the shift. They’re still optimizing for speed at the task level. They’re still treating AI as a tool. Helpful. Fast. Impressive in demos. But still sitting on the edges of the business. It writes. It summarizes. It assists. It doesn’t decide. It doesn’t orchestrate. It doesn’t change how work flows through the company. > Tools improve tasks. Systems change outcomes. ## What is the electric motor mistake in AI? Early factories made the same mistake with electricity. They replaced steam engines with electric motors and expected the same work to get faster. Nothing happened. Only when they [redesigned the factory floor](https://www.nber.org/papers/w9730), rethinking how materials moved, how workers collaborated, how decisions got made, did productivity jump. AI is at that same inflection point. And the companies cutting headcount before redesigning their operations are making the electric motor mistake all over again. I’ve spent the last two years building Revolv around a single frustration: the questions most AI strategies never bother to ask. Not questions about models or vendors. Questions about the business. Where do decisions slow down? Where does context get lost? Where do relationships quietly determine outcomes, but never show up in any system? Here’s an example. A CFO is about to approve a vendor switch. The spreadsheet says yes: better pricing, stronger SLA, cleaner integration. What the spreadsheet doesn’t say is that the incumbent’s CEO just joined the board of their biggest client. One relationship, invisible to every system in the building, changes the entire decision. That kind of context lives in people, not dashboards. No CRM captures it. No AI tool surfaces it. ## Who’s getting it right? [McKinsey’s 2025 State of AI report](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai) found that high-performing companies are **nearly three times as likely** to have fundamentally redesigned workflows around AI, not just deployed it. The difference isn’t better models. It’s better questions about how work actually flows. One example: a North American fleet services company stopped treating AI as a reporting tool and rebuilt its entire repair order workflow around a custom model that reads the context of every job. The result was a [90% reduction in error detection time](https://www.ninetwothree.co/blog/ai-adoption-case-studies), with over 30% of orders resolving automatically. They didn’t add AI to the process. They redesigned the process so AI could operate inside it. ## Three questions before your next AI investment Before approving another AI tool, every leadership team should answer three questions: 1. **Have we measured what we’re trying to improve?** Not adoption metrics. Outcome metrics. If you can’t name the decision, cycle time, or cost you’re targeting, you’re not ready. 2. **Where do decisions actually slow down?** Map the real bottleneck. It’s rarely execution. It’s usually context: the relationship a CRM doesn’t capture, the institutional knowledge that lives in one person’s head, the strategic alignment that never made it past the slide deck. 3. **Are we redesigning the work, or just accelerating it?** If the workflow stays the same and AI makes it faster, you’ve bought an electric motor for a steam-era factory. The gains come from rethinking how materials move, how people collaborate, how decisions get made. The executives in that NBER study expect impact to come. They’re right. But not because the models will get better. Because the companies that figure this out will stop optimizing tasks and start redesigning how their organizations think. **AI makes execution cheap. Systems thinking makes it count.** --- *We built [Revolv](/advisory) to help leaders answer these questions before the next budget cycle.* --- ## The End of Networking: The Rise of Relationship Intelligence - **Canonical URL**: https://www.therevolv.com/signal/relationship-intelligence - **Author**: Jon Chu | **Published**: March 7, 2026 | **Updated**: March 24, 2026 | **Reading Time**: 11 min - **Tags**: Relationship Intelligence, Networking, AI & Technology I walked into a coffee meeting last fall having reviewed everything from our last conversation six months earlier. Her startup pivot. Her Q2 fundraise timeline. The introduction I had promised to make to my Series A investors. She noticed. She told me later that it was the first follow-up in months where someone actually remembered what they had talked about. I remembered. But it was not easy. Before that meeting, I spent twenty minutes searching through scattered notes, old calendar entries, and half-written follow-ups trying to reconstruct the context. The information existed. It was just fragmented across five different places. I almost walked in cold because the prep felt like too much work for a single coffee. That experience stays with me because it is not unusual. Most professionals I know face the same friction. They care about their relationships. They want to follow through. But the context they need is buried, scattered, or gone. They do not need a tool that talks for them. They need a system that helps them remember and does not let them forget. For decades, professional success followed a simple rule: build a network. Collect contacts. Attend events. Follow up occasionally. That system worked when professional circles were smaller and easier to manage. Today, professionals interact with hundreds of people across conferences, digital communities, introductions, and online platforms. The challenge is no longer meeting people. **The challenge is remembering them.** --- ## Why Is AI-Generated Outreach Killing Trust? AI-generated messages have flooded professional inboxes, making polished outreach the default. When every message sounds perfect, trust shifts to a different signal: whether someone actually remembers you. Three LinkedIn messages hit my inbox last week. All clearly AI-generated. All mentioning my "impressive background." None mentioning the conversation we actually had. This is what the AI communication explosion looks like from the receiving end. Messages that once required time and effort can now be generated instantly: - AI-drafted follow-up emails - Automated LinkedIn outreach messages - Generated introductory messages and meeting summaries - Templated "just checking in" sequences Communication got faster. Trust did not follow. Many professionals now assume that incoming messages may have been generated by AI rather than written by a person. LinkedIn built the largest professional network in the world. But the platform was designed for connecting, not remembering. Profiles are exchanged like business cards at a conference. You accept, you move on. Three months later you are staring at a name and a job title with zero context on why you connected. The context of why you met someone lives somewhere else, if it lives anywhere at all. When every message sounds polished, the real signal shifts elsewhere. **The signal becomes context.** People notice when someone remembers a previous conversation, a personal detail, or an earlier project discussion. The strongest professional signal is often the simplest: *someone remembered.* --- ## What Does It Cost When Professionals Lose Touch? The hidden cost of losing touch is missed opportunity. Most professionals have lost meaningful career moments not because they lacked skill or ambition, but because they failed to maintain the relationships that would have opened doors. Meeting people is rarely the hardest part of professional networking. The difficulty appears later, when you attempt to maintain relationships over time. The best opportunity I ever received came from someone I almost forgot. A former colleague, someone I had worked with briefly three years earlier, mentioned my name in a room I was not in. She told a founder that I was the person who understood both the operational complexity and the product vision for what he was building. That introduction changed the trajectory of my career. I did not earn that moment through networking strategy. I earned it because years earlier, I had paid attention to her work and she remembered that I had. That story had a happy ending. Most do not. I have watched this pattern repeat across every founder and executive I advise: **meaningful career opportunities lost simply because someone failed to stay in touch.** The cause is rarely indifference. It is capacity. Human memory has limits. Over the course of a career, professionals may interact with: - **Thousands** of colleagues across companies and roles - **Hundreds** of partners, clients, and collaborators - **Dozens** of mentors and sponsors - **Countless** introductions that never converted to relationships Each interaction contains context. Career goals, projects, personal milestones, challenges discussed. Those details build trust. But without a system to preserve them, they fade. [Robin Dunbar's research](https://en.wikipedia.org/wiki/Dunbar%27s_number) suggests humans can actively maintain roughly 150 relationships. Most professionals meet far more people than that in a single year. > Context decay is the silent killer of professional relationships. Not indifference. Not distance. Forgetting. --- ## Why Are Relationships Your Most Defensible Asset? As AI commoditizes individual skills, professional relationships become the only career asset that cannot be replicated. Social capital, the trust and context accumulated across your network, compounds in ways that credentials and technical ability cannot. I see this every week in the companies I advise. AI is rapidly expanding what individuals can accomplish alone. Coding, research, analysis, writing. All increasingly supported by AI tools. As these capabilities become widely available, skills become easier to replicate. Relationships do not. Research consistently shows that many important career opportunities come through existing relationships rather than cold outreach. Mark Granovetter's [foundational study on weak ties](https://en.wikipedia.org/wiki/The_Strength_of_Weak_Ties) demonstrated that most job leads come not from close contacts, but from acquaintances whose context fades fastest: - A colleague introducing you to an investor - A mentor recommending you for a leadership role - A friend bringing you into a new company or startup - A former client referring your business to their network These moments demonstrate a larger truth: **professional relationships function as long-term career infrastructure.** [Social capital](https://en.wikipedia.org/wiki/Social_capital), the accumulated trust and context within your network, compounds over time in ways that skills and credentials cannot. AI leveled the playing field on individual capability. [Your relationships are what is left](https://www.therevolv.com/signal/why-we-built-revolv). --- ## What Do Professionals Actually Want From AI? Professionals do not want AI to replace their relationships. They want AI to help them remember. The demand is not for better outreach automation but for systems that preserve the context that makes relationships meaningful. When I started building Revolv, I expected people to ask for AI that could write better outreach messages or automate follow-ups. They did not. What they asked for, overwhelmingly, was help remembering. The professionals I spoke with wanted AI systems that can: - Surface context from past conversations before a meeting - Remind them when to reconnect with someone important - Recall details about previous interactions and commitments - Identify patterns across their professional relationships At the same time, people prefer to maintain their own voice when communicating. As one professional described the ideal balance: > "Give me the context. I'll bring the humanity." This distinction is critical. **Automation can replace communication. Memory strengthens relationships.** The future of AI in professional networking is not about generating more messages. It is about preserving the context that makes each message meaningful. --- ## What Is Relationship Intelligence? I looked at every tool on the market before building Revolv. CRM systems track clients. Project management tools track tasks. Financial systems track transactions. Not one was designed to help an individual manage relationships over the course of a lifetime. That gap is closing. > Relationship intelligence is the practice of systematically preserving the context that makes professional relationships meaningful: who you met, what you discussed, what you committed to. And using that context to deepen connections over time. Relationship intelligence recognizes that relationships are not static records. They evolve over time through shared experiences, conversations, and collaboration. Traditional CRM tools treat relationships as data entries. A relationship intelligence platform treats them as living, evolving connections that require context to thrive. The difference matters: - **CRM**: "Last contacted 47 days ago. Stage: Lead." - **Relationship intelligence**: "You discussed her startup pivot at the Denver conference. She mentioned fundraising in Q2. You offered to intro her to your Series A investors." When context disappears, relationships weaken. When context is preserved, relationships strengthen. This is not a productivity tool. It is [a system that makes your professional relationships more intelligent over time](https://www.therevolv.com/platform). [Revolv](https://www.therevolv.com/platform) is the agentic layer for relationship intelligence. It does not wait for you to look something up. It connects the dots across your conversations, your calendar, and your history, and brings you what matters before your next meeting. --- ## Why Does Consistency Beat Intensity in Networking? Long-term professional relationships are not built through occasional bursts of outreach. They grow through consistent, context-rich engagement over time. The barrier has never been intention. It has been memory. Traditional networking often appeared transactional. People reached out when they needed something. But long-term relationships are built differently. They grow through consistent engagement: - Checking in periodically without an agenda - Remembering important milestones: promotions, launches, life events - Referencing past conversations that demonstrate attention - Reconnecting before you need something, not after The barrier has never been intention. **The barrier has been memory.** With the right relationship intelligence systems in place, maintaining those connections becomes significantly easier. Consistency stops being a heroic act of willpower and starts becoming [a system outcome](https://www.therevolv.com/signal/stop-chasing-greatness). --- ## The Shift Has Already Started The professionals who will build the strongest careers over the next decade will not be the ones with the most connections. They will be the ones who remember. Not because remembering is polite. Because it compounds. Every detail you preserve is a deposit in a relationship. Every forgotten conversation is a withdrawal. Over a career, the difference between the person who remembers and the person who forgets is not marginal. It is exponential. That is why I built [Revolv](https://www.therevolv.com/platform). Not to automate relationships. Not to generate more messages. To make professional relationships more intelligent over time by preserving the context that makes them meaningful. The traditional model of collecting contacts assumed that the hard part was meeting people. It was not. The hard part was always what came after: maintaining relationships with clarity and continuity across years, not just weeks. This shift marks the transition from networking toward **relationship intelligence**. And it raises a question most professionals have not yet considered: what would your career look like if you had never forgotten anyone who mattered? When anyone can generate a perfect message, the most meaningful signal will remain deeply human. > Someone remembered. --- ## Key Takeaways - **Polished messages stopped being a signal.** When every outreach can be AI-generated, memory becomes the trust signal. Context is what cannot be faked. - **Human memory was never built for this.** Dunbar says 150 active relationships. Most professionals blow past that in a single year. The math does not work without a system. - **Your skills are a commodity. Your relationships are not.** AI is leveling individual capability. Social capital is the asset that compounds and cannot be replicated. - **Relationship intelligence is the practice, not the product.** Systematically preserving context: who you met, what you discussed, what you committed to. That discipline strengthens connections over time. - **Consistency beats intensity.** Relationships grow through regular, context-rich engagement. Not through transactional outreach when you need something. *If you want early access to the relationship intelligence platform that helps you remember every professional relationship, [join the waitlist at Revolv](https://www.therevolv.com/).* --- ## Stop Chasing Greatness. Start Building the System. - **Canonical URL**: https://www.therevolv.com/signal/stop-chasing-greatness - **Author**: Jon Chu | **Published**: March 1, 2026 | **Reading Time**: 5 min - **Tags**: Strategy, Relationship Intelligence When Michael Jordan says he did not chase greatness, most people hear something soft. Let go. Trust the process. Believe and it will come. That is not what he meant. He said that if he had chased being "the greatest," he might never have reached it. Instead, he focused on the work. The standards. The daily execution. The team. The outcomes followed. That is not passivity. That is systems thinking. Greatness is not an individual act. It is a system outcome. ## The Dangerous Myth of the Individual We romanticize singular talent because it makes for clean storytelling. One genius founder. One visionary CEO. One transcendent athlete. But Jordan without Phil Jackson is a different career. Without Scottie Pippen, a different ceiling. Without an offensive system designed for spacing and flow, a different statistical arc. The mythology celebrates the highlight reel. The reality is structure. The same distortion shows up in business. > Founders do not scale companies. Systems do. A brilliant product leader inside a chaotic operating model will stall. A visionary CEO without incentive alignment will create confusion. A high performing engineer inside a drifting roadmap will burn out. Individual excellence is fragile. Systemic excellence compounds. ## Status vs Standards Listen carefully to what Jordan actually implies. He did not lack ambition. He redirected it. There is a difference between chasing status and committing to standards. Chasing status distorts behavior. You force shots. You overhire. You overpromise. You scale optics instead of substance. Standards do the opposite. They tighten feedback loops. They clarify tradeoffs. They make performance measurable. They make winning more probable. Jordan optimized controllables. Conditioning. Repetition. Defensive intensity. Competitive edge. The inputs stacked the odds in his favor. He engineered probability. That is leadership. ## People + Outcomes = Transformation Most organizations chase visible metrics. Valuation. Headcount. Press cycles. AI adoption theater. They rarely chase outcome integrity. Revenue quality. Customer retention. Trust density across teams. Execution velocity. [Transformation happens when people are aligned around shared, measurable outcomes](https://www.therevolv.com/advisory#apex-framework). Not slogans. Not value statements. Outcomes. When people know exactly what matters and how they contribute, politics drops. Ownership rises. Feedback tightens. Capability compounds. When capability compounds, outcomes improve. When outcomes improve, confidence strengthens. When confidence strengthens, culture stabilizes. That is a flywheel. And flywheels beat heroics. ## Systems Fail Where Memory Fails If greatness is a system outcome, then the real question is simple: what breaks systems? Not effort. Not intelligence. Not even ambition. **Memory.** Organizations decay when context disappears. Why a decision was made. What tradeoffs were accepted. Who committed to what. Where trust was earned or strained. When memory erodes, alignment erodes. When alignment erodes, outcomes drift. You see it everywhere. New leaders reopen old debates. Teams duplicate work. Institutional knowledge hides in inboxes. High performers leave and take context with them. Velocity drops, not because people are less capable, but because the system forgot. I have watched this happen firsthand. A key leader leaves and takes three years of product context with them. The team that replaces them spends six months relearning decisions that were already made. Nobody got less talented. The system just lost its memory. Jordan's teams did not just have talent. They had continuity. Roles were understood. Adjustments layered on shared context. Patterns repeated until execution felt inevitable. That is compounding memory. > Most companies never build that layer intentionally. They invest in hiring. They invest in tooling. They invest in AI. But they do not invest in preserving and compounding context across relationships. And that is where transformation stalls. ## Context Is the Architecture Transformation is not a hiring problem. It is an alignment architecture problem. You do not need more "great" people. You need people operating against clear outcomes with high trust and preserved context. Because context lives inside relationships. When context compounds: - Decisions get sharper. - Collaboration accelerates. - Trust builds instead of resetting. - Execution becomes less political and more mathematical. Systems become more intelligent over time. That is leverage. And leverage is what makes outcomes durable. ## How to Build the System If you want transformation that lasts, start here: 1. **Define the outcome clearly.** Measurable. Shared. Non negotiable. 2. **Align incentives to it.** Compensation, recognition, promotion. 3. **Make performance visible.** Dashboards over narratives. 4. **Invest in capability.** Training, tools, feedback loops. 5. **Preserve context.** Build systems that remember and learn. Notice what is missing. Chasing greatness. > Greatness is a trailing indicator. It is what the market calls you after your system works. ## The Shift The world prefers individual mythology because it is simple. But transformation is structural. Stop asking how to become great. Start asking how to design the conditions where excellence becomes statistically inevitable. The organizations that figure this out will not call it transformation. They will just call it [how they work](https://www.therevolv.com/advisory#apex-framework). --- ## Key Takeaways - **Greatness is a system outcome, not an individual act.** Jordan's success was built on structure, continuity, and compounding context. Not just talent. - **Status chasing distorts behavior. Standards compound it.** The difference between scaling optics and scaling outcomes is structural clarity. - **People + Outcomes = Transformation.** When people align around shared, measurable outcomes, capability compounds into a flywheel. - **Systems fail where memory fails.** Organizations decay when context disappears. Decisions reopen, trust resets, velocity drops. - **Build the system, not the mythology.** Define outcomes, align incentives, make performance visible, invest in capability, and preserve context. *If you're building the system that makes transformation inevitable, [learn how Revolv helps leaders scale with clarity](/advisory).* --- ## Unlocking the Hidden Work of Enterprises - **Canonical URL**: https://www.therevolv.com/signal/unlocking-hidden-work-enterprises - **Author**: Jon Chu | **Published**: November 11, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 4 min - **Tags**: AI & Technology, Strategy Most people still see AI as a tool to make existing work faster or cheaper. The real shift will come from uncovering hidden work: the valuable tasks and opportunities that were never possible before. ## A New Kind of Work Is Emerging Over the last several weeks, I spoke with ten corporate leaders across industries. Each conversation revealed the same pattern. AI is moving beyond cost reduction and optimization. It is beginning to take on work that companies never had the people, time, or budget to handle. In wealth management, it means analyzing every portfolio and client interaction to detect risks and life events before they happen, allowing advisors to deliver proactive, personalized guidance. In relationship intelligence, it means capturing every signal across your network to surface opportunities that would otherwise remain invisible. This is what we are building at Revolv - expanding human connection through intelligence, not noise. In finance, it means analyzing historical deal outcomes, market cycles, and transaction behaviors to reveal opportunities that conventional models miss. Instead of relying solely on human memory or intuition, AI can surface the subtle shifts in timing, structure, or partner mix that consistently drive outsized returns. It becomes a discovery engine for monetization that was never possible at human scale. In law, it means unlocking entire client tiers once considered out of reach by automating contract, compliance, and review tasks so firms can focus on higher-value opportunities. These examples are not about efficiency. They are about expansion - unlocking entirely new forms of work that were previously beyond reach. ## AI Is Expanding the Surface Area of the Economy Historically, productivity meant squeezing more output from the same inputs. AI changes that equation. It introduces a new input: scalable digital labor that operates at the speed of compute. This expansion is widening the surface area of the global economy. Work that once sat below the cost line - too detailed, too small, or too time-consuming - can now be done profitably. The organizations that act first will not only move faster but compete in markets that others cannot yet see. ## When Capacity Becomes Infinite, Imagination Becomes the Limit Traditional productivity was defined by tradeoffs. Every new initiative required another to pause. Every analysis carried a cost ceiling. AI removes those limits. When execution becomes nearly free, the constraint shifts from capacity to imagination. The right question is no longer "How do we make this cheaper?" but "What can we now achieve that was once impossible?" This is where People + Outcomes = Transformation becomes essential. Technology alone does not transform a business. People do. When AI expands capacity, the real differentiator is how leaders align talent, data, and purpose to produce better outcomes. Transformation happens when people are empowered to direct this new capacity toward meaningful goals. ## The Human Parallel At Revolv, we see this same shift in how people connect. Most professionals only manage a fraction of the relationships that could shape their careers. The limitation isn't interest. It's bandwidth. Now imagine an intelligent system that remembers every conversation, tracks shared goals, and helps you act on them at the right time. An investor tracking a hundred founder connections instead of twenty. A consultant identifying the exact moment a contact needs their specific expertise. That isn't automating networking. It's creating a deeper form of relationship intelligence, where connection itself becomes transformative. Just as enterprises will uncover hidden work, individuals will uncover hidden opportunities. When capacity expands, connection deepens. And when connection deepens, transformation follows. --- ## Key Takeaways - **AI is moving beyond optimization into expansion.** The real shift isn't making existing work faster - it's uncovering entirely new forms of work that were never possible before. - **Hidden work exists in every industry.** From wealth management to law to relationship intelligence, AI is enabling tasks that were previously below the cost line. - **When capacity becomes infinite, imagination becomes the limit.** The constraint shifts from "How do we make this cheaper?" to "What can we now achieve that was once impossible?" - **Transformation is a people problem, not a technology problem.** When AI expands capacity, the differentiator is how leaders align talent, data, and purpose. - **Individuals will uncover hidden opportunities too.** Just as enterprises find new work, professionals will find new connections - when bandwidth is no longer the bottleneck. *If you're exploring how AI can unlock new forms of value in your organization, [learn how Revolv helps leaders scale with clarity](/advisory).* --- ## When AI Speeds Up Engineering, Product Must Slow Down the Thinking - **Canonical URL**: https://www.therevolv.com/signal/when-ai-speeds-up-engineering - **Author**: Jon Chu | **Published**: October 14, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 6 min - **Tags**: AI & Technology, Strategy, Product There's a new tension emerging inside every company adopting AI. Engineering teams are moving faster than ever. AI copilots write, test, and deploy code at speeds that used to take weeks. The barrier to building is gone. But while engineering velocity has exploded, the organizational metabolism hasn't caught up. I recently read a conversation in the Wall Street Journal Leadership Institute discussing how AI is reshaping software teams. He said the idea that "AI will kill software" is overblown. We're not replacing software. We're abstracting it. Just as no one writes in ones and zeros anymore, we're now writing in natural language and intent. The architecture, design, and systems thinking still matter. The product we ship isn't code. It's software that fulfills a business need. That last point is the hinge: software is a business system, not a technical artifact. And that's where product leadership becomes essential. ## Product Teams Are the Translators of Velocity When AI accelerates engineering, it shifts the bottleneck from building to absorbing change. Marketing, sales, and operations can't always move at the same pace. They're still governed by human processes, planning cycles, and narratives that don't update overnight. The result? A growing gap between what's possible and what's understood. This is where product teams play an operational role, not just strategic. They become the translators between velocity and comprehension. Their job is to normalize the new, to translate the solution created into a shared narrative that makes sense across the company. ## This Tension Isn't New. But AI Makes It Structural. This dynamic - engineering moving faster than the organization can absorb - is not unique to product teams. It's the same structural gap I've been tracking across every leadership team I've worked with this year. In the Apex Pyramid framework I built with executive teams navigating AI transformation, this shows up as a failure in Layer 3: Scalable Systems. Most organizations treat systems as isolated tools. Marketing has its stack. Engineering has its tools. Product lives somewhere in between. But scalable systems aren't about tooling. They're about integration, feedback loops, and connective tissue that allows one part of the business to move without breaking another. Product teams operating with systems thinking are essentially building that connective layer in real time. They're not waiting for the org chart to catch up. They're designing the operating system the company needs to function at AI speed. That's what separates companies that scale AI from those that stall. It's not the technology. It's whether you've built the organizational metabolism to absorb it. ## The Upskilling Paradox: You Can't Transform While Standing Still Here's what most executives miss: they're asking teams to adopt AI, learn new systems, and redesign how they work - while maintaining 100% of their existing output. There's no slack in the system. No transition bandwidth. [BCG found](https://www.bcg.com/publications/2024/from-potential-to-profit-with-genai) that only 25% of AI initiatives deliver expected ROI. One of the biggest reasons? Organizations treat AI adoption like a software rollout. Install the tool. Run a training. Expect productivity gains by next quarter. But AI isn't just new software. It's a new way of working. And you can't upskill people in motion without creating the space to absorb that change. This is where the structural gap becomes operational. Engineering velocity increases because AI tools directly augment their workflow. But marketing, sales, operations - they're not writing code. They're navigating narrative shifts, process redesigns, and cross-functional dependencies that AI doesn't automate. They need time to translate what's possible into what's actionable. And most organizations haven't built that time into the system. The companies breaking through? They're redesigning capacity planning alongside AI adoption. They're embedding learning into workflow, not bolting it on. They're giving people permission to slow down in order to speed up later. That's not a luxury. It's a structural requirement for transformation that sticks. ## Systems Thinking Is the New Product Operating System Systems thinkers understand that every change reverberates. Ship a new feature and you're not just changing a screen. You're changing how sales tell the story, how support handles tickets, how finance forecasts revenue. In a world where AI lets you build and throw away code in hours, the real leverage comes from structural clarity. Systems thinking gives product leaders a way to see the dependencies, design feedback loops, and align incentives before chaos compounds. This is why I say: systems thinking is not philosophy. It's an operator skill. It's what allows a product team to scale speed into sustainability. ## Embedded Teams, Embedded Thinking As velocity increases, engineering teams are becoming more embedded inside business functions. The same should happen with product. Embedded product operators working side-by-side with GTM, marketing, and customer teams create empathy loops. It's no longer about "handoffs." It's about shared ownership of outcomes. In that model, alignment becomes the product. Clarity becomes the deliverable. ## AI Makes Iteration Cheap. Coherence Makes It Valuable. AI reduces the cost of experimentation. You can now build, test, and discard ideas in a day. But coherence - the story that ties those ideas together - is what gives them power. That's the new job of product teams in an AI era: to make speed strategic. To ensure that every experiment fits within a larger system that compounds, rather than fragments, the business. The best product operators today don't just manage roadmaps. They design systems that keep everyone rowing in rhythm. Fast, but together. ## Final Thoughts AI may accelerate the code, but it's systems thinking that synchronizes the company. In the end, the real product is not the app. It's the organization that builds it. And the organizations that win? They don't just adopt AI. They redesign how work flows, who owns outcomes, and how systems connect. The organizations that scale AI successfully don't just buy better tools. They redesign how people learn, how teams flex, and how capacity gets allocated during transformation. They treat upskilling as an operational discipline, not a training event. That's the difference between moving fast and building something durable. That's the difference between ROI on paper and ROI in practice. --- ## Key Takeaways - **The bottleneck has shifted from building to absorbing change.** AI makes engineering fast, but marketing, sales, and operations still run on human timelines. - **Product teams are the translators of velocity.** They bridge the gap between what's technically possible and what the organization can comprehend and act on. - **Systems thinking is the new product operating system.** Every feature change reverberates across sales narratives, support workflows, and revenue forecasts. - **You can't upskill people in motion.** Organizations must build transition bandwidth into capacity planning - not bolt training onto existing workloads. - **Coherence makes iteration valuable.** AI makes experimentation cheap, but the story that ties experiments together is what compounds the business. *If your team is navigating the tension between velocity and coherence, [learn how Revolv helps leaders design for AI-speed operations](/advisory).* --- ## Most Orgs Aren't Built to Scale. Here's the Structure That Changes That. - **Canonical URL**: https://www.therevolv.com/signal/most-orgs-arent-built-to-scale - **Author**: Jon Chu | **Published**: July 8, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 4 min - **Tags**: Strategy, AI & Technology Every executive I've worked with this year has faced the same pressure: "We've made the investment in AI. Now make it count!" But that is not the place to start. In the first half of 2025, I worked closely with leadership teams navigating AI transformation. The focus was not just on experimentation. It was about moving from fragmented pilots to sustainable execution. Across those conversations, one thing became clear: > "Only 25 percent of AI initiatives have delivered the expected ROI, and just 16 percent have successfully scaled across the enterprise." [BCG, 2025](https://www.bcg.com/publications/2024/from-potential-to-profit-with-genai) Most organizations aren't falling behind because of missing technology. They're falling behind because their structure wasn't built to adapt. Some moved quickly. Others stalled. The ones that broke through weren't just adopting tools. They were redesigning how they work. That insight led to the creation of the Apex Pyramid, a framework for execution at scale, built from the ground up for today's environment. ![The Apex Pyramid framework: Scalable Systems, Workforce Planning, Transformation, and People + Outcomes](/signal/apex-pyramid-framework.webp) Every organization's transformation looks different. But beneath the surface, the patterns are strikingly similar. The organizations breaking through follow a clear pattern: ## Layer 1: People + Outcomes = Transformation Before systems and workflows, there must be trust and clarity. Organizations that scale well start here: - Clear ownership of outcomes - Decentralized decision rights - Alignment on what "good" looks like AI doesn't fix ambiguity. It amplifies whatever already exists. If your foundation is misaligned, no tech will fix it. ## Layer 2: Workforce Planning That Adapts This is where structure becomes a lever, not a blocker. Most orgs rely on static hierarchies designed for predictability. High-performing teams re-architect their workforce to match how work actually flows. The defining characteristics: - Org design around real workflows, not legacy functions - Clear definition of product ownership - Strategic mix of full-time, contingent, and AI-augmented roles - Innovation teams that operate outside bureaucracy, yet stay connected - Resourcing that flexes with strategy This is where the old org chart breaks and smart orgs rebuild from the workflow up. ## Layer 3: Scalable Systems This is the layer that makes transformation durable - not just possible, but repeatable at scale. In high-functioning orgs, systems are not siloed tools. They are operating platforms designed for agility and impact. What distinguishes these systems: - Built around customer value, not internal complexity - A defined data strategy connected to outcomes - AI agents embedded where decisions happen, not in separate tools - Governance that encourages experimentation without creating chaos - A culture of systems thinking - connecting dots across silos and layers These aren't tech issues. They're structural gaps - in clarity, ownership, and integration. It's about building the operating system your org needs to scale with intent. ## Why It Matters Now AI is no longer a side project. It sits at the center of how modern orgs operate, compete, and grow. But transformation doesn't happen through tools. It happens when leadership creates the conditions for scale. The Apex Pyramid gives teams a structure to: - Align people around outcomes - Design workforces that flex with demand - Build systems that multiply execution This isn't about chasing the latest technology fad. It's about building the kind of org that delivers. Every company talks about transformation. Few are structured to deliver it. The Apex Pyramid is how we're helping executive teams move from friction to focus - and from pilot thinking to real momentum. --- ## Key Takeaways - **Only 25% of AI initiatives deliver expected ROI.** The problem isn't technology - it's organizational structure that wasn't built to adapt. - **The Apex Pyramid has three layers.** People + Outcomes (trust and clarity), Workforce Planning (adaptive structure), and Scalable Systems (durable execution). - **AI amplifies whatever already exists.** If your foundation is misaligned, no technology will fix it. Start with people and outcomes. - **The old org chart is breaking.** Smart organizations rebuild from the workflow up, not from the hierarchy down. - **Transformation requires structural intent.** Every company talks about transformation. Few are structured to deliver it. *If your team is navigating structure, operating models, or AI-enabled execution, [learn how Revolv helps executive teams design for scale](/advisory).* --- ## The Journey From Product Builder to Business Leader in the Age of AI - **Canonical URL**: https://www.therevolv.com/signal/journey-from-product-builder-to-business-leader - **Author**: Jon Chu | **Published**: April 29, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 5 min - **Tags**: Strategy, AI & Technology, Founder Stories Over the years, whether speaking on panels, partnering with top corporations, or building Revolv, I learned something that took me longer to appreciate than I'd like to admit. > Being a great Chief Product Officer isn't about building great products. It's about building great businesses. Serving as a panelist recently made me realize how often this truth gets overlooked: the real journey isn't just from PM to leader, it's from builder to operator to owner. It's the lived experience that brings it fully into focus. And honestly, that evolution never really stops. --- ## The Shift They Don't Talk About When you start out, you think success is measured by how many features you ship or how quickly you solve user problems. That's necessary, but it's not sufficient. As you grow into executive leadership, the expectations shift - quietly, but massively. Suddenly, you're not measured by what you ship. You're measured by business outcomes: revenue growth, margins, customer retention, long-term scalability. You have to stop being the hero who "fixes" things yourself and start building systems and teams that can operate independently at scale. You can't just be a visionary. You must be an operator. The best CPOs aren't the ones who can only craft the perfect roadmap. They're the ones who can architect the engine that keeps the entire business moving. And they know one thing for sure: Product Operations is the secret weapon - customer experience, onboarding, support, feedback loops. When you operationalize these well, you build an organization that wins consistently, not occasionally. --- ## AI Is Changing the Game - But Fundamentals Still Matter Layer AI into the mix, and suddenly the stakes and the opportunities grow even bigger. Yes, AI unlocks new capabilities: it can predict customer behavior before patterns emerge, personalize experiences at unprecedented scale, and automate decisions that once took days or weeks. But with that power comes a new leadership challenge. > Instinct without insight falls short. And in today's world, moving fast without thinking clearly isn't bold - it's unsustainable. Today, leading in the age of AI demands more than just vision - it demands discipline. It demands frameworks that surface the truth faster. It demands systems that reduce bias before it compounds. And it demands teams that move with clarity, not just speed. While technology accelerates everything around us, the core principles of leadership remain unchanged. If anything, they matter even more now. It's still about the ability to execute consistently. The ability to deliver real, measurable outcomes. And the ability to sustain operational excellence over time. These are the traits that separate the great from the merely good, especially when AI raises both the floor and the ceiling of what's possible. --- ## What I Tell Myself (and My Teams) These principles have stayed with me, no matter the size of the team or the scope of the problem: 1. **Build businesses, not just products.** 2. **Operate like it matters.** 3. **Stay a student.** 4. **Be ruthless about outcomes.** 5. **Lead with heart and discipline.** --- ## Rethinking Product-Market Fit: Stop Over-Analyzing, Start Observing One of the biggest mistakes I see teams make is confusing product-market fit with analyzing small sets of customer data. They run experiments, collect a few hundred users - often family & friends, Reddit, beta invitees - and then overanalyze data. If you want to find real product-market fit, stop acting like a data analyst chasing sample sizes. Start thinking like an observer - someone who's genuinely curious about real human behavior, not just numbers. Your "analytics" should literally just be a simple table made up of Name, Account Creation Date, Last Active Time, and Sessions. Sort the table by Last Active Time to identify your most engaged users. Study their online presence and behavior to better understand who they are and how they interact with your product. Personally reach out to them for feedback, and be gracious - early customers are your foundation. Whenever possible, give back, even something as simple as a small gift card, to show appreciation and build lasting loyalty. --- ## Why This Matters Now The market doesn't need more teams chasing feature checklists - it needs leaders who can balance vision with reality, operators who can scale with discipline, and builders who can adapt with speed and purpose. If you're aiming for the CPO seat or already sitting in it, this is the reality: Operate. Execute. Lead. Stay human. Because even in the age of AI, the companies that win will be the ones who never forget: **We are still building for people first.** --- ## Key Takeaways - **The shift from builder to operator is the real leadership leap.** Success stops being about what you ship and starts being about the business outcomes you drive - revenue, retention, scalability. - **Product Operations is the secret weapon.** Operationalizing customer experience, onboarding, support, and feedback loops builds organizations that win consistently. - **AI amplifies everything - including the need for discipline.** New capabilities demand frameworks, systems, and teams that move with clarity, not just speed. - **Real product-market fit comes from observation, not over-analysis.** Track your most engaged users, study their behavior, and build relationships with them directly. - **We are still building for people first.** Even in the age of AI, the companies that win never lose sight of the humans they serve. *If you're navigating the shift from product builder to business leader, [learn how Revolv helps leaders scale with clarity](/advisory).* --- ## AI Isn't Replacing Jobs - It's Replacing Companies That Can't Adapt - **Canonical URL**: https://www.therevolv.com/signal/ai-isnt-replacing-jobs - **Author**: Jon Chu | **Published**: February 25, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 5 min - **Tags**: AI & Technology, Strategy In the last month, I've spoken with executives at large corporations about AI strategy. The biggest challenge? Not adoption - but making AI actually work. Many executives still chase cutting-edge AI models, thinking the model itself is the differentiator. It's not. What matters is how AI fits into workflows, enhances security, and drives decisions. Nobody swaps AI models for fun - it's the results that count. --- ## Stop Over-Focusing on AI Models - Start Thinking About Business Impact Many companies still believe the best AI model equals a competitive edge. But here's the reality: it's not the model - it's the business impact that matters. Think about it: most enterprises switch AI models behind the scenes all the time, and no one even notices - as long as the outputs remain strong. This tells us something important. AI isn't about technical superiority - it's about operational leverage. The most successful AI-driven companies aren't the ones with the flashiest models. They're the ones that remove complexity, improve efficiency, and reduce friction. --- ## The AI Model Market Is Facing a Hard Reality We're past the gold rush of AI models. Open-source AI (like Meta's Llama and Deepseek) has leveled the playing field, and businesses are realizing something uncomfortable: > The cost of AI is quickly converging with the cost of the GPUs running it. Selling AI models alone is no longer enough - real value comes from enterprise-grade security, compliance, and deployment. One AI vendor told me they cut customer costs by 60% in six months - but demand skyrocketed. Once AI becomes efficient and accessible, usage doesn't shrink - it explodes. That's the shift: AI isn't about which model you use - it's about how easily, securely, and effectively you deploy it. --- ## AI Is Reshaping Enterprise Workflows and Decision-Making > AI isn't just automating tasks - it's transforming how decisions are made. Instead of spending hours sifting through documents or navigating complex databases, employees can now ask AI for real-time insights and get immediate, actionable answers. This shift means less time wasted searching for information, more time making strategic decisions, and fewer bottlenecks slowing down execution. As a result, AI-powered tools in HR, CRM, and workflow automation are quickly becoming the norm. Rather than investing time and resources in building AI models from scratch, companies are realizing it's far more efficient to adopt enterprise-ready AI solutions that integrate seamlessly into their existing systems. The real question for leaders isn't whether AI should be adopted - that's already a given. The real challenge is identifying where AI can create the most leverage, how it can eliminate inefficiencies in decision-making, and how to integrate it without adding unnecessary complexity. --- ## Enterprises That Delay AI Adoption Will Lose Top Talent Big companies - think Goldman Sachs, Amazon, and others - aren't waiting. They see what's coming: AI-driven companies will dominate not just in efficiency, but in talent acquisition. > Companies that don't modernize their AI strategies will struggle to attract and retain the best people. The next generation of employees expects AI-driven tools that make work faster, smarter, and more efficient. Ignore that, and you'll start losing top talent to competitors that actually get it. --- ## AI Isn't Taking Jobs - It's Expanding Markets Let's get this straight: AI isn't just about cutting costs or replacing jobs - it's creating new opportunities. An executive I spoke with recently said they invested in AI to improve efficiency but ended up unlocking an entirely new customer segment they hadn't even considered. That's the real power of AI - it doesn't just optimize workflows; it expands what's possible. AI-driven companies aren't just saving money - they're scaling faster, making better decisions, and finding new ways to grow. --- ## What Should Enterprise Leaders Be Doing Right Now? If you're a decision-maker, here's what you should be focusing on: 1. **Forget the hype - focus on execution.** AI isn't magic. It's a tool. The value comes from how well you integrate it into your business, not which model you use. 2. **Think beyond cost savings.** AI should drive revenue, expand market share, and increase operational efficiency - not just cut costs. 3. **Move fast - but don't ignore compliance.** AI adoption is inevitable, but companies that neglect security, privacy, and governance will hit serious roadblocks. 4. **Don't lose sight of talent.** The best people want to work at AI-driven companies. If your enterprise isn't evolving, you're making it harder to attract and retain the talent you need to scale. AI isn't just reshaping industries - it's defining the next market leaders. The real question isn't whether to invest - it's whether your business is ready to lead. --- ## Key Takeaways - **It's not the model - it's the business impact.** The most successful AI companies remove complexity and reduce friction, not chase the flashiest model. - **The AI model market is commoditizing.** Real value comes from enterprise-grade security, compliance, and seamless deployment. - **AI is reshaping decision-making, not just tasks.** The shift from searching for information to getting instant, actionable answers is transforming workflows. - **Delaying AI adoption costs you talent.** The next generation of employees expects AI-driven tools. Companies that don't modernize will lose their best people. - **AI expands markets, not just efficiency.** Companies investing in AI are discovering entirely new customer segments and revenue streams. *If your enterprise is navigating AI strategy, [learn how Revolv helps leaders scale with clarity and conviction](/advisory).* --- ## The AI Maturity Gap - **Canonical URL**: https://www.therevolv.com/signal/the-9-phases-of-ai-transformation - **Author**: Jon Chu | **Published**: February 24, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 9 min - **Tags**: AI & Technology, Strategy A founder I advise called me last quarter with good news: "We rolled out ChatGPT Enterprise to the whole company. We're officially an AI company now." Three months later, nothing had changed. Same workflows. Same bottlenecks. Same manual processes. The only difference was a $30/seat/month line item and a Slack channel called #ai-experiments that had gone quiet after week two. This pattern repeats in almost every advisory engagement I take. A $5M ARR company buys AI tooling, announces a transformation, and then watches as exactly zero workflows actually transform. The CEO thinks they're at Phase 4. They're at Phase 2. The problem isn't the tools. It's that most founders have no diagnostic for where they actually are - or what's actually blocking them from the next level. ## The 9 Phases of AI Transformation After working with dozens of $1M-$50M ARR companies on AI strategy, I've mapped a progression that nearly every organization moves through. Some of these phases take months. Some take years. Most companies are stuck far earlier than they think. ### Phase 1: AI Curious **What it looks like**: The CEO reads AI articles, forwards them to the team, and books a strategy offsite with "AI" in the title. There's a lot of conversation about what AI could do. Nothing has been tried. **What's blocking you**: Action. You can't learn about AI from articles. You learn by shipping something, even something small, and watching what happens. The gap between reading about AI and using AI is where most companies lose their first 6 months. ### Phase 2: Guerrilla AI **What it looks like**: Your best people are quietly using ChatGPT in browser tabs. Your top sales rep is drafting cold emails with it. Your marketing lead is generating first drafts. Nobody told them to. There's no policy, no sharing, no institutional knowledge about what works. **What's blocking you**: This phase is more dangerous than most founders realize. Your IP is being pasted into third-party tools with no data governance. Quality is wildly inconsistent. And the productivity gains are invisible - happening in individual browser tabs, never captured or replicated. *Most $1M-$50M ARR companies are here right now.* If your team is using AI but you couldn't tell me exactly how, where, or with what guardrails - you're at Phase 2. ### Phase 3: Licensed & Locked **What it looks like**: The company bought Copilot seats, negotiated an enterprise agreement, and IT wrote an acceptable use policy. There might be a training session. Leadership feels good about this - the box is checked. **What's blocking you**: Tool access is not transformation. Buying Copilot is like buying a gym membership - it doesn't mean anyone's working out. The tools are deployed, but nobody changed how they work. The workflows are identical. The tools just sit on top, underutilized. ### Phase 4: Process-Embedded **What it looks like**: AI is in the actual SOP. Support tickets get AI-drafted responses that agents review and send. Sales calls auto-summarize into CRM notes. Financial reports generate first drafts that analysts refine. AI isn't a tool people use - it's a step in the workflow. **What's blocking you**: This is the phase that separates companies that *talk* about AI from companies that *run* on it. And the constraint is almost never technical. It's organizational clarity. You can't embed AI into a workflow if nobody owns the workflow. You can't automate a decision if the decision rights aren't defined. You can't build on a process that lives in three people's heads. ### Phase 5: Context-Aware **What it looks like**: AI answers questions from *your* data. Not generic responses - specific ones. "Which customer segments have the highest churn risk and why?" "What did we commit to in the Q3 board deck that we haven't delivered?" The AI knows your business context. **What's blocking you**: Clean data, shared definitions, and someone who owns the truth. Most scaling companies have data scattered across 15 tools with no single source of truth. The AI can't be context-aware if the context is fragmented. ### Phase 6: Supervised Agents **What it looks like**: AI executes entire tasks with human checkpoints. An agent stages deals in the CRM, drafts follow-up sequences, and flags anomalies in pipeline data. A human reviews and approves, but the heavy lifting is automated. **What's blocking you**: Agent sprawl, unclear ownership, and coordination overhead. Every team wants their own agent. Nobody wants to own the integration layer. The agents multiply, but the coherence doesn't. ### Phase 7: AI-Native Roles **What it looks like**: Job descriptions are rewritten assuming AI participation. Every function has a copilot. The marketing team doesn't have a "content writer" - they have a "content strategist" who directs AI-generated first drafts. Roles are redesigned around human judgment, not human execution. **What's blocking you**: Fragmented intelligence across departments. Each team optimized their own AI stack, but nobody built the connective tissue. Sales AI doesn't talk to marketing AI. Support insights don't flow to product. ### Phase 8: Intelligence Platform **What it looks like**: One unified intelligence layer across all systems. Any leader can ask cross-functional questions and get real answers. "What's the relationship between our Q4 marketing spend, support ticket volume, and churn rate?" The AI connects the dots across silos. **What's blocking you**: Human decision latency. The system can surface insights faster than the organization can act on them. The bottleneck shifts from "we don't know" to "we can't decide fast enough." ### Phase 9: Adaptive Organization **What it looks like**: Pricing, staffing models, and operational parameters adjust dynamically. Closed-loop AI systems make micro-decisions within human-defined guardrails. The organization responds to market changes in hours, not quarters. **What's blocking you**: Deep institutional trust in AI systems. This phase requires the organization to be genuinely comfortable with AI making consequential decisions - and that trust has to be earned through years of reliable performance at earlier phases. ## Where You Actually Are Be honest with yourself. If your team is using ChatGPT but you don't have a policy, shared prompts, or any way to capture what's working - you're at Phase 2. If you bought enterprise licenses but your workflows haven't changed - you're at Phase 3, and barely. The gap between "we have AI tools" (Phase 3) and "AI is in our workflows" (Phase 4) is enormous. And it's where the vast majority of scaling companies are stuck right now. ## The Phase 3 → 4 Wall This is the most important transition in the entire model, and it's where I spend most of my advisory time. Phase 3 → 4 is where companies stall indefinitely. And the reason is counterintuitive: **it's not a technology problem. It's a structural problem.** Buying Copilot seats is easy. Embedding AI into how work actually gets done requires organizational clarity that most $1M-$50M ARR companies simply don't have yet. You need: - **Clear workflow ownership**: Someone has to own each process end-to-end before AI can be embedded in it. - **Defined decision rights**: If it's unclear who decides how a support ticket gets resolved, you can't automate parts of that decision. - **Documented processes**: If the process lives in a senior team member's head, AI has nothing to embed into. This is exactly what I address in advisory with the APEX framework. The first layer - People + Outcomes - exists to create the ownership clarity that makes Phase 4 possible. You can't leap to AI-embedded workflows if the workflows themselves aren't defined, owned, and documented. AI maturity is downstream of organizational maturity. Every time. ## The Bottleneck Pattern The real value of a maturity model isn't "what level am I?" - it's "what's actually blocking the next level?" Look at the pattern across all 9 phases: | Transition | The Real Bottleneck | |---|---| | 1 → 2 | Leadership attention and willingness to experiment | | 2 → 3 | Governance, security, and data policy | | 3 → 4 | **Workflow ownership and process clarity** | | 4 → 5 | Data infrastructure and shared definitions | | 5 → 6 | Trust frameworks and guardrail design | | 6 → 7 | Organizational redesign and role evolution | | 7 → 8 | Cross-functional coherence and shared intelligence | | 8 → 9 | Institutional trust and adaptive culture | Notice what's missing from this list? *Better AI tools.* At no point in the progression is the bottleneck "we need a better model" or "we need more features." The constraints are organizational, structural, and cultural - every single time. This is why the companies that will win the AI transition aren't the ones with the biggest AI budgets. They're the ones with the clearest organizational structures, the best-defined workflows, and the leadership willing to redesign how work gets done. ## Where Are You Really? Three honest questions to diagnose your phase: **1. Can you name, right now, every workflow where AI is an embedded step (not a tool someone might use, but a defined step in the process)?** If you can't name any: you're at Phase 2-3. If you can name a few: you're approaching Phase 4. If AI is in most core workflows: you're at Phase 4-5. **2. When your best performer quits, do their AI workflows leave with them?** If yes: you're at Phase 2. The knowledge is individual, not institutional. If partially: you're at Phase 3. If no, the workflows are documented and owned: you're at Phase 4+. **3. Can your AI answer questions about *your* business, or just generic questions?** If generic only: Phase 3 or below. If it knows your data but only within one department: Phase 5. If it connects dots across functions: Phase 7-8. ## Key Takeaways - **Most $1M-$50M ARR companies are at Phase 2 (Guerrilla AI)** - individuals using AI in browser tabs with no policy, no sharing, and no institutional capture. - **The Phase 3 → 4 wall is where companies stall indefinitely.** Buying tools is easy. Embedding AI into workflows requires organizational clarity most scaling companies lack. - **AI maturity is a structural problem, not a technology problem.** The bottleneck is never "better AI tools" - it's workflow ownership, data infrastructure, and organizational design. - **Every phase's constraint tells you exactly what to fix.** The model is diagnostic, not aspirational. Find your real phase, identify the blocker, and work on that. - **Organizational maturity precedes AI maturity.** You can't embed AI into workflows that aren't defined, owned, and documented. Structure first, technology second. *If you're stuck between Phase 2 and Phase 4, that's exactly where I work with founders. The fix isn't more AI tools - it's organizational clarity. [Learn about my advisory practice](/advisory) and how the APEX framework helps scaling companies build the structure that makes AI transformation possible.* --- ## The Anatomy of a Great AI Product: How to Build for 2025 and Beyond - **Canonical URL**: https://www.therevolv.com/signal/anatomy-of-great-ai-product - **Author**: Jon Chu | **Published**: February 11, 2025 | **Updated**: February 25, 2026 | **Reading Time**: 6 min - **Tags**: AI & Technology, Product, Strategy Behind every exceptional product lies a fundamental truth - it must solve real problems, deliver a seamless experience, and scale effectively. Imagine an AI-driven tool that anticipates customer needs before they even realize them, or a product so intuitive that users immediately feel it was built just for them. In today's AI-driven landscape, these capabilities are not just enhancements; they define what makes a product truly great. However, in today's AI-driven world, what makes a product truly stand out has evolved. AI is no longer just an enhancement - it's a core driver of differentiation, personalization, and efficiency. ## Understanding Market Needs with AI Traditional product development relied on surveys, customer interviews, and intuition. AI has transformed this landscape. Predictive analytics can now anticipate customer needs before they even arise. For example, in e-commerce, AI-powered recommendation engines analyze user browsing and purchase history to predict and suggest products before a customer actively searches for them. Similarly, in healthcare, predictive analytics can identify early warning signs of disease by analyzing patient data, allowing for proactive treatment and better health outcomes. Natural language processing (NLP) analyzes vast amounts of user feedback to detect sentiment and emerging trends. AI's ability to recognize behavioral patterns enables businesses to refine their products continuously, ensuring they meet user needs proactively rather than reactively. ## Creating Unique Value with AI AI doesn't just improve existing products; it enables entirely new experiences. Personalized recommendations, like those from Netflix or Spotify, make users feel understood. AI-driven learning systems adapt to individual behavior, continuously improving over time. Automated chatbots and agents provide real-time support, making interactions more seamless and efficient. These capabilities enhance a product's value far beyond what traditional software can achieve. ## Revolutionizing User Experience A product's success is deeply tied to how intuitive and enjoyable it is to use. AI is redefining user experience by making interfaces more natural and engaging. Voice and gesture recognition allow users to interact with products effortlessly. Conversational AI simplifies interactions, reducing friction and making technology more accessible. Real-time accessibility features, such as speech-to-text and instant translations, ensure that products cater to a diverse range of users, further broadening their impact. ## The Power of AI-Driven Infrastructure Behind every great product is a strong, reliable infrastructure. AI plays a crucial role here as well. It enables automated testing and debugging, identifying inefficiencies before they become costly problems. It optimizes performance, allocating resources dynamically to ensure smooth operation even under heavy demand. AI also strengthens security by continuously monitoring for threats and fraud. Additionally, the rise of AI Web App Builders, as [highlighted by a16z](https://a16z.com/), is transforming how software is developed, shifting away from traditional programming models to AI-driven workflows that optimize efficiency and usability. ## The Rise of Vertical AI: The Biggest Opportunity in 2025 AI is moving away from general-purpose applications and toward Vertical AI, where products are built for highly specific industries and user needs. Some of the biggest opportunities in 2025 will come from AI solutions that are so tailored to their target market that users immediately recognize their value. A guiding principle for Vertical AI products is that their first version should be so specific that: - When a target user lands on the product page, their first reaction is, "This was built exactly for me - I need to sign up now." - When explaining the product to others, it feels so niche that it's almost embarrassing how specialized it is. By focusing intensely on a narrow but urgent problem, Vertical AI products gain immediate traction and establish early dominance before expanding to broader markets. ## Keeping Users Engaged and Retained Great products don't just attract users; they keep them engaged. AI-driven personalization tailors experiences to individual preferences, increasing retention. Intelligent gamification techniques can predict when users might disengage and adjust experiences accordingly. AI also enables businesses to anticipate churn, allowing them to intervene proactively and retain customers before they leave. ## Optimizing Monetization with AI AI isn't just about better experiences; it also drives better business models. Dynamic pricing adjusts costs in real time based on demand and user behavior. Predictive analytics help companies understand the long-term value of customers, optimizing acquisition and retention strategies. AI-driven ad models ensure that advertising remains relevant and non-intrusive, improving engagement while maximizing revenue. ## The Agility of AI-Powered Decision-Making One of AI's most transformative impacts is in decision-making. AI-driven A/B testing allows companies to run thousands of experiments simultaneously, identifying the most effective product iterations. Real-time analytics provide continuous feedback, enabling on-the-fly optimizations. Automated feature rollouts allow businesses to introduce new capabilities gradually, ensuring a smooth user experience while testing impact in real-time. ## AI's Role in Go-To-Market Strategies Launching and scaling a product requires precision, and AI is reshaping how businesses approach go-to-market strategies. AI-driven growth hacking automates marketing campaigns, optimizing performance through real-time testing. Smart segmentation clusters users based on behavior, ensuring messaging is relevant and compelling. AI-powered lead scoring prioritizes high-value customers, increasing conversion rates and maximizing sales efficiency. ## The Need for Ethical and Transparent AI Leadership With great power comes great responsibility. As AI becomes embedded in products, ethical considerations must take center stage. Companies must proactively address bias in AI algorithms, ensuring fairness and inclusivity. Transparency in AI decision-making is critical to maintaining trust, particularly in areas like finance, healthcare, and hiring. Additionally, businesses must prioritize privacy-first AI practices, staying ahead of evolving regulations and consumer expectations. ## Measuring Success in an AI-Powered World In the AI era, success is measured not just by growth, but by impact. AI-powered analytics provide businesses with real-time insights into engagement, behavior, and retention. Cohort analysis based on AI models helps companies understand user segments more deeply, refining their strategies accordingly. Beyond user metrics, AI is also improving operational efficiency - optimizing inventory, logistics, and supply chains to ensure seamless execution. ## Final Thought: AI Is Not the Product, It's the Superpower AI-driven products succeed by seamlessly integrating into user workflows. As we enter the next phase of AI-powered product strategy and development, companies that embed AI into customer workflows will shape the future. Those who recognize AI as the backbone of innovation will define the next generation of world-class products. --- ## Key Takeaways - **AI is now the core driver of product differentiation.** It's no longer just an enhancement - it defines personalization, efficiency, and user experience. - **Vertical AI is the biggest opportunity in 2025.** Products so specific that target users immediately say "This was built for me" gain immediate traction. - **AI transforms every layer of product building.** From understanding market needs with predictive analytics to optimizing monetization with dynamic pricing. - **Ethical AI leadership is non-negotiable.** Bias, transparency, and privacy-first practices are essential as AI becomes embedded in products. - **AI is not the product - it's the superpower.** Companies that embed AI into customer workflows will define the next generation of world-class products. *If you're building AI-driven products and want to sharpen your strategy, [learn how Revolv helps leaders scale with clarity](/advisory).* --- ## Why Company Culture Is the Missing Key to AI Success - **Canonical URL**: https://www.therevolv.com/signal/why-company-culture-missing-key-ai-success - **Author**: Jon Chu | **Published**: November 5, 2024 | **Updated**: February 25, 2026 | **Reading Time**: 7 min - **Tags**: AI & Technology, Strategy As AI redefines industries, organizations are at a pivotal moment to embrace AI not only as a tool but as a catalyst for cultural transformation. The success of any AI initiative depends on its alignment with a culture of innovation, agility, and continuous learning. When woven into a company's cultural fabric, AI's potential is fully realized, driving measurable returns and deeper employee engagement. Reflecting on my experience in AI integration, I've found that the most transformative applications occur when organizations focus on culture first. Successful AI initiatives align deeply with company values, are growth-oriented, and are embraced across departments. This article explores how leaders can build a culture that enables AI's success and positions it as a positive, empowering force. --- ## Assessing Cultural Readiness for AI Implementing AI effectively begins with assessing the organization's readiness for change. AI thrives in adaptable, curious environments. Do employees view AI as an opportunity for growth? Do leaders encourage learning and experimentation? Companies that foster a growth mindset and continuous learning are well-positioned to make AI feel natural and beneficial. Leadership can start by gauging cultural readiness through surveys and focus groups. These insights can uncover any disconnects, allowing leaders to address concerns early. Aligning culture with AI goals prepares the workforce to view AI as a career enhancer, not a disruption. ## Building Transparency and Trust Transparency is essential for AI adoption. Employees need a clear understanding of how AI will impact their roles, the ethical standards in place, and the value it brings to the company. Transparent communication - emphasizing AI as a supportive, not replacing, tool - helps build trust and reduces fear of the unknown. For example, [IBM's approach to AI](https://www.ibm.com/artificial-intelligence/ethics), with ethical guidelines and open discussions, fosters a climate of trust. IBM's success highlights the value of creating open forums where employees can discuss AI's ethical and practical impacts. ## Aligning AI with the Company's Mission AI initiatives gain traction when aligned with the company's broader mission and goals. Leaders should communicate the "why" behind AI initiatives, connecting them directly to company objectives. When AI supports the mission, it becomes a powerful tool for employees to drive meaningful, mission-aligned work. Leadership sessions dedicated to exploring AI's purpose with teams are effective. Asking questions like "Why is AI essential to our goals?" and "How will it enhance, not replace, employees' roles?" reinforces AI as a positive force. ## Fostering Cross-Functional Collaboration AI's true impact comes from cross-functional collaboration, drawing on diverse insights across the organization. Encouraging interdepartmental collaboration unlocks new AI use cases and maximizes AI's value. Cross-functional collaboration ensures AI-driven insights are relevant and impactful across functions. For example, a project between marketing and data science teams could reveal new customer insights, enabling personalized outreach. These projects break down silos, transforming AI into a tool that benefits the entire organization. --- ## Ten Critical Strategies for Integrating Generative AI To fully harness generative AI, leaders must look beyond the technology and focus on the organizational changes it requires. While employees are often eager to experiment with AI, a structured approach ensures sustainable and scalable impact. **1. Reframe AI as an Enabler of Human Potential.** Position AI as a tool that enhances human capabilities rather than replacing them. By sharing real-world examples that show how AI improves efficiency, accuracy, or creativity, leaders can reduce resistance and foster enthusiasm for AI as a growth partner. **2. Encourage a Growth Mindset.** Promote a culture of continuous learning. Encourage employees to view AI as an opportunity for skill enhancement, cultivating resilience and openness to new approaches that are essential in a rapidly changing AI environment. **3. Provide AI Training for All.** Make AI training available to everyone - from entry-level to executives. This democratization of knowledge builds inclusivity, empowering all employees and establishing a strong foundation for AI literacy organization-wide. **4. Support Safe Experimentation.** Innovation thrives in environments where experimentation is safe. Establish "safe zones" for AI exploration, allowing employees to test tools without fear of mistakes. Low-stakes projects and sandbox environments help build confidence with AI. **5. Gain Insight from Resistance.** Engaging skeptics early can reveal valuable insights. Addressing employee concerns openly often turns skeptics into advocates, fostering a stronger commitment to AI across the organization. **6. Communicate AI's Role Clearly.** Regularly share AI's purpose, benefits, and limitations to build trust. Transparent communication helps employees see AI as a supportive asset rather than a threat. **7. Set Ethical Standards.** Create ethical guidelines for AI that reflect organizational values, focusing on data privacy, transparency, and fairness. Responsible AI practices build trust with employees and stakeholders alike. **8. Prioritize Human Skills.** Focus on skills like adaptability, creativity, and problem-solving - key qualities for working alongside AI. Encouraging hands-on experimentation with AI tools demystifies the technology and enhances comfort. **9. Measure What Matters.** Establish metrics that track AI adoption and impact. Empower team champions to customize AI for specific needs, and create a Center of Excellence (CoE) to centralize expertise and scale AI initiatives. **10. Recognize and Reward AI Champions.** Celebrate employees who embrace and effectively use AI in their roles. Recognizing these efforts motivates others and reinforces AI as a valued cultural pillar. > By embedding these strategies, organizations can nurture an environment where AI becomes integral to the company's culture - driving growth, innovation, and engagement. --- ## Leadership's Role in AI-Driven Culture Change Leaders are essential to AI adoption, modeling AI engagement, mentoring others, and ensuring resources are available for learning. They must align AI policies with organizational values and legislative requirements. Inclusivity is critical; AI can improve accessibility, such as generating captions or alt text for employees with disabilities. However, responsible design is necessary to prevent bias. Transparent, accountable AI practices build a culture of ethical, equitable AI use. Executives should stay informed about AI trends and communicate AI's potential and limitations, ensuring stakeholders see it as a valuable tool rather than a "fix-all" solution. By identifying where AI can add real value and investing in AI literacy, executives can position AI as a tool that enhances human insights and collaboration. --- ## The Bottom Line: Aligning Culture with AI Aligning AI with a growth-oriented culture unlocks its transformative potential. Organizations that focus on cultural alignment see AI as an empowering force, accelerating innovation and fostering inclusivity. Such organizations are future-ready, adaptive, and resilient, with AI as a powerful enabler of human potential across functions. In a rapidly evolving world, aligning AI with organizational culture is key to building a future-focused organization - where AI is not just a tool but a catalyst for sustainable growth and positive change. How can your organization embed AI into its cultural DNA? --- ## Key Takeaways - **Culture readiness determines AI success.** AI thrives in adaptable, curious environments where employees view it as a growth opportunity, not a threat. - **Transparency builds trust.** Clear communication about AI's role, ethical standards, and impact on roles reduces fear and fosters adoption. - **AI must align with company mission.** When AI supports broader organizational goals, it becomes a tool employees embrace for meaningful, mission-aligned work. - **Ten strategies for sustainable AI integration.** From reframing AI as a human enabler to recognizing AI champions, a structured approach ensures scalable impact. - **Leaders must model AI engagement.** Executives who stay informed, invest in AI literacy, and champion ethical practices build cultures where AI and humans thrive together. *If you're looking to build a culture that enables AI success, [learn how Revolv helps leaders embed AI into their organizational DNA](/advisory).* --- ## Why We Built Revolv - **Canonical URL**: https://www.therevolv.com/signal/why-we-built-revolv - **Author**: Jon Chu | **Published**: December 15, 2024 | **Updated**: February 25, 2026 | **Reading Time**: 4 min - **Tags**: Founder Stories, Relationship Intelligence The dinner was going well. Too well, actually. I was pitching a major investor on our Series A. The conversation flowed naturally as we talked about market dynamics, our traction, the vision. Then, halfway through the main course, she mentioned her daughter's graduation from Columbia. "My niece went there too," I said casually. She paused. Looked at me strangely. "We talked about this. At the Founders Fund dinner. Two years ago." The silence was deafening. I had no memory of that conversation. No memory of meeting her before at all. And in that moment, I watched the deal slip away. Not because of our metrics. Not because of our product. Because I forgot a human being. ## The Hidden Cost of Forgetting That dinner cost me $4 million in funding. But more than that, it revealed a truth I couldn't ignore: **I was losing relationships faster than I was building them.** > Relationship memory is the ability to recall important details about people you've met: where you met, what you discussed, and what you committed to. Unlike a contact list that stores names and numbers, relationship memory preserves the context that makes reconnection meaningful. I started counting. In the previous year: - I'd met 500+ people at conferences and events - I'd followed up with maybe 50 - I'd maintained real relationships with perhaps 10 The other 490? Gone. Lost to the chaos of business cards, LinkedIn connections, and the persistent delusion that "I'll remember them later." ## Everyone Has This Problem When I started talking to other founders, executives, and professionals, I discovered I wasn't alone. A survey we conducted found that **73% of professionals have lost touch with valuable connections** they fully intended to maintain. The reasons were always the same: - "Out of sight, out of mind" - "I meant to follow up, but life got busy" - "I can't remember where we met or what we talked about" Traditional CRMs didn't help. They're designed for deals, not relationships. LinkedIn became a graveyard of connections we never engage with. Our brains simply can't maintain 500 relationships the way our grandparents maintained 50. ## The Relationship Memory Gap What struck me most was the *compounding* nature of the problem. Every relationship you let fade is a potential: - Introduction that never happens - Deal that never closes - Collaboration that never forms - Friendship that never deepens And unlike financial capital, relationship capital degrades rapidly without attention. A connection you made three years ago who remembers you fondly is worth infinitely more than a fresh LinkedIn request. ## Building the Memory Layer That's why we built Revolv. Not another CRM. Not another contact manager. But a **relationship memory layer**: technology that remembers everyone you meet so you never have to. The core insight was simple: you don't need more tools to manage relationships. You need tools that make relationships *impossible to forget*. So we built features like: - **Connect**: Exchange contact info in 3 seconds. No business cards, no "how do you spell that?" - **Travel Mode**: Know who you forgot you knew in every city you visit - **AI Reminders**: Surface the right relationship at the right moment But the real magic isn't in any single feature. It's in the cumulative effect of never losing a connection again. ## What's Next We're still early in this journey. The investor from that dinner? She actually became one of our first advisors after I tracked her down and apologized for forgetting. (She found it funny, in retrospect.) The mission now is bigger than my own missed connections. We're building technology that helps every professional maintain the relationships that matter, at the scale their ambitions demand. Because the next generation of networking won't be about collecting contacts. It'll be about **never forgetting a single one**. --- ## Key Takeaways - **The cost of forgetting is real**: A single forgotten connection can cost millions in lost deals, missed opportunities, and damaged trust. - **The follow-up gap is widespread**: in our survey, 73% of professionals had lost touch with valuable connections they intended to maintain. - **CRMs don't solve this**: Traditional CRMs track deals, not relationships. They're designed for pipelines, not people. - **Relationship memory is the solution**: Technology that remembers everyone you meet so you never have to, surfacing the right person at the right time. *If you're tired of losing touch with the people who matter, [explore Revolv](/platform) and start remembering.* --- ## The Hire You Already Knew Wasn't Working - **Canonical URL**: https://www.therevolv.com/signal/the-hire-you-already-knew - **Author**: Jon Chu | **Published**: May 19, 2026 | **Reading Time**: 6 min - **Tags**: Strategy, Founder Stories, Best Practices A founder I advise called me on a Thursday afternoon. Not to ask for advice. To tell me he had finally done it: he had let someone go. The relief in his voice was unmistakable. So was the math he walked me through afterward. Nine months. That was how long it had taken. From the first moment he knew the hire was not working to the afternoon he actually ended it. Nine months of one-on-ones that went nowhere. Nine months of KPIs he quietly adjusted so the dashboard would look better. Nine months of telling himself it was probably just a rough quarter. He did not waste nine months on the exit. The exit took forty-five minutes. He wasted nine months on the knowing. --- ## The Gap Between Knowing and Acting This is the conversation I have had more than any other with founders and senior operators. Not about how to let someone go. About how long they waited after they already knew. The conventional assumption is that bad hires get caught at 90 days. That is what the onboarding literature says. That is what most companies plan for. A review cycle with structured check-ins and clear expectations. But the actual pattern tells a different story. The average bad hire does not exit at 90 days. They exit at six months. Sometimes twelve. And the gap between the first clear signal and the final conversation is almost always measured in quarters, not weeks. That gap is the cost. Not the severance. Not the recruiting fees. The months of deferred clarity are what drain companies, and what quietly erode the trust of everyone around the person you are managing. --- ## Why Operators Wait Part of it is optimism. You hired this person. You told your team you believed in them. Reversing that takes something most leaders underestimate: the willingness to be publicly wrong. Part of it is ambiguity. The signals in month one are never perfectly clean. The person is still finding their footing. The role is still being shaped. It is easy to find reasons to give it more time. But mostly? Operators wait because they do not have a forcing function. There is no structure that makes the truth undeniable at 30 days instead of 90. No designed mechanism to separate "this person is new" from "this person is not a fit." And without that mechanism, the default is always to wait. --- ## The Part No One Talks About Here is what makes this pattern harder to break than it looks. Most onboarding frameworks focus on output: what did this person ship, what numbers did they move, are they executing against the role. Those are the easy things to measure. They fit cleanly into a spreadsheet. You can point to them in a review. But the majority of hires that do not work out, by a significant margin, do not fail because of output. They fail because of something that is much harder to surface on a dashboard. And because most onboarding processes are not designed to make that thing visible, it stays invisible until it is everywhere. The best operators I know have figured this out. Not through better instincts. Through better structure. They have built their process so that the things that actually predict failure become observable in the first 30 days, not discoverable at month nine, after the rest of the team has already adapted around the problem. --- ## What the Signal Looks Like The founder I mentioned told me something I keep coming back to. "I saw it in week two," he said. "I just didn't know what I was looking at." That is usually how it goes. The signal was present early. The hire did not hide it. There was simply no framework that made the signal legible as a signal rather than noise. The operators who avoid the nine-month tax are not more decisive. They are more deliberate about what they build before someone's first day. They know that clarity at 30 days is not a function of how well the hire performs in the first month. It is a function of how well the environment was designed to surface truth. The difference is structural, not intuitive. And it is available to anyone willing to design it in before the hire starts, not reconstruct it afterward when the pattern is already clear to everyone except the spreadsheet. --- ## The Compounding Cost of Inaction There is a version of this story that ends at the exit. The founder lets the person go, the team resets, you move on. But that is not how it usually plays out. The more common version is that the team adjusts. They route around the problem. They learn which conversations to avoid, which projects to keep out of the person's lane, which decisions require extra coordination. They adapt. And then when the hire finally exits, you discover that the team has been carrying a structural workaround for months. That workaround has calcified into how things get done. And now the problem you thought was one person is woven into the system. The cost of a bad hire is not just the hire. It is the culture that forms around them while you wait. > The most expensive part of a wrong hire is almost never the severance. It is the months you spent managing around a truth you already knew. --- ## The First 30 Days Are the Whole Game The founders who get this right share one orientation: they treat the first 30 days as the entire investment thesis for the hire. Not a ramp. Not an adjustment period. A signal collection window. They design that window deliberately. They know exactly what they are looking for, and it is not output. By the time most operators realize a hire is not working, the signal was already there in week two. They just did not have the right frame to read it. The exit is not where the work happens. It is the last thing that happens, after a process that either surfaced the truth in time or did not. *If you work with operators who have learned to read the signals that compound (across hires, relationships, and teams), [Revolv was built for that kind of thinking](/platform).* ## Social - Twitter/X: https://x.com/therevolv - LinkedIn: https://www.linkedin.com/company/joinrevolv/ ## Contact - Email: hello@therevolv.com - Website: https://www.therevolv.com/contact