Where AI Processing Ends and Advisory Judgment Begins

I reviewed a brief on my phone last week while making breakfast for my kids. My team had processed 12 documents overnight. I read the synthesis, found three errors and two missed connections, added my analysis, and had the deliverable updated. 10 minutes. I have no human employees.

That's the operating model of Fieldway Intelligence Services. I run an intelligence service for boutique advisors and consultants – surfacing what they need to know before they walk into a client conversation. I'm working about eight times faster than I was two years ago. That number makes me uncomfortable every time I say it, but it holds up, and I didn't hire anyone to get there.

What This Means if You're the Advisor, Not the Builder

Most boutique advisors reading this aren't building an AI research system. They're running client engagements and figuring out where AI belongs – in their own workflow or in a service they're considering.

The question that usually surfaces is "how much can AI do?" That's not quite the right frame. The useful question: where does my judgment have to live?

Every engagement has two distinct layers. The processing layer – reading, comparing, extracting, structuring – is what AI handles well, at a pace and scale no individual practitioner can match. The judgment layer is different: knowing what a pattern means for this client's specific history, reading what the data can't see, making the call that requires years in this particular room. AI doesn't improve that work.

The design question is the same whether you're building your own AI advisory workflow or evaluating a managed service: where does this engagement require my judgment? If you haven't decided that in advance, the live situation will decide it for you.

AI handles roughly 70% of what each engagement requires: reading, comparing, extracting, organizing. My last engagement featured 90 documents and a CRM with 16,000 rows. The systems I've built excel at pattern recognition across sources that no one would read cover-to-cover in the available time. That work happens while I'm not watching. The system processes; I review when it suits me, from my desk or from the kitchen. What I do – the other 30% – is read the synthesis, find what the system got wrong, make the connections it missed, and then have AI turn that into a brief the advisor can actually walk into a room with.

That boundary between AI processing and human judgment is an important line. It sounds obvious enough that we can skip talking about, but it isn't.

I've watched advisors try to let AI handle the interpretation by asking it what a data set means for a specific client relationship. It produces confident-sounding analysis. The confidence isn't earned, and the AI is often wrong in ways that are invisible until you've spent a decade in the room: a detail that changes meaning given that client's history, a pattern that looks like signal but is noise. My own workflow has the same exposure. My job is to catch what the system missed, not assume it didn't.

Getting that line wrong doesn't cost time. It costs trust.

Where the 30% Actually Matters

Earlier this year, a competitive brief came back with a clear finding: pricing pressure was building across a specific market segment. Multiple sources, consistent signal. The synthesis was accurate.

What the processing layer couldn't know – because it doesn't know the client's history – is that this segment was already off their strategic table. The pricing trend was real. Its relevance to the engagement wasn't in the documents. It was in a conversation that had happened months earlier.

The brief that went to the advisor was correct. But only because the synthesis had been designed to stop before conclusions. It surfaced the pattern; the judgment layer applied the context. What that pattern meant for this client stayed where it belonged.

That's what the human layer in this workflow is actually for – not catching AI errors, but knowing what the synthesis can't know, and building a process where that knowledge determines what the output means.

The 8x speed only holds if the output holds up. That means the division of labor has to be deliberate – designed before it gets tested in a live situation, not discovered by accident when a client is in the room. The solopreneur advantage isn't that AI does everything. It's that one person can now do what used to require a team. The catch is that you have to decide, in advance, exactly where your work starts.

The Question Worth Answering Before You're in the Room

If you're thinking about AI in your own advisory practice – building internal workflows, evaluating an intelligence service, or deciding which parts of your research to let AI touch – the design problem is the same one above. Where does your judgment live? What do you know about this client's history, their context, the things that won't show up in any document corpus, that has to stay with you?

That's your 30%. Not a hedge against AI getting things wrong. A deliberate protection of the work your clients are actually paying for.

The question isn't how much AI can handle. Most practitioners are surprised by how much it can. The question is whether you've decided in advance exactly where it stops – not because AI can't go further, but because further is where your value starts.