Sorry about the confusing product and pricing page.There are typically two different scenarios for pricing: Users can be employees, consultants, contractors etc. or Users can be consumers, customers etc. Depending on the context, the pricing differs.
Not only can you remove the user/employee from the centralized service (Okta) but you can also hook-up to various HR systems (if you so desire) like AD, Workday, Ultipro, BambooHR etc. and have them act authoritatively to determine if an employee is employed, on-leave or has terminated their employment.
Wow, that developer site linked by in the comment I responded to is advertising a WAY different (more specific) product than your normal website (from what I understand at least).
The regular website is advertising something that makes more sense to me but there are still dozens of pages advertising dozens of different features and different prices. I guess that might work for larger corporations that have already solved internally some of these problems and can pay for bureaucratic solutions but I just want a solution to a known problem.
I'm not saying catering to enterprise customers is a bad thing (they have lots of money so you probably should),
But there is a reason VC's ask for a vision. What problem does okta solve because I have spent over 10 minutes trying to read through all of your web pages and I still don't know why I should use you guys.
I'm not a marketing person, but as a customer, i generally want to know what problem a company solves in 5-10 seconds and know how they solve it within a minute. If you cannot convey that simple information, then I think your product is crap and you are just marketing your product with vague/complex/buzzword terms.
If you expect to understand identity in 10 seconds, you don’t even know what you don’t know.
You know how we hear about dopey password disclosure breaches every month? Using a service like Okta, Azure AD, etc lets you avoid that type of embarrassment/liability and lets you control the dozens of SaaS and other accounts that your employees use.
> If you expect to understand identity in 10 seconds, you don’t even know what you don’t know.
I'm not asking to "understand identity in 10 seconds" whatever that means. I literally just want to know what problem they are solving in a simple abstract use case so i can tell if their product relates to the problems that I have. If so, I will gladly spend more time researching your product. Telling me that I have to spend hours just to figure out if my problems even relates to the solutions marketed by your products is your failure in marketing your product.
> You know how we hear about dopey password disclosure breaches every month? Using a service like Okta, Azure AD, etc lets you avoid that type of embarrassment/liability and lets you control the dozens of SaaS and other accounts that your employees use.
Go read Y combinator's "how to apply blog" [0] with the relevant text starting with "The first question I look at is, ". I recommend reading all of it because it is pretty good but that section explains how conveying a product quickly in a concise matter is crucial.
Here is some relevant text:
"We are going to transform the relationship between individuals and information."
That sounds impressive, but it conveys nothing. It could be a description of any technology company. Are you going to build a search engine? Database software? A router? I have no idea.
One test of whether you’re explaining your idea effectively is to ask how close the reader is to reproducing it. After reading that sentence I’m no closer than I was before, so its content is effectively zero. Another mistake is to begin with a sweeping introductory paragraph about how important the problem is:
Information is the lifeblood of the modern organization. The ability to channel information quickly and efficiently to those who need it is critical to a company’s success. A company that achieves an edge in the efficient use of information will, all other things being equal, have a significant edge over competitors.
Again, zero content; after reading this, the reader is no closer to reproducing your project than before. A good answer would be something like:
A database with a wiki-like interface, combined with a graphical UI for controlling who can see and edit what.
We are aware of Nymi, they have cited some of our ECG biometrics research papers, and we theirs.
But Nymi makes the user constantly wear a band. As soon as you take off the band, their authentication stops working. Also, you have one more gadget to charge.
In CardioID's case, the ECG sensors are embedded into everyday life objects, so the system is ready whenever the user wishes it. Beyond that, we also continuously track other heart parameters, like heart rate and cardiac arrhythmias.
But if you have several locations where you'd like to log in you require multiple of these devices, right?
With wrist band you could sell to something like FitBit or just add step-, distance-, calorie tracking, watch, silent alarms and call/sms notifications into the mix.
Yes, you're right. That's why we're primarily targeting a B2B market. Imagine that a gym has machines with our technology embedded. The gym's users would be able to seamlessly track their workout across different machines, just by using them as they normally would, no need for extra weight.
Note that, for continuous ECG monitoring, you need skin contact with 2 electrodes, from different limbs. That's why with Nymi, authentication is performed only once when the user puts it on, with one finger touching the visible electrode (the other electrode is on the underside of the band). In this case, there is no continuous verification of identity, or other parameters.
