Starting Second Business - Remote Repair Outsourcing

vitalgeek

New Member
Reaction score
0
Location
Orlando, FL
All,

I've been thinking about it for a little while and I'm about to pull the trigger and do it.

I'm looking at starting a second company as an outsourcer for remote repair clients. I.E. you forward us their (the client's) information, we call them, provide the service with your branding, etc, and we charge a flat rate for each service. No outsourcing to India, either.

What do you think? Would you be interested? If so, what would be your major "things to look for" that would make or break your decision to go with us?
 
No offense, but I don't know you from a hole in the wall. I think I would just do it myself and keep all of the money. If remote service turns into a nice chunk of business I'd hire a tech to do it and keep most of the money. Either way, I have all of the control and all (or most) of the money.

Good luck!
 
No offense, but I don't know you from a hole in the wall. I think I would just do it myself and keep all of the money. If remote service turns into a nice chunk of business I'd hire a tech to do it and keep most of the money. Either way, I have all of the control and all (or most) of the money.

Good luck!

None taken!

Question is though, what would you look for if you were to outsource your business like this?
 
Last edited:
None taken!

Question is though, what would you look for if you were to outsource your business like this?

For me, I agree with Richmond, I would not outsource this. Remote support can be virtually done from anywhere, and close to any platform.

However, for hypothetical, I would only consider outsourcing something if it were within my state. That way, if I get screwed over, I have legal recourse. It gets much harder outside of state boundaries. I admire your enthusiasm, but there are already companies that offer this as a service.
 
None taken!

Question is though, what would you look for if you were to outsource your business like this?

OK, I'll bite. Here are a few thoughts off my head.

My perspective is that of a full time IT guy with my repair business on the side. I'm skeptical of the efficacy of remote support, particularly virus removal. However, a remote support tech that I trusted and had confidence in would expand my abilities when I'd otherwise be unavailable (or God forbid - on vacation) without the hassle and expense of actual employees or a local subcontractor who might be more likely to steal my customers.

With that in mind:

1. My customers would never know the tech on the phone wasn't a local employee of my company. No accents, no "what time is it there?", etc. BUT when asked directly the tech should have an honest but disarming response (don't lie about it).

2. My customers get the same tech(s) each time. A familiar voice, name, etc. That would also allow me to be more comfortable with the situation knowing "Joe and Brenda" are my team.

3. Rates have to be competitive to MY area. The location of your call center doesn't matter. If you can't compete with my local rates, there's no point. Likewise, if I learned you were charging lower rates somewhere else, I wouldn't complain. Not too much anyway.

4. Remote techs need to be excellent, patient and polite communicators. Not many techs are as good on the phone as they are with Windows registry. Yours must be.

5. The customer is always MY customer, never yours. They are never to be approached or contacted in any way outside the purview of a particular support job.

6. No fix, no pay. By that I mean your guys need to quickly identify situations where remote support is NOT the best option and escalate the issue to me for onsite service. Don't linger on the phone straining the customer's patience and running up a support bill. That is double true if the remote tech inadvertently creates a problem (boot loop, BSOD, etc) that they can't quickly resolve remotely.

7. Collect payment when the work is performed and settle with me on a weekly basis. Whatever name appears on my customer's credit card statement should be both generic & descriptive.

8. I might go days, weeks or even months between needing such a service. Don't forget about me in the meantime and don't expect me to pay.

9. Online access to DETAILED tech notes about each job. Much more than just "removed virus". This is another area YOUR people would have to be excellent communicators above and beyond what is normal for techs.

I'm sure I could think of another 20 points if I had time, but maybe this will get you started.
 
Last edited:
To add to what mraikes said,

I would be most concerned about your techs screwing up a job. It's my company's name on the line, not yours. Will you guys give the same effort I would or will you take shortcuts? Is there some guarantee I can fall back on in case something goes wrong?

Also, I'd need to know the work that was done(notes).

That's what I would need to know before even considering something like this.
 
To add to what mraikes said,

I would be most concerned about your techs screwing up a job. It's my company's name on the line, not yours. Will you guys give the same effort I would or will you take shortcuts? Is there some guarantee I can fall back on in case something goes wrong?

Also, I'd need to know the work that was done(notes).

That's what I would need to know before even considering something like this.

My thoughts exactly. I've worked with outsourcing before (not this business) but in the past and it is your name the person represents from start to finish you outsource your work to someone or some other company, they are getting money that you should keep. Also if you outsourced, as mentioned earlier do it in your state. A good reputation you worked hard for could get ruined in a hurry.
If I was in your shoes, I would do everything possible first to keep the money to yourself.
 
Business is like this : Techs lined up for work, but none coming in - Start a United States based Oursource company to bring in additional work from other businesses.

good idea - especially for the solo tech who just got a call at 7pm and doesnt feel like going out there, but also doesnt want to lose the customer, and now has the option to outsource to another Company with a (hopefully, eventually, ya know) good reputation, and still get some money out of it.

