Tools · Index
Your whole market, ranked and briefed before the first call.
Index maps every company in your market from the public record, ranks each one against the customer you actually sell to, and writes a short, sourced brief for every account worth calling. It replaces the hour a rep spends researching before a call with something already done, and done the same way across the team.
What a team sees
One page. Every account that could buy, in order.
A ranked table of the market, filtered by territory, with a fit score out of 100 and, beside it, how much of that score rests on evidence rather than inference. A 92 that is mostly observed and a 92 that is mostly guessed are different accounts, and the table says so.
Fictional accounts, real method. Nothing in Index is ever shown to a prospect, and nothing in it is a benchmark of one.
What a rep opens
A one-page brief, written from the evidence.
Every account worth calling gets a brief. It leads with why now, who buys, and one question to open with. Every claim carries its source and the date it was read. The most trusted part is the last section: what we do not know, in plain words, so nobody walks into a call over-confident.
- Signals are quoted only if the pipeline re-fetched the page and found the words still there.
- Conversation starters ask about their situation. They never assert how the prospect works.
- Competitors found on the account's own pages are flagged in words, never deducted from the score.
- Why now
- Head of security role opened 9 days ago, the first such role at the company. observed
- Who
- CTO named on the leadership page; two platform engineering roles open. observed
- Open with
- How are enterprise security questionnaires handled today: by engineering, or by someone whose job it is?
- Watch out
- A competitor's badge on their trust page. observed
Moving upmarket. "We now serve three of the ten largest US insurers." Press release, read 2026-09-14. observed
Formalising security. A posting asks for "experience owning a company's first SOC 2 audit." Careers page, read 2026-09-14. inferred, medium
- Whether a SOC 2 audit is already under way.
- Who answers security questionnaires today: the CTO, or sales.
- The renewal date of the tool named on their trust page.
How it scores
Six questions a rep would ask, answered from public evidence.
Your rubric is four to six factors with plain integer weights, written as a document before any code, so your team can argue with every one of them. Each factor sits under one of six questions, and the evidence order is always the same: the account's own published data first, public registries and filings second, third-party pages last.
- ScaleIs this account big enough for the deal to matter?headcount, units, beds, sites, open roles
- MomentumIs something happening that makes this the moment?hiring swings, expansion, funding, filings, enforcement
- FitDoes the shape of the business match what you sell into?industry codes, portfolio type, segment mix
- Technology postureDo they buy platforms, and what is already installed?job postings naming systems, portals, served HTML
- GeographyWhere are they, and does the footprint suit your rollout?HQ, locations, states and countries
- Buying centreIs the team that buys this visible, and is it active?open roles for the buyer and champion titles
An account is in the market because a public record shows one observable fact: runs platform P, holds licence L, files form F, operates N sites. Gates are never scored, and accounts that fail are kept and marked, so nothing disappears.
Observed means read from a public page, with the URL and the date. Inferred means a judgment from the evidence, with a confidence. The table shows how many of the six factors were observed, so a rep knows which numbers are solid.
How it is built
Six steps, from a public record to a page your team uses.
- 01Gate. One observable condition defines your market, taken from a public registry or index, never from a bought list.
- 02Map. Every account that passes the gate, found through at least two public sources, so "seen by a crawler" is never mistaken for "everyone".
- 03Identity. Each entry resolved to one operating company: subsidiaries rolled up, wrong matches removed, hand corrections kept across every rerun.
- 04Score. Your rubric, applied to every account, with a one-sentence reason per factor that names the evidence and whether it was observed or inferred.
- 05Brief. For the accounts worth calling: verified signals, an operating picture from their own data, an opener, and what we do not know.
- 06Page. One page for the team: a filter rail by territory, the ranked table, and the brief a click away. Hosted by RVNU, exportable at any time.
Markets where the qualifier is a public fact. Runs on a named platform. Holds a licence a state publishes. Files a form a regulator indexes. Operates a number of sites a registry counts. The pattern has been run across seven markets so far, from enterprise recruiting teams to hospitals to sterile compounding pharmacies.
Markets where the qualifier is a private behaviour, such as using a particular spreadsheet or feeling a particular pain. There, the first step is discovery, not a map, and Wayne will say so on the call.
Built inside the engagement, then kept fresh.
Index is built for one client at a time, inside a fractional engagement, around that client's market, rubric and territories. RVNU keeps the method and the source maps. The client's data, rubric and briefs are theirs, and everything exports as a page and CSVs whenever they want it.
On the same skeleton, an engagement can add a scheduled rerun with a visible last-run date and a feed of accounts new to the market, weights tuned against the client's own closed-won and closed-lost outcomes, and separate views for inbound and outbound work.
Public sources only. Nothing in Index is shown to a prospect.
See what your market looks like ranked.
Fifteen minutes with Wayne. Bring the customer you sell to and the one public fact that puts a company in your market.