Your investor list is wrong, and it's costing you the first twenty intros

A fundraising list is not a static asset. It is a snapshot of a market that moves weekly, and the half-life of the average row is shorter than most founders assume. If you built your list in January and you are still working it in April, a meaningful share of it is fiction – and you will discover that one wasted introduction at a time.

What actually decays

Not everything rots at the same rate. Fund names are stable. Partner rosters are not. In our reading of publicly disclosed partner movements, roughly one in eight investors changes firm or role in any twelve-month window, and it clusters – a fund that loses one partner often loses two.

• Partner roster – the fastest-moving field, and the one that invalidates your warm path entirely.
• Stated thesis – funds drift a stage earlier or later between cycles, and the website is the last thing to change.
• Cheque size – a fund that wrote $250K last cycle may have a $1M minimum in the new fund.
• Deployment pace – a fund at the end of its cycle is not writing new cheques, whatever the site says.

The four-field pre-send check

Before a batch goes out, check four things per row: is this partner still at this fund, has the fund invested at your stage in the last two quarters, does your ask sit inside their cheque band, and is your warm path still live. This is tedious by hand, which is exactly why founders skip it – and exactly why it is worth automating.

A stale row costs you more than one send. It burns the warm path you would have used for the next three funds in that partner's network.

Why the failure mode is invisible

The insidious part is that a bad row produces silence, not an error. You send, nothing comes back, and you attribute it to a weak deck or a crowded market. In practice a share of your non-responses are simply mail arriving at a partner who left eighteen months ago. You cannot fix a conversion problem you have misdiagnosed as a messaging problem.

The practical move

Stop treating list building as a one-time project at the start of the raise. Treat it as a continuously refreshed input, and re-verify before each batch rather than each round. If you are doing this manually, verify in batches of twenty right before you send, and keep a dated note on every row so you know how old your information is. The founders who convert best are not the ones with the longest lists – they are the ones whose lists are true on the day they send.