Portrait Analytics: The Thought Partner Category – Neither Copilot Nor Agent

Portrait Analytics: The Thought Partner Category—Neither Copilot Nor Agent

When the market gives you two boxes to fit into, the ambitious move is building a third box entirely.

In a recent episode of Category Visionaries, David Plon, CEO and Co-Founder of Portrait Analytics, an investment research platform that’s raised $10 million in funding, shared why he refuses to position his product as either a copilot or an agent—and how the “thought partner” framing transforms budget conversations with institutional investors.

The False Dichotomy

By 2023, the AI product landscape had crystallized into two clear categories. You were either building a copilot—software that assists users in real-time, completing their thoughts and augmenting their work—or you were building an agent that operates autonomously, completing entire tasks without supervision.

GitHub Copilot defined the first category. Autocomplete for developers, predicting the next line of code. ChatGPT in conversation mode. Claude suggesting completions. The copilot sits alongside you, helping but never taking over.

Autonomous agents defined the second category. Systems that take a goal and execute multi-step workflows to completion. Email responders. Data analysts. Research assistants working in the background while you focus elsewhere.

When asked about Portrait’s market category, David’s response reveals immediate discomfort with this framework. “I don’t know. It’s the honest answer, I think.”

The Category Rejection

David can describe who Portrait serves—institutional investors doing fundamental research on public companies. But product categorization? That’s where it gets interesting.

“I do think we are building a different category of solution if you want to define it from a product perspective,” he explains. The existing framework doesn’t capture what Portrait actually does.

“There are AI products out there that tend to be co pilots. So something like GitHub, Copilot or whatever is like a classic example of that where it’s like, you know, something that is auto completing for you or a chat bot,” David notes, establishing the first category.

“And then there are also products out there that are very much agents doing specific kind of tasks in a fully automated way,” he continues, acknowledging the second category.

Then comes the pivot: “And I try to think about like what Portrait is doing is a bit of it’s a different category and more of a synthesis engine.”

The Synthesis Engine Concept

What makes a synthesis engine different? David’s definition reveals sophisticated thinking about workflow integration versus task completion.

Portrait is “doing a lot of challenging research tasks at a very broad scale, but it’s doing so in a way that deeply integrates within existing research workflows.”

This is neither copilot nor agent. It’s not completing your sentences as you write. It’s not autonomously generating entire reports while you’re away. It’s operating at a different level—synthesizing information at scale while remaining embedded in how investors actually work.

The distinction matters because it changes how users interact with the product. A copilot requires constant attention. An agent requires trust in autonomous operation. A synthesis engine requires neither—it works at your pace, integrating into your process without demanding real-time interaction or complete delegation.

The Thought Partner Articulation

But “synthesis engine” is product language, not buyer language. David needed something institutional investors would immediately understand. His solution: the thought partner metaphor.

“The best I’ve thought of is a thought partner, right?” David says, then unpacks what this means in practice.

“Like if someone was on your team as an investor, you are not going to sit next to them and talk to them every single day about every piece of work that they’re doing.”

This eliminates the copilot comparison. Copilots require constant interaction. Thought partners don’t.

“But they’re also not going to be like in a silo just doing work all by themselves with no interaction with the team.”

This eliminates the agent comparison. Agents work independently. Thought partners collaborate.

“And that’s kind of how we think about what a thought partner is on an investment team.”

Why The Metaphor Works

The brilliance of “thought partner” is that it maps to something buyers already understand: team dynamics. Every institutional investor has worked with different types of team members. Some need constant oversight. Others work better independently. The best ones—the thought partners—hit a balance.

This reframes the entire evaluation. Instead of comparing Portrait to other software tools, prospects compare it to hiring decisions. “When we position this as someone you would hire onto your investment team, that tends to really resonate,” David explains.

The budget conversation transforms. You’re not competing for software budget against other tools. You’re competing for headcount budget against junior analysts. “There aren’t people going out there and saying, I need a thought partner. There are absolutely firms going out there saying, I need to hire more junior analysts.”

The Hiring Decision Parallel

David makes this explicit: Portrait positions itself against a hiring decision, not a purchasing decision. “Ultimately there aren’t people going out there and saying, I need a thought partner. There are absolutely firms going out there saying, I need to hire more junior analysts.”

This changes everything about how prospects evaluate the product. The question isn’t “Should we buy this software?” It’s “Should we add this capability to our team?”

The comparison criteria shift entirely. Instead of features and pricing, prospects evaluate leverage and productivity. “Anything that can join the investment team and immediately add leverage to what every other person in that investment organization is doing. Much in the same way a junior analyst would goes a really long way.”

The Limitation Acknowledgment

David doesn’t oversell the metaphor. He’s clear about what Portrait can’t do. “While as a junior analyst, Portrait won’t be able to do a lot of the deep research like tasks that require interviewing people, for instance, or financial modeling in a really detailed way.”

But he immediately pivots to where Portrait excels: “Portrait can be a very useful member of your team that massively accelerates the speed and depth of idea generation, context building and industry level context maintaining.”

This honest assessment strengthens the positioning. He’s not claiming Portrait replaces all analyst functions. He’s claiming it handles specific, high-value tasks better than human alternatives—while integrating into workflows like a team member, not a tool.

The Asset Frame

The thought partner positioning works because it aligns with how investment firms think about value creation. “Especially in a field like this where ultimately for an investment firm, their main asset is the people, right? They have IP and humans.”

This is the key insight. Investment firms don’t optimize for software efficiency. They optimize for intellectual capital. Positioning Portrait as intellectual capital rather than software efficiency changes the entire value proposition.

The metaphor implies appreciation over time. Tools depreciate. Thought partners become more valuable as they learn your preferences, understand your style, integrate into your process. This sets up longer-term thinking about ROI.

The Category Creation Challenge

When asked directly about category, David admits uncertainty. “I probably should come up with one,” he says about finding a better name than “thought partner.”

This honesty reveals something important: category creation is hard, especially when you’re genuinely building something new. The copilot and agent categories emerged from clear paradigms. GitHub’s autocomplete. Autonomous task completion. Both map to familiar concepts.

Synthesis engines that act as thought partners? That’s genuinely novel. The challenge isn’t marketing—it’s articulating something that doesn’t have an obvious precedent.

The Learning From Others

David’s approach to category positioning shows up in how he thinks about marketing more broadly. When discussing companies he learns from, he mentions Stripe’s clarity: “It was just so clear like what the value proposition is and how to get started in a really quick way.”

The thought partner framing achieves similar clarity. It might not be a formally defined category with analyst reports and conference tracks. But it’s immediately comprehensible to the target buyer.

The Long-Term Bet

Category creation isn’t about today—it’s about where the market goes. David’s five-year vision hints at why the thought partner framing matters: “Ultimately, I believe these models within the context of an investment research firm really become like core synthesis engines that are consuming every piece of content that the investment firm has access to and generating synthesis and insights in a really high quality and auditable way.”

The thought partner today becomes the operating system tomorrow. But you can’t position as “operating system” when you’re early-stage. You need an intermediate framing that’s ambitious but believable. Thought partner hits that balance.

For founders building products that genuinely don’t fit existing categories, David’s approach offers a framework: acknowledge the existing categories, explain why neither fits, create a metaphor that buyers immediately understand, and map it to existing budget conversations they’re already having. Sometimes the best category isn’t a category at all—it’s a role.