---
title: "Friendly Node: A Business Strategy Framework for the AI Era"
description: "A framework for analyzing businesses as networks of nodes — and how understanding information flow can reveal where AI creates the most value."
publishedDate: 2026-03-03
author: Alec
tags: ["AI", "Strategy", "Business"]
---


import FriendlyNodeDiagram from '../../components/FriendlyNodeDiagram.astro';
import BusinessNodesDiagram from '../../components/BusinessNodesDiagram.astro';
import RequestTimelineDiagram from '../../components/RequestTimelineDiagram.astro';

We're all trying to get our brain stems wrapped around AI. In a previous blog post, I described our migration from "Ye Olde Worlde" to the New World of AI-enhanced business. Some of us are already on board the ships en route to this New World, but even we are seeing it imperfectly. We're visitors from a foreign land with outdated assumptions; just like the first colonists to the Americas, we need new words and new frameworks to adapt to our New World. Enter Friendly Node.

[Friendly Node](https://friendlynode.com/) is an attempt to start analyzing businesses to prepare them for success in the AI-dominated New World. It bills itself as a company "operating system"…if you're an individual of the non-technical persuasion (read: you don't geek out about software), don't let this analogy put you off. Friendly Node looks at companies both as a node within a greater network of companies in the economy, and as a network internally.

<FriendlyNodeDiagram />

## Information is Processed into Value

In these systems, we're looking at information being the core currency passed between nodes. A node receives, processes, and transmits information. Raw information is processed into decisions that produce value via products and services.

Nodes receive "Requests for Value" (RFV), information coming into the node demanding transformation into a "Return of Value" (ROV). The most direct RFV is a customer order: a direct request to transform the request into a valuable product or service. However, nodes also receive RFVs that are less direct: potential customer questions, government requests for taxes and filings, requests for employment, partnership inquiries, etc. Each business has an internal network of nodes to provide ROVs for these RFVs.

Over time, inefficient nodes wither and are eliminated. Nodes that efficiently receive information and create value are rewarded.

## Startup Founders Identify Inefficient Nodes in the Economy

Startups are a chance to replace inefficient nodes in the economy with alternative, more efficient nodes.

An "inefficient" node might be one that's poorly connected to other nodes; for example, a company that lacks partnerships or sales acumen to adequately distribute an otherwise great product. Or it might be a node that poorly processes information, like a business with bad product-market fit.

Successful startup founders are geniuses at finding these inefficient nodes and replacing or bypassing them with new, efficient businesses.

## What Are Your External Connections to Other Nodes?

Identifying your business's position within the greater network of the economy requires understanding what other nodes you're connected to. Namely…

- Who are your customers?
- Who are your suppliers?
- Who are your partners?
- What information do they send to your company?
- What channels do they use to transmit that information?

## Optimizing Your Business's Network of Nodes

A core principle of Friendly Node is that, in addition to being a node within the network of the greater economy, your business is a network itself.

The nodes within your business also respond to RFVs (requests for value) with ROVs (returns of value). For example, an e-commerce business receives an RFV in the form of a customer order. That RFV goes through several internal nodes which might include…

- Ecommerce website
- Sales
- Fulfillment/Inventory
- Customer success/satisfaction
- Product feedback/development

<BusinessNodesDiagram />

### Tracing a Real Request

The best way to expose inefficiency is to follow a single customer request from the moment it arrives to the moment it resolves. Before you optimize anything, document the actual path — not the ideal one:

- How long did each transformation take?
- Where did delays accumulate, and why?
- Where did errors force a request to be sent back?
- What was the total cycle time versus actual processing time?

<RequestTimelineDiagram />

In this example — a client inquiry moving toward a signed contract — the full cycle took eight days. Actual work: roughly five hours. The rest was waiting: for someone to notice the form submission, for a calendar slot, for legal to review. One handoff was sent back entirely because budget information was missing from the initial scope call.

That ratio — 8 days of cycle time for 5 hours of processing — is typical. And it's where AI creates the most obvious value: collapsing wait times, pre-filling missing information before handoffs, and catching the "missing budget" class of errors before they trigger a loop.

These nodes are usually task-based. You can start by identifying general node "buckets": for example, sales. But ideally you can break these general nodes into more granular responsibilities: sales might include prospecting, RFP responses, and maintaining existing customer relationships.

By atomizing your business into nodes, we can identify weak points or spot opportunities for further automation. Of course the million dollar question of the day is…

## What Nodes Can Be Optimized by AI?

By looking at your business as a network of nodes, we can identify nodes that can be replaced or augmented by AI. The key to optimizing your network is understanding what "friendly" means within the Friendly Node framework.

In network design, "friendliness" is how well you're improving the speed and quality of a node's processing while minimizing the direct cost of the node and network debt. To quote the [Friendly Node website](https://friendlynode.com/), "Friendly operations are those that maintain or strengthen network connections over time rather than degrading them."

## Making Nodes Friendly

Consider your CRM. If you've ever taken over a legacy CRM with a variety of non-standardized tags, duplicate records, and poor connections to the other nodes in your organization, you've experienced an "unfriendly" node. Chances are it was difficult for that CRM to respond to common RFVs, like generating a list of sales prospects for a campaign or finding the history of a specific prospect or customer.

The pain you're experiencing may be partially the direct cost of the CRM (a costly Salesforce contract, for example), but the greater cost is network debt. Over time, bad decisions have accumulated to degrade the node's ability to process requests for value.

Making the CRM node friendlier could take a variety of forms. You might consider…

- Adopting a new CRM
- Standardizing records and deduplicating
- Augmenting existing records with information from other nodes
- Finding better integration pathways with other nodes

All of these efforts should either reduce the direct cost of running the system or reduce the network debt that degrades the node's performance over time.

## A Telescope to the AI-Native World

As we continue our journey to the AI New World, Friendly Node offers us a "telescope" to start seeing that new landscape and adapting our businesses to it. Nodes are solution agnostic: our goal is making them friendlier (processing greater value at lower cost). Once we identify the nodes and target our most inefficient ones, we can find opportunities for deploying AI.

I'll be producing some case studies of my first real-world applications of the Friendly Node framework in the coming months, but if you're interested in using it now, [get in touch](/contact)!