The fastest schedule is rarely the safest one. A platform does not judge your posts one at a time; it judges the shape of your activity, and a shape that no person could produce - instant, simultaneous, unchecked - reads as automation whatever the content says. Pace is how you keep a busy schedule inside a human shape. Three dials control it, and they work as risk controls, not as speed limits imposed for their own sake.

Typing delay: the pause between actions

Real typing has pauses. People hesitate, correct themselves, and slow down on a long word. A typing delay puts those pauses back into an automated run: a short wait between keystrokes and actions, so the work lands at a rhythm a person could have produced.

Turn it down too far and the gain disappears. A run that types a whole post in an instant, then fires the next one the same way, is a burst with a human name on it. The delay costs seconds per post and buys the one thing a burst cannot: plausibility. Content is unchanged; only the rhythm changes.

Concurrency: how many posts run at once

Concurrency is how many posts run in parallel. One at a time is the slowest shape and the easiest to read. Raise it, and the combined rate climbs even when every single post is reasonable on its own: three troops posting at once triple your rate, and the platform only ever sees the combined picture.

Keep concurrency low where the risk is highest: a new troop, a platform that just tightened its rules, or a first run after a change. Raise it only after clean runs prove the shape holds, and watch the combined rate across troops, not each troop in isolation. The scheduling craft article in this series covers that combined picture.

Approval gates: a human look before it goes out

An approval gate holds a post, or a troop's first run, until a person has looked at it. It catches what pace alone cannot: the wrong target list, a stale link, a post written for one platform landing on another. It is the last check before an action that cannot be taken back.

Approval feels like friction when everything is going well, and that is exactly when it is cheapest to keep. Use it on every first run, after any platform change, and for any post where a mistake would be public and embarrassing. Once a troop has posted clean for a full cycle, you can loosen the gate for its routine runs - and put it straight back on the moment the pattern changes.

Set the pace, then step it up slowly

The three dials work together, so set them together:

  1. Start a new troop with approval on, concurrency low, and a generous typing delay.
  2. Let it run for a full cycle before judging it.
  3. If it posts clean, change one dial at a time, not all three at once. If it fails or slows down, slow the pace first; never answer a limit by retrying faster.

That trade is the whole argument. A run that finishes a little later but posts clean beats a fast run that trips a limit, and an account that survives a platform change beats a schedule that saved ten minutes. Pace does not disguise a spammy volume as honest work - it keeps an honest volume looking like the person behind it.

This is the fourth article in the Product intelligence series. The first three covered reading your results, the scheduling craft, and what happens when a platform changes the rules. Next: failed posts are data, and how to read a failure reason instead of retrying blindly.