Why Identity Risk Loses the Budget Conversation

 

By Navneet Lounsberry

---

 

In May 2026, Verizon published the nineteenth edition of its Data Breach Investigations Report. For the first time in the report's history, stolen credentials lost the top spot as the leading initial access vector. Vulnerability exploitation climbed to 31 percent. Credential abuse dropped to 13 percent, down from 22 percent the year before.

I watched that finding travel through the market in about a week. Vendors repositioned. Analysts wrote it up. And somewhere in a budget review, a finance leader pulled up the headline and asked a reasonable question: if identity attacks are falling, why does the identity program need more money this year?

The security team in that room knows the answer. Verizon tracked credential abuse across the full breach chain, not just the front door, and found it present in 39 percent of breaches. The report also introduced a new pretexting category that absorbed some of what previously counted as credential abuse. The headline describes first contact. The 39 percent describes what attackers actually do once they arrive.

Knowing that answer and delivering it are two different skills. Most security teams have the first one. Fewer have the second. That gap explains more stalled identity programs than any technical shortcoming I have seen across twenty years of enterprise selling.

Why does identity security lose the budget conversation?

Identity security loses budget conversations because practitioners describe risk in architectural terms while executives allocate money in consequence terms. The technical description is correct. It simply does not answer the question the person holding the budget is actually asking.

A security architect says the organization runs password hash synchronization with a single Entra Connect server that sits outside the Tier 0 management boundary. Every word of that carries meaning. None of it tells a CFO what breaks, what it costs, or what happens if the company does nothing for another year.

This is not a communication failure in the soft sense. It is a translation failure with a measurable price. Programs that never get funded never reduce risk, and the exposure compounds quietly while the architecture documentation gets more accurate every quarter.

The identity bridge shows the problem clearly

The clearest example I know sits in almost every large hybrid environment: the connection between on-premises Active Directory and Microsoft Entra ID.

What is the identity bridge?

The identity bridge refers to the components that link on-premises identity to cloud identity. In most Microsoft environments that means Entra Connect synchronization servers, pass-through authentication agents, and Active Directory Federation Services where organizations still run federation.

Microsoft does not treat these components casually. Its own documentation classifies Entra Connect servers, AD FS, Entra application proxy, and Active Directory Certificate Services as Control Plane assets, the tier formerly called Tier 0, alongside domain controllers themselves. Microsoft recommends restricting administrative access to these servers to tightly controlled groups, denying NTLM authentication to the Entra Connect server, and hardening the platform to the same standard applied to the directory it serves.

The reasoning is direct. Entra Connect holds privileged access to both sides. It reads objects from Active Directory using a connector account and writes synchronized objects into Entra ID using a dedicated service account. In password hash synchronization deployments it reads Kerberos hash material from the directory. Anyone who controls that server controls the credentials of every synchronized account.

Why do attackers target the identity bridge?

Attackers target the bridge because compromising it converts a local foothold into complete access across both environments, and because the resulting access looks legitimate.

Golden SAML illustrates this better than any other technique. CyberArk Labs first described the attack in 2017. An attacker who obtains the private key of an AD FS token-signing certificate can forge authentication assertions for any user, in any role, against any application that trusts that federation service. The forged token validates correctly against the public key. Multifactor authentication does not apply, because no authentication actually occurs. Conditional Access policies do not apply for the same reason. The relying party cannot readily distinguish the forged assertion from a genuine one.

This is not theoretical. The threat actor behind the SolarWinds intrusion used exactly this technique in the wild, compromising SAML signing certificates and minting valid tokens to reach hosted resources including email. Mandiant documented the technique in further detail in 2021, and its researchers recently found that manual certificate rotation can silently leave active signing keys recoverable from Machine DPAPI, meaning organizations that believed they had rotated remained exposed.

Read that sequence carefully. An attacker who reaches one server bypasses every identity control the organization purchased, and does it in a way that generates authentic-looking activity.

Why does the bridge stay underfunded?

Here is where the commercial problem shows up. The technical case for protecting the identity bridge is overwhelming and publicly documented by the vendor itself. The work still does not get funded, for four reasons that have nothing to do with architecture.

• Nobody senior owns it. The sync server usually belongs to a Windows infrastructure team that reports through IT operations, not security. It sits between two org charts and appears fully in neither.
• No compliance framework names it. Auditors ask about MFA, access reviews, and privileged accounts. Few ask whether the synchronization server carries a Control Plane hardening standard, so the finding never appears on the remediation list that drives spending.
• It never fails loudly. A misconfigured firewall causes an outage. An underprotected sync server runs perfectly for years, right up until it does not.
• It has no business name. Executives fund things they can name. "Entra Connect hardening" is not something a board member can repeat to a peer.

That last point matters most. Budget follows narrative, and the identity bridge arrives without one.

How do you translate identity risk into business language?

Translation is a discipline, not a personality trait. Three moves do most of the work.

Name the consequence, not the mechanism

Executives do not need to understand token forgery. They need to understand what an attacker gains and what the organization loses.

Compare two descriptions of the same risk. The first: an attacker with administrative access to the AD FS server can extract the token-signing certificate and forge SAML assertions that bypass Conditional Access. The second: one compromised server lets an attacker log in as our CFO, from anywhere, without a password, and our multifactor investment does not stop it.

Both statements are true. Only one of them ends with someone asking what it would take to fix.

I want to be precise about what this is not. Translation does not mean simplifying until the claim stops being accurate, and it does not mean reaching for fear. Buyers eventually catch overstated risk, and the credibility loss outlasts the deal by years. The goal is to state the real consequence in the vocabulary of the person deciding.

Attach the risk to something leadership already funds

Unnamed risk competes badly. Risk attached to a funded priority competes well.

Nearly every enterprise currently runs a cloud migration, an ERP program, a merger integration, or a compliance deadline with executive attention behind it. The identity bridge sits underneath all of them. A migration that synchronizes identities into a cloud tenant depends entirely on the integrity of that synchronization. A defense contractor working toward CMMC assessment cannot demonstrate access control over systems where a single server undermines every access decision.

Framing the work as protecting an initiative the organization already committed to does something a standalone security request cannot. It moves the conversation from new spending to protecting existing spending, and those two conversations have very different success rates. I wrote about a related version of this dynamic in CMMC in the Plant, Not the PowerPoint, where compliance programs succeed or fail based on whether they touch operational reality.

Offer the smallest credible first step

Large identity programs stall because they ask for a decision proportional to their scope. Executives approve things they can reverse.

A hardening assessment of three servers is a decision someone can make in a single meeting. A three-year identity governance transformation requires a steering committee, a business case, and a budget cycle. The first one creates evidence that makes the second one easier to approve later.

