Skip to content

NexusRevenue Intelligence

The shortlist, and the argument behind every name on it.

Nexus evaluates the candidate universe overnight, scores each company on dated public evidence that a buying window is opening, argues with itself about the ones sitting near the line, and publishes a ranked shortlist before the day starts. Every score comes apart into the signals that produced it, and every signal carries the URL it came from.

Pipeline
Stages 01–07, 09, 11
Decides
Who to contact, when, on what evidence
Refuses
Volume as a substitute for targeting
Today's shortlist2026-08-16 06:00 UTC20 of 4,812
  1. 01Halverson Freight SystemsRegional freight brokerage · 210 staffThree SDR roles and a RevOps role opened inside eleven dayshalverson-freight.com/careers · 3d91/100
  2. 02Meridian Cold ChainTemperature-controlled 3PL · 340 staffPublished a migration notice for its transport management systemmeridiancold.example/newsroom · 6d87/100
  3. 03Castellane InteriorsCommercial fit-out · 64 staffThird lease filed this year, two of them in new regionspublic company register · 9d84/100
  4. 04Ardenway ManufacturingPrecision components · 480 staffFirst recorded paid search on a competitor's brand termsads transparency centre · 4d79/100
  5. 05Pentworth LegalMid-market practice · 95 staffNew COO appointed from a firm that already buys this categorypress release · 12d72/100
  6. 06Orbit Dental GroupMulti-site dental · 28 practicesCareers page rebuilt and four operations roles addedarchive diff · 5d68/100
4,812 companies evaluated20 shortlistedthe rest are not contacted today, and that is the product

Illustrative record. Every company named on this site is fictional: Arvyn is new and has no customers to name, so it names none.

Position

Nexus is the spine, not a feature.

Scout and Sonar are specialists — one reads a company, one sits on the call. Nexus owns everything else: it decides who is worth a conversation, gets that conversation started, and rewrites its own scoring depending on how the conversation went.

The order matters more than it looks. Research before qualification is how teams end up writing beautiful emails to companies that were never going to buy this year. Nexus qualifies first, on cheap public signals, and only spends real research effort on the accounts that survive.

By the time Scout opens a company, that company has already argued its way onto a list of twenty out of several thousand.

The trade

A capped shortlist means most of your candidate universe is not contacted today. That is not the engine holding back. That is the entire thesis: the constraint is what makes the twenty worth reading.

Pipeline11 stages
  1. 01Understand the businessYour site, your deck, your own wordsNexus
  2. 02Define the ICPSegments, sizes, regions, buying committeeNexus
  3. 03Build the candidate universeThousands of companies, none contacted yetNexus
  4. 04QualifyShould we contact them — not can weNexus
  5. 05Score the buying windowObservable evidence only, each one citedNexus
  6. 06PrioritiseThe shortlist, capped on purposeNexus
  7. 07Find the decision-makerDiscovered, then verified before useNexus
  8. 08Research the accountThe cited dossierScout
  9. 09Write and sendPer-account brief, sending windows, repliesNexus
  10. 10Take the conversationRehearsal first, live coaching secondSonar
  11. 11Learn from the outcomeEvery reply re-weights the scoringNexus

04–05Qualify, then score

Should we contact them — not can we.

Contactability is commoditised: anyone can sell you an address. The question Nexus answers is whether there is credible, dated, public evidence that this company is moving toward a purchase this quarter — and how much of it would survive an argument.

QUAL04

What counts as evidence

A signal is admissible when it is observable by anyone, carries a date, and can be re-fetched tomorrow from the same address. Nine families qualify. Everything else — sentiment, inferred intent bought from a third party, “similar companies also bought” — is excluded, because none of it can be shown to you as a URL.

Families are combined, never summed blindly. Hiring on its own is weak. Hiring against a named renewal date is the strongest pattern the engine knows, and it is strong precisely because two independent sources have to agree.

