NexStep

A patent is rarely about a single product. It is about claiming a category as institutional infrastructure rather than as an engagement or an idea. For a CFO evaluating where to invest in the people side, that shift matters. We recently filed a patent for the methodology behind our diagnostic. The point of this post is not the filing itself. It is what the filing signals about the work, and what it should signal to anyone allocating capital to the people side of a business. When a category transitions from advisory to infrastructure, three things change for the buyer. The work becomes repeatable across cycles and across companies. Infrastructure-grade work compounds. Engagement-grade work resets. The work becomes comparable. Different organisations can be read with the same instrument, which is the entry condition for benchmarks, standards, and portfolio-level views. The work becomes auditable. Decisions made on the back of the read can be defended structurally, the way financial decisions are. For a CFO, the question is not whether to file a patent. It is whether the people-architecture work in your business is currently operating at engagement grade or infrastructure grade. The two have very different cost structures and very different shelf lives. The category is now reaching the point where the second option is becoming available. #PeopleStrategy #Leadership #CFO

Retention numbers are read as one number, but they have at least two underlying causes. Architectural causes are about how the company is built. Market causes are about what is happening outside it. The same retention figure can mean either, and the response differs entirely. Seven diagnostic questions separate them. 1. Function-concentrated, or distributed? Concentration signals architecture; distribution signals market. 2. Concentrated in one tenure band? First-six-months exits suggest onboarding architecture; three-year exits suggest career-path or compensation architecture. Even distribution signals market. 3. Regretted or expected? A spike in regretted exits is structural. A spike in expected exits is often a performance system finally working. 4. Similar destinations or diverse? Concentration in one destination type, especially competitors, signals market. Diverse destinations more often signal architectural fit. 5. Themed or idiosyncratic exit conversations? Themed exits are architectural. Idiosyncratic exits are usually individual or market. 6. Tracking with engagement scores, or diverging? Tracking is usually market. Diverging suggests engagement is masking an architectural issue people are not yet voicing. 7. Did anything in the operating model change in the last two quarters? Most architectural retention issues map back to a structural change that was not visible at the time. Seven questions, two underlying causes. The number is the same. The response is not.

At 80 people, decisions flow through the founder. At 250, they cannot. At 1,000, the room itself has multiplied. Where you sit on this curve determines what you should be reading. At 80, you are reading the founder’s decision throughput. The architecture is essentially the founder, with everyone feeding context into them. The right question is whether the founder is the bottleneck and whether the next 100 hires assume they will continue to be. At 250, you are reading the translator layer. The founder cannot be in every decision; a second tier has emerged. The right question is whether that tier is empowered, calibrated, and resourced, or whether it is a layer of executives forwarding decisions to the founder anyway. At 1,000, you are reading the operating system itself. No one person makes most of the decisions. The architecture is the rules, the cadence, the handoffs, the escalation paths. The right question is whether the system is reliable enough that the founder can spend most of their time outside it. Each altitude has different failure modes, different leading indicators, and a different definition of good. Reading them with the same lens, which most organisations do, is the source of much of what gets misdiagnosed as culture. Calibration begins with knowing which altitude you are reading, and which architecture is supposed to be there. #Startups #StartupGrowth #ScalingStartups

Two CFOs see the same retention number: regrettable attrition up 4 points quarter on quarter. One acts immediately. The other does not. The number is identical. The reading is not. The first CFO knows their organisation is at a stage where retention shifts of that size usually precede operating issues by two quarters. They have seen the pattern. They act because the number, read in context, is a leading indicator of something else. The second CFO is in a business where similar shifts are seasonal and self-correcting. Acting would be expensive overcorrection. Their inaction is not negligence. It is calibration. Both CFOs are right. The difference is not analytical capability. It is context. This is what calibration means in the practice of reading numbers about people. The number is the input. The structural conditions around it determine what it signals. Without those conditions, the number is just a number. The financial side of an organisation learned this decades ago. Different businesses read the same revenue trajectory differently because the context differs. The same discipline has not reached the people side, where the same retention number, the same engagement score, the same time-to-fill, gets read identically across very different operating conditions. A number is a measurement. A reading is a measurement plus its context. The two are not the same, and the people side has been treating them as if they are. #PeopleAnalytics #HRAnalytics #DataDriven #DecisionMaking

Five things change between 80 and 250 people. Founders feel them before they have words for them. Here is the language. 𝗧𝗵𝗲 𝗿𝗼𝗼𝗺. At 80, you can have everyone who matters in one room for a decision. At 250, you cannot. Decisions that used to need one conversation now need three. 𝗧𝗵𝗲 𝘁𝗿𝗮𝗻𝘀𝗹𝗮𝘁𝗼𝗿 𝗹𝗮𝘆𝗲𝗿. At 80, you talk directly to anyone shaping a product, a number, a relationship. At 250, you talk to people who talk to those people. Context gets lost there, and the founder is the last to know what was lost. 𝗧𝗵𝗲 𝗰𝗼𝘀𝘁 𝗼𝗳 𝗰𝗹𝗮𝗿𝗶𝘁𝘆. A single all-hands at 80 transmits direction faithfully. At 250, the same all-hands needs three follow-ups before the message lands. Communication that was free becomes expensive. 𝗧𝗵𝗲 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘄𝗮𝗹𝗹𝘀. At 80, engineering and sales know each other personally. At 250, they know each other through tickets. Cross-functional work shifts from collaboration to coordination. 𝗧𝗵𝗲 𝗮𝗰𝗰𝗼𝘂𝗻𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝘀𝗵𝗮𝗱𝗼𝘄. At 80, you can tell who owns what by looking around. At 250, two people often think they own the same thing and three think no one does. Accountability stops being self-evident. You feel these before the numbers reflect them. Naming them is half the work. Reading the architecture beneath them is the rest. 𝗡𝗲𝘅𝗦𝘁𝗲𝗽 𝗶𝘀 𝗯𝘂𝗶𝗹𝘁 𝗳𝗼𝗿 𝘁𝗵𝗮𝘁 𝗿𝗲𝗮𝗱. Structured, calibrated to your stage and sector, ready before the architecture starts to cost a quarter. #ScalingTeams #FounderJourney #OperatingSystems #OrganisationalDesign #PeopleArchitecture

