The Method

Four operating positions, published as practiced. This is how every R.O.I.C.P. engagement runs — the same standard whether you start with a free market report, a $249 First List, or a monthly retainer.

Salty twists through tangled data and comes out holding the leads.

No results are guaranteed — not meetings, not replies, not sales. What we stand behind is the data and the process: spec approved before build, verified at build time, bad rows replaced free.

Questions about the method? See Support

Worked examples — the shape of a finished engagement, end to end.

M1 — No meetings

The position. We don't book meetings. Not for sales, not for delivery, not for support. Everything runs async, in writing: spec → draft → approval → build → report. No sales call — the spec is the meeting.

Why. Meetings tax both sides: the scheduling, the waiting, the things said on a call and recorded nowhere. Writing is auditable. Your spec, our QA notes, and your ROI Report are documents you keep and can check — not conversations you have to remember. Your calendar stays yours.

How it runs.

1. You describe the target on the five-field form — two minutes.
2. We draft your spec and market report in writing, sent within 1 business day.
3. You approve the spec in writing. Nothing builds before approval.
4. We build and deliver; questions and answers stay in the same written thread.
5. The ROI Report closes the engagement — in writing.

M2 — Metric before work

The position. Every engagement carries a headline metric, agreed in writing before work starts — and reported at the end. If a number can't be named, the work doesn't start.

Why. If it can't be measured, it can't be priced honestly. A named metric is what lets you judge a renewal on evidence instead of our say-so — and it's what lets us be wrong in the open and fix it.

How it runs.

1. The spec names the metric for your line: cost per verified contact, cost per reply, hours returned, pipeline created per dollar, or a data-health delta.
2. You approve the metric together with the spec.
3. The build is measured against it as the work runs.
4. The ROI Report shows the arithmetic on labeled inputs — what we measured, what you reported from your own systems — what it cost, what it produced, what it returned.

M3 — The QA standard

The position. Every row is verified at build time, against sources the companies themselves publish — and carries a confidence label. Zero pattern-guessed emails, ever.

Why. A list is only worth what survives contact with the real world. Guessed addresses bounce, damage your sending reputation, and waste your follow-up — mailbox providers track bounces and sender reputation, and a poor reputation cuts delivery (source: Google's Email sender guidelines). We would rather ship a smaller true file than a bigger invented one.

How it runs.

1. Research starts from your approved ideal customer profile, across company-published sources.
2. Each record is checked at build time — title currency, company fit, email validity — and the basis for the email is recorded with the row.
3. Every row carries a confidence label. Conflicts are flagged, never smoothed over.
4. A First List ships a 25-row checkpoint from the actual build — you approve it before the rest of the build completes.
5. QA notes ship with the file, including the rows we downgraded and why.

M4 — Bad rows replaced free

The position. If a row is wrong, we replace it — free. That holds on every list and every refresh.

No results are guaranteed — not meetings, not replies, not sales. What we stand behind is the data and the process: spec approved before build, verified at build time, bad rows replaced free.

Why. We sell data quality, not outcomes we don't control. Your offer, your timing, and your follow-up decide replies and sales — anyone who guarantees those from a list is guessing. What we control is the data and the process, so that is exactly what we stand behind.

How it runs.

1. Send us the bounce report, or flag any row that plainly doesn't match your approved spec.
2. We rebuild those rows to the same QA standard as the original build.
3. Replacements ship free — on the first list and on every retainer refresh.