Mike Logashov, portrait

Mike Logashov

Director of Product, CFP, CLU, Objectway

Mike is the Director of Product for Financial Planning at Objectway Solutions Inc. With over a decade of experience in the financial services industry, Mike has held both client-facing and product management roles, specializing in financial planning. Before joining Objectway in 2024, Mike worked at one of Canada’s largest financial institutions, leading national projects across various aspects of wealth planning. Mike holds a Bachelor of Commerce in Economics from Toronto Metropolitan University (formerly Ryerson University) and is a Certified Financial Planner (CFP) and Chartered Life Underwriter (CLU).

Lessons from the field on simplifying advice

A few weeks ago, I had the pleasure of speaking at the IFB Summit. I was initially planning to revisit a presentation and demo I’ve given on how to leverage financial planning software to uncover business opportunities. It’s an important topic, but over the summer and early fall I had the opportunity to speak with many different advisors, associates, financial planners and senior managers at the firms that employ them, and I felt that sharing a few themes from those conversations would be more helpful and relevant. Interestingly enough, it made me reflect on my own time in the field, and specifically on what worked and what didn’t.

One early mistake I learned to correct was assuming that rigour equals clarity. I thought good advice meant a dissertation of portfolio optimization, retirement analysis and visual aids. As many young advisors learn, sometimes you get a polite nod of understanding, only to realize you lost the client 20 minutes ago. A colleague, friend and mentor of mine once told me that “complexity kills sales,” and nearly every advisor I’ve spoken with since has said a version of it. That message has stuck with me and has influenced my decisions in the technology space ever since. A few weeks after hearing that quote, a senior decision maker at a large insurance company told me that “people say they want something complex, but they don’t use it,” and that the loudest feature requests often come from a small, vocal minority. These conversations solidified an idea: complexity is not the same as sophistication.

Complexity in financial planning software, and in wealth management technology at large, is very easy to find. To the vendor, the firm and the advisor, complexity feels like rigorous work done by professionals, and a large quantity of output feels like the right direction. In reality, it often confuses clients, creates quality challenges for staff and impresses peers more than clients. Complexity can hide in a number of places in the advisor’s tech stack. A prime example is the plan output itself. After speaking with many advisors, I’ve found that the most impactful visuals come down to three concepts: a lifetime cash flow chart that shows no shortfalls, a net worth chart showing assets growing over time, and some kind of comparison between where the client is with and without the plan. It reminded me of working on a case with a very successful planner. The client was a high-net-worth financial professional who I assumed needed to be impressed with pages and pages of analysis. At the start of the presentation, the planner flipped the plan to page 15 or so and put her finger on the large number representing the client’s net worth at life expectancy. “OK, let’s start by saying that you’ll be fine.” The meeting went from there. It taught me that a single idea can be enough to satisfy even the most sophisticated client.

Similarly, one of the best planning specialists I’ve worked with was a prolific simplifier. He was efficient, charming and razor sharp (no pun intended). In contrast, many colleagues tried to model everything perfectly. To them that seemed like a good idea, but it took a lot of time, created friction with clients and the team, and ended up being more error-prone and requiring rework. What I took from that is that simplification is a skill, not a shortcut. The depth and expertise need to be there, but the best outcomes happen when that depth stays underneath and a layer of clarity sits on top of the client experience.

Beyond the plan itself, complexity also hides in the discovery phase. One advisor shared how often clients get overwhelmed by detailed fact finders and intake questionnaires. To simplify his workflow, he created his own, asking one question at a time, with the goal of taking no more than 10 minutes of the client’s time. The idea was to start with what matters most to the client and deepen the relationship over time. This advisor had intuitively discovered the design principle of progressive disclosure: clients should be exposed to complexity gradually, and a straight, linear path is often the easiest to commit to.

From a technology perspective, the most common pain point shared with me was that there are “too many platforms.” They often compete with one another, don’t communicate with one another, and require manual re-keying of data, which hurts efficiency. For independents, integration is left to vendors, so advisors become their own CTOs and CIOs. During the presentation, I asked participants to audit their tech stack: where do they enter data more than once, where does communication break down, and what are they paying for but not using? A close second was a question senior leaders keep facing: “How do I leverage AI in my practice?” Interestingly enough, AI adds its own layer of complexity. Ten platforms means ten chatbots, all competing for eyeballs and attention. Non-deterministic, black-box numbers that can’t be explained to clients or compliance teams. Language models confidently providing incorrect or incomplete information. In our view, AI should make plans easier to explain and understand, not harder to trust.

When I consider these lessons and conversations and apply them to the product lines my teams work on, a few key ideas emerge. First, depth should be available on demand, not served by default. Second, decisions should be presented one at a time. Third, data should be entered once. And finally, software should perform well enough to be used live in front of clients. We’re applying these lessons across our product suite, and I’m excited about our future in this space. I’d like to close with a quote from Charles Mingus that sums up my feelings about the complexity paradox perfectly: “Making the simple complicated is commonplace; making the complicated simple, awesomely simple, that’s creativity.”

Engage your prospects. Assess their needs. Deliver real results.

Free 30 day trialRequest a demo