I started Naftiko Signals because I wanted to read enterprises the way I used to read API providers — from the outside, with public data, on a continuous loop. Job postings, press releases, newsroom content, open-source activity. Not quarterly. Not paywalled. Not curated by an analyst desk with its own incentives. Just the public footprint, parsed against the same scoring rubric for every company.
For most of the last two quarters that ambition was a half-built corpus. This week it stopped being half-built.
The Numbers
- 884 new company signals pages built as the second Fortune 1000 sweep completed.
- All 50 industry pages refreshed in the same window.
- Role-aware “What’s Next” capabilities now surfaced on every company page.
- 1,554 jobs pulled from HSBC in a single Friday afternoon through Eightfold AI, with the corpus skewing heavily across Greater China, Hong Kong, Taipei, and the wider APAC banking footprint.
The corpus now spans the majority of the Fortune 1000, with the same scoring, the same maturity radar, and the same role and regional roll-ups applied uniformly across every company and industry. The radar is now reading from a corpus large enough to be predictive at the industry level rather than anecdotal at the company level. That is the line we crossed this week.
What Signals Reads
Every company gets profiled across four dimensions: Areas of Technology (AI/ML, APIs, cloud, security, containers, platform engineering, and more), SaaS Portfolio (services and platforms a company buys, builds, or integrates), Standards (participation in OpenAPI, AsyncAPI, JSON Schema, MCP, A2A, and the open standards conversation), and Tooling (developer tools and open-source projects the company adopts or contributes to). Across those four dimensions, every company is scored against 44 signal categories — from AI FinOps to Provider Strategy to Talent & Organizational Design.
That scoring is not the end of the work. It is the substrate. The analysis layers sit on top: AI Waves (recurring adoption patterns as the technology matures — LLMs, Coding Assistants, Context Engineering, Model Routing, Agent-to-Agent, and the waves still forming), Roles (how each wave reshapes which roles grow, which shrink, which new ones emerge), and Impact (the downstream effect on markets, workflows, and the cost / velocity / risk balance inside enterprises).
The “What’s Next” Capabilities
The new role-aware “What’s Next” capabilities are the part of this week’s build I am most excited about. Every company page now surfaces a small set of capability recommendations — shaped exactly like the capabilities Naftiko Shipyard teaches in its tutorial tracks. Same YAML shape. Same execution path. Same governance posture. A reader who lands on a company page can see what a credible next move looks like, expressed in the same vocabulary the open-source Fleet runs on.
That is the part that finally closes the loop. Signals is no longer just intelligence. It is a path from “what is this company doing” to “what would your team build on top of what they’re doing” — and the build is shaped as a capability you can author in Crafter, run on Ikanos, lint with Polychro, govern with Warden, and orchestrate with Skipper.
A Buyer-Side Lens Just Showed Up
This week’s Signals build was accompanied by the first market-data-partner feedback Naftiko has received. That feedback surfaced five net-new problem statements the existing 15 enterprise-practitioner personas did not cover — including employee-count-band filtering, industry-cluster highlights, tiered feed access, and a Naftiko Skills bundle for Claude with tiered pricing that mirrors how Apify packages its scrapers. Those statements are live now on market.naftiko.io and will shape the next round of Signals packaging.
That is the first time the Signals work has been pulled on by a buyer who is not an enterprise practitioner. The feedback rhymes with what design partners have been telling us, but the framing is different — and the differences are what is going to drive the next pass.
Open by Design
Naftiko Signals stays an open site backed by structured YAML — companies, industries, signals, services, tools, standards, and waves are all versioned in Git and available for inspection, contribution, and reuse. Intelligence about enterprise technology investment should be as accessible as the open-source projects it tracks. Signals is built that way deliberately.
If you want to see what your nearest peer’s public footprint says about where they are investing across AI, data, integration, and governance, go pull up their company page on companies.naftiko.io. If you want the industry-level view, industries.naftiko.io is where the rolled-up read lives. The radar is at signals.naftiko.io/radar.
An enterprise that can read itself from the outside can govern itself differently. That is the bet. As of this week, the corpus is finally large enough to back it.
