Blood, Sweat and Years: Raising Money as a Deep Learning Startup
mattermark.com
mattermark.com
Many open source startups pre built their product to commercialize before the company. (red hat -> linux, hadoop -> cloudera) . We ended up doing both at the same time (do not do this unless you want to tear your hair out).
When it started it was actually just the 2 of us with me writing all the code. The thing that made it work: We put it out there and got user feedback and paid very close attention to users.
A lot of machine learning startups have their "secret algorithm that's actually just using an open source python based deep learning toolkit for their mvp" .
For these product based deep learning startups, there isn't much actual deep learning going on. Half of the appeal here is focusing on a specific domain and accumulating data and expetise/partners in that domain.
We did the opposite by "giving it away".
This is ultimately what culminated in our support first culture as well as the bulk of our engineering hiring.
Having our customers,users, and engineering team co located has been a blessing in disguise.
Lastly: You should also write a book while doing a startup. http://shop.oreilly.com/product/0636920035343.do
If there's any particular questions on any of these things happy to answer.
From there, it's really just normal product knowledge. Eg: what will make money?
Don't "embed machine learning" for fun - pick a simple problem with real value like a normal customer analytics problem to start. Everyone has web traffic - try to see if there's any value you can extract from that. It could be optimizing conversions, churn prediction, or anything similar to that.
And this - > To get users, you need a product, to get a product, you need funding, and to get funding, you need users. I’m sure you can appreciate the catch-22
But especially this- >bootstrapping marathon of many nights
Thanks for writing this. Its hard to empathize with these crazy folk, until you become one of them & then you realize Woah! Its a relentless sleep-deprived grind. Haven't felt so groggy since grad school. That said, light at the end of tunnel etc. Keeps me going. I actually use DL4J on the backend, so thanks again!
So, I think you may benefit by showing specific examples of catching fraud. For instance: what is your performance compared to, say, human auditors? What sort of features can you find that human auditors cannot? And what is your false positive / true positive (ROC) like?
The main bit with orange that isn't in the marketing material: We used unsupervised methods for this, not supervised.
https://www.youtube.com/results?search_query=adam+gibson+dee...
http://www.slideshare.net/agibsonccc
http://shop.oreilly.com/product/0636920035343.do
I frequent the big data circles quite a bit. This is our main audience though, not the DL research folks.
As far as my customers go that's actually enough. You're right it's still hard though. I've done my fair share of outreach and speaking though. Anyone who does their research will fine ample credit that we aren't just random folks off the street.
We built up that credibility over time though. I'm still the creator of the dl4j framework itself. So in practice people see we can build software.
I've heard of Skymind, just not the founders.
I already mentioned that? Not claiming otherwise.
We tend to stay away from the R&D side. That's the thankless side of the space where you end up on a perpetual feature staircase with a user base you know won't pay ;). That would be hard for us to build a business on.
That's a job for orgs like OpenAI and google where they need to hire more folks like that. They are doing a great job at that.
Research code ends up being thrown away. The focus on the JVM and the like is for codebases that are meant to be maintained for a long time. We don't expect researchers to use us. It's far from our target. Thus we appear in the places where it counts for us.
My main point is to demonstrate that if a VC or someone was vetting us - they'd at least find a "presence".
The fact you've heard of us at all proves we're doing our job then :).
By way of analogy, Cloud Foundry is a PaaS that can run on top of any of the established IaaS platforms.
The other thing here: It would more or less be redundant. If one is more accurate than the other you're not going to bother using them really.
Maintaining something like that would be a nightmare (compatibility issues an updates among others). The ROI here doesn't seem to be there for me.
I might be the wrong person to answer this though: My prejudice against SAAS Infra (eg: ML as service) runs pretty deep. I tried building one before (NLP focused) back in 2012 and learned developers don't like to pay and they will always ask for more features. I'm also not the right kind of founder to build a SAAS business though. I don't like the idea of chasing after 10s of millions of people for $5/month when I could produce value for 1 company I know and sell software several times and make equivalent revenue (hence skymind's on premise focus)
Note: Whether the thing you build on top is a product or a service is open. Cloud Foundry as an example is really more of a PaaS product (which can be deployed on prem or on various IaaS platforms).
As for having a few big customers vs. many small ones, there are advantages to both approaches (enterprise sales vs. self-serve, higher margins vs. lower volatility, etc.).
We do our stuff we build on top closed source. Easier to monetize. This is known as open core.