Skip to content
Start a conversation

Built by people who have worked inside operations.

Kevin, Ben, and Ryan come from production, supply chain, enterprise technology, data, and commercial delivery. At ArcherKey they look at the same problem together.

  1. Portrait of Kevin De La Concha

    Kevin De La Concha

    Founder and CEO

    Before ArcherKey

    Eight years in the U.S. Air Force as a production supervisor, then nearly six years as an operations project manager at Raytheon Technologies on aerospace and defense programs, where a process redesign cut production cycle time by more than twenty percent. Later, digital technology leadership at Collins Aerospace.

    At ArcherKey

    Connects the people doing the work, the processes they follow, the information they rely on, and the technology that supports them.

  2. Portrait of Ben Evans

    Ben Evans

    Co-founder and Chief Commercial Officer

    Before ArcherKey

    Supply chain and data work across Mars Petcare, GEODIS, 1010data, and Sigmoid. At 1010data, Ben launched Sam’s Club’s MADRiD data-sharing platform in the United States and Mexico. Most recently, growth and partnerships at ChatRank.

    At ArcherKey

    Connects operating data to adoption, partnerships, and commercial value.

  3. Portrait of Ryan Buxbaum

    Ryan Buxbaum

    Co-founder and Chief Operating Officer

    Before ArcherKey

    Operations and logistics leadership at Hilti, where Ryan led a nine-person team that changed the North American order-to-cash model and delivered more than $11 million in annual value through Lean and operations initiatives. Earlier, supply chain leadership at Mars Petcare and project management at Amazon. Most recently, chief development officer at RealTimeCase.

    At ArcherKey

    Makes operating strategy executable: clear objectives, a workable sequence of work, and a realistic view of what delivery takes.

Three views of the same problem.

Operating leadership, technical systems, data, and commercial delivery meet in the problems businesses face. A workflow decision can affect software design, workload, financial performance, and the customer’s experience, so the three examine a proposed change from each angle before committing to it.

They challenge one another’s assumptions, and they keep the reasons behind each decision available as the work moves from investigation into delivery.