The role of the financial analyst is being transformed by AI. I’m exploring the rise of AI-powered ‘robo-analysts’ that can do everything from building financial models to writing research reports. What does this mean for the future of Wall Street research?
What I've Learned From 68 Companies
A few patterns in robo-analysts come up again and again.
The founders who handle robo-analysts well understand that your team matters more than your technology.
Why Most Approaches Fail
Many common approaches to robo-analysts are flawed at the root.
The root cause is usually one of three things:
Copying what big companies do without understanding why they do it. What works for Google doesn't work for a 10-person startup.
Over-engineering the solution when a simple approach would work better. I've seen teams spend six months building something that could have been done in two weeks.
Ignoring the human element. Technology is the easy part. Getting people to actually use it is where the real challenge lives.
What I Tell Founders
Before deciding anything about robo-analysts, start with three questions:
What's your timeline? Because the right approach for a company with 6 months of runway is very different from one with 3 years.
What have you already tried? Most founders have tried something. Understanding what didn't work is often more valuable than knowing what might.
Who on your team owns this? If the answer is "everyone" or "no one," that's your first problem to solve.
These questions seem simple but they reveal a lot about where a company actually stands.
This connects to broader themes around robo-advisors, AI risk management, AI trading that I've been thinking about a lot lately.
Final Thoughts
There are no shortcuts in robo-analysts, but there are smarter paths.
The strongest teams treat robo-analysts as a competitive advantage, not a checkbox. They invest in it early, measure it obsessively, and never stop improving.
If you're just getting started with robo-analysts, don't be intimidated. Everyone starts somewhere. The key is to start with the right mindset and the right framework, and then execute like your company depends on it. Because it probably does.
Frequently Asked Questions
Q:What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 234 startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
Q:How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.
Q:What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.
Q:How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.