4 ms·
We actually "launched" as a company[1] way before 2013, but now that I think about it, 2013 was significant for us in that we only really had a product "for sal
by mindcrime 13y ago
We actually "launched" as a company[1] way before 2013, but now that I think about it, 2013 was significant for us in that we only really had a product "for sale" this year. We announced[2] LA (Limited Availability) of two of our products in 2013. We had hoped to close our first deal in 2013, but barring a miracle in the next week, that isn't going to happen. But going in 2014, things are looking very encouraging.
So, given that, I'd say that the following points from TFA resonated with me:
Your idea was too big
What we're working on is big, and as a result, it's taken what feels like forever just to get to this point. In hindsight, we might could have decomposed things a bit more, and done more to look for a way to get traction with a subset of the overall vision. And that's an adjustment that we are actually still looking into making. In 2014, we'll probably launch a SaaS version of our Information Discovery Platform, tailed for use as a "sales intelligence" tool, and targeted at sales teams. We've gotten some very positive feedback on this idea from a number of sales teams, so we're pretty excited about that. Had we decided to go this route sooner, we might be a lot better off now. But, hindsight is 20/20.
You didn’t build an audience
We only started really "working" social-media with an eye towards specifically trying to grow our audience, in 2013. I mean, we had a blog and a Twitter account and a Facebook page and the gamut all along... but last year we started taking it seriously. What I have come to realize is that growing an audience is a lot of work, but it is somewhat predictable. There are things, that if you do those things, will result in more Twitter followers, more mailing list signups, etc. We haven't dived full-bore into "growth hacking" but are definitely seeing the importance of these ideas.
The other thing we hope to do in 2014 is more marketing efforts, including: presenting at user-groups and Meetups that relate to what we do, hosting Google Hangout sessions, and/or Twitter "live chats" on topics related to our domain, still more "content marketing" via our blog, and maybe even writing and publishing a book (or two).
You tried doing it alone
Did that for the first year I was working on Fogbeam, but we've grown in fits and starts. IMO, you should invite people to join you when the time is right, and not just to say you "aren't a solo founder". We have three members on the founding team now, and a fourth person we're talking to about joining up to do sales. It's taken time, but we've been patient and looked for good fits.
[1]: http://www.fogbeam.com http://www.fogbeam.com
[2]: http://fogbeam.com/news.html#press_release_08282013 http://fogbeam.com/news.html#press_release_08282013
- shubb 13y agoCan I ask the thinking behind how you name your products? I had some difficulty understanding what you are selling - a groupware suite with API integration? If all your sub-products make sense used as part of a suite, why not talk about the suite and it's capabilities, rather than a collection of products with strange names? (hope this is useful feedback, good luck!)
- mindcrime 13y agoCan I ask the thinking behind how you name your products? Sure, it's all based on our overall branding theory. The company name is "Fogbeam Labs" and the logo is a lighthouse, and our (current) slogan is "Cut through the information fog". So everything is based on ideas around light, illumination, and helping people see what is currently unseen. Given that, Quoddy, Heceta, Neddick and Hatteras are all named after famous lighthouses. At one time we debated using a model where those names would be more like "internal names" and would be the name of the Open Source project, and then using a different name for the "branded" commercial release. Something like the way Red Hat use "Fedora" for their upstream distro and "RHEL" for their branded release, or "Wildfly" for the upstream JBoss and "JBOSS EAP" for the branded release of that. But when we sat down to think about doing that, we kept coming back up with scenarios like "Quoddy" -> "Fogbeam Enterprise Social Whatever" or "Hatteras" -> "Fogbeam Business Event Engine" and nobody on our team liked "Fogbeam Enterprise Social Whatever" and the ilk. So we decided just to use the "base" names, and tag "Enterprise" onto the end to discriminate between the underlying OSS project and the commercially supported releases. "Quoddy" -> "Quoddy Enterprise" etc. Is it perfect? Probably not, but we're running with it for now. If it doesn't seem to be working, we may revisit it. As an aside, I did learn one important lesson during all this... at one time, I was trying to be too cute with using lighthouse related terms, and we had a project named "Screwpile". A little later, one of our advisors pointed out that "it makes sense if you know what screwpile means[1], but nobody does, and if you don't, it just sounds ugly, almost vulgar even". And then I realized just how bad that was. We yanked that and renamed it "Fogcutter" instead. :-) I had some difficulty understanding what you are selling - a groupware suite with API integration? I try to shy away from using the term "groupware" because it has existing connotations that don't necessarily apply to what we're doing. I'd probably say a "suite of knowledge management tools" over saying "groupware", but we are kind on the boundaries of the existing terminology to some extent, so we're still iterating on the terminology to use in our messaging. But basically, we have - in Quoddy - an "enterprise social network" (kinda like Jive or Yammer), but with much better support for integrating with other enterprise applications and knowledge sources, and using semantic integration to fully unite knowledge and information across disparate sources, so we can provide relevant context at the user's fingertips when they are examining any given event, task, or piece of content. Neddick, on the other hand, is like "Reddit for the Enterprise". It's link sharing, social news, and that sort of thing, but - again - tailored more to be useful as a tool within an organization. If all your sub-products make sense used as part of a suite, why not talk about the suite and it's capabilities, rather than a collection of products with strange names? That's another place where we're still exploring what's going to make the most sense. Are people going to want to hear about (and buy) the entire suite, or are significant numbers of people going to want one piece, or the other, but not both? We don't know the answer to that yet, so it's all still in a state of flux. Ideally, as we learn more about how people react to this, the messaging and branding will become more clear. (hope this is useful feedback, good luck!) It is, and thanks! [1]: http://en.wikipedia.org/wiki/Screw-pile_lighthouse http://en.wikipedia.org/wiki/Screw-pile_lighthouse