Home / Deliverables

Not "activity."
Documents you can hold.

Most agencies describe a process and show you a dashboard at the end of month one. Here is every artifact a Miles engagement produces, in its real format, before you sign anything.

Book a call
These are illustrative samples. The companies, names and numbers below are fictional, invented to show format and depth of work, not real client results. Miles is a new firm and does not have case studies yet; when we do, they will be labelled as such and named.
01 · week one

The ICP & signal brief.

The targeting contract. It defines who counts as qualified, which makes it the document the guarantee is enforced against.

icp & signal brief · v1.2 · signed off 14 May Illustrative sample

Northwind Data · targeting definition

Firmographics
B2B software, 80–600 employees, Series B–D, US & UK. Data-intensive products where pipeline reliability is a board-level concern.
Buying committee
Champion: Head of Data / Data Platform Lead. Economic buyer: VP Engineering or CTO. Blocker: Security, at contracts above $75K.
Qualified means
Firmographic match + attendee is champion or economic buyer + meeting held. No-shows excluded, two reschedules attempted.
Anti-ICP
Agencies and consultancies · pre-Series-A · companies under 12 months old · anyone running a competing platform installed in the last 6 months.

Signal stack: an account enters a campaign only when the ICP gate plus two of these agree:

New data leader <90 days Funding, last 60 days 2+ data/platform roles open Warehouse migration signal Public reliability incident Conference attendance · low precision, tier B only

Estimated addressable universe: 2,140 accounts. At observed trigger frequency, roughly 55–80 accounts enter a qualifying signal state per month, which is the real constraint on volume, and the reason we don't promise 4,000 sends a month.

Changes to this brief reset targeting and are agreed in writing. Version history is kept.

Why it matters: "qualified meeting" is where most agency relationships break down. Ours is a signed document with an anti-ICP list, not an adjective in a proposal.

02 · before every meeting

The meeting prep note.

Sent the day before every booked call. You walk in knowing why they replied, so a cold meeting behaves like a warm one.

prep note · call tomorrow 10:30 PT Illustrative sample

Vantra AI · Dana Whitfield, VP Revenue Operations

Series A · 62 employees · San Francisco · sells ML observability into enterprise data teams

Signal that fired
Series A closed ($14M, Redpoint), announced 11 days ago. Stacked with 3 open GTM roles posted the same week.
Why she replied
Email 2, the "before the AE hire" angle. Her reply: "We're hiring two AEs in Q3, what does this look like alongside that?"
What she has not said
No budget signal, no timeline, no mention of incumbent tooling. Treat as early.
Likely buying committee
Dana (champion, owns the number) → Marcus Feld, CRO (economic buyer, joined 4 months ago) → data eng lead for technical validation.
Suggested opener
"You mentioned two AEs in Q3. Are they replacing pipeline you already have, or being hired to create it?" Her answer tells you whether this is a capacity problem or a demand problem, and which of your two stories to tell.
Watch out for
New CRO four months in almost certainly has a 90-day plan he's being measured on. If Marcus joins the call, the frame shifts from tooling to "how does this make your plan land."

Do not pitch the platform in the first ten minutes. She replied to a pipeline-math argument, not a product argument.

Why it matters: the difference between a booked meeting and a useful one is whether the person walking in knows what the prospect already told us. This is the artifact that makes the meeting count, and the reason clients stop describing our meetings as "cold."

03 · every two weeks

The biweekly report.

Full funnel, including the parts that went badly. If we are behind guarantee pace, it says so at the top. You should never learn that from a renewal conversation.

biweekly report · day 44 of 90 Illustrative sample

Northwind Data · reporting period 12 Jun – 26 Jun

7 of 15 meetings day 44 of 90 on pace
MetricThis periodLast periodRunning
Prospects added6125981,842
Emails delivered1,4311,3883,977
Delivery rate98.4%98.9%98.6%
Replies51 (3.6%)44 (3.2%)128 (3.2%)
Positive replies14 (27%)11 (25%)34 (27%)
Meetings booked438
Meetings held337

