A separate service for people who have accounts but no time or understanding: you warm the fleet, watch for restrictions, replace losses and keep it working.
Your cost base
The subscription divides across all clients at once. Proxies and accounts are either theirs or yours, and those are materially different models: in the second you carry the attrition risk and the price has to cover it.
The main line is time. Running a fleet is not set-and-forget: status checks, reacting to restrictions, replacements, reporting. Count the hours honestly or you will discover in a month that you are working for less than you thought.
What the client is buying
Not actions — the absence of a problem. They do not need to know about warm-up or flood waits; they need the accounts to be alive and working. Selling a list of operations therefore misses the point: what sells is the outcome and the predictability.
Setting the price
Cost base, plus a margin for attrition, plus your hourly rate times the hours. Compare the result with what doing it themselves would cost the client, including their own early mistakes — that is your argument in the negotiation.
Where it breaks
When one person takes on too many clients. Management looks easy while everything works; the week three clients hit restrictions at once, it stops looking easy. Cap the number of projects in advance — a refusal is cheaper than a reputation.
Agree the awkward parts up front: who replaces lost accounts and at whose cost, where session files live and what happens to them when the work ends. Session files are full access to an account, and raising that yourself is the best advertisement for your reliability. The protections themselves are on the automation page.