1) In the second sentence, I'm expecting to hear the first pitch for the product.
Generally speaking: with Spaceship, we ultimately aim to lift your creative process to a new level of productivity and fun.
Why "generally" speaking? You don't want to speak generally, you want to speak specifically about what you're offering. Secondly, you introduce your product with its benefits. That's great for most sales situations (think of all of the TV commercials that start with "Imagine if..."), but can be confusing for technical products like software. I want to know what your product does.
2) This is a really strong insight:
We found and tried a lot of products that try to simulate analog tools like note-taking apps or virtual whiteboards. Web afficionados work together in Google Docs. A forward-thinking filmmaker might manually copy character mugshots into a Dropbox folder. We heard of people who like the experience of Evernote.
3) The video is great. You're using the application to demo the application. Fantastic. But where's the audio? Why aren't you speaking with me directly? If you aren't comfortable with speaking, hire a friend for cheap.
1) True. I'll do a better job next time.
3) Yes. We'll add audio in the next iteration.
Even saying something like, "Spaceship is a collaborative mind mapping application that supports rich media," would have helped me understand quicker.
Oh... and... what is it that spaceship does?
The first paragraph needs to be specific. I read all the way to the tl;dr mark and still don't know what's brewing.
Overall, I have to admit that I'm skeptical about the whole enterprise of contextual mapping, but one of the things that could possibly convince me to try your software would be if the implementation looked exceedingly simple and well-executed. One of the reasons a lot of contextual map software fails is that clicking and dragging things around is extremely tedious, and with most software, the interactions are not implemented very well. I'm talking about things like: distinguishing click-moves and click-edits, or boxes in a flow chart staying connected to each other when I drag them around.
Think about the whiteboard you're trying to replace (I think). The reason a whiteboard works so well is that it's incredibly easy to put any kind of data into it, because drawing things on a whiteboard is trivial. You don't have the ability to draw that way with a computer program, so whatever facilities replace drawing need to be comparably easy to use.
It's kind of hard to do a concrete example for an audience that has very different problem domains (i.e. engineers, designers, students, communications people etc.). But as soon as we're going into public beta, we'll probably have to produce high quality examples for different audiences, that's right.
We're not trying to replace analog media. I think that's kind of impossible. But we're working on ways to augment them (for example making it very easy to capture a white board or scribbled notes).
With that all said however, the page offering explanation leaves much to be desired. I think there should be more doing and less talking so to speak. Even the text though feels unstructured and out of place, its placement seems rather haphazard, and the rag is especially rough. While I do realize this blog post isn't the product, the typography is seriously lacking there.
As dwynings figured out quite well, our Space is a mix of a virtual whiteboard with media sharing, annotation and clustering features. You can use it to work on ideas, concepts, to review or decide on things.
The next thing we'll be releasing is Processes. These will allow you to work through projects in well-defined steps, where each step has its own Space.
Currently, we're not in selling/marketing mode (hence the sloppy effort on that side). Instead, we're trying to accumulate feedback and critique from potential users and hackers, so we have a bigger chance of building the right thing.
So, my feedback for this tool is to make input much easier. Instead of "click, type, move" over and over again.. smooth that process out by having a type-only input mechanism.
Great work so far!
Edit: Grammar and last line.