flounderfounder

Thanks I will be in touch.

It's actually a tiny portion of the total market but does seem to represent some big players within it.

I think you are right with not being as concerned with the overall impact as we are. We aren't really worried about someone scooping the idea, there are other players in the field who could implement our same technology and we are trying to make sure we capture a bigger market before they offer anything.

Thanks!

>Is it really broken for the users or broken is your definition of broken because that's your baby and your dreams etc etc etc?

That is a part of it certainly but when we are doing our unit tests about 1/2 to 3/4 of the time the service doesn't do what it should and the user has to reload all their data from scratch (takes about 15-20 minutes).

>let the users know what's missing and what's your plan to ship the rest of the service, and possibly show them a milestones timeline so they see this is not the crappy final version of the whole thing and that you are working hard on the other 75%.

I like that approach - largely because all of our first customers have been really enthusiastic and engaged in the product development. Thanks.

The thing is, we don't have any extra features because we wanted to nail down getting our core service right. So the key process that is the primary feature is the thing that only works about 25-50% of the time right now.