Resources
How the work actually works — written down.
Salty twists through tangled data and comes out holding the leads.
Guide 1 — How we verify a lead list
We start from your ideal customer profile and research matching companies and decision-makers across sources the companies themselves publish. Every record is verified and confidence-labeled at build time — title currency, company fit, email validity — so you're not paying for a raw scrape or a guessed address. Zero pattern-guessed emails, ever.
Any address that hard-bounces on your first send is replaced free — and so is any row that plainly doesn't match your approved spec. Send us the bounce report or flag the rows and we rebuild them.
Guide 2 — Writing the spec before anything builds
You describe the target — industry, size, geography, the titles that buy.
We draft your spec + market report — sent in writing within 1 business day, including the ROI metric your engagement will be judged on. You approve the spec; nothing builds before approval.
Three things we need from you: (1) your approved spec — no meeting required; (2) examples of your best current customers, if you have them; (3) any do-not-contact list or excluded accounts. We handle everything after that.
Guide 3 — Reading your ROI Report
Every engagement's spec names its headline metric — cost per verified contact, cost per reply, hours returned, pipeline per dollar. Your report shows the arithmetic on labeled inputs: what we measured (rows delivered, messages handled, response times) and what you reported from your own systems (replies, pipeline). We never publish your numbers or fold them into our marketing. The report exists so you can judge renewal on evidence, not on our say-so.
What you receive: a spreadsheet or CSV you own — contact name, job title, company, verified business email, phone (direct-dial where available, otherwise company line), industry, employee count, location, website, LinkedIn URL where available — plus the spec, QA notes, and your ROI Report.
Sources & labels — how numbers on this site work
Every number here is one of three things, and it is labeled as what it is. Our own offer and process facts — prices, counts, timelines — are stated plainly. An external figure always carries its source next to it. A figure we modeled rather than measured is always labeled [ESTIMATE]. If a number has no source and is not ours, it does not ship.
The Method — how every engagement runs.
No meetings. A metric named before work starts. Every row verified at build time. Bad rows replaced free. The four positions behind every list we ship — published in full, with the reasoning and the process for each.
Glossary — every term we use, defined once.
Spec, checkpoint, headline metric, bad row — the words on this site mean the same thing on every page, and they're all defined in one place, in plain English.
ROI calculator — run your own numbers.
Pick a product, enter your own reply rate, close rate, and deal value, and see the arithmetic — cost per verified contact, cost per reply, cost per deal — with every result labeled an estimate and every assumption listed. Your numbers, not ours.
Worked examples — the shape of an engagement, end to end.
Two sample engagements walked through every stage — sample spec, sample build, sample checkpoint, sample QA notes, sample ROI Report. Every number is a labeled sample; the shape is exactly how the work runs.
For MSPs — territory supply, one metro, one MSP.
500–750 fresh verified contacts a month in one metro, a quarterly full-territory refresh, and exclusivity in writing — the Territory Retainer, written for managed service providers.
For agencies — white-label supply your clients never see us in.
1,500 verified contacts a month, unbranded in your format, with QA notes your clients can read — the Supply Retainer and its volume tiers, written for agencies.
Updates — what shipped, dated.
The public changelog: every page, product, and system we ship, dated as it lands — starting October 2026.
How we handle data — sources, labels, storage, removal.
Where lead records come from (published sources only), how each one is confidence-labeled, where data is stored, and how to get a record removed — stated plainly, matched to the practice.
Support — where to get help.
Questions about a list, an app, the board, the coin, or your data — every support route in one place, all of it in writing.
Sample artifacts — the documents, labeled inside and out.
The sample spec, a 10-row sample list excerpt, and the sample ROI Report — each shown as the document a client receives, and each labeled as a sample inside the document itself: in its header, in its rows, and in its footer. Not just in the caption around it.
Salty stamps SAMPLE on the header, the rows, and the footer — a label that only sits around a document washes off; his is printed through it, like the watermark in good paper.