This sequencing is not a sales technique. It reflects how organizations genuinely absorb change, and practitioners who understand it get more of their work funded than practitioners who insist on the complete program up front.

What buyers actually say when identity risk stalls

Certain objections repeat across industries. Each one signals a specific gap.

When a buyer says they already deployed MFA, they believe they solved the identity problem. They have not heard that token forgery and session theft operate downstream of authentication entirely.

When a buyer says they cannot explain this to their board, they are asking for language, not information. That request deserves a direct answer rather than more technical detail.

When a buyer says the sync server belongs to another team, they have identified an ownership gap that will block the work regardless of how strong the technical case becomes. Somebody has to resolve that before anything else moves.

When a buyer says nothing has happened yet, they are applying the reasonable heuristic that quiet systems are healthy systems. The identity bridge is specifically the place where that heuristic fails, and saying so plainly tends to land.

What this means for commercial teams in cybersecurity

I have spent my career on the commercial side of enterprise technology, at IBM, SAP, Manhattan Associates, UKG, and most recently in identity and access management consulting. The pattern I keep returning to is this: technical depth and commercial effectiveness are not competing skills, and the strongest people in identity security refuse to choose between them.

The sellers who consistently win complex identity deals do not win because they know more about Kerberos than their competitors. They win because they can hold an architecture conversation with a security engineer at nine in the morning and a consequence conversation with a CFO at two in the afternoon, without changing the underlying facts between those two meetings.

That second conversation is where most identity programs live or die, and it receives a fraction of the preparation the first one gets. For anyone building a career in this market, the translation skill compounds faster than any product certification.

That translation skill sits alongside the rest of the commercial toolkit. Full Throttle Media covers the adjacent territory in B2B Displacement Campaigns: Win Competitor Customers, which works the same problem from the account strategy side.

Frequently asked questions

Is the identity bridge only a Microsoft problem?

No. Microsoft environments make it most visible because Entra Connect and AD FS are widely deployed and well documented. Any organization that synchronizes or federates identity between an on-premises directory and a cloud provider carries the same structural exposure, including those running third-party identity providers alongside a legacy directory.

Does multifactor authentication protect against Golden SAML?

No. Golden SAML forges the authentication assertion itself, so the authentication event never occurs in a form that MFA or Conditional Access can evaluate. Protecting against it requires securing the federation infrastructure, controlling and monitoring token-signing certificates, and auditing certificate export and configuration changes.

How should an organization prioritize the identity bridge against other security work?

Prioritize it by blast radius rather than by likelihood. Most security findings expose one system. A compromised synchronization or federation server exposes every synchronized identity across both environments simultaneously, which places it in the same category as a domain controller.

What is the first question a security leader should ask about hybrid identity?

Ask who administers the synchronization and federation servers, and whether those administrators use the same accounts and workstations they use for ordinary IT work. The answer reveals whether the organization treats the bridge as a Control Plane asset in practice or only in documentation.

Did identity risk actually decline in 2026?

The 2026 Verizon DBIR showed credential abuse falling as an initial access vector, partly because a new pretexting category absorbed some incidents previously counted as credential abuse. Across the full breach chain, credential abuse still appeared in 39 percent of breaches. Attackers changed how they get in more than they changed what they do afterward.

The work is a translation problem

The identity bridge deserves attention on its technical merits, and the vendor documentation, the threat research, and the incident history all say so clearly. None of that has been enough on its own, which tells us something worth taking seriously.

Security programs do not fail only because teams miss the risk. They fail because the people who see the risk most clearly describe it in a language the people holding the budget do not speak. That is a solvable problem, and solving it does not require anyone to dilute the technical truth. It requires naming consequences, attaching risk to priorities the organization already values, and asking for a first step small enough to approve.

 

---

About the Author

Navneet Lounsberry brings over two decades of enterprise sales and business development experience across IBM, SAP, Manhattan Associates, UKG, and Idenhaus Consulting, where her work spanned identity and access management and cybersecurity compliance, including CMMC. A Georgia Tech graduate, she writes about how enterprise buyers in regulated industries actually evaluate, procure, and operate compliance programs.

 

 

Copyright © 2026, Full Throttle Media, Inc. FTM #fullthrottlemedia #inthespread #sethhorne

CMMC in the Plant, Not the PowerPoint: Finding CUI Where Manufacturers Least Expect It

 

By Navneet Lounsberry

---

A tier-two precision machine shop with 80 employees and an aerospace prime customer sits down for a pre-assessment scope review. Leadership is confident. Controlled Unclassified Information (CUI) lives on the engineering file server, access is restricted to five engineers, email runs through a GCC High tenant. The team believes it is ready.

The assessor walks the floor. Within an hour, CUI has been found on a shared tablet at a first-article inspection station, on two CNC human-machine interface (HMI) screens displaying PDF drawings, in a print spool queue on an unmanaged network printer, in the scheduler's email inbox where traveler sheets quote controlled dimensions verbatim, and on a USB drive in a machinist's toolbox. Scope expands from 12 workstations to more than 60 devices. The assessment is pushed back six months while remediation catches up. The budget triples.

This scenario is a composite drawn from patterns I have watched recur across defense manufacturing environments, not a single client. It is what Certified Third-Party Assessor Organizations (C3PAOs) report seeing over and over. C3PAOs are required to validate CUI asset identification independently, not to accept engineering's initial scope at face value, which is why the plant walk carries the weight it does. The underlying issue is not a defensive posture problem. It is a scoping problem, and it is solvable. The catch is that scoping has to be addressed before the plant walk, not during it.

Why CMMC Scoping Is the Whole Game for Manufacturers

Phase 2 of the Cybersecurity Maturity Model Certification (CMMC) rollout begins November 10, 2026. Starting on that date, third-party C3PAO Level 2 assessments are expected to be required in most new Department of Defense contracts involving CUI, driven by the applicable DFARS clauses and individual solicitations. This is no longer a future planning exercise. Prime contractors including Lockheed Martin, Boeing, RTX, General Dynamics, and BAE Systems are already issuing supplier notices, portal-based questionnaires, and flow-down packages. The pressure reaching tier-two and tier-three manufacturers is coming from the top of the supply chain, not from the DoD directly.

Assessor capacity is the compounding factor. Industry estimates place the number of Certified CMMC Assessors in the hundreds against an affected contractor base of roughly 300,000, with reported C3PAO backlogs of six to twelve months. A failed or delayed assessment does not just generate remediation costs. It pushes an organization back into a queue that is only growing.

