ICP definition
The team chose one narrow segment for the first 30 to 60 days, filtering by industry, company profile, geography, a credible why-now trigger, and one reason the accelerator's offer was relevant.
See how a Web3 startup accelerator launched a new-market sales motion, booked three meetings in its first week, and generated more than 40 meetings in three months.
Meetings booked3 months
No prior pipeline and no playbook for the new market.
A Web3 startup accelerator was entering a new Middle East market with no established sales process, no defined ICP for that expansion, and no pipeline to build from. The immediate goal was to test whether the new market could produce qualified conversations before committing further resources.
Four pieces went in place before the first call was ever booked.
The team chose one narrow segment for the first 30 to 60 days, filtering by industry, company profile, geography, a credible why-now trigger, and one reason the accelerator's offer was relevant.
LinkedIn was used to identify companies and decision-makers matching that narrow ICP instead of building a broad list of anyone active in the region.
The first sequence led with one problem and one offer angle. Different angles were tested against response and meeting quality, then the stronger version was carried forward.
Two SalesPipeline SDRs ran LinkedIn outreach and booked meetings. A part-time AE handled qualification, proposals, and later-stage sales conversations.
This is the exact shape of problem a from-zero pod build is made for.
These are the numbers from this engagement, not an average across clients.
Meetings booked during the first week of test outreach
Meetings booked in the first three months
Proposals produced; all but two booked meetings met the qualification bar
The mechanism above didn't land all at once.
The team launched a narrow LinkedIn test, compared initial message angles, and booked three meetings.
Targeting and messaging were tightened using response quality and meeting feedback. Thirteen meetings were booked during the month.
More than 40 meetings had been booked and 20 proposals produced. This case study does not claim a client or revenue outcome because that result was not verified.
Week-one calls depended on the offer already being validated somewhere else, before the new market was ever approached. It also depended on a founder or lead available to adjust messaging and targeting in real time during the first two weeks, not through a committee.
If the offer itself is still being figured out, expect the first few weeks to be slower, that's a product question, not an outreach one. It's also a different shape of engagement if no one internally can make fast calls on messaging and targeting while the motion is still being tuned.
There was no established playbook for the new market. SalesPipeline staffed the motion with two SDRs and a part-time AE.
Calls were booked from week one here, but that depended on the offer already being validated elsewhere and fast, real-time decisions in the first two weeks. See the honesty section above for when it's likely to be slower.
The team tests a different problem or offer angle, reviews which accounts respond, and narrows the ICP or message before increasing volume.
All but two of the 40-plus meetings met the qualification bar, and 20 proposals were produced. No client or revenue outcome is claimed here.
No. This expansion used two SDRs and one part-time AE. Pod composition is sized to the market and sales motion rather than copied from another client.
Go deeper on the parts of this engagement that might apply to your team.
Bring the market you're entering and what's worked elsewhere. We'll tell you honestly how fast a motion like this could realistically move.
A Web3 startup accelerator was entering a new Middle East market with no established sales process, no defined ICP for that expansion, and no pipeline to build from. The immediate goal was to test whether the new market could produce qualified conversations before committing further resources.
Four pieces went in place before the first call was ever booked.
The team chose one narrow segment for the first 30 to 60 days, filtering by industry, company profile, geography, a credible why-now trigger, and one reason the accelerator's offer was relevant.
LinkedIn was used to identify companies and decision-makers matching that narrow ICP instead of building a broad list of anyone active in the region.
The first sequence led with one problem and one offer angle. Different angles were tested against response and meeting quality, then the stronger version was carried forward.
Two SalesPipeline SDRs ran LinkedIn outreach and booked meetings. A part-time AE handled qualification, proposals, and later-stage sales conversations.
This is the exact shape of problem a from-zero pod build is made for.
These are the numbers from this engagement, not an average across clients.
Meetings booked during the first week of test outreach
Meetings booked in the first three months
Proposals produced; all but two booked meetings met the qualification bar
The mechanism above didn't land all at once.
The team launched a narrow LinkedIn test, compared initial message angles, and booked three meetings.
Targeting and messaging were tightened using response quality and meeting feedback. Thirteen meetings were booked during the month.
More than 40 meetings had been booked and 20 proposals produced. This case study does not claim a client or revenue outcome because that result was not verified.
Week-one calls depended on the offer already being validated somewhere else, before the new market was ever approached. It also depended on a founder or lead available to adjust messaging and targeting in real time during the first two weeks, not through a committee.
If the offer itself is still being figured out, expect the first few weeks to be slower, that's a product question, not an outreach one. It's also a different shape of engagement if no one internally can make fast calls on messaging and targeting while the motion is still being tuned.
There was no established playbook for the new market. SalesPipeline staffed the motion with two SDRs and a part-time AE.
Calls were booked from week one here, but that depended on the offer already being validated elsewhere and fast, real-time decisions in the first two weeks. See the honesty section above for when it's likely to be slower.
The team tests a different problem or offer angle, reviews which accounts respond, and narrows the ICP or message before increasing volume.
All but two of the 40-plus meetings met the qualification bar, and 20 proposals were produced. No client or revenue outcome is claimed here.
No. This expansion used two SDRs and one part-time AE. Pod composition is sized to the market and sales motion rather than copied from another client.
Go deeper on the parts of this engagement that might apply to your team.
Bring the market you're entering and what's worked elsewhere. We'll tell you honestly how fast a motion like this could realistically move.