LionelJohnson
Member
- Reaction score
- 1
- Location
- UK
First of all let me say this thread is only about B2B. I also 'fired' my residential customers and am pretty happy after doing so. I've spent most of my IT career in a corporate environment (sys admin) and always felt like a fish out of water with residential.
I love Micah Lahren's recent articles on being a one man shop in the B2B world. It seems to work well for him. I also read Technibble's guide to B2B book which was interesting but didn't give much in details of how B2B operations are actually run. Delegation makes things simple (I have worked in IT service companies before) but I think being a one man shop adds extra complications to plan for, such as:
How do you support customers when you are out of town. Will customers accept that you may only be able to help them 'remote only' for a few days or however long you happen to be gone for. Obviously if you are a one man shop, you are not always going to be available so it would be pointless to include guaranteed response times (at least for on site work) in your contracts.
What happens if you are on site at one client office but get a call from another client who needs you at their office? Making them wait their turn is going to make your business look unresponsive. Assume that neither support calls can be resolved via remote. I would love to hear how people manage their time and commitments between customers.
I would think that it's probably a bad idea to answer phone calls while on site and talking to other customers, even if it's urgent. The client business you're attending is not going to be pleased with you using blocked hours (if that's the arrangement) and distracting your attention talking to other clients.
Some of this requires common sense to find the best solution, but I am curious about what other's procedures are. There is a huge downside of course to a) being out of town, b) making business customers wait their turn, and c) being unavailable by phone while working on site somewhere. Not that these situations occur everyday, but still requires some forethought because it effects the contracts and service description.
And please don't say employ someone, I am determined to manage as a one man army! It's a selling point in a way, because as the point was made recently, "the buck stops here" and the much lower overheads.
Thoughts?
I love Micah Lahren's recent articles on being a one man shop in the B2B world. It seems to work well for him. I also read Technibble's guide to B2B book which was interesting but didn't give much in details of how B2B operations are actually run. Delegation makes things simple (I have worked in IT service companies before) but I think being a one man shop adds extra complications to plan for, such as:
How do you support customers when you are out of town. Will customers accept that you may only be able to help them 'remote only' for a few days or however long you happen to be gone for. Obviously if you are a one man shop, you are not always going to be available so it would be pointless to include guaranteed response times (at least for on site work) in your contracts.
What happens if you are on site at one client office but get a call from another client who needs you at their office? Making them wait their turn is going to make your business look unresponsive. Assume that neither support calls can be resolved via remote. I would love to hear how people manage their time and commitments between customers.
I would think that it's probably a bad idea to answer phone calls while on site and talking to other customers, even if it's urgent. The client business you're attending is not going to be pleased with you using blocked hours (if that's the arrangement) and distracting your attention talking to other clients.
Some of this requires common sense to find the best solution, but I am curious about what other's procedures are. There is a huge downside of course to a) being out of town, b) making business customers wait their turn, and c) being unavailable by phone while working on site somewhere. Not that these situations occur everyday, but still requires some forethought because it effects the contracts and service description.
And please don't say employ someone, I am determined to manage as a one man army! It's a selling point in a way, because as the point was made recently, "the buck stops here" and the much lower overheads.
Thoughts?