[jimkri]

I've created agents for the following:

- ICP / Sales Agent: I hired an offshore resource and built a GPT that they can send titles and other identifiers to, and it would say if it was in our ICP or not. I created it for a specific process that has outlined steps and FAQ from that person on things they have encountered, I plan on adding more questions and answers. This was super helpful on saving time on answering questions about titles / improving the results of their work.

- Domain Policy Scan (SPF, DKIM, DMARC): I scan domains and find SPF records and then use an Agent and a prompt to break out all the system tokens from the SPF to understand the systems companies are using. The prompt is a consent work in progress, but I have it done to be really consistent

Both have been really helpful to my overall workflow.

[Lionga]

Isn't that just simple glorified workflow automation? Shouldn't "agents" do and decide what to do themselves based on the holy prophecy of VC and AI Startups ?

[PhilippGille]

Yes, for example from Anthropic's definition [1]:

> Workflows are systems where LLMs and tools are orchestrated through predefined code paths.

> Agents, on the other hand, are systems where LLMs dynamically direct their own processes and tool usage, maintaining control over how they accomplish tasks.

[1] https://www.anthropic.com/research/building-effective-agents

[jimkri]

This is helpful, thanks for sharing that.

[OutOfHere]

Those sound like basic LLM workflows with nothing agentic about it.

[jimkri]

You are right, it is more of an LLM workflow.

The workflows can be easily updated to be an agent, the scan already creates sales opportunities for me and can be updated to create messages based on active email campaigns that I have created.