Sales intelligence API

Account firmographics that update themselves

company returns industry, employee count and range, headquarters, other locations, founding year, specialities, website and follower count. Keyed on the company ID rather than the vanity URL, so a rebrand does not orphan the record.

Companies change slowly. Re-resolving your whole account table nightly is a waste of balance; rotating through the oldest 1% each night gives complete refresh over a quarter for a few dollars, with an on-demand refresh when a deal opens.

Mapping the buying committee

Enterprise deals are lost by talking to one person. profile-search filtered on currentCompany plus a set of titles gives you the committee: the economic buyer, the technical evaluator, the person who will have to operate the thing.

Run it as several narrow queries rather than one broad one — title=CTO,VP Engineering, then title=Head of Data,Data Engineering Manager, then procurement. Each query has its own result window, so several narrow ones surface more distinct people than one wide query paged to exhaustion. Deduplicate on profile ID.

The signals worth alerting on

Three are consistently worth a rep's attention, and all three are cheap:

• Hiring. job-search filtered by companyId. Three roles posted on the team you sell into is a budget decision that has already been made.
• Company publishing. company-posts with postedLimit. Product launches, funding, new markets — announced by the company, in public, before any vendor tells you.
• People moving. A champion who changes employer is simultaneously a churn risk at the old account and your warmest possible lead at the new one. Re-resolving tracked profiles on a rotation catches it.

Route these as account-level signals into your CRM rather than as leads. A rep who opens the account and sees "posted 3 data engineering roles last week" does not need a score.

Where it fits alongside an intent vendor

Intent data platforms infer interest from anonymised browsing and sell you a probability. This is different: it is public, first-hand, attributable and much cheaper — a company either posted the role or it did not.

It is also narrower. It will not tell you that someone at an account has been reading comparison pages, and it will not surface accounts you have never heard of unless you go looking with company-search. Most teams that use both treat this as the verification layer: intent proposes, public signal confirms.

Getting signals in front of the right person

A signal nobody sees is worth nothing. Route account-level signals to the owner of the account rather than into a shared queue, and include the evidence — the job title posted, the post that was published — not just a score.

Reps act on facts they can repeat in a call. They ignore numbers they cannot explain.