Scope determines the economics of certification. Published case data on a 40-person defense manufacturer documents total first-year investment dropping from roughly $140,000 under an enterprise-wide approach to about $78,000 when scope was architected through a properly segmented enclave, a 45 percent reduction on identical compliance obligations. C3PAO assessment fees alone range from approximately $15,000 for a tightly scoped enclave to more than $100,000 for a sprawling full-organization boundary.

Here is the trap most manufacturers walk into: overscoping and underscoping both fail, for different reasons. Overscoping commits the organization to implementing all 110 NIST SP 800-171 Rev. 2 controls (currently incorporated by reference in 32 CFR 170 as the CMMC Level 2 control baseline, despite being superseded by Rev. 3 in the NIST publication series) across systems that never needed them, inflating cost and stretching the timeline past what primes will wait for. Underscoping leaves gaps that a C3PAO will challenge during pre-assessment, pushing the organization back into the same assessor queue. Recent CMMC FAQ revisions, including Revision 2.2, have focused heavily on correcting common scoping errors surfacing in live assessments.

Scope is architected, not described. That architectural work is what separates manufacturers who certify on schedule from those who keep slipping.

Where Does CUI Actually Live in a Manufacturing Environment?

The short answer: in many more places than engineering thinks. The long answer requires walking the plant.

Most defense manufacturing CUI falls under the Controlled Technical Information (CTI) category in the official CUI Registry. CTI includes drawings, three-dimensional CAD models, specifications, geometric dimensioning and tolerancing data, bills of materials, and manufacturing process documents. These are typically marked with DoD Distribution Statements B through F. For most tier-two and tier-three manufacturers, the highest-volume CUI exposure is customer-supplied technical data arriving from a prime contractor or original equipment manufacturer.

That data does not stay where engineering puts it. It follows the part.

The Shop Floor Itself

Assessors consistently cite shop floor CUI exposure as the single most common finding category in manufacturing assessments. The patterns repeat across facilities. Technical drawings display on CNC HMIs at the point of operation. Unencrypted tablets travel between inspection stations with first-article specifications loaded as PDFs. Printed specifications sit unsecured near machining centers. Job travelers ride with parts through the plant, quoting controlled dimensions in plain text. Setup books in machinist toolboxes hold copies of drawings. These are not exotic edge cases. They exist in nearly every defense manufacturing environment because they serve legitimate operational needs.

MES, ERP, and Quality Systems

The manufacturing execution system sits at Purdue Enterprise Reference Architecture Level 3 and routinely holds statistical process control data tied to specific controlled dimensions, first-article inspection records, and nonconformance documentation that references the original drawing. Enterprise resource planning platforms common in the defense supply chain, including Epicor, Plex, Infor, JobBOSS, IQMS, and E2, hold work orders, routing sheets, customer purchase orders, and scheduling records derived from the drawing package. Coordinate measuring machine programs and inspection plans derived from CTI carry the same sensitivity as the source drawing.

Controllers, Programs, and Removable Media

Engineering drawings get translated into G-code and programmable logic controller logic that can embed controlled dimensions, tolerances, and process parameters derived from CTI. USB drives used to move programs from engineering to the machine are ubiquitous in manufacturing and almost always in scope.

The Overlooked Digital Corners

Email archives between the company and the prime often contain the original RFQ attachments, and those attachments frequently include the full technical data package. OneDrive and Dropbox profile sync can silently replicate CUI from an endpoint to cloud services that lack FedRAMP authorization. Under DFARS 252.204-7012, cloud services handling CUI are required to meet FedRAMP Moderate baseline equivalency, which rules out most consumer-grade sync tools by default. Backup systems capture every CUI-bearing file on protected systems and become in-scope assets themselves. Managed service provider remote access tools that touch any CUI-handling endpoint pull the MSP into scope as a Security Protection Asset. The CEO's laptop, where the original RFQ attachment still lives months after award, belongs on the list as well.

Paper and Hybrid Workflows

The DoD clarified in CMMC FAQ Revision 2.2 that pure paper workflows do not by themselves trigger a CMMC assessment, but the moment paper CUI is scanned, photographed, emailed, uploaded, or printed from a system, that system enters scope. Hybrid paper-digital handling is the manufacturing norm, which means most paper CUI conversations eventually become digital CUI conversations.

When manufacturers map their CUI footprint for the first time, most discover it is three to five times larger than they assumed.

Legacy OT, IT Convergence, and the Specialized Assets Lever

The fear among manufacturers with older equipment is that a 2003-vintage programmable logic controller or an unpatchable supervisory control and data acquisition server automatically fails CMMC Level 2. That is not how the framework actually works.

Per 32 CFR 170.19(c)(1) Table 3, the CMMC Scoping Guide defines a category called Specialized Assets. It covers operational technology (PLCs, SCADA, HMIs, building management systems, physical access control panels), Internet of Things and Industrial Internet of Things devices, Government Furnished Equipment, Restricted Information Systems, and Test Equipment. The critical mechanics: Specialized Assets are part of the CMMC Assessment Scope, but they are not assessed against the full set of 110 NIST SP 800-171 controls. The organization must inventory them, document them in the System Security Plan (SSP), show them on the network diagram, and detail how they are managed under risk-based security policies. The assessor verifies the documentation and may perform a limited spot check if it is insufficient.

This is the legacy industrial control system lifeline. Older equipment that cannot support multifactor authentication, modern patching, or endpoint detection can coexist inside a compliant environment when properly categorized with specified compensating controls.

The trap is assuming the label alone is sufficient. Assessors require justification for Specialized Asset designation, not just the designation. If an unpatched PLC shares a VLAN with the CUI file server, the designation fails because the asset has unrestricted access paths to CUI.

The Purdue Enterprise Reference Architecture gives the organizing framework for this scope decision. Levels 0 through 3 cover the OT side (sensors and actuators, controllers, supervisory HMIs, MES and historians). Levels 4 and 5 cover IT (ERP, enterprise networks). A Level 3.5 Industrial Demilitarized Zone sits between them. For most manufacturers, the IDMZ is where the CMMC boundary should be drawn, with the OT side documented as Specialized Assets and the IT side treated as the CUI enclave.

Compensating controls that hold up in assessment include network segmentation with an IDMZ between IT and OT, identity-based microsegmentation overlays for environments where traditional VLAN segmentation cannot be fully retrofitted, data diodes for one-way telemetry flows out of OT, jump boxes with session recording for vendor remote access, and documented program transfer procedures that log and approve every file movement from engineering to the controller. Vendor remote access matters especially because Dragos reporting indicates that the majority of OT attacks, often around three-quarters of observed incidents, begin as IT breaches.

Practical CMMC Scoping Tactics That Actually Work