What worked. The "new VP of Data" trigger segment is carrying the period: 9 of 14 positive replies came from accounts where a data leader started in the last 90 days, at a 6.1% reply rate against a 3.6% blended average. We are reallocating roughly 40% of next period's volume into that segment.

What didn't. The Series-B-and-later funding segment is underperforming badly: 340 sends, 4 replies, 0 meetings. Our read is that they already have incumbent tooling and the funding trigger alone isn't enough. We're pausing it rather than iterating. The message isn't the problem, the segment is.

One miss on our side. A reply on 18 Jun sat 31 hours before it was answered, against our same-day standard. The prospect had gone quiet by then. That's on us; the alert routing has been changed.

Needed from you: two of the held meetings scored 3/5 on fit. Fifteen minutes on what made them weak would sharpen the ICP filter for the back half.

Why it matters: the misses are in the document. An agency that only reports wins is an agency you'll be surprised by in month three.

04 · before every launch

The sequence, with reasoning.

You approve copy before anything sends. Every email arrives with the argument for why it's written that way, and what we're testing.

sequence v3 · segment: new data leader <90 days Illustrative sample

EMAIL 1 · DAY 0 · SUBJECT A/B: "your first 90" / "data reliability at {{company}}"

{{firstName}}, saw you stepped into the data platform lead role at {{company}} last month. Most people in that seat inherit a reliability problem they didn't create, and find out about it from a dashboard that's already wrong. We give data teams a 90-day read on pipeline reliability before it becomes a board conversation. Two of your peers at {{peerCompany1}} and {{peerCompany2}} started the same way. Worth 20 minutes?

Why this way: the trigger is in line one and it's verifiable, so it can't read as mail-merge. No link (step 1 links suppress placement). The peer reference is segment-level, not fabricated. CTA is time-boxed, not "book a demo."

EMAIL 3 · DAY 7 · NEW THREAD

{{firstName}}, a different angle. When we look at teams 90 days into a new data leader, the pattern is the same: nobody can say which pipelines are silently degraded, and the first real answer arrives during an incident. Wrote up how three teams found theirs before the incident: {{link}} If it's not a priority this quarter, tell me and I'll close the file.

Why this way: new thread resets the open rate. Single link, on our tracking domain. The explicit out at the end is deliberate. It raises negative-reply rate, which protects the domain and gives us cleaner segment data than silence does.

Currently testing: subject line A vs B, one variable, minimum 200 sends per arm before any verdict. Everything else is held constant. Last test, peer reference versus metric-led opener, went to the peer reference at 4.1% vs 2.8% reply.

Why it matters: you keep every sequence, subject line and test result. If you take outbound in-house next year, this is the asset you inherit.

05 · every morning

The daily signal digest.

What fired in the last 24 hours, what cleared both gates, and what's already in an inbox. This is the 48-hour clock, visible.

signal digest · thursday Illustrative sample
AccountSignals stackedDetectedStatus
Halden SystemsNew VP Data (day 6) + 3 platform roles open18h agoin inbox · 31h
Corvid AnalyticsSeries B ($30M) + warehouse migration post22h agoin inbox · 40h
Pellham Retail GroupNew CTO + 2 data roles open7h agodrafted · awaiting approval
Brightmoor HealthFunding only, second signal not found11h agoheld at gate 2
Sable FreightHiring spike, but 340 employees + logistics14h agofailed ICP gate · dropped

Yesterday: 34 signals scanned · 11 cleared the ICP gate · 4 stacked to two or more signals · 3 entered sequence within 48 hours. Two accounts were dropped on purpose: single-signal accounts are roughly 20% true positive and aren't worth a warm domain.

Why it matters: you can see what we chose not to contact. Any agency can show you volume; the discipline is in the drops.

Every one of these lands in your inbox
in the first three weeks.