Daniel Ladner: How FinTech Certification Strengthens Decision-Making in Tech Investment Advisory

Technology has stopped behaving like a sector and started behaving more like the infrastructure underneath everything else. It sits behind the payment rails moving client money, the platforms pricing risk, and the reporting systems telling a family office what it actually owns. The technology itself may be invisible to the client, but the decisions built around it aren't.

Overall, it has changed what clients need from the people advising them. Daniel Ladner, a Certified Portfolio Manager and Senior Vice President of Wealth Management, has spent more than 25 years in finance watching technology become harder to separate from the businesses and portfolios his clients depend on.

A fintech certification can help advisors get closer to that underlying machinery. At its best, the training goes beyond learning financial terminology or adding another credential to a résumé. It teaches advisors how financial technology is built, how data moves through these systems, and where the assumptions behind a technology-driven business can start to break down. For someone working across institutional mandates and private wealth, that knowledge can stay useful long after the coursework ends, especially as new technologies keep changing the investment landscape.

What a FinTech Certification actually covers

Ladner earned his Certified Portfolio Manager designation from the Columbia School of Engineering Fu Foundation School, in conjunction with the Academy of Certified Portfolio Managers and Fintech Computer Programming. The program reflects a straightforward idea: understanding an investment increasingly requires understanding the technology and systems behind the business.

The quantitative side of that training teaches advisors to work with data more directly. That means understanding what a model assumes before relying on its output, recognizing a data set's limitations, and knowing when a backtest reveals something meaningful about a strategy and when it's simply describing the past.

Then there's the computational side.

Learning to program, even at a practical level, can change the way someone looks at a software company. Code stops looking like an abstract technical detail and starts looking like part of the business itself. It has costs. It has dependencies. It breaks. It needs to be maintained. And those realities can have a direct effect on a company's margins and long-term prospects.

That perspective can lead an advisor to look past the story a technology company tells about itself and start asking what has to be true for that story to work.

Why technology investing punishes surface-level analysis

Technology companies can be particularly difficult to evaluate because so much of their value depends on what happens next. Two businesses can report similar revenue while carrying very different risks. A subscription model and a licensing model may look comparable at a glance, but the underlying economics can be very different.

The same goes for margins. A company's gross margin may look like a durable advantage until someone examines how dependent it is on inexpensive infrastructure. A technical moat may depend heavily on contracts with customers or suppliers. Those contracts can change.

Technical knowledge gives an advisor another way to test those assumptions.

How much of a company's costs rise as usage increases? What happens to margins if an infrastructure provider raises its prices? Is a product genuinely difficult to replicate, or have customers simply had little reason to look elsewhere? How much engineering capacity is devoted to developing new products, and how much is spent keeping existing systems functioning?

Security raises another set of questions. For a company handling financial assets or sensitive customer information, the strength of its technology infrastructure can quickly become a business risk. An advisor who understands how those systems work is better positioned to assess whether security is built into the business or simply discussed in the risk section of an annual report.

How Daniel Ladner applies certification training to client decisions

Dan Ladner began his career with his current firm in 2008. His responsibilities include analyzing client objectives, developing strategic and tactical asset allocation policies, selecting investment managers, and reviewing investment results.

Each of those decisions has a technical component.

Understanding a client's objectives means looking beyond what they say they want and examining what their financial circumstances actually require. Building an allocation means understanding how investments behave together, including what can happen when correlations that normally look stable change during a period of market stress. Evaluating an investment manager means separating the decisions that drove performance from the market conditions that happened to help. Reviewing results means asking why a strategy worked, not simply whether it made money.

His team develops customized wealth management strategies for entrepreneurs, venture capitalists, private foundations and endowments, and privately controlled corporations. That mix of clients brings technology into the conversation in very different ways.

An entrepreneur selling a software company may suddenly have significant exposure to the technology sector through the business they built. A foundation may view technology exposure as one small piece of a portfolio designed to support spending for decades. The circumstances are different, but both situations benefit from an advisor who can look beyond a sector label and understand what actually drives the businesses involved.

Certification as a discipline, not a one-time credential

The designation itself is only part of what a certification can provide. The lasting benefit may be the expectation that learning doesn't stop once the credential is earned.

Ladner has continued his education well beyond the CPM. His professional development includes the Chicago Booth School Certified Private Wealth Advisor Program and graduate studies at Harvard University Extension School.

His regulatory credentials require the same kind of ongoing attention. He maintains Series 7, 9, 10, 31, 63, and 65 licenses, along with life insurance licensing, and is registered to conduct securities business and provide investment advisory services in more than 30 states, including New York, California, Florida, and Texas.

Technology presents an obvious challenge to that kind of education. No certification program can stay perfectly current with an industry that keeps producing new technologies, business models, and risks.

What can endure is the method.

An advisor who understands how to examine an unfamiliar technology, question its assumptions, and figure out where the risks actually sit has something more useful than a list of technologies they learned about several years ago. That's why keeping up with new developments becomes part of the job itself. The questions change as the technology changes.

What clients should ask about an advisor's technical training

A list of credentials doesn't tell a client much about how an advisor actually thinks. A few direct questions can reveal much more.

What did the certification require? A program involving examinations and applied work tells you something different from one based primarily on attendance.

How does that training affect the advisor's investment process? Ask for an example. A specific decision usually says more than a general statement about the importance of technology.

How does the advisor evaluate a technology company they don't already understand? The answer can reveal how much of their process depends on a familiar narrative and how much depends on understanding the business underneath it.

And perhaps the most useful question: What did the advisor get wrong during a previous technology cycle, and what changed afterward?

None of this requires a client to become a technology expert. The advisor should be able to translate. Someone who understands the underlying systems should be able to explain why they matter without hiding behind technical language.

---

About the author

Daniel Ladner, CPM, is Senior Vice President of Wealth Management at a financial services firm, where he has provided tailored investment advice for more than 17 years. A Certified Portfolio Manager accredited through Columbia University, Daniel Ladner works with entrepreneurs, venture capitalists, private foundations, endowments, and privately controlled corporations on long-term wealth strategy. He was named to the Best-In-State Forbes Wealth Management Team for 2023 and 2024, a recognition selected independently by SHOOK Research in partnership with Forbes.