Federal Posture Lead · Outside-In Analysis
Book 1 · Ch 4 · Your Best Product Already Exists

Outside-In Mirror: What a Buyer Sees in 10 Minutes

What a federal contracting officer, VC associate, or allied-market buyer actually finds when they search for NorthAI or CHN Analytics today, and what that gap means for the engagement.

1.1 · Federal Posture Lead · artifact id: outside-in-mirror-v0.html · 2026-05-28 · v0
From Shrink-Wrap It, applied to NorthAI · Ch 4: Your Best Product Already Exists
Your delivery history is a gold mine of hidden IP that you've already proven works in federal environments.
Shrink-Wrap It · Ch 4 · Contract archaeology is the process of reviewing your delivery history to identify and extract hidden IP

The hidden-IP extraction problem has a mirror image: even when the IP exists and is proven, if it is invisible to outside buyers, it cannot generate revenue. NorthAI's 5.5-year OSI&A engagement represents validated, Pentagon-grade intelligence-fusion methodology. A buyer doing 10-minute due diligence today cannot see it. The outside-in mirror documents the gap between what NorthAI has built and what any buyer can verify without insider access.

Entity disambiguation (critical): Searching "NorthAI" surfaces a UK media-analytics firm of the same name that dominates English-language search results. The engagement target is NorthAI (defense) operating through CHN Analytics LLC (UEI HGMHPZK5GED3, Loveland OH, northai.io). These are completely separate entities. A buyer's first 10 minutes of due diligence will encounter both. This memo focuses exclusively on what a buyer finds about the defense entity.

The 10-minute buyer view: channel by channel

Channel 1: SAM.gov entity record

UEIHGMHPZK5GED3
Legal nameCHN Analytics, LLC (formerly Chapel Hill North Group Ltd per SBIR.gov 2021)
Address6452 Branch Hill Miamiville Rd, Loveland, OH 45140-7536 (confirmed via ETI 2025 exhibitor listing)
StatusWoman-owned (2021 employee count: 12; current count unconfirmed)
DUNS556422140
NAICS (inferred)541512 (Computer Systems Design), 541715 (R&D in Physical Sciences), 541990 (Other Professional Services), requires direct SAM.gov authenticated verification
ExclusionsNo exclusions visible in public sources
V1 verification note: SAM.gov requires authenticated / CAAC access for the full entity record including reps/certs, NAICS codes, and current POC. Direct URL lookup returned 404 without authentication. The above data is drawn from entity-map cross-references and ETI 2025 exhibitor confirmation. Full SAM.gov pull requires Tim to confirm they are SAM-registered and active for FY2026.

Channel 2: USASpending.gov visible total

$49,500
Visible prime-award total (all years)
1
Prime contracts in public FFATA record
2021
Year of sole prime award (AFWERX STTR)

The single visible award: FA8649-21-P-0756, AFWERX STTR Phase I, $49,500, 2021. PI: Alec Daling. This is the only publicly traceable prime contract under UEI HGMHPZK5GED3 in the FFATA (Federal Funding Accountability and Transparency Act) reporting system.

The credibility gap: On the discovery call, NorthAI described serving OUSD R&E / OSI&A for 5.5 years (2018-2023). That engagement history does not appear in the public FFATA record. The most probable explanation: NorthAI/CHN operated as sub-of-prime (or sub-of-sub) below the $30K FFATA reporting threshold, under a prime such as SOSi or Exovera. A federal buyer reviewing USASpending.gov will see $49.5K and conclude "small vendor, single award", not "5.5 years of Pentagon intelligence community delivery." This is a verified credibility gap, not a data error.

Channel 3: FedRAMP Marketplace

V1 verification (live browser search, 2026-05-28): Zero results for "NorthAI" and zero results for "CHN Analytics" in the FedRAMP Marketplace. 651 authorized products in the marketplace as of the verification date; none matched. No in-process authorization (Provisional or Interim) found.

Status: Pre-FedRAMP. Consistent with the entity-map stage notation ("post-services pivot, active PE/VC raise, pre-FedRAMP"). A federal buyer searching for an authorized product will not find NorthAI or CHN Analytics. See fedramp-20x-path-memo-v0.html for the recommended authorization path.

Channel 4: Search engine result landscape