Admissible
Public, dated, re-fetchable, attributable to a URL or register
Excluded
Bought intent data, scraped private profiles, model guesses
Re-checked
Nightly. A source that goes dark is flagged, not silently kept
Signal familiesAdmissible9
  • HiringRoles opened that only exist when a function is being built
  • Buying cycleA renewal, a tender, a contract end date stated publicly
  • Tech gapWhat is running on the site, and conspicuously what is not
  • Org changeA first-time role, a new owner for the function, a departure
  • ExpansionLeases, registrations, new regions, new entities
  • PositioningPricing and messaging rewritten inside a short window
  • RegulatoryA rule that lands on this sector with a date attached
  • Operational strainPublic complaints, delivery times, review patterns
  • CommitmentSomething said in public that they now have to deliver

READY05

The buying window

Buying readiness is not a property of a company, it is a property of a moment. Signals arrive one at a time, from different places, over weeks, and only their arrangement means anything. Four ordinary signals landing inside eleven days is a different fact from the same four spread across a year.

So the engine keeps the sequence, not just the total. Evidence decays on its own half-life — sixty days for a pricing rewrite, two hundred and forty for a lease — which means a score that is not re-earned falls without anybody deciding to lower it.

Window
Rolling 90 days, per account
Recomputed
Nightly at 02:10 UTC
Half-lives
60d positioning · 90d hiring · 180d org · 240d expansion
Signal trace9 signalsWindow open
Hiring
Buying cycle
Tech
Expansion
Verdict
90 days agoToday
Qualification
91%
Hiring
First SDR role posted
14d ago
Hiring
Two more SDR roles posted
6d ago
Hiring
RevOps role posted
3d ago
Buying cycle
Q4 renewal named in a tender notice
18d ago
Tech
Analytics tag replaced
34d ago
Tech
Pricing page rewritten
7d ago
Tech
Still no CRM detected
1d ago
Expansion
Depot lease registered
41d ago
Expansion
Second depot lease registered
20d ago

LEDG05

Every score comes apart

A number you cannot audit is a number you cannot argue with, and a number you cannot argue with is one you will quietly stop trusting. So the score is kept as a ledger: each line is one signal, its family, its half-life, its source, and the points it contributed.

Including the lines that took points away. An entrenched incumbent subtracts. A missing budget owner subtracts. If a ledger only ever adds, it is a chart with a total on the bottom, not an account of anything.

Score ledgerACC-2291 · Halverson Freight Systemsreadiness 91
SignalContribution
Evidence subtotal+102
Penalties (2)-11
Buying readiness91 / 100

Recomputed nightly at 02:10 UTC. Points shown after decay. Click any source to open the record the claim was read from.

06Prioritise

A model asked to justify a score will always justify it.

That is the failure mode of every AI scoring product, and it is why the score is not produced in one pass. A qualifier states the case. An adversary attacks its weakest link. An arbiter rewrites it or drops it — and the transcript is kept for every account, including the ones that lost.

  1. ProposeA qualifier states the case from the evidence.
  2. ChallengeAn adversary attacks the weakest link in it.
  3. ReviseThe case is rewritten, or dropped.
Deliberation3 turnsqualified

Contact Halverson Freight Systems this week?

  1. ProposeQualifier

    Four revenue roles in eleven days against a Q4 renewal date is a team being built to run a purchase. Recommend contact inside seven days.

  2. ChallengeAdversary

    Hiring can be replacement, not expansion. Two of those SDR posts reuse the wording of roles posted in February, which is what backfilling looks like.

  3. ReviseArbiter

    Two are backfills, so hiring alone would not carry it. The RevOps role is new to the company and lands on the renewal date, and that pairing is what holds. Contact, lead on the renewal, not on the hiring.

VerdictContact within 7 days, renewal-led
91%
Deliberation3 turnsrejected

