There are two ways to sell outbound software, and the industry has quietly split down the middle.
One approach ships everything in a single product: sequencing, data, mailboxes, warmup, inbox, AI. The other breaks the same job into separate products with separate names, separate sites and separate subscriptions. Leads over here, mailboxes over there, warmup as its own thing, an AI SDR on top.
Salesforge is the clearest example of the second model. Alongside the core product there is Leadsforge for lead data, Primeforge for Google and Microsoft mailboxes, Infraforge for private infrastructure, Mailforge for distributed infrastructure, Warmforge for deliverability and Primebox for the inbox. Instantly and Smartlead have both drifted in the same direction with data and infrastructure add-ons.
This is usually framed as a philosophical question. It is really a pricing question, and the answer depends on how much of the stack you actually need.
What unbundling genuinely buys you
It would be easy to write this as a hit piece. It would also be wrong, because the model has real merits and buyers choose it for real reasons.
You pay for what you use. If you already have a data provider you like, an unbundled vendor lets you buy the sending layer alone. Bundled platforms charge you for the data whether you touch it or not.
Each product has to compete on its own. A warmup product that is sold standalone has to be good enough that somebody would buy it without the rest. A warmup feature buried inside a suite does not face that test, and quite a few bundled warmup features would fail it.
Blast radius is smaller. If the infrastructure product has an outage, the sequencer keeps running. A monolith has fewer failure boundaries.
Switching costs are lower per component. You can replace the data provider without replacing the sequencer.
Those are not small advantages. For a team with an existing stack and one specific gap, unbundled is frequently the right call.
What it costs, once you add it up
The problem is that outbound is not one gap. A functioning programme needs a list, mailboxes, domains, authentication, warmup, sequencing, an inbox and reply handling at minimum. Buy those separately and three things happen.
The bill is larger than the headline. Take Salesforge as the worked example, using publicly listed pricing at the time of writing. Growth sits around $96 a month. Agent Frank, the AI SDR, is roughly $499 a month. Infrastructure through Infraforge runs in the region of $4.00 to $4.50 per mailbox plus around $100 for each additional dedicated IP. Lead data is metered separately through Leadsforge. Validation and personalisation consume their own credits.
A team running 50 mailboxes with the AI SDR and a modest data allowance is realistically looking at $900 to $1,100 a month before anybody sends anything. The $96 figure is accurate and it is also about a tenth of the real number. Verify all of this against current pricing pages before you plan around it, because this part of the market changes often.
The seams are your problem. When a reply lands in one product, the lead lives in another and the sending domain is administered in a third, reconciling them is work somebody on your team does every week. Vendors describe this as integration. In practice it is data living in four places with four slightly different ideas of what a lead is.
Support becomes triage. Deliverability drops. Is that the infrastructure product, the warmup product, the sequencer, or the list? Each team can credibly point at another. On a single platform that argument does not happen, which sounds trivial until it costs you a fortnight.
Metering multiplies. This is the one that surprises people. Unbundled vendors tend to meter within each product as well as across them, so you are tracking sending credits, data credits, validation credits, personalisation credits and social action credits, each with a different unit and a different top-up flow. Salesforge, for instance, meters LinkedIn activity as social actions, budgeting roughly 400 to 500 per profile per month against a 1,000-credit Growth allowance, which works out to about two profiles before you are buying more.
The comparison that actually matters
Not feature checklists. Two questions.
First: what does this cost fully loaded, at my volume, with everything I need switched on? Build the number yourself from every product page involved. Vendors quote the entry product because that is the number that wins comparison tables.
Second: how many of these products would I be buying anyway? If the answer is one, unbundled wins on price. If it is five, you are paying a coordination tax to the vendor for the privilege of coordinating it yourself.
| Unbundled stack | Single platform | |
|---|---|---|
| Entry price | Low, per product | Higher, includes more |
| Real cost at 50 mailboxes | Often $900+ across products | Usually $300–$600 |
| Logins and bills | Four to seven | One |
| Where a lead lives | Split across products | One record |
| Deliverability debugging | Cross-team triage | One vendor |
| Replacing one component | Easy | Harder |
| Best for | Teams with an existing stack and one gap | Teams building the whole programme |
Where the unbundled model is the right answer
Worth being specific, because this is not a universal argument.
If you have a data contract you are locked into, buy sending alone. If you are an agency reselling infrastructure to clients and want the infrastructure vendor’s brand out of the way, a standalone infrastructure product with a whitelabel is genuinely the cleaner architecture. If you need one very specific capability at a quality no bundled platform matches, buy the specialist.
And if you are experimenting, a $96 entry price beats a $400 one for finding out whether outbound works for you at all, even if the $96 is not the real number long term.
Where it stops making sense
The model breaks down at the point where you are buying most of the stack from the same vendor anyway. At that point you have all the disadvantages of a suite, because you are locked into one company’s ecosystem, and none of the advantages, because it is still four logins and four invoices.
That is a surprisingly common end state. Teams start with the cheap entry product, hit a gap, add the sibling product, hit another gap, add a third, and eighteen months later they are paying suite prices for a stack they assemble themselves. Nobody ever made that decision. It accumulated.
The way to avoid it is to price the endpoint at the start. Not what you need this month, but what the programme looks like running properly in a year. Then compare that number, not the entry one.
The short version
Unbundling is a real strategy with real benefits, and for a team filling one gap it frequently wins. It is also priced in a way that makes the entry point look four to ten times cheaper than the working configuration, and the difference shows up as extra products rather than a higher number on the plan you chose.
So do the arithmetic on the full stack before you compare anything. Count the logins, the bills and the credit types as well as the dollars, because each one is a recurring cost in somebody’s week. And if the honest answer is that you would be buying five products from the same vendor, you are not choosing unbundled over bundled. You are choosing bundled with extra steps.
Next: Salesforge alternatives compared, or what cold email infrastructure really costs.
Frequently asked questions
How much does a full outbound stack cost?
On unbundled pricing, a 50-mailbox programme with an AI SDR and a modest data allowance commonly lands between $900 and $1,100 a month once every product is counted. Bundled platforms covering the same scope typically run $300 to $600. Prices move, so build the number from current pricing pages.
Is it better to buy outbound tools separately or as a platform?
Separately, if you already have most of the stack and need one component. As a platform, if you are building the programme from scratch, because you will otherwise end up buying the same pieces from the same vendor with more logins and more invoices.
What is the Forge Stack?
Salesforge’s family of separate products covering outreach, AI SDR, lead data, mailboxes, private infrastructure, distributed infrastructure, deliverability and inbox management, each sold and billed on its own.
Why do vendors unbundle their products?
It lowers the entry price, lets each product rank and sell independently, and expands the addressable market to buyers who only want one piece. Those are sound commercial reasons. They are not the same as being cheaper for a buyer who needs the whole programme.