V1 verification (live browser search, 2026-05-28): A Google search for "NorthAI" returns a cluttered result page. The defense entity (northai.io) is visible but not dominant. Non-target variants appear prominently, including NorthAI.app (a field-sales CRM, completely unrelated) and other commercial "North AI" products. Sponsored results (unrelated) occupy top positions.

Confusable-entity search problem: Searching "NorthAI" in English will surface a UK media-analytics firm of the same name before the defense entity in some result configurations. This firm has received recent press coverage (2024 funding round), has named leadership, and has a professional company profile. A buyer's first 10-minute due diligence almost certainly encounters both entities. The defense NorthAI has no recent press, no funding announcements, and no Google News hits in the 90-day window ending 2026-05-28. The disambiguation burden falls entirely on the buyer.

CHN Analytics search: Searching "CHN Analytics LLC" surfaces Stephanie Hughes' LinkedIn profile (Co-Founder at North AI, Division of CHN Analytics LLC) as the first organic result, followed by a Form D SEC filing confirming the entity. B2B directories (Crunchbase, ZoomInfo, RocketReach) provide secondary confirmation. No mainstream press coverage.

Channel 5: GitHub presence

Findings: A GitHub organization referenced as CHN-GITHUB (github.com/CHN-GITHUB) exists with activity described as "CHN Projects" and software-build activities. Public repository visibility is limited, the organization did not surface in GitHub search for "NorthAI." Direct navigation to github.com/CHN-GITHUB would be required to confirm current public repo count and last-commit dates.

Assessment: The GitHub presence exists but is not algorithmically prominent. A buyer checking GitHub for technology maturity signals will find limited public evidence of active development. This may reflect intentional IP protection (keeping product code private) or limited open-source contribution.

Channel 6: LinkedIn

V1 verification (live browser search, 2026-05-28): The North AI LinkedIn company page (linkedin.com/company/northai) is accessible without authentication. The page is active: it shows company branding (orange/black logo), mission statement ("Defense technology intelligence platform for military, defense and government leaders"), employee profile photos, and recent company posts. The page is maintained.

North AI (LinkedIn company)

Page: linkedin.com/company/northai. Active. Employee profiles visible. Recent posts accessible logged-out. Employee list gated (requires login).

CHN Analytics (LinkedIn company)

518 followers. Page: linkedin.com/company/chn. Company type: Software/Technology Services. Active. Stephanie Hughes visible as co-founder.

V1 correction to initial R5 assessment: The North AI LinkedIn company page IS fully readable without login via direct URL. Initial assessment ("not visible logged-out") referred to LinkedIn algorithmic search, not direct page access. A motivated buyer who knows the company name can access the page and confirm current operations without authentication.

Six observations (pattern + implication)

Observation 1

Stealth posture: zero Google News presence

Pattern: No press releases, no funding announcements, no award announcements, no LinkedIn activity visible in search (company page exists but not featured), no Google News hits in the 90-day window ending 2026-05-28.

Implication: Federal buyers perceive stealth as either pre-launch or quietly executing. The absence of messaging creates a credibility gap (no proof of traction) and a trust advantage (no hype). Most defense SaaS vendors maintain public customer case studies or NDIA speaker slots. NorthAI has neither. For a federal evaluator, the absence of press is unusual at the "active PE/VC raise" stage.

Observation 2

Sub-of-sub footprint masks actual delivery scale

Pattern: USASpending.gov shows $49.5K (2021 STTR). The discovery call described 5.5 years of OUSD R&E / OSI&A engagement (2018-2023). The gap is explained by sub-of-prime or sub-of-sub work below the $30K FFATA reporting threshold.

Implication: A buyer reviewing USASpending.gov concludes "small vendor, single award, limited prime experience." They cannot see the 5.5-year Pentagon relationship without insider disclosure. Closing this gap requires either (a) confirming the prime contractor name for citation in RFP responses, or (b) developing unclassified case study materials that describe the customer relationship in non-attributable terms.

Observation 3

Confusable-entity disambiguation burden falls on the buyer

Pattern: Searching "NorthAI" returns a cluttered result page. A UK media-analytics firm of the same name dominates English-language press coverage (recent funded round, named leadership, professional company profile). The defense entity has no recent press.

