It is hard to see why and how a functioning and talented team would be assembled outside those circumstances. I mean a team built to sell suggests that the members are not ideally busy solving technical problems.
It is hard to see why and how a functioning and talented team would be assembled outside those circumstances. I mean a team built to sell suggests that the members are not ideally busy solving technical problems.
As you quite rightly point out this is a long way away from OPs original vision.
It actually works pretty well as long as you realize that the "accounting" works differently offshore -- for every good developer you get, you're paying to have someone's dead weight cousin on the project as well. In the end, it's still cheaper than on-shore, just don't expect everyone to pull equal weight.
It's all about learning what work to do on-shore (anything involving client contact / communication, like requirements gathering) and how to package and hand off requirements to offshore.
The big consulting firms will have an advantage over small ones in this model though, because hiring/training developers becomes an operational task that you're doing all the time. If you can grapple with the training and skills development you end up needing to do offshore, the model does work very well.
It will distance you from the technology side of the business, however... and soon enough you'll find that you're working in professional services rather than software development. :)