> I would pay 10x more for consulting instead support. The constant need for support means your team is incompetent. If you need external support to keep things

> I would pay 10x more for consulting instead support. The constant need for support means your team is incompetent. If you need external support to keep things moving, chances are you won't get very far. Totally, agree > I don't really understand what 'rely on a community' means here. Who does not depend on open source software? I'm sure you know this - that's how a huge chunk of non-tech people view anything labelled with "open-source", they all view it as "unreliable" or "geeky". By how I constructed my sentence it seems I'm saying this from my perspective, but we're like minded in that aspect: everyone depends on open source software one way or another. I'm just assuming that's how his client thinks. I'm assuming the decision maker for his client is one of those 'guys' who's outside the tech bubble, and probably worse: they don't listen to engineers. I mean, if OP has already built a nice prototype on Backbone and it's all good why would they go towards ExtJS? Backbone is widely used and constantly worked upon, if his client is well aware of the software development industry they wouldn't just dismiss the prototype and go towards something with 5-digit contracts. Again I'm just assuming the worst case scenario about OP's client by trying to understand the situation from what he said about their decisions. > I'm also a co-founder and technical guy, I assure you spending money is always the last thing any company wants to do. I'm also sure you know this: any hard-headed, non-tech decision maker outside the software industry who is very desperate would throw a lot of money for a problem to go away.