Four tactics do most of the work.

Start With Data Flow Mapping, Not the SSP

Most manufacturers write SSP narratives before mapping actual CUI flow. The result is documentation that drifts from reality the moment it is filed. The correct order is to map the flow first, classify assets against the five CMMC asset categories, and then write the SSP to match. Under NIST SP 800-171, organizations are explicitly required to identify where CUI is processed, stored, and transmitted. Data flow mapping is how that identification gets done with evidence behind it.

The workshop method that produces defensible results is a "book to bill" walkthrough, tracing one representative contract from arrival of the drawing package through production, shipment, and invoicing. Cross-functional participation is not optional. Engineering, quality, production scheduling, operations, business development or contracts, and at least one shop floor supervisor need to be in the room. Single-department mapping exercises commonly miss 40 to 60 percent of the actual CUI flows. The workshop should produce durable evidence artifacts, including annotated data flow diagrams, meeting notes, asset inventories, and categorization rationale, all of which can be reused during the C3PAO assessment to demonstrate how scope was derived.

Use the Enclave Strategy to Shrink Scope

An enclave is a logically or physically segmented environment where CUI is processed, stored, and transmitted, treated as a distinct CMMC Assessment Scope separate from the rest of the organization. The DoD explicitly recognizes this approach in the Program Rule. Published cost reductions versus enterprise-wide compliance range from 20 to 45 percent across documented case studies.

Architect the Right Kind of Enclave for a Real Plant

This is where marketed cloud enclaves often fail manufacturers. A pure cloud virtual desktop infrastructure enclave, the pattern sold to five-person engineering firms, does not survive contact with a real machine shop. Drawings have to reach CNC workstations at the point of operation. The architecture that works for manufacturers is hybrid:

• A cloud enclave, typically Microsoft GCC High or Azure Government, for email, document collaboration, contract management, and most knowledge-worker CUI handling. This layer inherits the bulk of the 110 controls through FedRAMP-authorized infrastructure.
• A hardened on-premise CUI segment for engineering workstations and the controlled-drawing path to the floor. This layer focuses on segmentation, access control, and physical security for the narrow path from engineering to production.
• An IDMZ separating the CUI environment from the OT network where PLCs, CNCs, and MES terminals operate as documented Specialized Assets.

Apply Scope-Limiting Levers That Hold Up Under Assessment

Several structural decisions consistently reduce scope without creating assessment risk:

• Separate commercial and DoD business units behind identity and network boundaries. If only certain programs handle CUI, other programs can stay out of scope entirely.
• Exclude departments that do not require CUI access, including most of finance, HR, sales, and marketing.
• Put operational technology on dedicated VLANs behind an IDMZ, with documented justification in the SSP.
• Use dedicated hardware for CUI handling, with no BYOD and no corporate Wi-Fi in scope for the CUI segment.
• Where possible, replace printed drawings on the floor with role-based access on viewer-only tablets.
• Establish removable media procedures with logging for the moments when physical transfer to a machine is unavoidable.

Why the SSP Has to Match What Is Actually Happening on the Floor

The SSP, network diagram, data flow diagram, and asset inventory are living documents, not filing cabinet artifacts. The 48 CFR final rule introduced a continuous compliance obligation and an annual affirmation requirement signed by a senior company official. Configuration Management is one of the 14 NIST 800-171 control families, with nine Level 2 practices dedicated specifically to tracking and approving change.

Manufacturing environments make this unusually difficult. New work cells come online. New CNCs get installed. ERP modules get added. Vendor technicians plug laptops into HMIs for diagnostics and leave behind connections no one documents. Contract machinists get onboarded for a rush job with access to the engineering share. Kaizen events reorganize physical layout every quarter. Each of these is a potential scope change, and most manufacturers have no process connecting operational changes to scope documentation.

The practical fix is a cadence paired with a trigger list. A quarterly scope review catches drift, and a defined trigger list forces immediate re-examination whenever any of the following occurs:

• A new contract involving CUI
• A new supplier receiving technical data
• A new hire with CUI access
• New hardware on the floor
• A new cloud service adopted anywhere in the organization
• A merger, acquisition, or significant reorganization

A lightweight change-impact workflow routes these events through a security review before they hit production.

The False Claims Act overlay elevates the stakes meaningfully. Annual affirmations now carry potential FCA liability. Submitting an affirmation against an SSP that no longer matches reality is not just an assessment risk. It becomes a legal risk the moment the senior official signs. Multiple leading defense-contractor law firms have published alerts on this point. The reframe that matters for executives: SSP maintenance is not a compliance chore, it is executive risk management that belongs on the general counsel's radar.

How Does CMMC Flow-Down Affect a Manufacturer's Scope?

A clean internal scope is not sufficient if CUI leaves the building through uncontrolled channels. Flow-down is driven by the data type shared, not by the prime's certification level. If a prime shares Federal Contract Information (FCI) with a subcontractor, that subcontractor needs Level 1. If a prime shares CUI, the subcontractor needs Level 2. The same logic applies when a manufacturer shares CUI with its own sub-tier suppliers.

Primes cannot see subcontractor SPRS certification status directly. They rely on supplier portals, the Cybersecurity Compliance and Risk Assessment questionnaire, and annual attestations to verify compliance. For a manufacturer sitting in the middle of the supply chain, this means the scoping exercise has to extend outward. A heat-treat vendor, a coating supplier, or a specialty machining house receiving the same drawing package is part of the scope conversation.

Practical implications: route supplier file sharing through secure portals rather than email, include CUI handling requirements in subcontract language, and maintain documented flow-down verification for every supplier that receives technical data. Flowing CUI to a sub-tier supplier carries an obligation to verify that supplier's ability to protect it, which means contract clauses, attestations, and documented verification records are part of your own scoping evidence, not just theirs. A manufacturer with a locked-down internal scope can still fail a prime contract review because of how it shares CUI with its own subs.

Frequently Asked Questions About CMMC Scoping in Manufacturing

What is Controlled Unclassified Information (CUI) in a manufacturing context?

In defense manufacturing, CUI most often takes the form of Controlled Technical Information (CTI): drawings, CAD models, specifications, GD&T data, BOMs, and manufacturing process documents supplied by a prime contractor or OEM, typically marked with DoD Distribution Statements B through F. Derived records, including work orders, routing sheets, and inspection plans that quote controlled dimensions, carry the same sensitivity in practice.

When does CMMC Level 2 certification become mandatory for manufacturers?

Phase 2 of the CMMC rollout begins November 10, 2026. On that date, third-party C3PAO Level 2 certification becomes a mandatory award condition for most new DoD contracts involving CUI. Full implementation across all applicable contracts is scheduled for November 10, 2028, but most manufacturers will face the requirement well before then as primes flow down requirements on new awards.

