Public signal first
We rely on company-level events, filings, job activity, and other public evidence. The product explains every lead with the signals that triggered it.
Methodology
MandateSignal combines public company signals, niche-specific scoring, and a QA gate before a digest goes out. The goal is not volume. The goal is to show recruiters why a mandate is likely to exist and what to do next.
We rely on company-level events, filings, job activity, and other public evidence. The product explains every lead with the signals that triggered it.
The value is timing. The system tries to identify openings before the formal requisition shows up, then ranks the most plausible companies and roles.
MandateSignal measures its own prediction quality and publishes that result in the methodology surface instead of asking buyers to trust a black box.
Candidate data is handled only with attested consent. Candidate-ripeness features stay gated until the legal review is complete.
Signal sources
Company announcements, leadership moves, filings, hiring patterns, and other public events that tend to precede a search brief.
QA gate
The lead QA agent blocks bad digests. If the evidence is thin or the confidence floor is not met, nothing ships until the recipe is corrected.
Limits
Candidate-ripeness detection is intentionally gated on legal review. Public trust matters more than feature count.
FAQ
The lead has to clear a confidence floor and show a readable evidence trail. If the evidence is weak, the QA gate blocks the digest instead of sending noise.
No. Job boards list posted openings. MandateSignal tries to predict which companies are about to post and gives recruiters a timing edge.
Yes. The methodology page is meant to show the hit rate, the inputs, and the limits of the model so the product earns trust in public.
Public methodology exists so buyers can see the difference between a prediction engine and a generic list. When the hit rate changes, the page should explain why.