Contact Verrow Analytics on the funding signal?

  1. ProposeQualifier

    A funding announcement usually means new budget and new headcount. On the raw signal this is a strong candidate.

  2. ChallengeAdversary

    The round is an extension of an existing one, not a new round, and headcount on their own careers page has fallen by nine since March. That is a runway extension, not an expansion.

  3. ReviseArbiter

    The funding signal is real but it points the other way. Drop from the shortlist and re-open only if net hiring turns positive for two consecutive months.

VerdictNot contacted. Re-open on sustained net hiring
78%
The rejections are the product.
Every outbound tool can produce a list. The difficult, valuable, unglamorous work is in the names that did not make it, and in being able to say exactly why each one was left out. A shortlist without a rejection log is just a longer list that stopped early.

09–11Send, then learn

The part the category calls the whole product.

Sending is the easy half, and it is the half ten years of tooling has already optimised. Nexus does it properly, refuses the tricks that quietly cost you replies, and treats every result as evidence rather than as a scoreboard.

CAMP09

A brief, not a template

Every draft is written against the account’s own ledger, and every specific claim in it is tied back to a numbered source. The constraint does the work: a sentence that cannot be traced to a dated public fact does not get written, which removes at a stroke the fabricated familiarity that makes personalised outreach embarrassing.

You approve the draft, edit it, or reject it and say why. A rejection with a reason is worth more to the engine than an approval, because it is the only signal that separates a bad account from a bad sentence.

Sequence
Three touches by default, stopped instantly on any human reply
Language
Drafted in the language of the account's region
Provenance
Every claim numbered to a source on the account record
DraftSEQ-1/3queued
Account
ACC-2291
Sequence
1 of 3
Window
Tue 08:15 UK

Subject

Q4 renewal — before you rebuild the team around it

Priya,

Your transport management contract comes up in Q41, and you have just created a Head of Revenue Operations role2 — the first one at Halverson. Those two things usually happen in that order for a reason.

The part that tends to bite at this stage is that the new RevOps hire inherits no CRM of record3, so the renewal decision gets made on spreadsheets and memory.

Worth twenty minutes before the renewal window opens?

  1. [1]Tender notice HF-40912 — renewal date, observed 18d ago
  2. [2]Careers page — RevOps role, first of its kind, observed 3d ago
  3. [3]Stack detection — no CRM on the public site, observed 1d ago

SEND09

The sending engine, and what it refuses

Sending runs on your own mailboxes, connected over Gmail or Microsoft OAuth, or plain SMTP. Per-inbox daily caps, per-region send windows, and a hard stop on any thread the moment a human replies. Addresses are verified through independent providers before use, and anything that comes back risky is held rather than sent.

Open tracking is off by default. The pixel costs more in deliverability and in replies than the open rate returns as a signal, and nothing in the scoring depends on it. You can turn it on. The engine will not turn it on for you.

Mailboxes
Gmail OAuth · Microsoft OAuth · SMTP
Verification
Independent providers, before the first send
Stop rule
Any human reply halts the whole sequence
Send windowsPerICP region
  • UK & IrelandTue–Thu 08:15–11:0040 / inbox / day
  • US EastTue–Thu 07:45–10:3040 / inbox / day
  • DACHTue–Thu 08:00–10:4530 / inbox / day
  • IndiaMon–Thu 10:00–12:3035 / inbox / day

No 03:00 local sends. No Sunday sends. Local public holidays skipped per region.

LEARN11

The loop, and its brakes

Every reply, meeting and closed deal is fed back as an outcome against the evidence that produced the contact. Over time the weights move: signal families that preceded real conversations count for more, families that looked convincing and led nowhere count for less.

The brakes matter more than the loop. A weight cannot move on fewer than thirty outcomes, because below that a change is noise wearing a result’s clothes. When the engine wants to move a weight and cannot yet justify it, it says so and waits.

Scope
Your workspace only. Nothing is pooled across customers
Threshold
30 outcomes minimum before any weight moves
Reversible
Every weight change is logged and can be rolled back

