Worked Examples
Two engagements, walked end to end – the sample spec, the sample build, the sample QA notes, and the sample ROI Report – so you can see the shape of the work before you ever start it.
Salty twists through tangled data and comes out holding the leads.
Worked examples, not case studies.
Every company, person, and number below is a sample invented to show the shape of the work – R.O.I.C.P. publishes no client results. Nothing here is a promise, either: no results are guaranteed, on this page or anywhere on this site.
Salty counts the client results on this page: zero – because there are none yet, and he never seasons a sample into proof.
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.
Example A — A First List, end to end (sample)
A fictional managed service provider – call it Sample MSP Co. – wants its first prospect list. What follows is the full path every First List takes: spec, build, checkpoint, QA notes, ROI Report. The path is real. Everything on it is a sample.
A1 · The sample spec
It starts with the free Spec & Market Report. The sample report counts 212 sample matching decision-makers in the sample market – a sample count, from a sample count of a fictional market. The sample spec the sample client approves in writing:
- Sample client: Sample MSP Co., a fictional managed service provider.
- Sample market: Sample Metro – a fictional mid-size metro, named as a sample.
- Sample ICP: professional-services firms – sample law firms, sample accounting firms, sample clinics – with 10–50 sample employees.
- Sample titles that buy: Owner · Managing Partner · Office Manager · Operations Manager.
- Sample exclusions: the sample client's sample competitors, and its own sample customer list (a do-not-contact list, per the standard intake).
- Headline metric: cost per verified contact – the metric this sample engagement will be judged on, named before any build.
Nothing builds before this sample spec is approved in writing. That part is not a sample – it is the rule on every engagement.
A2 · The sample build
The sample build produces 150 sample contacts – the First List's published size, filled here with sample rows. Each sample row is checked at build time – title currency, company fit, email validity – against sources the sample companies themselves publish. Zero pattern-guessed sample emails. Every sample row carries a confidence label; the sample build's labels land at 96 sample HIGH · 41 sample MEDIUM · 13 sample LOW. Three sample rows, exactly as they would appear in the sample file:
Sample row 1 – Sample Person 1 · Owner · Sample Company 1 (a sample law firm) · email basis: the sample firm's own published contact page · confidence: HIGH (sample)
Sample row 2 – Sample Person 2 · Managing Partner · Sample Company 2 (a sample accounting firm) · email basis: the sample firm's own published team page · confidence: MEDIUM (sample) – sample note: title confirmed at build time; the published email path is the firm's partner page, not a direct listing
Sample row 3 – Sample Person 3 · Office Manager · Sample Company 3 (a sample clinic) · email basis: the sample clinic's published general inbox · confidence: LOW (sample) – sample note: general inbox, flagged in the open, never smoothed over
A3 · The sample checkpoint
Before the sample build completes, the first 25 sample rows of the actual sample build go to the sample client for approval – 17 sample HIGH · 8 sample MEDIUM. Not a teaser and not a separate sample of the sample: the real first rows of the build the sample client is paying for, judged before the rest are built.
Approval looks like this – a sample reply, in writing: "Sample approval – the 25 sample rows match the sample spec. Build the rest." If the sample rows missed the sample spec, the build would stop here and the spec would be fixed first. The checkpoint exists so a wrong build stays a checkpoint-sized conversation, not a full-build problem.
A4 · The sample QA notes
QA notes ship with the sample file, including the rows we downgraded and why. Three sample notes:
- Sample downgrade 1 – Sample row 44: HIGH → MEDIUM (sample). The sample person's title on the sample company's own site changed between research and build; the label follows the published source at build time.
- Sample downgrade 2 – Sample row 97: MEDIUM → LOW (sample). The only published email path for the sample company was a general inbox; flagged, not hidden.
- Sample bad-row replacement – Sample row 112 hard-bounced on the sample client's first send. Rebuilt to the same standard and replaced free; the sample replacement row is verified the same way and labeled HIGH (sample). This note lands after the first send – the replacement promise runs on every list, sample or otherwise.
A5 · The sample ROI Report
Every engagement ends with an ROI Report: what it cost, what it produced, what it returned – arithmetic shown, on labeled inputs. The sample report for Example A:
- Cost: $249 – the published First List price. A fact, not a sample.
- Measured by us (sample build): 150 sample verified contacts delivered · 25 sample checkpoint rows approved before the build completed · 1 sample bad row replaced free after the sample client's first send.
- Cost per verified contact (sample arithmetic): $249 ÷ 150 sample contacts = $1.66 per sample verified contact – the headline metric, computed on sample counts.
- Reported by the sample client: nothing on a First List report. Replies are the sample client's to count in their own systems; client-reported numbers enter the picture on retainer reports – see Example B.
Inputs labeled – measured by us, reported by the sample client. Your real report runs on your real numbers, and we never publish them.
Example B — A Supply month, end to end (sample)
A fictional agency – call it Sample Agency Co. – runs client campaigns on a Supply Retainer and takes its lists white-label. What follows is one sample month: the setup, the drop, the refresh, and the sample ROI Report the month closes with.
B1 · The sample retainer setup
The sample engagement runs on the Supply Retainer – $750/mo, the published price. The sample spec, approved in writing before the first sample drop:
- Sample client: Sample Agency Co., a fictional agency reselling lists under its own brand – so every sample file ships unbranded, in the sample agency's format.
- Sample supply: monthly sample drops built to the sample ICPs of the sample agency's sample campaigns, plus a monthly refresh of prior sample drops.
- Headline metric: cost per reply – named in this sample spec, because this sample engagement is judged on the replies the sample lists produce, not just the rows they contain.
B2 · The sample monthly drop + refresh
The sample month's drop: 1,500 sample contacts, built and verified to the same standard as Example A, delivered as a clean sample file in the sample agency's format.
The same drop refreshes the prior sample drop: every prior sample row is re-checked against the sample companies' published sources. In this sample month, 112 sample rows had gone stale – sample people changed roles, sample companies moved – and 112 sample replacement rows shipped in the same drop. The sample client also flagged 3 sample bad rows from the prior sample drop; all 3 sample rows were rebuilt and replaced free.
B3 · The sample ROI Report
The sample month closes with its sample ROI Report – the same shape as Example A, with one difference: on a retainer, the sample client reports what the sample lists produced in their own systems, and those inputs are labeled as theirs.
- Cost: $750 – the published Supply Retainer price for the sample month. A fact, not a sample.
- Measured by us (sample month): 1,500 sample contacts delivered · 112 sample refresh replacements · 3 sample bad-row replacements.
- Reported by the sample client: 41 sample replies · 6 sample deals – the sample client's own sample numbers, from their own sample systems. Their numbers, never ours to invent – and never published by us.
- Cost per reply (sample arithmetic): $750 ÷ 41 sample replies = $18.29 per sample reply – the headline metric, computed on client-reported sample inputs.
- Cost per deal (sample arithmetic): $750 ÷ 6 sample deals = $125.00 per sample deal.
In this sample, the sample client judges renewal on the $18.29 per sample reply. In a real engagement that judgment is yours, on your real numbers – which is the entire reason the report exists.
<
The sample artifacts — the documents themselves
The walk-throughs above tell the story. These are the documents the story produces – a spec, a list excerpt, an ROI Report – restated in the shape a client actually receives them, so you can inspect the paperwork before you ever commission it. Each one is labeled as a sample inside the document – in its header, in its rows, and in its footer – not just around it. The label is part of the artifact.
Artifact 1 — Sample Spec
Artifact 2 — Sample verified-list excerpt
Artifact 3 — Sample ROI Report
Questions about an example? See Support
Start with the report. Judge us on the numbers.
Your market is countable. Your return is measurable. Start with the free Spec & Market Report – we'll draft your spec and tell you honestly how many matching decision-makers exist, before you spend a dollar.