For many advice businesses, building a technology stack has historically meant selecting the right tools—choosing a CRM, layering on document generation software, and gradually adding systems to support compliance and operations.
But that model is starting to shift.
In a conversation between Patrick Gardner and Shaye Marx, General Manager of Operations at Kafka Bond & Co, a different philosophy emerges—one where technology is not simply adopted, but deliberately designed around the client experience and the long-term scalability of the business.
At the centre of this approach is a simple idea: technology should not dictate how an advice business operates. Instead, it should enable a better, faster, and more consistent experience for both clients and advisors.
Rather than thinking in terms of individual tools, Kafka Bond frames its approach through what it calls the “DARES” model—a framework that guides every decision across the business.
The model is built around five principles:
While each element is relatively straightforward in isolation, together they create a filter through which every process, system, and decision is evaluated.
This shifts the conversation from “what tech should we use?” to “how should the business actually operate?”
Technology becomes the output of that thinking, not the starting point.
One of the more subtle, but important, insights from the discussion is the emphasis on future scale.
Many businesses build systems that work for their current size, only to discover they break under growth. Kafka Bond takes the opposite approach—designing processes that will still function if the business doubles or triples in size.
This means identifying gaps early. A process that works for a small team may not hold under pressure later, and addressing that proactively avoids future bottlenecks.
It also creates clarity. When every initiative is measured against scalability, it becomes easier to prioritise what matters and ignore what doesn’t.
Despite the forward-thinking philosophy, the underlying stack itself is not radically different from many advice firms.
Kafka Bond uses Dash as its core CRM and document generation system, alongside tools like Xplan for research and additional data providers for market insights. AI tools—particularly Microsoft Copilot—have also become a central part of day-to-day operations.
What is different is how these tools are used.
Rather than treating each system as a standalone solution, the focus is on how they connect. Integration—whether through APIs, low-code tools, or custom-built solutions—becomes the priority.
Because without connection, even the best tools create friction.
AI plays a significant role in this ecosystem, but not in the way many expect.
The most immediate value comes from removing low-value tasks. Meeting notes, for example, have shifted from a time-intensive manual process to something that can be completed in minutes.
The impact is not just efficiency—it changes how advisors engage with clients.
Instead of focusing on capturing information, advisors can be fully present in meetings, observing reactions, asking better questions, and building stronger relationships. In this sense, AI does not replace the human element of advice—it creates more space for it.
This distinction is critical.
As Marx explains, AI should be used to support decision-making, not replace it. It can structure information, highlight risks, and suggest improvements—but the final judgment remains with the advisor.
A large part of Kafka Bond’s focus is on automation, but with a clear boundary.
Automation is most valuable when applied to repetitive, process-driven tasks—things like workflow triggers, document generation, compliance reminders, and data handling.
Several initiatives currently being explored reflect this:
These are not headline-grabbing innovations, but they are highly practical. Each one removes a small amount of friction, and collectively, they transform how efficiently the business operates.
While the potential of technology is clear, one of the biggest challenges remains integration.
Financial advice tools are not always designed to work seamlessly together. Many offer limited connectivity, requiring workarounds or custom solutions to bridge the gaps.
This is where low-code and no-code tools—such as Zapier or Make—become valuable. They allow businesses to connect systems without building everything from scratch, although even these solutions have limitations within financial services.
As a result, many firms are moving toward a hybrid approach—combining third-party tools with internally built solutions to create a more cohesive system.
One of the most practical insights from the discussion is the risk of over-adoption.
With new tools emerging constantly, it is easy to be drawn toward the latest solution—particularly when it promises efficiency or automation. But without a clear strategy, this can lead to fragmented systems and unnecessary complexity.
Marx highlights the importance of resisting this impulse.
Rather than building around individual tools, the focus should remain on the core system. Once that foundation is established, additional tools can be layered in where they genuinely add value.
This approach also reduces what he describes as “decision fatigue”—the tendency to continuously evaluate new options without committing to a clear direction.
Technology adoption is not just a systems challenge—it is a people challenge.
One of the key lessons shared is that change cannot be forced. Simply telling advisors or staff to use a new tool rarely works.
Instead, adoption improves when:
When individuals see how a tool saves time or improves their workflow, they are far more likely to embrace it.
This approach turns adoption into a pull, rather than a push.
Despite the heavy focus on technology, the conversation ultimately returns to a familiar point: the value of financial advice remains human.
AI can process information, generate documents, and support analysis. But it cannot replicate emotional understanding, judgment, or trust.
As Marx puts it, advice is not just about logic. It is about aligning strategies with how clients feel—something that cannot be fully automated.
In this sense, technology does not diminish the role of the advisor. It clarifies it.
The evolution of advice technology is not simply about adopting better tools. It is about rethinking how advice businesses are structured.
Kafka Bond’s approach demonstrates that:
Ultimately, the firms that succeed will not be those with the most advanced technology, but those that use it most effectively.
In that sense, the future of advice is not being built tool by tool—but process by process, decision by decision, and experience by experience.