Recent weight changes

  1. Weight changeLRN-0114

    Tender-notice renewal dates were re-weighted upward for logistics accounts

    Moderate
    Workspace outcomesrecomputed weekly
  2. Weight changeLRN-0119

    Generic 'recently funded' signals were down-weighted to near zero

    Moderate
    Workspace outcomesrecomputed weekly
  3. GuardrailLRN-0122

    A weight cannot move on fewer than thirty outcomes

    Strong
    Engine rulealways on

Specification

The unglamorous detail.

Everything a sceptical buyer asks in the second meeting, written down before the first one.

On autonomy

Nexus ships with every stage requiring approval. Autonomy is raised one stage at a time, by you, after you have read a few deliberations and disagreed with at least one of them. A system you have not argued with is a system you should not let run unattended.

SpecificationNEXUS

Inputs

onboarding
Your domain. Optionally a deck, a pricing page or a PDF of your own positioning.
icp
Generated from those inputs, then edited by you. Segments, sizes, regions, buying roles.
candidate universe
Built per workspace. Thousands of companies, none of them contacted at this stage.
your outcomes
Replies, meetings and closed deals from this workspace feed the weights. Nothing crosses between workspaces.

Scoring

score range
0–100 buying readiness, recomputed nightly at 02:10 UTC.
decomposition
Every point traces to one signal, one source URL and one observation date.
decay
Signals carry a half-life from 60 to 240 days. A score that is not re-earned falls on its own.
deliberation
Accounts near the shortlist boundary are argued propose → challenge → revise before they are ranked.
penalties
Missing budget owner, entrenched incumbent and stale evidence all subtract. The ledger shows them.

Outreach

shortlist size
Capped per day. The cap is a setting, not a limit of the engine.
approval
Manual approval by default. Autonomy is unlocked per stage, per workspace, once you have watched it work.
contact discovery
Discovered, then verified through independent providers before a single send.
sending
Your own mailboxes over Gmail or Microsoft OAuth, or SMTP. Per-inbox daily caps.
windows
Per-region send windows. No 03:00 local sends, no Sunday sends, set per ICP region.
open tracking
Off by default.

Operations

integrations
HubSpot and Salesforce sync, a REST API, and webhooks on qualification, send, reply and meeting.
notifications
Telegram or email on positive replies, meetings booked and anomalies.
audit
Every score, every deliberation and every send is retained with its evidence for review.

Limits

What Nexus refuses to do.

A refusal is a design decision, and the decisions are more informative than the feature list. These are permanent, not a roadmap gap.

  • It will not score a company without a source

    If a claim has no retrievable URL or public record behind it, it contributes nothing. An unsourced hunch is not evidence, and a score built from hunches is a horoscope.

  • It will not send more to compensate for weak targeting

    There is no volume dial to turn when the shortlist is thin. A thin shortlist is information: the candidate universe or the ICP is wrong, and more sending would only bury that.

  • It will not use an address it could not verify

    Guessed patterns are checked against independent verification before use. Anything that comes back risky or unknown is held, not sent, and the account waits for the next run.

  • It will not treat silence as disqualification

    A company with no public signals is unknown, not unqualified. It stays in the candidate universe and is re-checked, rather than being scored low and quietly discarded.

  • It will not run A/B tests on small samples

    Separating two subject lines honestly takes far more positive replies per arm than a real shortlist produces in a month. Variants are allocated adaptively instead, and the engine says when a difference is not yet real.

  • It will not act autonomously on day one

    Every stage ships needing your approval. You raise the autonomy threshold per stage, after you have read the deliberations and disagreed with a few of them.

  • It will not track opens by default

    The pixel costs more in deliverability and replies than the open rate is worth as a signal. Turn it on if you need it; nothing in the scoring depends on it.

  • It will not learn across workspaces

    Weights move on your outcomes only. Your reply data does not improve a competitor's targeting, and theirs does not shape yours.

Connect a domain and read tomorrow's twenty.

Fifteen days. You approve every send. The first shortlist arrives once the candidate universe has been built and scored, and each name on it comes with the ledger that put it there.