The AI technology intelligence agent.
What a company runs on, named in its own documents. Open repositories, open-source packages, the skills in its job adverts and the vendors its records point at - read together, so the stack comes with the evidence for each item.
Knowing what a company builds with changes two conversations. In sales it decides whether there is anything to integrate with and which objection arrives first. In product and strategy it is the earliest honest sign of what somebody is building - a team hires for a technology months before it ships anything that uses it.
The usual source for this is a vendor list bought from somebody who scanned the web once. It is a snapshot, it is often wrong, and it never says how it knows. A stack read from documents the company itself posted is checkable in a way that a purchased list is not.
- Tech map - What each account runs on, with the document that named each item.
- Capability map - Which technologies a company is building with, and since when.
- Release cadence - How often it actually ships, read from its own public release history.
- Early signals - The role that appears before the product does.
The agents on this job, and how each one proves itself
Each line is the agent's own description from the roster the product runs on, not a paraphrase written for this page.
- 01 · Scout
Finds what is on the record. Thirty credible sources, read for every company you watch. The list of sources, and their licences, is on the Trust page.
- 02 · Recruiter
Reads hiring as intent. Job postings, from the boards companies post them on. A requisition is a company stating in public what it will pay for.
- 03 · Sifter
Decides what matters. Every signal carries the score that let it through, and everything held back stays in a log you can read.
- 04 · Analyst
Writes the brief. The brief, written from the shortlisted signals, with every line tracing to a dated source.
Named sources, every one of them something you could open yourself
Nothing is bought from a data broker. The full source list, and the licence for each, is on the Trust page.
- It reads what is open. A company with no open repositories, no open-source packages and vague job adverts will produce a short map, and the map says which parts are unknown.
- A technology named in a job advert is evidence that somebody is being hired to use it, not proof that it is in production.
- Vendor records show what a domain points at, which is a strong hint about infrastructure and a weak one about everything else.
- Nothing here scans, probes or touches a company’s systems. Every item comes from a document that was posted.
Part of the innovation and revenue lenses. Starter chooses one lens, Growth three at once, Enterprise all of them.
What people ask
How do you know what a company uses without scanning them?
Is this the same as a technographics list?
Can it tell us what a company will build next?
See it on your own market.
A working run against the companies you actually care about, not a recorded video.