Service-oriented startup #
sweat, work and marketing
Service startups are all about lean methodologies and aquiring community. For example Edukami, Facebook, Trello are all service oriented startups and their scope is a lot more different than the product-alternatives. For comparison to Facebook check app.net (the other comparisons I will leave to you).
Most of the times we didn't build a web app - we build community. A community that is living and thriving while you build your service. That's why I focused to feed the community because it's hungry for more information regarding the service and everything around it. This community building is hard, takes a lot of effort and time and sometimes you end up with something you didn't quite expected because everything is constantly changing.
Everytime when I think about service-oriented startup I end up with thinking how the service will be 6 months from now or 1 year, in order to preserve and maintain a mid-long term mission. This sometimes can be exhausting and anti-agile but is necessery evil when you're building something that will "stay". Because it is evolving there's no versioning (do you know what version of Facebook you're using? :P) and the application is living.
- A lot of errors
When building a service startup I think you should need to be prepared for a shit load of errors because of the ever-evolving nature. If you are building a product you easily can submit a hotpatch
- Large scope
Frequently I try to avoid out-thinking what can become if the community release it's wisdom upon Edukami but when I think about these things I realise that Edukami has such large scope that I can't even traverse it in my mind. This large scope can be a suicide for the mind because you lose precious time trying to out-think every possible realisation of your service startup.
- Just release
I've read http://gettingreal.37signals.com/ and http://37signals.com/rework/ and for some things I agree with them - just realease. This state of the mind is crucial when building a community and fearsome when trying to build a product.
- It's all about the movement
In order to build a community I need to establish a tribe, people who believe in the idea. This is different from the early adopters you can see in product-oriented startup who will just write a review or something. Creating a movement can be colossal in terms of magnitude - it can start small and grow exponentially. So when building service-oriented startup I want to