Most CHROs see the real signal in their organisation before the financials do. The credibility gap is not in seeing. It is in how it gets framed. Three shifts change the board conversation. First, replace adjectives with mechanisms. "Engagement is dropping" is a board-stopper. "Three engineering managers have absorbed two senior hires each without backfill, and decision throughput in their pods has halved" is a board topic. The board cannot act on an adjective. It can act on a mechanism. Second, link the signal to a forward stake. The board has limited room for the current quarter. It has unlimited interest in next year's plan. "The architecture that delivered this quarter cannot deliver the FY plan" travels further than "we have a culture issue." Third, compare. The board reads comparison fluently. Compared to where the company was two quarters ago, compared to the peer cohort, compared to the architecture the plan assumes. Comparison turns an internal observation into an institutional read. The signal does not change. The framing makes it actionable. When the board sees mechanism, stake, and comparison, the people side becomes a conversation it can hold. Without these, it stays a feeling the CHRO has to defend. NexStep-CPR™ is built to turn that feeling into evidence the board can act on. Mechanism, forward stake, and comparison, rendered in a single structured read before the conversation begins. #Leadership #PeopleStrategy #StartupLeadership #BoardLeadership #ScalingCompanies

Capital diligence has a blind spot on the people side of an organisation. It is not careless work. It is structurally incomplete, and there are three signals that make this visible. CHROs see them first, because they live inside the gap. The first is the standard. Financial diligence has one. Operational diligence has one. People diligence still rests on calls with three or four executives and an inference. The same company would never sign off on a deal where the financial model was assembled from three conversations. The second is the comparison. Financials get benchmarked, modelled, stress-tested. The team gets described, not compared. No common scale, no common language, no portfolio-level view. The third is the consequence. When the people side falters after the deal, it is treated as a surprise. It is rarely a surprise to the CHRO. It is a structural failure of how the read was done, not a failure of who is reading it. CHROs are positioned to see what capital is not yet structured to see. The asymmetry is real, and it has not had an instrument built for it yet. #CHRO #HumanResources #TalentStrategy

An investment committee will stress-test a financial model for hours. It will accept the management team in a sentence. That asymmetry is where value erosion often begins. When a team is described as one that can execute, ask one question. Execute what? Execute the stage the company is in now, or the stage the plan is taking it to? Those are usually different organisational demands. A team that executed well at Series B can be structurally unready for what Series C requires. Not because the team lacks ability, but because it was only read against the last stage, not the next one. The financial model is always tested against the plan. The team rarely is. So here is the test. At your next investment committee, when you hear that a team can execute, ask what they are being asked to execute. Then ask whether anyone has assessed them against it. The answer tells you whether the diligence was structured, or inferred. #VentureCapital #PrivateEquity #DueDiligence #Management #Startups

Every hundred-day plan after a buyout rests on a single assumption: the operating system is intact. The assumption is rarely tested. Governance maturity is assumed. Decision flow is assumed. Leadership alignment is assumed. Role clarity between layers is assumed. The problem is not visible in month one. It compounds by month six. By the board meeting at month six, the question is no longer financial. It is operational. The diligence at month minus one was never designed to find what is now in the room. Execution slows without a visible cause. Escalations increase. Decisions revisit themselves. Leadership teams spend more time translating between functions than operating across them. None of these failures appear suddenly. They were already present in the system. The transition simply increased the load. A hundred-day plan without an instrument turns management into performance. The reporting cadence exists. The operating visibility does not. Financial visibility shaped the modern hundred-day plan. Operational visibility followed. The next layer is visibility into people architecture. That is what NexStep is building. #Business #PrivateEquity #DealSourcing #InvestmentCommittee

A document a board reads in fifteen minutes and discusses for an hour. That is the standard the people side of enterprise value has been missing. Most board reading on the people dimension arrives in one of two shapes. A long deck the board does not finish. A short summary the board cannot act on. Both fail for the same reason. They were not built to be read by a board. They were built by the function reporting up to the board, then translated. Translation is where the signal degrades. A board-grade document reads differently. It opens with the structural finding, not the activity. It separates what is working from what is not — and shows the cost of each. It names when intervention will matter most. It carries evidence, not assertion. It does not reduce the organisation to a single risk score. It does not rely on engagement averages. It does not report function metrics in isolation. Because none of them reflect how the organisation actually operates. What it presents instead is a structural read: Where the architecture holds. Where it is degrading. Where the cost of inaction will surface. And what the next ninety days, six months, and twelve months should produce. Fifteen minutes to read. An hour of board discussion. The first item on the agenda, not the last. The people side of enterprise value has rarely had a document at this standard. We call it the Board Pack. #CorporateGovernance #BoardofDirectors #AuditCommitee #RiskManagement