A customer calls because something has gone wrong. By the time the conversation reaches a company’s contact center, the problem may already have crossed product, billing, operations and policy. The person on the headset inherits the whole untidy bundle. Dave Rennyson has spent much of his career in that bundle. Long before artificial intelligence could summarize a transcript, he was running telecom contact centers and learning the first law of customer experience: the front line receives every promise the rest of the business fails to keep.
This is useful context for understanding Rennyson, the co-founder, president and CEO of SuccessKPI. His company sells software for joining contact-center data, finding patterns in conversations and turning those patterns into action. But the more revealing product may be his résumé. He has worked in engineering, construction, corporate development, marketing, sales, operations and product. He has led a company through acquisition, integrated cloud businesses, carried a large international revenue target and returned to founder mode. He is a full-stack operator in a business culture that often rewards narrow labels.
The labels never mattered as much as the handoffs between them. A salesperson can promise what engineering cannot ship. A product team can build what an agent cannot explain. An analytics system can produce a handsome chart that changes absolutely nothing before Monday’s queue opens. Rennyson’s career keeps returning to that last gap: the distance between insight and action.
The full-stack operator
Before the cloud had a personality
Rennyson began in telecom operations, including first-line and second-line management and the running of contact centers at the business that became Verizon. Later came senior roles at Broadband Office, engineering and construction leadership at Zephion Networks, and marketing and sales work at Spirent. The progression looks restless on paper. In practice, it gave him multiple views of the same machinery: the network underneath the call, the people handling it, the software surrounding it and the commercial system paying for it.
In 2007 he joined Angel.com as vice president of sales. Angel provided cloud-based voice and contact-center technology at a time when “cloud” still required explanation in polite company. Two years later he became its president. The company grew, and Genesys acquired it in 2013. Rennyson described the deal in practical terms: Genesys offered a broad global channel, while Angel brought an established SaaS product and team. The point was reach, not confetti.
After the acquisition, he ran SaaS and cloud at Genesys and helped combine multiple cloud businesses. Then came MicroStrategy, first as chief revenue officer and later as senior executive vice president of worldwide sales. The numbers attached to that job were not decorative: a 400-person organization, more than $500 million in revenue and work across 25 countries. In 2018, Interactions recruited him as chief revenue officer to lead global sales, support and professional services.
“None of these great ideas are ever your own idea.”Dave Rennyson, on the origins of SuccessKPI
The reunion became a company
The first conversations behind SuccessKPI began around the middle of the 2010s, when Rennyson reconnected with former colleagues. Several would become part of the founding team. That origin matters because the company did not begin with a lonely inventor guarding a napkin. It began with people who had already watched customer-service systems fail in familiar ways and had learned they worked well together.
Rennyson remembers Angel as a culture with strong work ethic, room for creative conflict and an unusual degree of focus on customers. SuccessKPI carried that social architecture forward. Its stated values include solving problems for customers, caring for partners and teammates, making simple things easy and complex things possible, and working hard without taking itself too seriously. Corporate values can become lobby wallpaper. These read more like scar tissue translated into sentences.
His favorite image for building a SaaS company is a nautilus shell. It starts with a grain, winds around itself and gains complexity without losing the structure underneath. The metaphor is more patient than the usual rocket ship. Rockets are thrilling and spend a great deal of energy escaping the ground. Shells simply keep adding useful rooms.
That patience appears in SuccessKPI’s data architecture. Contact centers produce unruly material: transcripts, sentiment, topics, keywords, call lengths, channels, agent records and customer outcomes. The platform was designed to join those structured and unstructured records in one place. Generative AI arrived later and made that unglamorous plumbing newly valuable. Rennyson’s compact explanation deserves to survive several budget meetings: “Generative AI eats data for breakfast.” A clever model placed over confused information remains a clever model with indigestion.
Build the connective tissue before the magical feature needs somewhere reliable to stand.
Even the machine needs a coach
Rennyson’s current argument is that companies are automating customer conversations faster than they are learning to supervise them. When AI agents handle routine work, human agents receive a larger share of the strange, emotional and genuinely difficult calls. That makes the human role more demanding, not obsolete. Meanwhile, an AI system talking directly to customers cannot reasonably grade its own performance and declare the exercise complete.
His proposed standard is simple: measure human and AI agents within one performance framework. Quality-manage the automated conversations. Decide where work should go based on complexity, demand and outcomes rather than a crude target for maximum automation. Put independent oversight above the system. He compares self-inspection by an AI platform to letting a builder conduct the inspection on the builder’s own house. The house may be excellent. The clipboard still belongs elsewhere.
“Even Messi needs a coach.”Rennyson’s shorthand for continuous training
The coaching line is not random. Rennyson’s public profile lists years as a youth soccer head coach, first with Chantilly Soccer Club and later with the Southwestern Youth Soccer Association. He also talks about constant training as a trait of high-performing companies. Skill does not eliminate feedback. It makes good feedback more valuable.
A purple thread through the story
Rennyson graduated from James Madison University in 1991 with a degree in economics and history. He later earned a master’s in information technology from University College London and an MBA from Duke’s Fuqua School of Business, where he was named among five Fuqua Scholars for a perfect GPA. The combination is almost suspiciously tidy for his career: human systems, technical systems and commercial systems, studied in that order.
JMU provided more than a diploma. He met his wife, Alisa, there in the early 1990s. His siblings attended too, and friendships from those years endured. When the couple’s youngest son toured the College of Business decades later, the decision to attend arrived quickly. Rennyson subsequently joined the college’s Board of Advisors, bringing 35 years of business experience to conversations about curriculum and the effect of AI on what students can do from their first year.
There is an appealing symmetry in the return. A career built by moving across boundaries leads back to a school trying to prepare students for boundaries that are moving beneath them. Rennyson talks about JMU graduates in the language of an operator: grit, personality and readiness. He and Alisa also support internships through SuccessKPI, with Alisa leading recruitment and coaching students to ask for direction rather than quietly struggle.
The useful residue
Rennyson’s story is not a parable about always listening to calls or collecting enough job titles to fill a conference badge. Its useful residue is connective. He learned the infrastructure, then the customer operation, then the sale, then the integration. He worked with people, left on good enough terms to work with some of them again, and built a product around a problem that survived every corporate reorganization he had seen.
The contact center remains an unusually honest corner of a business. Customers do not call to admire the strategy. They call because the password failed, the delivery wandered off, the invoice became surreal or the policy collided with ordinary life. Every conversation is evidence. Rennyson’s bet is that modern software can read far more of that evidence, connect it to the operating record and prompt a useful response. His warning is that the software must itself be coached and inspected.
For founders, there are three things worth stealing. First, functional range compounds when each role teaches you where the next one breaks. Second, architecture built for clear information can become an advantage when technology changes faster than the plan. Third, a team you would gladly build with twice may be more valuable than an idea you insist was yours alone.
The rest is the daily work: another conversation, another grain in the shell, another chance to make the system hear what the customer has already said.