Implication: A buyer's first 10 minutes of due diligence almost certainly involves disambiguating between the two entities. The northai.io homepage (defense platform) is discoverable by a motivated buyer but requires intent to find. A buyer who stumbles across the UK entity first may not investigate further. The brand-name collision is a negative first impression for the defense entity. Proactive disambiguation messaging (e.g., "US defense technology intelligence platform, not affiliated with any UK entity of the same name") on northai.io would address this.

Observation 4

NorthAI / CHN brand split creates federal buyer friction

Pattern: Marketing and product face externally as "NorthAI" (northai.io). Legal and services operations run under CHN Analytics LLC (chnanalytics.com, co-branded as "North AI" with competitive intelligence / tech forecasting reports). The two domains and brand names serve different functions but are not clearly explained on either website.

Implication: A federal buyer asking "who is the contracting entity?" cannot answer this from public sources alone. The split creates friction for RFP responses, CAGE/UEI lookups, and past-performance citations. Clarifying the partnership structure publicly (without exposing internal business arrangements) would reduce buyer friction significantly.

Observation 5

ETI 2025 attendance confirms active market engagement

Pattern: NorthAI (booth #7754, joint with CHN Analytics) is confirmed as an exhibitor at NDIA Emerging Technologies (ETI) 2025 conference (August 27-29, 2025, Washington DC). Category: "Services, Trusted AI and Autonomy."

Implication: ETI attendance confirms active federal buyer and industry-partnership pursuit. For a buyer attending ETI in August, this is the first opportunity to see NorthAI in person and disambiguate from other entities. ETI also suggests a DoD-aligned sales motion (NDIA is DoD-focused) rather than a commercial-only positioning.

Observation 6

Pre-FedRAMP status creates authorization gap for federal SaaS sales

Pattern: FedRAMP Marketplace V1 verification: zero results. No authorized, in-process, or provisional ATO found for NorthAI or CHN Analytics.

Implication: Federal agencies cannot buy unauthorized SaaS products regardless of how much the program manager wants them. A contracting officer reviewing NorthAI's platform cannot approve a purchase without an ATO. The FedRAMP 20x LI-SaaS sponsorless path (see fedramp-20x-path-memo-v0.html) addresses this directly. Until an authorization path is public and in-progress, the FedRAMP gap is visible to any evaluating buyer.

Critical questions Tim + Stephanie should answer

A federal contracting officer evaluating NorthAI on a competitive bid would ask these questions. A VC associate doing 30-minute diligence would ask most of them. The answers should be crisp, consistent, and available without requiring classified disclosure.

  1. Brand clarity, northai.io: When a federal buyer lands on northai.io, does the homepage immediately clarify that this is a US defense-technology intelligence platform operated by CHN Analytics LLC? What language distinguishes the platform from any entity of the same name in other sectors or geographies?
  2. Contracting entity: In a federal RFP response, which entity appears as the offeror: CHN Analytics LLC, a NorthAI-branded entity, or a partnership between both? Which UEI and CAGE code appear on the contract? A buyer needs a single answer, not a partnership explanation.
  3. Customer wins visibility: Why is there no public case study, anonymized customer metric, or success outcome for the 5.5-year OSI&A engagement? A defense vendor with Pentagon customers typically has at least one unclassified win story (e.g., "helped a DoD intelligence-analysis team process 47% more technology assessments per analyst per quarter"). Is the 5.5-year relationship under a confidentiality agreement that prevents any public citation?
  4. Funding runway: Is NorthAI / CHN actively fundraising (as the entity-map suggests)? If so, what is the capital target, current stage, and investor profile? The absence of public funding announcements creates ambiguity about financial runway that a federal buyer evaluating multi-year contract performance risk needs to resolve.
  5. Prime contractor for OSI&A engagement: Who was the US prime contractor that carried the 2018-2023 OUSD R&E / OSI&A work? The prime's name can appear in past-performance citations and RFP submissions. Without it, NorthAI cannot demonstrate the scope of the engagement to federal evaluators who look up references.
  6. FedRAMP path: Has NorthAI selected a FedRAMP authorization approach (20x LI-SaaS, FedRAMP Moderate, DoD IL2)? When does authorization begin? An agency buyer evaluating a multi-year platform investment wants to know when authorized status is expected, not whether it will happen.
  7. Northai.io URL ownership: The entity-map flags northai.io as requiring verification: does the NorthAI defense product hold exclusive control of northai.io, or does the domain have a shared or disputed presence with any other entity? This question should be resolved before the microsite is shared.