Do legacy PLCs and CNC machines automatically fail CMMC Level 2?

No. The CMMC Scoping Guide creates a Specialized Asset category for operational technology, IoT and IIoT, Government Furnished Equipment, Restricted Information Systems, and Test Equipment. These assets are in scope but are not assessed against the full 110 NIST SP 800-171 controls. They must be inventoried, documented in the SSP, shown on the network diagram, and managed under documented risk-based policies with appropriate compensating controls such as network segmentation.

Does encrypting CUI take a system out of CMMC scope?

No. Encryption reduces risk during transmission and at rest, but it does not remove a system from scope. If a system processes, stores, or transmits CUI, it is a CUI Asset regardless of whether the data is encrypted. Cloud services that handle CUI must meet FedRAMP Moderate baseline requirements per DFARS clause 252.204-7012.

How much does CMMC Level 2 certification cost for a small manufacturer?

Costs vary widely by size, existing security maturity, and scope architecture. Published benchmarks for small and mid-sized manufacturers commonly fall between $75,000 and $150,000 for total first-year investment, with properly scoped enclave approaches coming in 20 to 45 percent below enterprise-wide approaches for comparable organizations. C3PAO assessment fees alone range from approximately $15,000 for a tightly scoped enclave to more than $100,000 for a sprawling full-organization boundary.

What is the difference between overscoping and underscoping?

Overscoping includes systems and users that do not need to be in the CMMC boundary, which inflates the cost of implementation, lengthens the assessment timeline, and commits the organization to controls on systems that never required them. Underscoping omits systems that actually handle CUI, which assessors will challenge during pre-assessment and force the organization to expand scope on the spot, often delaying certification by months. Both failure modes cost more than right-sized scope architected from the start.

What is a CUI enclave and why does it matter?

A CUI enclave is a logically or physically segmented environment where CUI is processed, stored, and transmitted, treated as a distinct CMMC Assessment Scope separate from the rest of the organization. The enclave approach is explicitly recognized in CMMC guidance and is the most effective lever for reducing assessment scope, assessment cost, and ongoing compliance burden without sacrificing security posture. For manufacturers, a hybrid enclave combining cloud collaboration (GCC High or Azure Government) with a hardened on-premise CUI segment typically fits the physical realities of a shop floor better than a pure cloud VDI approach.

The Bottom Line: Walk the Plant Before an Assessor Does

The manufacturers who will certify cleanly in the twelve to eighteen months leading up to Phase 2 are the ones catching the tablet, the print queue, the scheduler's inbox, and the USB drive before a C3PAO does. The work is not a compliance audit. It is a plant walkthrough with a different set of questions.

A Practical Starting Checklist

1. Map every CUI entry point, including prime portals, email, physical mail, removable media, and vendor handoffs.
2. Trace one representative contract from book to bill. Walk it physically. Note every system and location the drawing touches.
3. Inventory every device and location where controlled technical data appears, including tablets, HMIs, printers, toolboxes, and vehicles.
4. Categorize against the five asset types (CUI, Security Protection Asset, Contractor Risk Managed Asset, Specialized, Out of Scope) before writing a line of SSP narrative.
5. Test the boundary. If an assessor walked the floor tomorrow, what would they see that leadership did not?

Why Getting Scope Right Now Is a Competitive Decision

Three realities drive the timing. Phase 2 certification becomes mandatory November 10, 2026. C3PAO capacity is already constrained, with reported backlogs of six to twelve months. Primes are actively filtering their supply chains right now, not waiting for the deadline.

Manufacturers who architect scope correctly in the next year gain structural advantage: earlier certification, faster prime qualification, and stronger position in contract negotiations. Those who do not will be waiting in the assessor queue while their certified competitors take their work. Scope is not a paperwork exercise. It is the decision that determines whether certification is achievable on the timeline the market is already enforcing.

---

About the Author

Navneet Lounsberry brings over two decades of enterprise sales and business development experience across IBM, SAP, Manhattan Associates, UKG, and Idenhaus Consulting, where her work spanned identity and access management and cybersecurity compliance, including CMMC. A Georgia Tech graduate, she writes about how enterprise buyers in regulated industries actually evaluate, procure, and operate compliance programs.

Copyright © 2026, Full Throttle Media, Inc. FTM #fullthrottlemedia #inthespread #sethhorne

SEO, AEO, and GEO: Three Layers, One Strategy

Search visibility in 2026 is not a single-channel problem. It never really was, but the proliferation of AI-powered answer surfaces has made that reality impossible to ignore. You now have to be findable in traditional search results, structured to deliver direct answers, and authoritative enough to be cited by generative AI platforms. Three different objectives. Three distinct execution requirements. One underlying standard.

 

That is the framework. SEO is the foundation. AEO is the answerable layer. GEO is the citation layer. They are not competing disciplines or sequential phases of a roadmap. They are interdependent, and neglecting any one of them creates a gap the others cannot cover.

What each layer actually does

SEO: The infrastructure layer

SEO governs how search engines crawl, index, and rank your content in traditional results. Technical health, page speed, mobile performance, internal linking, and on-page optimization all live here. Without a structurally sound website, every other layer fails. AI crawlers use the same sitemaps and site architecture that traditional bots have relied on for years. If the foundation is weak, the rest of the strategy collapses.

This is not a legacy concern. From Google's own perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO. Google published an official guide on May 15, 2026 titled "Optimizing your website for generative AI features on Google Search," and its central argument is that the same fundamentals driving organic visibility are the same fundamentals driving AI feature inclusion. The technical mechanism behind this is retrieval-augmented generation (RAG), the process by which Google's AI features retrieve relevant indexed pages and generate responses based on that content. If your pages are not crawlable and indexed, they cannot be retrieved, no matter how well-written they are.

AEO: The answer layer

Answer Engine Optimization is the process of optimizing content so that search engines and AI-powered assistants can quickly extract and display answers to user queries. Unlike traditional SEO, which focuses on ranking web pages, AEO ensures that your content is structured for immediate retrieval in featured snippets, knowledge panels, and voice search results.

The goal of AEO is not to rank. It is to own the answer. This applies across the entire customer journey, from early awareness questions ("what is programmatic advertising?") through final decision-stage queries ("which ad platforms work best for B2B?"). The zero-click nature of these results adds complexity to measuring success. Traditional traffic metrics need to be expanded. With AEO, success measurements focus on visibility within AI-generated responses and brand authority establishment through citations.

GEO: The citation layer

