Q: Can agencies use follow.
it for clients in the future?
1) Sub-accounts for clients
2) Branding, CNAME per sub-account
3) Integrations (Zapier!) on sub-account level
4) Separated follower list for each sub-account
5) Allocate follower limits to sub-accounts
Just dreaming :-)

Nick_TasteWP
May 14, 2024A: Thanks Sebastian, dreaming is good! Even the inventor of the modern toilet started with a dream :D
Regarding your points 1-3, they are already on our roadmap, please see https://trello.com/b/IaPT0XQ3/followit-product-roadmap. Note though: You mention "Branding" under question 2, that is already possible today, as all the settings are per feed/website.
For point 4, that's per feed, so it is already separate (linked to the respective feed).
Regarding point 5 (and maybe also point 1): If it's important to you that it's all separate, maybe you just create separate follow.it accounts in the first place? Or do you have specific processes for which this wouldn't be a solution?
I'm happy to learn more about your use case. Maybe we take this discussion offline? You can always email us at ("help (at) follow (dot) it"). Thank you!

Verified purchaser
Hi,
In reading your response to #5 (and #1), are you asking why wouldn't we create multiple accounts by creating separate accounts using separate codes? If so, I can answer that. For agencies, it is much more convenient to have one account with sub-accounts where we can distribute the followers as needed (2k for sub-account #1, 10k for sub-account #2, etc.). Creating separate accounts prevents us from doing this. Are you considering #5 for agencies?

Thanks MrsOwens for your follow-up question/clarifications!
Yes, it's clear that from an agency perspective, it's easier to manage all from one account, instead of several. That is already possible to a large extent, as you can have various feeds in one account, and then tailor them individually (most settings are defined on a feed level, not account level).
The case where this breaks down is if you then also want to give your clients access (then only to their respective feed of course). It's a valid point, however please note that once set up, there isn't much need for clients to repeatedly access their feed (our solution is primarily an automatic solution, not like e.g. Mailchimp where the user needs to access it every time he wants to send a newsletter). So your clients could - if there are needs for adjustments - just inform you about them, and you can change them quickly.
But still, it would be nice to give your clients access, that's understood. That's why we'll look into this as well.
The point which isn't entirely clear to me yet is the allocation of follower limits to the separate feeds. Let's assume you stack it to the max. (7 AppSumo codes), and hence have a limit of 50k followers. How they are distributed is highly flexible, e.g. it could be 1 feed with 50k followers, or 20 feeds with each 2,500 followers. I assume the scenario you're concerned about is when there's a monster feed with 50k followers, which has eaten up all your limits, so there is no room for the other feeds? You could (just brainstorming here, it's not recommended) unfollow 40k follwers from your monster-feed, so there is room again for the others. But the better option would be to go beyond the 50k limit, e.g. to 70k, and then have your client with the monster-feed pay for the 20k additional ones. We could also think about implementing a hard cut, e.g. you can specify that the monster feed can only have 20k followers, and every follower beyond that who tries to follow gets an error (but I doubt that would be a preferable solution).
Does that clarify things a little? If not, please let me know. Thank you!