BDGL / Insights / Team

Business development as a service, and what it cannot cover

Business development as a service, and what it cannot cover

The model sits between a consultant who advises and a salesperson who sells. That gap is real, and so is the set of things it quietly cannot do for you.

Business development as a service is a rental arrangement. You pay a monthly fee, and in return a team outside your company runs some part of the work that would otherwise sit with a salesperson you have not hired. That is the whole model. Everything interesting is in which part.

The phrase gets used for three different arrangements that behave nothing like each other, and buyers routinely sign for one expecting another. It is worth separating them before comparing anything to anything.

Three things sold under one name

The first is list and outreach. A provider builds a target list, writes sequences, sends them, and hands you replies. The deliverable is meetings in your calendar. This is the most commonly sold version and the cheapest to run, because it can be staffed by people who never need to understand your product past the first reply.

The second is full-cycle representation. The provider takes the first call, qualifies, and sometimes runs the pitch. The deliverable is a qualified pipeline rather than a raw meeting. It costs multiples of the first because the people doing it have to be able to hold a conversation with your buyer without embarrassing you.

The third is system building. The provider does not sell at all. They construct the target definition, the message, the sequence, the CRM structure and the measurement, run it long enough to prove it works, and hand it to your own hire. The deliverable is a repeatable process, and it is the only one of the three that leaves anything behind when the contract ends.

Most disappointment with the model comes from buying the first and expecting the third.

What this covers
What this covers

Against a consultant

A consultant tells you what to do. The service model does it. That sounds like a straightforward advantage until you notice what the consultant arrangement forces: because they cannot execute, they have to make the plan legible enough for your team to run. The knowledge lands with you by necessity.

The service model has the opposite property. Execution happens elsewhere, so the learning accumulates elsewhere too. If the relationship ends after eighteen months, the consultant leaves you a process your team has been running. The outreach provider leaves you a spreadsheet and a gap.

This is not an argument against the service model. It is an argument for reading the contract for what transfers, which is a question almost nobody asks during procurement and everybody asks at renewal.

Against an agency retainer

The comparison people actually want is against a marketing retainer, because both are monthly fees paid to an outside team for something that is supposed to produce revenue.

The difference is what gets measured and how fast. A marketing retainer is generally judged on leading indicators for months before anything reaches a sales conversation, which is legitimate but slow. Business development as a service is judged on booked meetings, which shows up inside a quarter and is much harder to dress up.

That speed cuts both ways. It makes a bad provider obvious quickly, and it also pushes providers toward whatever books meetings fastest, which is not always what builds a business. A meeting with a badly qualified prospect still counts on the invoice.

The structural questions are close to identical in both cases, and the marketing side has thought about them for longer. KF Agency has a useful breakdown of the clauses that decide how an agency engagement goes, in Arabic, at their scope of work template for a marketing agency engagement. The clause logic there transfers almost unchanged to a business development contract, and it is worth reading before you sign one.

At a glance
At a glance

What never transfers

Three parts of the job stay with you no matter what the contract says.

Pricing. A provider can carry your price to a buyer. They cannot decide it, and they cannot defend it under pressure the way someone with margin responsibility can. Every outsourced arrangement eventually meets a prospect who asks for a discount, and the answer has to come from inside your company.

Product truth. When a prospect asks whether you can do a thing you have never done, the honest answer requires knowing your delivery capacity this month. That knowledge sits with your operations, not with a provider reading a battlecard.

Legal accountability. This one is not a matter of preference. If your outreach touches personal data of people in the EU or the UK, you are the controller and the provider is your processor, and the GDPR is explicit about what that means. Article 28 requires that you use only processors providing sufficient guarantees to implement appropriate technical and organisational measures, that the processing be governed by a binding contract setting out the subject matter, duration, nature and purpose of processing and the categories of data subject, and that the processor not engage a sub-processor without your prior written authorisation.

Read that last clause again in the context of how outreach providers actually work. Many of them use a data vendor, an enrichment tool and a sending platform, each of which is a sub-processor. If your contract has a general authorisation, the provider still has to notify you of intended changes and give you the chance to object. If you have never received such a notice from a provider who has obviously changed tools, the contract is not being followed.

When the model fits

It fits well in three situations.

You have proven demand and no capacity to work it. Somebody is already buying, inbound arrives, and nobody has time to chase the half of it that goes cold. That is a volume problem and renting volume solves it.

You are testing a market you do not know. Hiring a salesperson for a market that may not work is an expensive way to find out. A three month engagement is a cheaper experiment, and the exit is clean. Our note on the first 90 days of business development covers what a test like that should be expected to produce.

You are a partner-led or consulting firm where the founders sell and cannot stop. This is common and the constraint is real: business development for consultancies without a sales team is a genuinely different problem, because the thing being sold is partly the person selling it.

When it does not

It fits badly when you have not yet worked out who buys and why. A provider will happily build a list against the definition you give them, and if the definition is wrong you will pay for six months of well-executed outreach to the wrong companies. That is a system problem rather than an effort problem, and no amount of rented effort fixes it.

It also fits badly when the real decision is a hire you keep postponing. The honest comparison between the two is set out in outsourced BD versus hiring a salesperson, and the readiness tests in when to hire your first salesperson are worth running first. If you pass them, hire. The service model is not cheaper than a salesperson over three years, and it is not supposed to be.

Honest limits

Two things this piece does not give you.

It gives you no price. Rates vary by market, by whether the provider is offshore, and by which of the three models you are buying, and any single figure quoted here would mislead more people than it helped. Ask three providers for the same scope and the spread will tell you more than a benchmark would.

It also does not tell you whether the model works, because that question has no general answer. It works when the constraint it removes is genuinely your constraint. Most of the failures we see are not bad providers. They are correct answers to a question the buyer had not actually asked.

Read next