Live public example
The site explains account-level buyer intent and uses fictional examples to show the workflow.
Buyer intent
Prioritize accounts with evidence your team can inspect.
Buyer intent in Pursenda is account-level evidence, not a surveillance claim. The useful screen shows what changed, where it came from, how fresh it is, how much confidence to place in it, and what action to consider next.
Configurable evidence
Scoped implementations can define evidence categories, source labels, freshness, confidence, score contribution, and thresholds.
Limited beta scoring
Scoring and calibration guide investigation and prioritization; they do not claim certain prediction.
Planned boundaries
Named-person private search identity, universal data coverage, guaranteed accuracy, automated outreach decisions, and full privacy controls are not claimed as live.
Evidence drawer
Evidence drawer
Available in configured implementations: priority changes can open to source category, observed event, date, freshness, confidence, and reason code.
Score anatomy
Score anatomy
Available in configured implementations: fit, freshness, engagement, account context, and confidence can remain separate so a seller sees what moved the account.
Signal breadth
Signal breadth
Available in configured implementations: an account view can combine approved first-party activity, account news, CRM history, list criteria, territory rules, and human notes without flattening them into one unexplained number.
Freshness and decay
Freshness and decay
Available in configured implementations: older activity can lose weight and show when a signal was last seen.
Identity boundary
Identity boundary
Anonymous account activity is not described as a named person's private search history. A person is associated only when the event and identity link are supported.
Accuracy method
Accuracy method
Limited beta: scoring is checked against outcomes, seller feedback, false positives, and stale records so teams can improve it from use.
Customer controls
Customer controls
Suppression, export, deletion, and privacy-control wording are quoted in the customer scope until the product owner and data owner approve a public baseline.
Workflow next action
Workflow next action
Live concept and configurable implementation: priority ends in a concrete action to research the account, assign an owner, start a sequence, open an opportunity, or suppress a bad-fit record.
Score anatomy
Priority is separate from confidence.
Northstar Components uses fictional sample data to show the difference between priority, confidence, freshness, breadth, and fit. The score guides investigation; it is not a claim of certainty.
ComponentContributionEvidence shown
ICP fit29 / 35Manufacturing supplier, Midwest territory, target revenue band, operations role match.
Recent activity17 / 20Account news observed July 27 with freshness rule and expiry date.
Multi-signal breadth13 / 15Two source classes, account-level identity, duplicate handling note.
Engagement12 / 20First-party content activity with identity strength labelled as account-level.
Account context8 / 10CRM history, owner note, territory, and negative-signal check.
Evidence drawer
A score has to explain why it changed.
Configured implementations can expose source category, observed date, freshness rule, identity level, confidence, contribution, reason code, owner note, and the recommended next action in the same drawer.
Priority
The account ranking that decides review order.
Confidence
How much reliability the team should place in the available evidence.
Freshness
How old each signal is and whether decay has lowered its weight.
Breadth
How many approved signal classes support the account priority.
Controls and calibration
Limited-beta scoring improves through review, not magic.
The public site does not claim perfect prediction, universal coverage, named-person private search identity, or guaranteed accuracy. Calibration compares priority with outcomes, seller feedback, stale records, false positives, suppressed accounts, and stage movement.
Fit controls
Target segment, region, company profile, disqualifiers, and account rules.
Identity boundary
Anonymous account activity is account-level unless the event and identity link are supported.
Decay
Older evidence can lose weight and show expiry or review requirements.
Next action
Research, assign owner, start sequence, open opportunity, suppress, or recalibrate.
Buyer-intent FAQ
Questions the evidence panel answers or scopes.
Where does signal data come from?
A configured implementation labels each signal by source category, such as first-party activity, account news, CRM history, territory rules, list criteria, or human notes.
Can Pursenda identify the person who searched?
No named-person private search identity is claimed on this public site. A person is associated only when the event and identity link are supported and approved for the implementation.
How is the score validated?
Limited-beta scoring is compared with qualified opportunities, wins, losses, seller feedback, false positives, and stale records so weighting can improve from actual outcomes.
How quickly does old activity lose influence?
Freshness and decay are configured by signal type. The evidence drawer shows observed date, age, freshness rule, and expiry where configured.
What happens when signals disagree?
Conflicts remain visible as evidence. Confidence can drop, the account can be routed to review, or the team can suppress a bad-fit record.
Which privacy controls exist?
Correction, suppression, opt-out, deletion, and export routes are quoted in the customer scope until the product and legal owners approve a public baseline.
Next step
Start with the workflow before configuration starts.
Use the working session to decide what belongs in the first configured version and what stays out of scope.