Generative Engine Optimization addresses being cited by AI models like ChatGPT and Perplexity. If traditional SEO gets people to your content, AEO and GEO get your content into the conversation, even when there is no traditional click.

GEO operates across platforms that are not search engines in the traditional sense, and their citation behaviors differ meaningfully. Google's AI Overviews draw from pages already ranking in its index, making SEO strength a prerequisite. Perplexity integrates real-time web search and tends to favor recent, well-sourced content with clear provenance. ChatGPT's citation behavior weights authoritative, well-structured sources with verifiable factual claims. Optimizing for one does not automatically transfer to the others, but authoritative, clearly structured content is the shared requirement across all three.

AI Overviews now appear on more than half of all Google searches, used by over 2 billion monthly users globally. That scale makes GEO a practical business concern, not a theoretical one.

Why they cannot function independently

The mistake most content teams make is treating these three layers as separate workstreams with separate budgets and separate metrics. The result is disconnected execution: technical SEO that is solid but content not structured for extraction, or content formatted for snippets that lacks the credibility signals generative platforms use to decide what gets cited.

SEO makes your content accessible. AEO makes it answerable. GEO makes it citable. A brand that executes well across all of these layers does not need to game any individual one. The combined signal is strong enough that AI systems surface it naturally.

A page that cannot be crawled will never appear in a featured snippet. A page that appears in a featured snippet but lacks depth, original data, or first-hand perspective is unlikely to be cited in a generative AI response. The layers build on each other sequentially, but they also reinforce each other. It also helps to understand the technical reason: Google's AI systems use query fan-out, generating multiple related queries from a single user input to retrieve comprehensive answers. Content that covers a topic with genuine depth satisfies more of those derived queries, which increases the likelihood of citation in the synthesized response.

What Google's official guidance actually tells you

Google's official guide confirmed that traditional SEO remains the foundation for AI Overviews and AI Mode, while original content, accessibility, semantic structure, and authority become even more central in the era of generative search.

The guide also includes a section worth reading carefully if you are paying for specialist AEO or GEO retainers. Google explicitly debunked various optimization tactics as unnecessary for generative AI search, including the use of llms.txt files, content chunking, AI-specific rewriting, seeking inauthentic brand mentions, and implementing special structured data.

Reducing AEO and GEO to "just SEO" is also a convenient way for Google to avoid acknowledging that generative search introduces new layers of complexity not fully covered by traditional SEO, such as knowledge graph management, entity optimization, and AI citation analysis. That caveat matters. Google's guidance is authoritative for Google's own surfaces. The other major platforms operate different systems and their signals are not fully public.

The practical read: what Google says to stop doing is sound advice for Google. What drives citation across all generative platforms is authoritative, structured, genuinely useful content with a clear point of view.

The shared editorial standard across all three layers

SEO, AEO, and GEO all rely on the same underlying principles: understanding user intent and providing high-quality, relevant content applied to different endpoints. The tactical execution differs by layer, but the editorial standard is the same.

That standard has specific characteristics in practice:

• Depth over volume. A single comprehensive page on a topic outperforms a cluster of thin pages on related subtopics at every layer simultaneously.
• Original perspective. Google's guide introduces the concept of non-commodity content, meaning content with unique perspectives, original data, and direct experience, as a differentiating factor in the era of generative search. This applies equally to GEO citation logic across all platforms.
• Structural clarity. Clear headers, logical section organization, and direct answers at the top of sections improve crawlability, extractability, and citability in a single pass.
• Entity precision. Ensuring your brand, products, and key concepts are well-defined entities with consistent representation across your site and authoritative third-party sources strengthens how knowledge graphs associate you with relevant topics.

If you are already thinking about why AI-generated content is losing its early ranking advantage, you understand the underlying issue. The platforms are getting better at identifying commodity content, and the bar for what gets surfaced across all three layers is rising together.

A practical integration approach

There is no point running three separate optimization programs when the underlying editorial standard is the same. The integration work is largely structural:

• Run a technical audit first. Crawl errors, page speed issues, and mobile performance problems undermine every layer. Fix them before investing in content.
• Structure every piece of content to answer a question directly in the opening section. This serves both AEO and GEO without requiring separate rewrites.
• Build content depth around core topics your business has genuine experience with. First-hand perspective is what separates citable content from generic content across all generative platforms.
• Measure citation frequency alongside traditional traffic and ranking metrics. The AEO and GEO measurement ecosystem now includes platforms like Peec AI, Profound, and Semrush's AI Visibility Toolkit, which track citation frequency, brand mentions, and share of voice across AI surfaces.

FAQ: SEO, AEO, and GEO

Are AEO and GEO just versions of SEO? Google's official position is yes, for its own platforms. The foundational requirements are the same. The difference is execution emphasis and measurement. AEO focuses on answer extraction. GEO focuses on citation by generative systems. Both depend on solid SEO infrastructure to function at all.

Do I need a separate strategy for each layer? No. You need a unified editorial standard and targeted execution adjustments by layer. Content that is authoritative, well-structured, and factually precise performs across all three. The execution differences are tactical, not strategic.

What tactics should I stop using? According to Google's official guide: llms.txt files, content chunking for AI, AI-specific rewrites, and inauthentic mention campaigns. For platforms outside Google, the guidance is less definitive, but none of these tactics have demonstrated reliable citation impact on any major generative platform.

How do I measure GEO and AEO performance? Citation frequency, share of AI voice relative to competitors, and brand search volume trends are the core GEO and AEO metrics. Tools like Semrush's AI Visibility Toolkit, Profound, and Peec AI now provide citation tracking across Google AI Overviews, ChatGPT, and Perplexity. These metrics measure brand authority exposure, not just clicks, and that distinction matters for how you report ROI.

What is the most important thing to get right across all three layers? Non-commodity content. Original perspective, direct experience, and factual precision are the shared requirements. If your content could have been written by anyone without direct knowledge of the subject, it will underperform across every layer.

The framework is more coherent than it looks

Three layers, one editorial standard, one integrated execution. A consulting category has grown up around the premise that AI search requires a different methodology. Google's guide undercuts that premise on its own platform.

That does not mean execution is easy or that the layers are interchangeable. Each has distinct measurement requirements, distinct formatting considerations, and distinct technical dependencies. But the strategic foundation is unified, and that matters for how you resource, plan, and report on your content program.

The businesses that maintain visibility as AI-powered search continues to expand are not the ones with the most sophisticated AEO or GEO programs. They are the ones with the most authoritative content on the subjects they know best. The three layers surface that authority. They do not manufacture it.

 

Copyright © 2026, Full Throttle Media, Inc. FTM #fullthrottlemedia #inthespread #sethhorne

