Do you need liquidity before running a volume bot?

The short answer, and the number behind it

Yes, and the reason is arithmetic rather than opinion. A constant-product pool moves its price by roughly the ratio of your swap to the pool's reserve on the side you are buying. Push 1 SOL into a pool holding 10 SOL of depth and the price moves a lot. Push the same 1 SOL into a pool holding 400 SOL and it barely registers.

A volume campaign is many swaps in both directions. In a thin pool, each one pays that impact on the way in and again on the way out, and the round trip loses the spread twice. Multiply by a few hundred swaps and a meaningful share of the budget has been converted into price movement that nets back to nothing.

Here is the shape of it, using a swap of 0.15 SOL, the default band on this site:

These are illustrative rather than exact, because concentrated-liquidity and dynamic-fee pools behave differently from a plain constant-product curve. The direction is what matters: impact scales inversely with depth, and it compounds across every swap.

Thin pools do not just cost more, they fail more

The second cost is one people rarely connect to liquidity. Slippage failures are largely a depth problem in disguise.

If a swap moves the price by more than the tolerance you set, the transaction reverts. In a thin pool your own swap is generating most of that movement, so you are effectively failing against yourself. Widen the tolerance and the swap lands at a worse price; keep it tight and you pay the fee for a transaction that produced nothing.

This is measurable. We sample finalized blocks weekly and count execution errors per venue, and the spread between contested shallow venues and established deep pools is not subtle. The current figures and the method are on the measured data page. The practical takeaway is that a campaign's failure rate is decided substantially before it starts, by the depth of the pools it will route through.

How much is enough?

There is no universal figure, but there is a usable test that takes about a minute.

1. Decide what a realistic buy looks like. Not your biggest hope, the ordinary case. For most small tokens this is somewhere between 0.5 and 5 SOL.
2. Simulate that buy. Any aggregator interface will quote it and show the price impact without executing.
3. Read the impact. If a realistic buy moves the price more than one or two percent, the pool is too thin for a campaign to be worth running yet.
4. Repeat for the sell. Pools can be asymmetric, and a pool that fills buys but chokes on sells produces a chart that only goes one way.

That test is better than any threshold anyone could publish, because it measures the thing that actually matters: what happens to the person you are trying to attract.

Depth is not the same across pool types

Two pools with identical total value locked can behave completely differently, which is why a single depth number is a poor guide on its own.

• Constant product. Liquidity spread across the whole price range. Predictable, and the reserve figure means what you expect.
• Concentrated liquidity. Liquidity placed in a range. Inside the range it is very deep; outside it, there may be almost nothing. A pool that looks well funded can be effectively empty at the current price if the range has drifted. The Meteora guide goes through what that does to a campaign in practice.
• Bonding curves. Depth is defined by the formula rather than by deposits, and it changes as the curve fills.

The consequence for planning is that you should read impact on a simulated swap, not total value locked. TVL tells you how much money is in the pool; impact tells you what happens when you trade against it.

One asymmetry worth checking explicitly, because it catches people out after a migration. A pool seeded mostly on one side can absorb trades in one direction far better than the other. Buys land cleanly, sells move the price hard, and the chart develops a staircase shape that no amount of campaign tuning corrects. Simulating both legs takes ten extra seconds and is the only way to see it, since a single depth figure averages the two and hides the problem entirely.

Spreading across pools is the cheap fix

If your token has liquidity in more than one place, routing across all of it changes the arithmetic materially. A swap that would move a single pool noticeably becomes several smaller swaps that each move their pool very little, and the aggregate impact drops accordingly.

This is why concentrating a campaign into the single deepest pool is usually the wrong instinct even when that pool is the deepest. It maximises the impact per swap, maximises the failure rate, and produces the clearest possible pattern, all at once. Spreading fixes three problems with one decision.

What to do if the pool is too thin

The honest answer is: add liquidity first, or run a much smaller campaign than you planned.

Adding depth yourself is frequently the cheapest option available and is often overlooked because it feels like a bigger decision than paying for a service. It is not: seeding a pool costs no fee and no dilution, and it fixes the constraint permanently rather than working around it every time. If that is not possible, the fallback is to shrink swap size and raise wallet count, which produces the same volume with far less impact per trade at the cost of a slightly larger rent float.

Either way, the check comes first. Paste the mint into the console on the home page and it reads every pool holding your token, so you can see what depth actually exists before deciding how much to spend against it. If the answer is that there is not enough, that is worth learning in ten seconds rather than after the campaign.