Your pipeline is not short of names. It is short of an honest answer to "who first, and why".
Your CRM holds hundreds of leads and your tools shower you with signals: funding rounds, hiring posts, mentions, opens, replies. CORTEX turns that flood into one weighted, time-decayed score per entity and a ranked shortlist that can show its work, so your team spends today's limited attention on the warmest account instead of the loudest one.
Get a ranked, explainable shortlist from your own roster See one score decomposed
THE PROBLEM
Lead generation got cheap and then it got free, and 2026 finished the job: AI SDR tools and signal feeds now fill pipelines faster than any team can work them. The binding constraint moved. It is no longer finding names, it is defensibly choosing among them, and the tools most teams use for that fail in one of two ways. The black-box score cannot answer "why is this account first" in a pipeline review, so nobody trusts it and everyone goes back to gut feel. The hand-tuned point sheet answered that question once, in the quarter someone built it, and has been quietly stale ever since, which is how an account that was hot three weeks ago keeps outranking one that engaged yesterday. Either way the team works the wrong names, and the cost is invisible because nobody sees the deals that were never worked.
HOW IT WORKS
CORTEX scores every entity from three named parts, and keeps all three inspectable. First, intent: the entity's attached signals (funding, hiring, launches, pain-point mentions) are scored against weights you can read and edit, not a model you have to trust. Second, warmth: a 0-100 engagement heat computed from your actual interaction history with an explicit half-life, so the score reflects the relationship as it is, not as it was. Third, honesty about time: recency decay cools every score per day since the last engagement, so stale heat drops on its own. The sweep ranks the composite results, applies an explicit threshold, returns a shortlist with the full scoring breakdown per entity, and advances qualifying entities' pipeline stage with the score and the reason written to the record. Weights, decay rate, threshold, and stage rules all live as configuration you can edit, not code.
WHAT YOU GET
- One composite score per entity: weighted signals, plus engagement warmth, minus recency decay
- A ranked shortlist sized to your capacity, with an explicit inclusion threshold
- The full decomposition behind every rank, "why this account first" always has an answer
- Automatic pipeline advancement for qualifiers, with score and rationale on the record
- Honest cooling: an entity nobody touched for three weeks visibly descends, no manual cleanup
- A rubric that re-tunes with a config edit, not a data-science project
WHO IT IS FOR
Founders and sales leads at small B2B teams whose roster outgrew gut-feel triage but who will not buy a six-figure intent platform. RevOps leads at SMBs who are tired of defending a black box or maintaining a point sheet. Agencies and fractional operators who need one defensible prioritization rubric across a book of clients. It is not for teams with no CRM or signal stream to score, and it is not trying to be a full ABM suite.
PRICING
Pricing is a set of hypotheses we are validating in the open, not a committed rate card, and the idea is to price the ladder rather than a single number.
- Score, the always-on instrument: recurring sweeps, the ranked shortlist, and the full per-entity breakdown. Hypothesis: around $149 per workspace per month. - Score plus routing, the score wired into action: qualifiers auto-advance pipeline stages and hot entities feed the outreach and booking lines. Hypothesis: around $399 per workspace per month. - Multi-client, per-client weight rubrics across a book of accounts for agencies and fractional operators, value-metered and negotiated.
Every paid step is gated, a charge never happens without an explicit confirmation.
PROOF (the dogfood)
CORTEX's first subject is AYA's own roster. AYA's product roadmap now spans more than a hundred products, which produced exactly the problem this product solves: more prospects, partners, and signals than one founder's attention can triage. So the weekly CORTEX shortlist is the founder's own working queue, scored with AYA's own weight config over AYA's real CRM entities, and the hot names flow straight into AYA's own outreach and booking lines. We eat exactly the prioritization instrument we sell, and the product's own build already left a receipt: the deliverable pattern was quality-scored (84 out of 100, grade B) and all seven of the capabilities it composes were verified on disk before this page was written.
HONEST NOTE
Here is what is true and what is not yet. The scoring chain is built and structurally verified, and every capability it composes exists and is checked on disk. What has not happened yet is a live sweep: the composed pipeline has not yet run end-to-end against the live CRM roster, so we have structural verification, not runtime evidence. And the claim that matters most, that this ranking beats gut feel, requires a validation window against real outcomes, which has not happened either. We will not put a ranking-quality number in front of you until we have measured one on our own roster first. No live run and no spend happened in building this, and the prices above are hypotheses we intend to test with you, not settled numbers.
*This page is a specification. The capability it describes is not built yet, and nothing here is a claim that it runs today.*