It starts with one API key and a good idea. Six months later your team owns a place to hold the values, a check on who may be looked up at all, a score nobody fully trusts, a queue, a spreadsheet of who is doing what, and an approval step that lives in Slack. None of it is the product you sell. All of it is on the roadmap anyway, because without it the feed is just rows.
That middle is Runner. It is the record, the gate, the fit reading and the next move, with a person approving the part that matters. As of this week it takes your Crustdata key, so the feed you already pay for lands somewhere that is finished.
What you get the day you connect
- Company depth where the free sources run out: industry, size and country from a domain, spent only when a public registry had nothing to say.
- People filled in from the profile you already hold: name and title, read on your key, behind a gate decided for that one contact.
- A fit reading against your own ICP with the reasons shown, and one next move proposed every time, so a rep opens the record knowing what to do.
- A receipt for every lookup: the source, the time it was read, the confidence and the cost. That is the sentence your buyer’s counsel asks for, and Runner shows it on a screen.
You decide the order, the floor and the ceiling
Runner tries the free registries first and your vendors after them, and stops at the first answer it is sure enough of. Per field, you choose the order of sources, the confidence it must reach, and the most a record may cost. The paid rung earns its credit or it is not spent.
Every lookup shows its receipt
Each source in the order it was tried, what it answered, and what it cost. A vendor you have not connected is shown as skipped with a link to connect it, so the gap is a click rather than a mystery. Nothing lands on the record until a person accepts it, and every accepted field keeps its provenance for as long as the record lives.
It lands, reads fit, and hands you the next move
On a contact, Enrich fills what it can on the record itself and tells you where each value came from. Then it reads fit against your ICP, says why in plain language, and proposes one next move: an intro email, a working address, or the company link that makes the ICP checkable. Your team spends its time on the conversation, not on the spreadsheet.
Why procurement says yes
- Speed: the middle is finished, so the first useful record is the day you connect, not the quarter after you hire for it.
- Control: every value is a suggestion with a source until a person accepts it, every field has a spend ceiling, and the order is yours to change.
- Defensibility: every person lookup runs behind a gate decided per contact, for jurisdiction, suppression, and never anyone on your own team. The Crustdata person rung reads only a profile already on the record; Runner never searches a professional network for someone it has no profile for. Exports respect the vendor’s terms. The gates are product surfaces you can show, not plumbing you have to describe.
Who this is for
Teams building an AI SDR, a recruiting platform or a sourcing tool on a data feed: keep the feed, drop the build. Runner connects to the same key and gives you the middle finished, with the gates on.
Revenue teams that want the feed without the engineering: this is the product, and your first lookup is a key paste away.
Teams selling into the EU, the UK or Korea, where the first question is not “what can you find” but “show me the gate”.
The feed answers. Runner is what you do next.
Connect a Crustdata key under Settings, Integrations, Enrichment providers, run one lookup, and read the receipt. If you are not in Runner yet, build your team and bring the key with you: runtheworld.ai/vs/crustdata
Give your business a growth team.
Create your account and pick a plan. Your team is built once the plan is paid.
