The five steps
You send your website.
One field. Your contact details go on the next screen, not into a link. I read your site and work out who you sell to.
I answer in one business day, yes or no.
A yes comes with who I think your buyer is and what I would say to them. You see it before you have spent anything.
You approve two things on one screen.
The companies, named or described by criteria you sign off, and the exact first message, word for word. Your monthly cap is written down at the same time. Nothing is sent before all three.
The list opens in slices.
A first slice goes out, and you see what came back before the rest is released. A message that isn’t landing costs you a slice, not your market.
Replies come straight to you.
Email arrives in a mailbox on a domain you control. LinkedIn threads are sent to you every week in full, with names, dates and complete text, including the ones that went nowhere, and any thread on request the same day.
I am not going to tell you how long the first one takes. Nobody has run a month of this yet, and a date I invent is worth less to you than the admission that I don’t have one.
There are no calls in this
no discovery, no kickoff, no check-in
No discovery call, no strategy session, no kickoff, no weekly check-in, no quarterly review. Meetings are what a retainer has to produce in a month when nothing else did. This is invoiced by the warm conversation, so the time goes into the list and the messages instead.
The rule binds me, not the BDR. If the person working your account needs half an hour with your team to learn how your buyers talk, they’ll ask and you can say no. What you won’t be asked to sit through is a meeting whose purpose is to sell you something.
What approval actually covers
Two things go out under your name, so two things need your signature. Everything after that runs inside a boundary you set in writing.
- The companies. I draft the list from your site and tell you the source behind every name on it. You cut what you don’t want. Nothing outside the approved list is touched.
- The first message, word for word. Not a template, not a direction of travel. The sentences that will be sent.
- Written reply rules. What a BDR may say when someone answers, what they may offer, and where the edge is. A person writes the replies; the rules say what they are allowed to write.
- Anything outside that boundary comes back to you before it is sent. If you would rather approve every outgoing message instead, I’ll do that. It is slower and it produces fewer warm conversations.
Your monthly cap is agreed here too, in writing, before anything is sent. It is a ceiling on how much goes out, not a promise of what comes back.
The cap, the notice period and the strike windowWhat you get, what you set up
what arrives
- A proposed target list, with a named source behind every company, before you approve any of them.
- The exact first message, word for word, for your approval.
- A position line on the BDR’s profile, worded by you, down within five working days of the account ending.
- Every thread weekly, in full, including the ones that went nowhere, and any single thread on request the same day.
- Replies in a mailbox on a domain you control.
- A monthly statement showing which replies were billable and which weren’t, and seven days to strike any line.
what you set up
- A separate sending domain for cold volume. Yours or mine, settled per account. It is never the domain your invoices come from, and if you ask for that I’ll say no.
- Time to warm that domain before email starts. LinkedIn can start immediately; email can’t, and anyone who says otherwise is spending your domain reputation.
- Someone who can take a conversation within a week of it happening.
- About forty minutes when you approve, and twenty a month on the invoice.
Who does the outreach, and from where
A contract BDR works your account. They are contracted to Deal Baker Ltd, not to you: no headcount, no seat, no notice period, no interview. What you inspect instead is the list before it’s used, the message before it’s sent, and every thread afterwards. If the account isn’t working, say so and I change who is on it.
- Nobody logs into your LinkedIn. Not me, not the BDR, not once. Sharing credentials breaks LinkedIn’s User Agreement and puts your account at risk.
- Email goes from a separate sending domain, never your primary one. Who registers it is settled per account, and you can have it pointed away the day you ask.
- LinkedIn goes from the BDR’s own account, carrying a position line that names your company and the word contract. You word it before it goes up.
Who writes which message
You approve the first message word for word. After that a person writes the replies in their own words, inside the written rules you set, and you read every line in the weekly export.
what a BDR will never say
- Claim to have used your product, built it, or solved the prospect’s problem themselves.
- Say “we” about work they weren’t part of.
- Present as your employee. The answer is one sentence, “I do business development for your company on contract”, and you approve that sentence too.
where the software stops
- Not who gets contacted. That is the list you approved; nothing outside it is touched.
- Not what the first message claims. Personalisation fills blanks you can see in the draft.
- Not the reply. Once a person answers, a person writes back.
- Not anything of yours. Nothing of mine connects to your CRM or mailbox unless you connect it.
Software does the finding, the list-keeping, the sending, the drafting and the monitoring. The four above are what it is never allowed to decide.
What happens to the data