Would be a lot more cheaper tbh. I run the whole thing alone with only one va doing basic stuff.
Plus 100 VAs would be so much to do deal with as human error and people not doing things the way they need to. Would be very stressful. Also paying 100 VAs to manage that many accounts. You’d need 100s or phones. 100s of phone plans. Also too many accounts on one phone can cause links.
Definitely an alternative if you can’t get JV or a private bot working. But for those that can its not worth doing.
I’ve tried it and its so much management and work compared to jarvee. Also the cost is at least twice as much which means prices are higher which makes it harder to get clients.
If I was in your shoes. Id just hire a developer to make a bot that emulates human activity and then you won’t need VAs. Probably would cost the same and hiring 100s of people for hours a month.
Just my 2 cents. Manual is not very scalable and costly.
Even the guys I know that do manual are working on bots to take the load off.
I agree. VA’s are only useful for account creation and account branding. Using them for Child-Accounts only cuts off the profit margin. Why should you hire a VA, if you can do it all automated?
Manually could go well with a small operation but would never work at full scale with a huge setup. Would be very costly and time consuming. I agree automation is needed here
July 2021 Update:
Things on Instagram have changed a lot since a year ago. Jarvee has also changed with it, but not in a way that helps us. Will explain later what I mean by this.
Here are some tips to help:
Learn how to create accounts or find a provider that can give you good accounts. In my experience using the same proxy location as the creation ip helps the warming up process immensely. I am currently testing outsourcing and crossing countries but have had lackluster results. Do not use ghost browsers or applconer to create slaves. They can make scrapers but not good slaves.
Don’t skim on the necessities just to save money. Cheap proxies, cheap accounts, cheap vps means issues when scaling. When something is cheap, there is usually something wrong with it. Proxies can be shared, ips can be blacklisted and VPS are always shared (resources).
Take it slow when starting. Learn how to grow and manage 10 slaves before scaling to 30, manage 30 before 50 etc. The more slaves, the more issues will arise. You need to know how many scrapers per slave are need to run at 100%, how many accounts you can run on the system you are using before cpu/ ram gets burnt out.
Use a server or dedicated vps. This is where jarvee hasn’t helped with its updates. As Jarvee has changed the increased need for cpu and ram has changed. When I first started I could run 100 accounts on a crappy old laptop. Now, you need a decent server to run 100. A very good server to run 150+. If the cpu or ram is throttled you will have accounts not finishing their actions, accounts stuck on ‘searching’, lagging etc.
A server helps immensely and is needed to scale. People including Jarvee support forget to mention this. They will tell you its proxies, it’s your scrapers. But will forget to mention the server. I’m hoping that my recent interactions with Jarvee support have given them more insight into the causes of Jarvee problems. Their first response is always proxies and most of the time its not. My advice is to check the task manager, look at how your CPU and RAM are performing when at full actions.
Update: I have been so busy the past few months working with a big client! We are scaling up pretty fast.
Because of this I am not taking on new clients, but can still help with Jarvee consults if I have time.
The main keys of focus people need to know about are:
Quality Accounts- I find using the same country ip to create as the one I grow them on helps 100000% more. Less blocks, less issues.
Get a great server- Jarvee needs a big processor and lots of ram. lots of issues happen when those two get maxed out. Dm me if you want to know my server provider.
Get private 4g proxies- SO, cheaper doesn’t mean better. I found out the hard way that some proxies are overshared and will cause your accounts hard when they are running at full scale. A private proxy should be able to run 10 accounts, rotate and have no issues (If the accounts are good quality).
If you can afford it, you can buy your own proxy setup. Which is what I am working on at the moment. So, I can create accounts and run them on the same ips. Its more expensive at the start, but cheaper in the long run. Plus you have more control.
*Also for those that want to buy m/s, just watch out as lots of people like to outsource it. This means they get someone to do the hard work and they pretend it’s them. I’m not against the idea of it, but I do think people should know how many people are through the chain before they actually get contact with the guy in charge of the marketing. I would never let someone outsource my work, but if I had to I would like it to be known to the client. So, everything is on the table.
Good luck to anyone just starting out! It’s starting to get a little easier to start from scratch.
I run 10+ accounts per proxy. But only allow 30 eb browsers to run at once so the amount of accounts I have makes it so that most accounts won’t act at the same time, if on the same proxy.
That’s interesting. Of your 10 accounts, what Follows do they tend to hit max per day at full capacity? I am using 5 child accounts per 4G, running 18 hours per day hitting 195+ Follows each account. Wondering if your approach could be more cost-effective?
I usually hit 150 but that’s because ive always had issues with jarvee and going over 150 follows. Maybe some of my very old accounts could. But, my newer ones would all die. I tried 200 on one account a few weeks ago and it got locked out.
The proxies need to be private though as a lot of providers share them. So, if you have 10 and another person has 10 you are in trouble.
I see! I use my own 4G proxies so they are private for sure. Only thing is I use API as much less blocks, and with Jarvee there seems to be no way to limit concurrent account API usage like you can limit concurrent EB browsers under Settings. Therefore not sure if it is an option for me … EB gets too many blocks the way I run it lol
I’m the opposite haha. no blocks on EB, only just trialing api atm.
My api accounts easily hit their daily follow goals though. EB is very slow and murders my cpu.
Yeah, the concurrent browsers plays a big difference. I remember having an issue with EB being to slow and Jarvee support told me to increase the concurrrent browsers… MASS CAPTCHA lol
Update:
After the big wave a month ago I lost a few hundred accounts in total, It’s been a hard road trying to get more loaded up and figure out how to stop the captcha onslaught.
Ive have fully switched to api and with 60-70 follows everything is stable. I am now starting to push them back up to 100+ and add in dms to get my client back on track.
My advice for these big waves is to stop everything and wait a few days. Wait till things calm down and you can see the issues people are having on this forum. Then start slowly and test the waters till you get things running again.
Test: Settings. limits, proxies, tools and see what works best.
DO NOT START UP ALL YOUR ACCOUNTS AT ONCE! START ANY TOOL OR ACCOUNTS UP SLOWLY!
Been a rough few months on the IG field but things are becoming stable. Limits are lower but things are running well.
I’ve decided to go away from the fitness industry for abit and work on some other niches. Need a break and something fresh and exciting. Atm I am working on an art account and its growing faster than anything Ive seen!
I will be putting a Mother/Child advert up in marketplace soon. But only limited slots available.
Atm my warmup process is a week longer than it used to be and I’m finding 80 follows a day a safe amount of actions. I have a few slaves doing 100 but not all.
Been focusing on higher follow backs so less follows still works.
Usually wait for a certain limit but atm things are abit tempermental so im doing less UF. Really depends on how old the accounts are and how many accounts share the same proxy.