How did Okta find customers?

The pivot happened while the team was small

In the Pattern Breakers interview, McKinnon described leaving Salesforce and initially considering systems management. He and Kerrest redirected the company toward the difficulty of logging into and administering cloud applications while they were still a two-person team. His prior experience included building Salesforce’s engineering organization, with earlier work at PeopleSoft. [1]

[Inference] Changing direction at that stage can preserve the founders’ underlying market insight while limiting the amount of product and organizational structure that must be unwound. The useful distinction is between commitment to a customer problem and commitment to an initial implementation. A pivot is meaningful when conversations reveal a more specific need, not merely when a technology theme becomes fashionable.

The customer needed enough cloud work to matter

McKinnon said adoption depended on sufficient cloud applications and infrastructure existing for customers to accept security in the cloud. The account therefore describes gradual market formation rather than a single launch moment that instantly established demand. It does not supply a historical cohort showing exactly when that acceptance changed. [1]

[Inference] The beachhead can be understood through accumulated administrative pain. An organization with little cloud use may have limited urgency, while another may experience repeated access problems across applications. Counting companies interested in the cloud would be a weaker qualification signal than understanding how identity work already affects their users and administrators.

[Inference] That also changes how a slow sale should be diagnosed. Missing urgency, incomplete product fit and reluctance to change security practices are different problems, even when each produces the same delayed signature.

A convenient login is not the whole purchase

[Inference] An employee can recognize the inconvenience of repeated access steps, but an identity purchase reaches beyond personal convenience. The buyer must consider administrative control, continuity and the consequences of misconfigured access. That makes the decision structurally different from choosing a standalone personal productivity tool, even when the everyday user experience looks simple.

[Inference] A useful evaluation would identify the applications in scope, the people responsible for maintaining access and the work needed to change existing practices. These are proposed buying questions, not a claim about Okta’s historical sales methodology. The supplied interview does not establish sales stages, named early account executives or a particular demonstration process.

The post-sale organization remains an evidence gap

The record names McKinnon and Kerrest as the founding collaborators but does not provide a detailed Kerrest biography. It also leaves early customer-success leadership, account managers, onboarding expense and account-level expansion results unverified. Filling those gaps with a generic enterprise playbook would make the history appear more complete than the evidence permits. [1]

[Inference] The relevant adoption test would be whether the intended people can use the agreed applications while administrators understand how to manage changes. Expansion into additional use should follow that working foundation. Merely increasing the number of connected applications could create complexity without proving that the customer has obtained proportionate value.

Market education needs to fit the account

Historical and current prices, CAC, gross margin, payback and retention cohorts are not established in this research record. The founder’s description of gradual fit does not reveal how expensive early education was or when particular customer segments became economically attractive. [1]

[Inference] Okta’s transferable lesson is to test a structural technology shift through observable customer work. The market can be moving in the expected direction while individual prospects remain unready to purchase. A stronger operating assessment would compare urgency, implementation effort and retained value by application environment, separating justified patience from a product that requires more education and service than its contracts can support.