Why you should (or shouldn’t) trust a startup
blog.compile.com
Why you should (or shouldn’t) trust a startup
1–10 of 15 posts
Re: Why you should (or shouldn’t) trust a startup
#2> Your data stays with you: It is scary enough to hand over your company’s most precious data - your customer database - to a large company with all the data break-ins today. But with a start-up, the risks magnify, as there is the added worry that the start-up will fail, or will be acquired. What happens to your data then?
> We never ask our customers to provide us with their data. We ask our customers for descriptions of their products and descriptions of their customer’s pain points. That information is enough to provide a continuous stream of targeted leads to our customers.
Considering that the "data" being collected & sold by Compile doesn't belong to its "customers", where is the question of trust? Also, why would any customers who are buying leads from you ever share their customer data with you?
Or maybe I'm missing something here?
Re: Why you should (or shouldn’t) trust a startup
#3Re: Why you should (or shouldn’t) trust a startup
#4Clicking on your logo in the blog should go to your main site. If not, please add a link to your main site. It's very difficult to navigate as most in-app browsers don't have a url bar.
Re: Why you should (or shouldn’t) trust a startup
#5To slightly extend, there's also the question of "Will you raise your pricing for the same offering at any point?".
Plus, in addition to can I get my data back, "will it be of any use to me when I do get it back?". i.e. is it exported to some standard format, will I get enough source code to run it long enough to build (either myself or collectively) some way to get the information (as opposed to the data) out?
"Can I get my data back" actually figured in our architecture prior to building, that's why we went for bring-your-own-storage. Google Drive and Dropbox both now provide direct JavaScript on the client to their servers functionality, the data doesn't need to go your servers any more for storage (only for processing, should you need that).
Our SaaS isn't our main, or even a pay-for, product, we heard this constantly. We do now have a set of answers, but it's taken a good couple of years to put them together in a way that satisfies people.
Re: Why you should (or shouldn’t) trust a startup
#6I'm unsure what to make of this post. > Your data stays with you: It is scary enough to hand over your company’s most precious data - your customer database - to a large company with all the data break-ins today. But with a start-up, the risks magnify, as there is the added worry that the start-up will fail, or will be acquired. What happens to your data then? > We never ask our customers to provide us with their dat…
Re: Why you should (or shouldn’t) trust a startup
#7Re: Why you should (or shouldn’t) trust a startup
#8Re: Why you should (or shouldn’t) trust a startup
#9What does compile.com buy me for lead generation over a good data feed (bloomberg for my use case) + getto data mining/machine learning?
> Uses natural language processing based algorithm to find leads from the deep public web
How good's this? Y'all need to get your hands on a bloomberg terminal.
Re: Why you should (or shouldn’t) trust a startup
#10This is why startups tend to deal with startups, and Crossing the Chasm [0] is so difficult.