Why "we don't use AI" is a Losing Business Strategy

What happens to a business that makes a values decision inside a market that does not share those values? That is the real question worth sitting with, because the "human-powered" business owner is not making a technology decision. They are making a strategic one, and most of them have not fully thought through what it costs.

The owner who says "we don't use AI" is usually not unintelligent or stubborn. They built something real with their hands, their relationships, and their expertise. Keeping AI out of their business feels like protecting what they built. It is a values statement wrapped around an operational choice, and the two have become deeply confused with each other.

That confusion is what is going to cost them. The market does not care about the distinction, and neither do their competitors. The businesses building with AI tools today are not replacing their expertise with algorithms. They are compounding their output, lowering their overhead, and getting in front of more buyers before the first call is ever made. If you want to understand why your content needs to be part of that system, the piece on optimizing content for AI search and generative engines lays out exactly what is at stake for visibility in the current environment. Read it alongside this one, and the picture gets sharper.

 

Where this resistance actually comes from

If you have said "we are a human powered business" or "I want everything we produce to be human written," the logic probably felt airtight at the time. Your credibility comes from real experience. Your clients hired you because of your judgment, not because you have the fastest pipeline or the most automated workflow. The idea that a tool could shortcut any of that feels like it cheapens the whole thing.

That feeling is rooted in something real, which is precisely why it is dangerous. Research on professional identity and technology resistance shows that when a tool begins performing tasks previously associated with deep human expertise, it triggers what researchers call an identity threat. The resistance is not strategic. It is psychological. And psychological resistance dressed up as principle tends to survive far longer than it should, because it feels like integrity when it is actually inertia.

There is also a simpler driver that does not get enough credit: genuine uncertainty. According to Service Direct's 2025 research, 62% of non-adopting small businesses cite a lack of understanding about what AI can actually do for their specific operation as the primary reason for staying out. That is not ideology. That is an education gap masquerading as a position. Most of the business owners holding the "human only" line are not ideologically opposed to efficiency. They simply do not know what the tools would actually do in their context, and uncertainty produces caution that hardens over time into refusal.

The authenticity argument is the third pillar, and it has the most legitimate surface logic. Human-produced work carries a signal that AI-produced work does not, particularly in professional services where trust is the actual product. This is worth taking seriously, because it is partly true. Where it breaks down is the moment "authenticity" becomes a reason to avoid adoption entirely rather than a standard for how to use tools intelligently. Those are completely different positions with completely different consequences.

The category error driving the whole argument

The "human-powered" case collapses the moment you identify what the business owner is actually trying to protect. The business owner who refuses AI is protecting the wrong thing. Their credibility, their client relationships, their domain expertise. These are the product. None of them are threatened by using AI as a production tool. The confusion comes from treating the source of value and the mechanism of production as the same thing, which they are not.

Think about a cinematographer. The craft is in what they see, how they frame a shot, what story they are telling. It lives in the decisions they make, not in the mechanics of capture. A cinematographer who refuses to shoot on digital to preserve the artisanal quality of film is making an aesthetic choice that has no relationship to the actual quality of their vision. Nobody questions whether a film shot digitally represents genuine human artistry. The tool does not contaminate the craft.

The same logic applies to a service business using AI tools to draft, structure, research, or distribute. When a management consultant uses AI to synthesize research and structure an argument, the insight is still theirs. The strategic judgment, the industry context, the ability to read a client's real problem beneath the stated one. That is the product. The AI handled scaffolding. The expertise did the actual work. Conflating the two is a category error, and it is one that costs real money over time.

The question worth asking is not "did a human write every sentence?" The right question is "does this output accurately represent genuine expert thinking, and does it serve the client?" Those are not the same question, and the first one is far less important than business owners who hold this position tend to believe.

Two flanks of the same competitive erosion

The competitive damage from refusing AI adoption runs on two tracks simultaneously. Most business owners who think about this at all tend to think about only one of them: the operational track. They should be thinking about both, because they compound each other.

The operational gap, and why it widens every quarter

The data on revenue divergence between AI adopters and non-adopters is stark. Small business owners who invest in AI are nearly twice as likely to report year-over-year revenue growth, according to a 2025 industry analysis by Service Direct. In a Google Cloud-commissioned study of more than 2,500 C-suite leaders, 86% of early generative AI adopters reported revenue increases exceeding 6% annually. That number compounds. A business running flat while competitors compound 6% annually is getting smaller in real terms every single year, even if the owner does not feel it yet.

This plays out across four interconnected layers:

• Consumer expectations have been permanently recalibrated. Clients and prospects interact with AI-enabled businesses every day. Response speed, personalization, and availability have shifted as a result. The human-powered business is no longer competing on intimacy. It is competing on dimensions where it is structurally slower, and losing ground it may not even know it is losing.
• The baseline itself keeps rising. This is the part that most analysis misses. Even businesses adopting AI right now are only reaching baseline, not competitive advantage. The non-adopter is not behind the leaders. They are behind a standard that keeps moving. Opting out of infrastructure is a different category of decision than it looks like.
• The cost structure gap compounds exponentially. AI-enabled competitors are doing the same volume with fewer staff hours. According to IDC research, organizations lose 20 to 30% of annual revenue to operational inefficiencies that AI systematically eliminates. That gap does not stay constant. It widens as adopters refine their systems and the non-adopter's overhead stays fixed.
• The talent market moves toward AI-forward organizations. Skilled professionals calibrate toward businesses building with modern tools. As AI adoption among operating organizations reaches the high 70s percentile in survey data, the best candidates are choosing employers who invest in the tools that make their work more productive. The business that holds the "human only" line can quietly develop a people problem, which is the ultimate irony: the stance meant to honor human work ends up degrading the quality of the humans the business can attract.

Strategy from someone with skin in the game

Don't let your competitors read this twice before you act on it once.

Full Throttle Media covers content strategy, digital marketing, and B2B sales from the ground level of businesses actually running these plays. No recycled frameworks. No agency spin.

Read More at Full Throttle Media

The buyer behavior problem most owners don't see coming

The second flank is less intuitive, and in some ways more damaging because it is invisible until it is not. Buyers across virtually every B2B category now use AI tools to research vendors, services, and competitive landscapes before they ever initiate human contact. They are querying ChatGPT, Perplexity, and Google's AI Overviews to understand who the credible players are in a space. They are getting synthesized answers drawn from content that has been published, structured for AI consumption, and indexed by systems that favor recency, authority, and depth.