All good things.. might take awhile to build..... But the point is : Abilities are wasted if your sitting around not making money. so! if your not making money. do a promotion - FREE TECH SUPPORT THIS DAY ONLY.. or for 3 days or whatever. Its WASTED capacity. Fill that capacity.

However --- I have a couple of resturants as clients. 1 resturant was struggling. She just spent $5,000 on advertising and maybe saw a 5 % increase in business (which she doesnt know if that is because the advertising, or just luck) I told her - She can give me $2,500 - i'll hire 2 people to sit on a corner for a day with signs that say FREE LUNCH AND DINNER. Wasted Capacity = ZERO, New Customers coming in = a bunch (she really doesnt need to give me $2,500) and the cost per new customer was food costs, about $3.11 per customer-- she was paying her employees to sit outside and smoke.. so heck. the only real cost to this ad campaign was food.

Morale of the story

$5,000 Advertisement campaign, maybe 60 new customers that week?

Free Advertising = Maybe 50 new customers that day at about 3.00 per customer? thats $150.00 in food.. and maybe half will come back as paying customers?

wait - why was I responding to this thread? I dont remember, I got off on a rant about advertising and the wasteful spending of businesses. ANYWAY.. i'll shup up
 
If you could assure me that you or your employees would never contact my customers and sell them anything.....The customer is always mine.

That is key

Tony, this would of course be the key. Hell, I would feel the exact same way.

1) Our company would never be mentioned at all throughout the call. It's unnecessary on our part, so why do it?

2) We would want to build a lasting relationship with each and every account (with each account being a separate computer repair business) because, of course, word would be spread extremely fast on Technibble about bad work, stealing customers, etc. One customer is not worth losing all technibble accounts. Heck, all customers are not worth losing the technibble accounts. The better our reputation would become, the more people would trust sending their business to us as an outsourcer, repeat.
 
I guess one question I have right away, is are you doing remote support now? Or just building a 2nd business just for it? Took me many years to square up my processes, it's a lot of work to figure out. (Edited to add: took me years to figure out how to do just remote support, outside of a shop)
 
Last edited:
I guess one question I have right away, is are you doing remote support now? Or just building a 2nd business just for it? Took me many years to square up my processes, it's a lot of work to figure out.

It took you many years because you wanted to do it right and build a customer base. It isn't uncommon for boiler room operators to spring up overnight and dominate a specific area. Many times these places fleece their clients and make a boatload of money without actually providing a service. Then they disappear.

I should tell the story about the time I did sub-contract work for a shady operator in Southern California. Oh why not, its at least amusing.

Anyway, this was back in October 2007 after I was separated from my first wife. I was working a contract job for a company that had just ended. So, I went on Craigslist looking for a job or a gig to tide things over as I was moving to the San Francisco area later for a position at a realtor association. So I happened on this ad for a remote support company that wanted to subcontract jobs that they couldnt fix remotely. In my first day, I managed to get 8 jobs lined up.

My first job was in a pretty nice neighborhood in Anahiem. I got out of my truck and walked to the door and knocked. There was no answer. When I turned around, there were about 12 police cars. Naturally they had weapons drawn on me. I sort of freaked out. I did the usual by getting to my knees and laying face down so they could pat me down. After all this, a detective came over and asked what I was doing. I explained I was on a service call and gave him the name of the company I was contracting for that was out of St. Louis.

Turned out, it was a local fly-by-night place. But what I didnt know, they were using their people for service calls to case houses. Later, a team of people would show up and liquidate the contents of the house while the owners were gone. This apparently had gone on for months and the police set up a house to catch these people. The detective checked me out and found I was not a criminal. He then advised me I could go home or continue on the jobs for the day and pocket the money since I was legit.

In any case, after scrapping mud from out of my underwear, I proceeded to fill the rest of the service calls and made some clients that I passed onto my brother after I moved.

I guess the moral here is that you can start a firm that does the outsourced remote support. But the trick is doing it right.
 
I did the usual by getting to my knees and laying face down so they could pat me down.

I'm sorry, but that cracked me up LOL...sounds like getting pat down is a day by day thing for you? :p

I think what half of my problem and why it took so long, is that I didn't have anyone else to help me or learn from. Technibble and other online sources now have tons of information to get going a lot faster with better knowledge. I don't think it would take years to get a legit remote business going. Just take your time and practice, write it out and follow procedures. Trial and test I guess. I know a lot of people who are doing it and I applaud it. With how easy it is and how much it saves on time and gas, etc...it's well worth learning it for those jobs that are too far out, at least.
 
I guess one question I have right away, is are you doing remote support now? Or just building a 2nd business just for it? Took me many years to square up my processes, it's a lot of work to figure out.

I've done remote support for quite a few years under corporate IT support and we also had a program where once you were an employee for 6mo we would support your home computers remotely for a small fee. When I switched positions within the company to the software engineering field, I launched VitalGeek so that I could continue to do the work I love on the side. As of now, I have several technicians who I manage and I actually don't do much of the remote work anymore.
 
Back
Top