Recruitment is infrastructure, not a campaign

Affiliate recruitment usually happens in bursts. Someone decides the program needs more partners, a list gets built, emails go out over two weeks, a spreadsheet tracks replies, and then the quarter moves on to something else. Six months later the same work starts again from close to zero.

The cost of that pattern is not the effort in any single push. It is everything the push forgets. Who was contacted last time. Who replied but never signed up. Who was skipped because the reviewer was not sure. Who has since started publishing exactly the content you want. None of it survives in a spreadsheet that nobody owns.

Treating recruitment as infrastructure means the state persists. Every channel we have seen has a status: qualified or not, contacted or not, replied, registered, skipped and why. That record is what lets the engine run continuously without tripping over itself — nobody gets contacted twice, and a channel that was borderline last quarter can be re-evaluated when the criteria change.

It also changes what improvement looks like. In campaign mode, each push starts from the same guesswork. With persistent state, the partners who actually convert feed back into the criteria, so the definition of a good partner sharpens with every cycle instead of resetting.

The practical difference shows up in the shape of the growth curve. Campaign recruitment produces a sawtooth: a spike of signups, then a long flat stretch. Continuous recruitment produces a slope. Neither is dramatic in any given week, and after a year they are not remotely comparable.