Re: what we're better at than Google spreadsheets -- our big benefits come in simplifying complex spreadsheets, by using programmerly techniques such as objects/lists/NumPy arrays in cells, and in automated parallelisation for large calculations. These are definitely power user features, for normal cashflow spreadsheets and the like there's no advantage to using Dirigible instead of Google.
(Random thought: we're currently using the example of calculating the orbits of the planets to show a bunch of those features off. We chose that example specifically because it's simple enough for most technical people to grok pretty quickly and doesn't require any real domain knowledge to see what's going on. Perhaps we also need more industry-specific examples to make the same point -- eg. pricing portfolios of exotic options for the finance guys.)
Re: concurrent server support -- well, I guess a bit of A/B testing might be in order -- with a mind to the fact that we'll need to keep running the tests as time goes on and we (fingers crossed) cross the chasm.
Infact, there is a part in me that is still trying to figure out in which problems you are better than Google Spreadsheets and its programming model (even though I understand that you are different from it).
Perhaps what you need to do is talk about the problems that you solve instead of what you are building. This will definitely be helpful when trying to get to product/market fit.
Re: dropping concurrent server support - I doubt that anyone can really tell you what you should do there. You need to experiment. And the answer right now (with early adopters) might be very different from the answer a few months down the road.