One of our clients recently transitioned from a homegrown process built around Salesforce to a new operating model supported by Speakcore and an agency partner.
For years, their sales representatives had owned nearly every aspect of event planning themselves. After an event was approved, they contacted speakers, coordinated venues, confirmed logistics, managed communications, and handled much of the operational work required to get a program off the ground.
The process worked—but only up to a point.
As the program expanded, the process became increasingly difficult to scale. More events meant more administrative work, more coordination, more opportunities for inconsistencies, and greater compliance risk. While Salesforce supported the basic workflow, it wasn’t purpose-built to manage the operational complexity of speaker programs. The organization needed a platform that could support configurable workflows, compliance guardrails, reconciliation, and the broader lifecycle of planning and executing compliant events.
The decision was made to introduce an agency partner and redesign the process.
Under the new model, sales would continue focusing on customer relationships and promoting programs, while the agency would take responsibility for speaker outreach, venue coordination, logistics, and many of the operational activities that had traditionally been handled by the field.
From a technology perspective, the implementation itself was relatively straightforward.
The challenge wasn’t implementing new technology.
It was implementing a new way of working.
For years, the sales team had been accustomed to owning every step themselves. If they wanted to confirm a speaker or secure a venue, they simply picked up the phone and made it happen. Under the new operating model, those responsibilities shifted to the agency partner. Even when the agency responded quickly, the process became inherently asynchronous. Sales now had to wait for work they previously completed themselves, and that change naturally created friction.
It wasn’t a question of whether the agency was doing a good job.
It was a natural consequence of changing who owned the work.
As the organization gained experience with the new model, everyone began to recognize that some responsibilities felt better suited to sales, while others clearly belonged with the agency. Certain workflows worked well for one business unit but not another. What looked good during implementation needed refinement once people were living with it day to day.
This wasn’t a software issue.
It was a business process maturing through real-world experience.
Rather than immediately making configuration changes, we paused and stepped back to understand the broader operating model. Before updating workflows, we needed clarity around ownership across the entire event lifecycle—everything from speaker communications and venue coordination to attendee reconciliation, financial closeout, and the responsibilities shared between the agency partner and the field.
Those conversations became far more valuable than the configuration itself.
As the client and agency partner refined their process together, Speakcore evolved alongside them. Instead of forcing everyone into a one-size-fits-all workflow, we configured the platform to reflect the responsibilities that made the most sense for their organization.
Perhaps the most encouraging part of the project wasn’t that changes were needed.
It was that the client recognized them.
Successful implementations don’t end on go-live day. The best organizations continue evaluating what’s working, what’s creating friction, and where responsibilities should evolve as teams gain experience. That willingness to adapt is often what separates a good implementation from a great one.
The result wasn’t simply a revised workflow.
It was a clearer operating model, better alignment between internal teams and the agency partner, and a platform configured around how the organization actually wanted to work—not just how they initially thought they would.
The takeaway?
Technology implementations don’t just introduce new software—they introduce new ways of working. Even positive changes create friction while teams adjust to new responsibilities, new handoffs, and new expectations.
The hardest part of a new workflow isn’t learning the software. It’s learning to trust a new process.
