What Does a Custom AI Agent System Actually Cost?
Field Notes · 2026-06-03
Treating AI less like a search tool and more like something you give a proper task to. Here's the workflow I've landed on for research, and the prompts that actually make it work.
For a long time I was using AI the same way most people do — opening a chat, asking something, reading the response, moving on. Useful, but not that different from a smarter Google.
What changed was treating it less like a search tool and more like something you give a proper task to. That shift sounds obvious, but most people I talk to are still in the first mode. The gap between the two in terms of what you actually get done in a week is significant.
Here's what I've landed on for research specifically.
The workflow matters more than the model
Claude, ChatGPT, Gemini — all have search built in now and are genuinely capable for research tasks. The model choice matters less than most people think. What makes the difference is how you structure the task.
"Tell me about X" gets you an essay. "Research X and give me a structured brief — the five things I actually need to know, key sources, and anything that seems contested or unreliable" gets you something usable. The format instruction isn't cosmetic. It changes how the model organises its thinking.
The other pattern that's made a real difference: separating research from analysis into two passes. Ask it to gather first, then interpret. Running both in one prompt tends to produce shallow output on both — the model is still working through the information while trying to form conclusions about it.
What I use it for
A daily AI news digest
I automated this. A scheduled workflow runs each morning, sweeps the latest AI developments — new model releases, tool launches, anything notable — and produces a written summary before I've opened anything else. It also pulls YouTube recommendations on AI topics worth watching, with a brief note on why each one is relevant.
The prompt detail that made this actually useful: requiring it to explain why something matters, not just that it happened. "New image model dropped" is noise. "This is worth paying attention to because it's the first open-weight model at this capability level" is something I can act on.
Before this, I was staying across the space manually and inconsistently. The difference in what I actually know now versus six months ago is noticeable.
Tool and vendor research
When I'm evaluating tools to recommend to a client, I want to know what practitioners actually think — not the documentation, but the forums, the technical reviews, the edge cases people hit six months in. Agents are good at surfacing this if you ask for it explicitly.
One thing I've learned the hard way: agents are reliable for technical comparisons, unreliable for pricing. Pricing changes constantly and agents often surface figures that are out of date. Always verify pricing manually before it goes in front of anyone.
Getting up to speed fast
If I'm going into a client conversation about something I'm not deeply across, I'll run a 15-minute research session first. The instruction that works: "give me what I need to have a useful conversation about this, not a comprehensive overview." That constraint matters. Without it you get more than you can absorb.
Understanding the existing conversation before writing
Before writing about a topic, I'll ask an agent to surface the existing takes — mainstream view, pushback, where there's genuine disagreement. Not to copy any of it, but so I'm not writing something that's already been said better somewhere else.
What makes research prompts work
A few patterns I keep coming back to:
Ask it to look for the negatives, not just the positives. "Research these tools and flag limitations, known issues, and what users complain about" produces something more honest and more useful than "research these tools."
Specify recency for anything fast-moving. "Focus on the last three months" makes a real difference in AI specifically — a lot can change and older content dominates search results by default.
Always ask for a sources list. It makes the output more trustworthy and gives you somewhere to go if you need to go deeper.
Two-pass for anything important. Research first, then analysis.
What it doesn't replace
Talking to people who are actually inside a problem. Primary research is still irreplaceable.
And the judgement call about what matters in a specific context — that still sits with you. Agents are good at finding and organising information. Knowing which of ten things is worth acting on is a different skill, and it's still yours.
Most businesses I work with have a research problem they don't realise is solvable. Their teams are spending hours on information gathering that could be compressed significantly — staying across markets, evaluating vendors, preparing for client conversations. If that sounds familiar, let's talk.