If your content is not in that conversation, you are not in that consideration set. Not because a human dismissed you, but because an AI system had nothing to cite. The business that publishes sparingly, markets manually, and relies primarily on referrals is functionally invisible to a growing segment of its own addressable market. And that segment is not small. According to McKinsey's 2025 State of AI report, 88% of organizations now use AI in at least one business function. Buyers are AI-fluent. Their research process reflects that.

This is where the refusal to use AI for content production becomes self-defeating at a fundamental level. A consultant who refuses to use AI to produce articles, analyses, or explainer content because they only want "human written" material on their site is opting out of the research process that their own ideal clients are running right now. The competitor who uses AI to produce more content, structured for AI citation and featured snippet extraction, is being surfaced in that buyer's research session. The human-powered business is not. 

 

What actually happens when AI adoption goes wrong

The honest caveat deserves a straight answer: AI adoption done poorly produces nothing. MIT's NANDA research puts the generative AI pilot failure rate at 95% when leaders treat AI as a standalone project rather than as part of an integrated operating model. Only 29% of businesses report meaningful return on their generative AI investments, despite significant spending. That is a real failure rate, and anyone selling AI adoption as a guaranteed competitive fix is not being straight with you.

But here is the distinction that matters: the cost of a bad pilot is recoverable. You spent time, maybe money, got limited results, and learned something about what does not work for your operation. The cost of a five-year delay is systematic. By the time you start, your competitors have refined their systems, built their content libraries, established their AI citation footprint, and trained their teams. The gap you are trying to close gets exponentially more expensive to close with each passing quarter. A bad pilot sets a company back a quarter. Sustained refusal can set you back permanently.

The refusal crowd never even gets to fail at a pilot, which means they will never have the data to make the course corrections that eventually produce results. They are opting out of a learning curve that runs in the wrong direction the longer it goes uncorrected.

What the right position actually looks like in practice

The goal is not to use AI. The goal is to use your expertise more efficiently, reach more of your market, and serve your clients better. AI is the production tool that makes the first two possible without compromising the third.

Here is what this looks like in a working service business. Take a marketing strategy consultancy with two senior partners and a small support team. Every proposal they write draws on 20 years of combined pattern recognition across client industries. That knowledge base is the product. What has historically consumed the partners' time is the production work surrounding that expertise: drafting the proposal structure, populating the competitive context section, formatting the deliverable schedule, writing the follow-up emails, producing the monthly newsletter that keeps former clients engaged.

When AI handles the scaffolding of those tasks, the partners spend more time on the judgment layer: refining the strategic recommendation, pressure-testing the assumptions, having the client conversations that only their experience can navigate. The output volume increases. The output quality stays anchored to their expertise. The client never receives something that does not reflect the partners' actual thinking, because the partners are still setting the agenda and owning the conclusions. What changed is how much time they spend getting to those conclusions instead of typing around them.

That is the division of labor worth understanding:

• Expert judgment sets the agenda — the strategy, the recommendation, the diagnosis, the conclusions. This requires the human.
• AI handles the scaffolding — research synthesis, draft structure, formatting, distribution mechanics, first-pass content. This does not require the human to type every word.
• Expert review closes the loop — the finished output goes through the practitioner's filter before it reaches anyone else. This is where authenticity is protected, not in the refusal to use tools.

The business that operates this way publishes more content, ranks for more terms, appears in more AI-mediated research sessions, and has more time to do the high-value work clients actually pay for. The one that holds the "human only" line writes fewer pieces, appears less often, and spends more of its best people's time on production tasks instead of on expertise delivery.

Frequently asked questions about AI adoption for service businesses

Will clients know if AI was used to produce content or proposals?

In most cases, no. What clients evaluate is whether the output accurately represents expert thinking and serves their needs. An AI-assisted proposal that reflects the consultant's genuine strategic judgment is more valuable to a client than a purely handwritten one that took twice as long and reached the same conclusion. The question clients are implicitly asking is "does this person understand my problem?" Not "did a human type every sentence?"

Does Google penalize AI-assisted content?

Google's published guidance is explicit on this: the quality and helpfulness of content is what determines ranking, not the method of production. Thin, unhelpful, or inaccurate content performs poorly regardless of whether a human or an AI produced it. Well-researched, structurally sound, genuinely useful content performs well regardless of how the draft was assembled. The standard has always been quality, not authorship method.

Can a small service business realistically compete without using AI?

In some narrow categories and for some window of time, yes. But the window is closing. The tools that once required an engineering team now run on a subscription that costs less per month than a single billable hour. Adoption among companies with 10 to 100 employees jumped from 47% to 68% in a single year, according to 2025 industry tracking data. The competitive threshold is dropping while the stakes of non-adoption are rising. "Realistically compete" gets harder to answer favorably with each quarter that passes.

What is the difference between using AI and letting AI run your business?

The difference is where judgment lives. AI running a business would mean autonomous decision-making on strategy, client relationships, and problem diagnosis. Nobody credible is advocating for that in a service business context. Using AI means delegating production work to a tool that handles scaffolding while the practitioner handles everything that requires actual expertise. One is a science fiction concern. The other is standard operating procedure in most competitive markets already.

Where should a business owner who has been resistant to AI start?

Start with the overhead, not the product. Identify the three tasks that consume the most time from your highest-value people but do not require their expertise to complete. Draft emails, research compilation, proposal formatting, content structuring. Run AI on those first. When you have seen what it does to your production capacity on low-stakes work, you will have a much clearer view of where it can and cannot go in the rest of your operation.

The market does not grade on authenticity

The "human-powered" business owner is usually someone worth respecting. They built something real, they care about the quality of what they deliver, and they are trying to protect it. That makes the position sympathetic, and it makes it more dangerous, because it survives longer than it should on the strength of how principled it feels.

But the market does not grade on authenticity in isolation. It rewards value delivered efficiently and reliably, at the speed and scale that buyers now expect. AI is becoming the infrastructure through which that value is delivered. Opting out of infrastructure is not a differentiator. It is not a brand statement that buyers will reward. It is a slow erosion of competitive position that compounds quietly until it becomes visible all at once.

The decision to refuse AI is not permanent. But the gap it creates may become so. The businesses that figure this out now will have content libraries, AI citation footprints, refined workflows, and trained teams that late arrivals will spend years trying to replicate. The ones that hold the line will still have their principles. They just may not have much else.

Build the foundation that gets you found

Web development, technical SEO, AEO and GEO from Digital Upwelling

Digital Upwelling builds websites and digital infrastructure structured to be found by both human searchers and AI systems. Technical SEO, Answer Engine Optimization, and Generative Engine Optimization are not add-ons. They are built into every engagement from the start.

Work with Digital Upwelling

Copyright © 2026, Full Throttle Media, Inc. FTM #fullthrottlemedia #inthespread #sethhorne