First thing to get out of the way… your users “don’t” understand BETA. This means that when they visit your business, if it doesn’t solve their problem they won’t come back. They don’t care if its Beta or Gamma. That is why BETA must not be approached as a way to get some feedback while work is in progress, but as a way of having a controlled situation where your objective is to learn as much as possible about the not-so-obvious motivations of your clients.
We have been “in Beta” since May and now we approach BETA in a different way. Mainly dividing it in two phases. This is what we’ve learned:
First of all, as I have said many times, I haven’t got a technical profile… I’ve majored in Business Administration and have always worked in Business Development and Product Management during my “short” working life.
One common advice to all of us non-technical profiles that decide to start a new internet business is to “learn to program”… So that is what I did… And after some days of Python and Ruby-on-Rails I can tell you one thing: I am sorry to say but if you take into consideration all the implications and the time needed, that advice is… nonsense.
After attending some developer meetup and telling my story almost every advice I got was in fact the contrary… “Want to learn to program? don’t even try. Go find a CTO co-founder”. And that is what I did, and after a month doing that, I had a big breakthrough. That advice is, also… nonsense.