278 | How To Build AI Agents: A Step-by-Step Playbook for Business Leaders with Jim Spignardo

24 Mar 2026 · 52 min · 30 chapters

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

```markdown

Podcast Episode Notes

Leveraging AI - Episode 278

Episode Overview

  • Title: How To Build AI Agents: A Step-by-Step Playbook for Business Leaders
  • Guest: Jim Spignardo, Director of Cloud Strategy & AI Enablement at ProArch.
  • Description: Discussion on building effective AI agents to solve practical business problems, highlighting a case study of a company that significantly improved its proposal process using AI.

---

Key Themes and Concepts

  1. The Importance of Effective AI Implementation
  2. Main Argument: Companies often blame AI failures on the technology itself when the issue usually lies in poor implementation.
  3. Focus: Understanding how to build AI agents that integrate smoothly with existing business processes.
  1. Case Study: Proposal Response Optimization
  2. Example: A global organization with over 500 employees utilized AI to reduce proposal effort by 80% and improve response quality.
  3. Problem Addressed: Traditional RFP processes were time-consuming and had a low success rate (about 50%).
  1. Building AI Agents
  2. Framework Provided:
  3. Identify High-ROI Opportunities: Focus on areas where AI can reduce time and increase effectiveness.
  4. Data Structuring: Importance of aligning data with business needs.
  5. Effective Instruction Design: Crafting clear instructions for agents to follow.
  6. Avoiding Common Mistakes: Learning from prior implementations to mitigate risks.
  1. Use Case Specifics
  2. RFP Process Overview:
  3. Understanding client requirements deeply.
  4. Integrating internal knowledge to create winning proposals.
  5. Reducing the overall proposal drafting time.
  1. Discussion on Implementation Steps
  2. Identifying Use Cases:
  3. Organizations should assess where automation can drive growth and efficiency.
  4. Using AI Tools:
  5. Utilizing platforms like Microsoft Copilot to facilitate agent creation.

---

Actionable Framework for Building AI Agents

  1. Identify Opportunities: Assess where AI can solve high-impact problems.
  2. Data Preparation:
  3. Organize and clean data relevant to the tasks at hand.
  4. Ensure data security and compliance are addressed.
  5. Design Instructions:
  6. Develop a clear and structured guideline for the AI to follow.
  7. Testing and Iteration:
  8. Use iterative testing to fine-tune instructions.
  9. Engage in continuous learning to enhance agent functionality.

---

Additional Insights

  • Data Relevance: The quality of AI outputs is directly linked to the quality and relevance of the data fed into the system.
  • Automation Benefits: Effective AI implementation can drastically reduce workload and improve success rates in business processes.

Final Thoughts

  • AI has the potential to transform business practices by driving efficiency and generating better outcomes, but requires careful and thoughtful implementation.
  • Continuous improvement and adaptation of AI agents are crucial to leverage their full potential in the business landscape.

---

Resources Mentioned

  • Jim Spignardo’s LinkedIn: [Jim Spignardo on LinkedIn](https://www.linkedin.com/in/jim-spignardo)
  • ProArch: [Visit ProArch Website](https://proarch.com)
  • Ultimate AI Course for Business People: [AI Course](https://multiplai.ai/ai-course/)
  • YouTube Full Episodes: [YouTube Channel](https://www.youtube.com/@Multiplai_AI/)
  • Join Live Sessions and Events: [Event Link](https://services.multiplai.ai/events)

---

Conclusion This episode provided valuable insights into building AI agents effectively within organizations. By focusing on strategic implementation, data relevance, and iterative improvement, business leaders can unlock significant efficiencies and drive growth. ```

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Chapters

Tap a time to open that second in VO

Understanding AI Agents

0:45 to 2:50

Discussion on the importance of AI agents and their implementation in businesses.

“Arch, which is an IT services and consulting company that helps other businesses with their IT services.”

Introducing Jim Spignardo

2:50 to 3:48

Introduction of guest Jim Spignardo and his expertise in AI and IT.

“And so I'm very excited to welcome Jim to the show.”

Jim's AI Journey at ProArc

3:48 to 6:15

Jim shares his experiences and strategies in implementing AI at ProArc.

“I'll go ahead and share my screen and kind of get things rolling here.”

Effective AI Licensing Strategy

6:15 to 7:17

Jim highlights the importance of identifying use cases before providing AI licenses.

“We're going to jump around a little bit.”

The Importance of AI in Proposal Writing

7:17 to 8:10

Discussion on how AI can improve the proposal writing process.

“So that's one thing that is, you kind of said in a sentence in the background, like, no, this is actually pure gold.”

Building AI Agents

8:10 to 11:45

Jim explains the process of building AI agents for business applications.

“And that's been our intent all along our journey.”

The Best Method for Building Agents

11:45 to 12:39

Jim shares a method involving live chat to develop effective agent instructions.

“So I'm like, okay, I have these four RFP documents.”

Live Demo of AI Agent Creation

12:39 to 14:01

Live demonstration of creating an AI agent and its functionalities.

“Once it's working and you went through different lefts and rights and turns and kinks, this is where I ask it to actually turn it into instructions.”

Building AI Agents: Real-time Development

14:01 to 16:44

Learn how to create AI agents with real-time output and testing capabilities.

“And the nice thing is you kind of work in this canvas on the left-hand side, and then the right-hand side, it kind of starts to output and build what you're actually creating.”

Understanding Instruction Sets for AI Agents

16:44 to 19:44

Discover how to create effective instruction sets for AI agents to enhance their functionality.

“for clarification or additional documents, incorporate user feedback.”
Show all 30 chapters

Best Practices for Uploading Content

19:44 to 22:22

Explore the advantages of linking AI agents to SharePoint versus manual uploads.

“If you're uploading a document, that's the document it's going to use.”

Sharing AI Agents: Permissions and Access

22:22 to 25:08

Understand how to share AI agents within organizations while managing access permissions.

“Well, then you kind of have to go, hey, assume I'm a different role at this point.”

Editing and Customizing AI Agents

25:08 to 28:00

Learn how to edit and customize AI agents for specific organizational needs and compliance.

“and you then remove the agent, it doesn't remove the permissions.”

Crafting Effective RFP Responses

28:00 to 28:40

Learn how to structure RFP responses with best practices and past documents.

“We also have information in our sales and marketing website, which probably is going to fill in a lot of those sales pitchy parts of the RFP.”

Utilizing AI for RFP Analysis

28:40 to 29:44

Discover how to leverage AI agents to streamline RFP analysis and response.

“We also gave it our location for all of our previous RFPs.”

Building Multiple AI Agents for RFPs

29:44 to 30:47

Explore the advantages of using multiple AI agents for different RFP tasks.

“they could be in a chat in any application or just general chat.”

Integrating AI Agents in Conversations

30:47 to 31:55

Understand how to efficiently integrate AI agents into project discussions.

“and a third one that actually writes the proposal outline, and a fourth that writes the details for the proposal.”

Enhancing RFP Drafts with AI

31:55 to 33:44

Learn how AI can enhance the drafting process of RFP responses.

“primary task you want it to complete, it's a good chance you probably want to create another agent.”

Structuring Proposal Responses Effectively

33:44 to 36:12

Discover the importance of structured responses and data integration for proposals.

“And now you'll notice what it's doing here.”

Using AI for Compliance Checklists

36:12 to 37:49

Learn how AI can automate compliance checks for RFP responses.

“And it was even able to go down here when we started working on pricing models to know that we actually do penetration testing and access point lifecycle design.”

Achieving Detailed RFP Responses with AI

37:49 to 40:02

Explore strategies for achieving detailed responses using AI tools.

“And or do you want a compliance matrix and executive summary only?”

Efficiency Gains in RFP Processes

40:02 to 42:08

Learn about the efficiency gains in RFP processes through AI use.

“And this way, because if you ask AI to write the full document, let's say it's supposed to be 150 page of answer, you're going to get six pages, sometimes 12.”

Improving RFP Win Rates with AI

42:08 to 42:45

Learn how AI can significantly reduce drafting time and improve win rates for RFPs.

“This section reads a little inauthentic for who we are.”

Evaluating Expertise in RFPs

42:45 to 43:48

Understand the importance of evaluating company expertise in the RFP process and how AI can streamline this.

“It's because we're not qualified enough to do the work.”

Using AI for Document Collaboration

43:48 to 45:28

Discover best practices for using AI tools like Canvas for document collaboration and review.

“These are the people you don't want to get out of their day job because they're the one that generally need the most amount of revenue to the company.”

Data Management for AI Success

45:28 to 46:29

Learn the critical steps for organizing data to enable effective AI implementation in business.

“So you can take all of that ongoing kind of workshop benching stuff and say, now I'm done, put it in Word, and we'll send it off for approval or last draft or last review by humans.”

Iterative Development of AI Agents

46:29 to 47:49

Explore the process of iteratively developing AI agents and enhancing their capabilities.

“agent to be able to do the things that it knows how to do.”

Understanding Microsoft Licensing for AI

47:49 to 48:58

Get insights on Microsoft’s licensing models for AI agents and their implications for businesses.

“And it will write you another paragraph or two in bullet points and will tell you exactly where to put it in.”

AI Transforms Proposal Writing

48:58 to 50:03

Hear how AI has revolutionized the proposal writing process for efficiency and effectiveness.

“going to use 30 worth of copilot every month right yeah and now you have 300 employees i go So$30 is not a big deal.”

Connecting with Jim Spignardo

50:03 to 50:58

Learn how to connect with Jim Spignardo and access resources on AI and technology.

“I write about three articles a week, topics in AI and technology.”
Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00Jim Spignardo:Hello and welcome to another live episode of the Leveraging AI podcast, the podcast that shares practical ethical ways to leverage AI to improve efficiency, grow your business and advance your career. This is Isar Maitis, your host, and most companies today are looking for ways to build AI agents. And if they're not, they will be sometime very soon. Now, that being said, most companies do not really understand what's involved in building AI agents that will work effectively, consistently, and safely within the environment while leveraging the resources that they already have, such as the data, the knowledge, and so on.

0:38Jim Spignardo:And that is exactly what we're going to focus on in our episode today. Our guest today, Jim Spignardo, is the Director of Cloud Strategy and AI Enablement at Porch Arch, which is an IT services and consulting company that helps other businesses with their IT services. And as you can imagine, in the past two years, that means a lot of AI. And Jim is the one that has been leading it. Now, in addition, he has a couple of decades in the IT space, mostly in the Microsoft universe. So he comes with a lot of experience way before AI on how to implement business processes with an IT through an IT lens in an effective way, which makes him the perfect person to teach us this.

1:20Jim Spignardo:Now, this means that Jim in his day-to-day, he helps other companies identify opportunities for implementing AI agents and then helping them put together in place all the stuff that they need, such as data alignment with their business needs, data safety and security aspects, all these kinds of things come into play on what Jim does on the day-to-day. And today he's going to walk us through basically that process end to end. What to do in order to build an agent effectively and to make this even more interesting, the specific use case that we're going to use to give as an example. He's going to present a process on how to write effective proposals based on RFPs.

2:07Jim Spignardo:Now, even if you don't do RFP work and you just write proposals, this is still a very good thing for you to learn because it's basically saying, how can I deeply understand the requirements of my clients using AI? And how can I connect that to the knowledge base that I have inside my company in order to write a proposal that is going to win me the business, which I assume most of you want to know, because that means you can win more business with less effort, which is usually what businesses is trying to do. And because I think both these aspects, knowing how to write and create agents in an effective way, as well as winning more business by writing better proposals with a deep understanding of the requirements of the client, are both extremely valuable in today's era.

2:51Jim Spignardo:And so I'm very excited to welcome Jim to the show. Jim, welcome to Leveraging AI. Thank you so much, Isar. Appreciate it. Great to be here. We have a live audience. So we have people here joining us on Zoom. We had a technical issue on LinkedIn. So if you were trying to join us on LinkedIn, I apologize. We'll try to figure it out for next week. But if you are with us live, so first of all, thank you. Feel free to introduce yourself in the chat, say where you're from, what you want to learn today, kind of like why you joined this session. And if you have any questions, please write them in the chat.

3:25Jim Spignardo:I will bring them up to Jim in the right time. If you're not here with us live, the question is why not? We do this every single Thursday at noon Eastern, and you can come and join the cool people and be able to ask questions instead of just listening after the fact. So feel free to come and join us. There's a link on how to do this in the show notes. So with two clicks, you can sign up for this, have it on your calendar, and join us whenever you can. But now, Jim, the stage is yours. Show us the magic. Appreciate it. Thank you very much, Yisar. I'll go ahead and share my screen and kind of get things rolling here.

3:57For those of you who are just listening, by the way, we're going to tell you everything that's on the screen.

4:03Jim Spignardo:So you don't have to be worried about that this is a screen heavy kind of thing. But if you do want to see this, you can see the episode on YouTube and or on Spotify. There's now a way to watch the video. So either way, you can do that. But if you cannot, that's perfectly fine. We're going to explain everything that we're doing. Yeah, thanks. I appreciate that. And so Isar made a real interesting commentary. And we've been on this journey at ProArc probably almost two years now. And the way we kind of got started was really looking at the use cases, the high value, low effort use cases that we could deploy in our organization.

4:40And we rolled out our licenses of copilings, copilings over many months once we've established use cases for individual personas and roles. And one of the ones that we came to as soon as we got to sales was responding to RFEs, requests for proposals. Traditionally, as an organization, it is something we absolutely dreaded. It usually came with a very long document of requirements, scope in deliverables, and asked a lot of information about our organization. and although we responded to many in the past, it didn't make success, maybe about a 50 % success rate. But what it really did was took away from a lot of people's time because these things usually came out of nowhere.

5:27You know on a Tuesday and expect to be able to respond by Friday to this and put together something that was actually going to have impact and win you the business. And so in a lot of cases, we were becoming a little shy about responding. And so we knew there was an opportunity here to leverage AI, specifically Copile, to help us with this. What we really needed to do, though, was start organizing our data. And so we started pulling together various sources of information that we've used in the past, other RFPs, various information about our organization, as well as websites that actually talk about what makes up a good RFP.

6:08Jim Spignardo:And so that was kind of the starting building blocks. And what I'm going to show you today is kind of how we began that process. We're going to jump around a little bit. I'm going to show you initially how you can kind of get started from a known code perspective of just telling Copile what you want to do and show you how it starts to build the framework for that engine. And then we'll kind of switch over to the one we've actually built to show you what looks like in the background, what kind of sources it has. And then we'll actually put a simulated RFP into the system to see how it actually responds.

6:42Jim Spignardo:I want to pause you just for one second because you said two things that I think are really, really important. One, which I really like and too many companies do it the wrong way, is you said we started giving licenses to people after we identified use cases for them to use. Most companies get licenses to everybody and then they try to figure out what to do with them. So what Jim is saying is the right way to do this. find the right use cases for the right departments, for the right people, train them on how to use the licenses to do these things, hopefully give them some kind of a working environment so they can just use it and then develop from there and then give them the licenses.

7:19Jim Spignardo:So that's one thing that is, you kind of said in a sentence in the background, like, no, this is actually pure gold. The other thing is the way I tell people, the way you need to look at building agents is where you have business bottlenecks. and you described the perfect bottleneck. It is driving business to the company if you do this successfully, but if you consistently struggle with doing this, it means you're investing a huge amount of efforts of the company for maybe a 50 % success rate. This is the ultimate thing to automate, right? It's going to, by definition, it's going to drive new business and it's not going to do this by consuming more time that may not be useful for the business.

8:06Jim Spignardo:So you're winning on both sides. And so both these things are fantastic even before we get started. Yeah, no, absolutely. And that's been our intent all along our journey. We need to justify, because it's not cheap, this technology is not cheap, at least the stuff that's good and worth using. And so we need to make sure that we're making wise investment. And we've done this repeatedly across various groups. I'm in charge of tracking their adoption. And so, you know, this has been a very successful model for us. Awesome. If you're following along and you have a Copilot license and you wanted to kind of see what this is all about, I'm in the Copilot chat app, logged in with my M365 account.

8:56This interface is also accessible in the browser. It's also accessible from Teams if you're in there. So it's a similar interface no matter where it presents itself.

9:07Jim Spignardo:Yeah, and by the way, you can do exactly the same thing in Chatubiti, in Cloud, in Gemini. Like, it doesn't really matter. Whatever we're showing you now in Copilot, you can do on whatever platform you're using for work. Yep, absolutely. There's definitely a lot of cross-capabilities here. So what I'm going to do, go ahead, and I'm going to go ahead and clip my little sidebar here. and within this area, you'll see there's a section called for agents. And you'll see we have a lot of them. Our organization, I think, currently has 42 agents deployed. Oh, wow. Some of those I built, some of those other people in the organization built.

9:42So it's been kind of a real uptick in the usage of these. But the quickest way to get to being able to build an agent is just go ahead and click this new agent button here. And Microsoft has kind of changed the behavior a little bit as it relates to these no code agents. It used to throw you into the describe screen versus the configure screen. If you're very new to this, I would say flip over to the describe screen. Because what ultimately you're going to be doing here is using AI to help you write the instructions for your agent for you by simply explaining what it is you want to do. So I'm going to come near my chat window and I'm going to say, I want a, an RFP response, but that can, let's see, that can consume RFPs and provide a proposal output.

10:49Now, hopefully based on this, and this is very vague, I would say we'd probably want to spend a little bit more time providing some context sources of where we want to pull information from. And I'll show you the one that we've actually completed functions, but that's really all you need to do to get started here. The other thing I would tell you is another method that I use sometimes when developing agents and getting an instruction set is I'll actually go to chat, whether it's open AI, it's chat, chat, tbt, or copilot itself and say, I'm building an agent for this platform. This is what I wanted to do.

11:22Create me a really good instruction set. And oh, by the way, also ask me some clarifying questions that may help me make this a better agent.

11:30Jim Spignardo:So this is how I build all my agents. Exactly what you're explaining. Now I start and I actually do more than that. The way I do this is I start in a regular chat and I try to do the thing. So instead of telling it I'm building an agent, I'm actually trying to do what the agent needs to do. So I'm like, okay, I have these four RFP documents. And here is two proposals that we've written in the past based on previous RFPs. One of them was successful, the other one was not. Here is the proposal that actually won the RFP before, because if it's a public RFP, usually they will give you, show you who won and exactly why.

12:05Jim Spignardo:So you can put that in there as well. I said, I want to build a new proposal that will use the new RFP based on what I learned in the other RFPs. Let's work on that together. And then you work through the steps. And then when you get to the final outcome, like, okay, this is a pretty good proposal that was written or analysis or whatever step you're in. I'm like, okay, now I want to turn this into an agent or a custom GPT or a project, whatever. It doesn't matter, depending on the platform you're on, please write me the instructions. And they will write you incredible instructions that you can never write on your own.

12:36Jim Spignardo:And then that becomes my first draft. They're still fine tuning afterwards, but that is to me the best way to actually do the thing you're trying to do in a regular chat and then ask it to convert it in. Once it's working and you went through different lefts and rights and turns and kinks, this is where I ask it to actually turn it into instructions. Yeah. And that's actually the same process I'll use if I have someone who's reaching out to me within our organization says, hey, I want to build an agent. I will sit down and I'll say, first, show me how you would do this without an agent. And because I want to see it mind mapped out, we want to map every process, every type of output they're looking for.

13:17We then take that and we do, like you said, convert it to an instruction set, have them test it. And we go back and fine tuning through, you know, limiting certain things or adding certain other variables or criteria.

13:30Jim Spignardo:But yeah, that method is also one I employ as well. So, all right, we're ready to just see what happens here. So we're going to hit the submit button, give it a couple of seconds here to think about it. I'm sure it's going to probably ask me some from additional qualifying questions. So we'll give it a second here, depending on if Microsoft fed the squirrels today, it would depend on how quick this is. Yeah. We always have a backup with live demos. You never want to just, but I'm confident we'll get a response here in a moment. And the nice thing is you kind of work in this canvas on the left-hand side, and then the right-hand side, it kind of starts to output and build what you're actually creating.

14:15Jim Spignardo:Yeah, so for those of you who never used either Copilot, Agent, Builder, or Custom GPTs, they kind of look the same because they came from the same source. you're working on the left and you're seeing the output on the right and so you're basically in real time can see the output of what you're doing and you see it updates as it updates and you can test it still here in the quote-unquote development environment and so you deploy it only once it's ready which is very helpful yeah absolutely and you can see it's it set it up it gave it a name we don't have to stick with their name if we don't want to give it a description It did give it a fairly limited instruction set at this point, but also created some conversation starters or some suggested prompts.

15:00And then kind of determined that based on the capability, it was going to enable data analysis and code interpreters. So it understood those might be valuable skills for this agent to have. Now you'll notice down here, we could go through the process of uploading an RFP document or paste its content, or we could put in some information about our company. All things that we've done in the one that we've already built, so I'll kind of show you that in a moment. But I wanted to flip over to the configure tab and demonstrate what was pulled in from just that single line of prompt. So you'll see I have the name, I have a description, and down here we have a very extensive set of instructions.

15:42The purpose, its general guidelines, the skills that we will employ to essentially accomplish the task, and then some step-by-step instructions, right? Review the document provided by the user, extract and outline the objectives, requirements, timelines, all things that are typically in a good RFP, and then organize that into specific instructions, and then present the proposal to the user for review and making adjustments. There are some error handling in here. And this seems to be the default now. Microsoft is doing a much better job of creating these instruction sets from a statement now. When I first started using this, it was not as pretty.

16:25It was not giving you all these kind of sectioned areas. It didn't always include an error handling area. Now it seems to do that. As well as some things like feedback in examples. All things that will really improve the output of the agent. So you'll see in here, if there's anything incomplete or unclear, ask the user for clarification or additional documents, incorporate user feedback. Here's some examples, right? Here's an RFP. I've identified the refollowing requirements, blah, blah, blah. And then finally, the follow-up and closing. You also have the ability to give it source documented documents.

17:02So those could be internal websites, external websites. It can be documents within your environment. It could be things that you upload. This is actually something that's been added since this technology came out. It's the ability to bring documents that might be outside of your M3CC5 data, Steve. Now, one thing I would say about that, if you're linking to things that are in your environment, the agent will always use the latest information because it'll go and grab that. So if there's revisions to it or if there's new changes, it will continually be dynamic. If you're uploading content, you have to be aware that if that content changes, you have to upload new versions to the agent for it to be able to read it.

17:48Yeah.

17:49Jim Spignardo:Two things I want to add or maybe clarify to people who are not used this in the past. One is you talked about conversation starters. Conversation starters are basically buttons that show up when you use the agents that give you a way to start the agent. Now, you don't have to have them, but if you're going to deploy it in a business and other people other than you are going to use it, they may not know what to do because there's no instructions. So what this does is it makes you say, oh, click here and upload your RFP to get started. And then you're going to click here and upload your RFP because that's what I told you to do.

18:25Jim Spignardo:and you can have many of those. And you can even in the instructions, if you're putting a few of these, you can use them as different entry points to the process. As an example, one of them is you already have a draft. I already have a draft. I want to continue working on it. So click here if you already have a draft. And then the agent will pick up in a different step in the instructions, because in the instructions, it will say, if the user clicked on click here when it's set for the instructions, start here. And then it will know how to do these kinds of things. So this is for the conversation starters.

18:54Jim Spignardo:But the other thing is more critical because one of the cool benefits of using Copilot as a way to build these kind of agents is you can connect it to your SharePoint. You can connect it to a specific SharePoint drive, which means it will look to the drive, what's in the drive, every time it gets started. So if you upload a new document, if you delete an old document, now it has a new set of documents, a new set of data to work with. versus if you upload files into the agent, they're quote-unquote hard-coded inside the agent. The fact that you in your SharePoint now has version 3, it doesn't know that because it's looking at the one file that you uploaded.

19:38Jim Spignardo:So from a best practices perspective, what Jim said, that's not necessarily a bad thing. You just need to be aware of that. If you're uploading a document, that's the document it's going to use. If you're giving it access to a SharePoint drive, then it dynamically will look what in that SharePoint. The other thing which I'm not sure about, maybe you know, is does this provide a different level of number of documents or total volume in megabytes that it can have access to? So if I give a SharePoint drive, do I get more data it can look at? Or is it the same as if I upload the 20 files manually to the agent?

20:16Yeah, I have seen some limitations about the number of documents you can upload, but I have not seen any limitations as it relates to, I just pointed out, a library. And that library may have 20 subfolders with 600 subfolders with thousands of documents. That's really why when you can, it makes more sense to try and go that path. A hundred percent. Okay, perfect.

20:41Jim Spignardo:Absolutely. As I was mentioning here, you can add all this content in. you can upload content. You can also have it use the internet. I would say I tend to lean away from this, especially if I'm building an agent that I know is going to have a specific purpose and I want to control it to the degree that I want the output to look very consistent. When you allow the agent to search the internet, it can pull in all kinds of other data that may be or may not be accurate. So if you're trying to eliminate or reduce the number of hallucinations, I usually make sure I don't have that on. But again, it depends on the purpose of the agent.

21:19The other thing I always like to do is make sure I say only use the specified sources. What that does is essentially limits the agent to only the things that I provided it. And it can't go outside the bounds of that and try and find other data that may be related or relevant or try and make things up as well. And then the next one, really, this is kind of more towards whether or not the context of who you are in the organization would actually be beneficial to the agent. Microsoft, because Copilot lives inside your tenant, has the ability to understand relationships with what you do for work, but also how you work with others.

22:00So sometimes if that can be used to benefit an agent, I will turn this on. Sometimes where that comes into play is it can know my role and automatically answer based on the role that I play in my organization, which gives me answers that a bit more tailored to me. But the problem there is what if I didn't want it to be answering that role? Well, then you kind of have to go, hey, assume I'm a different role at this point. I'm going to leave that off on purpose of this. The other nice part that was just recently Microsoft added was the ability to change this icon, but actually have it generated by AI, which is kind of cool.

22:39You don't have to go out and create a cool badge for your agent in another system or in Copilot and drag it in here. I will tell you it's a little finicky. It doesn't work every single time. Sometimes it makes the agent error out, but what it will do is look at the instructions, the description, the name, and come up with some sort of badge that represents them. I do find that that's Very helpful when you have a lot of agents and people are trying to visually recognize them quickly. Instead of giving you this kind of default agent logo, which can kind of get lost in a sea of other ones. Do you see it start to materialize here?

23:17We'll give it a second to populate. And then we're going to probably bomb out of this and go into the actual live one that we have. So it's got a cute little robot, right? It's, and I've actually learned something about how visual image creation works. It's kind of like building a castle from just a pile of sand. And that's why it kind of does this thing where it's just assemble the bits. So you can see it's cute. It has a little checkmark, has a little document behind it. And now if I click apply, I can go ahead and add that in there. It will update my agent. You'll notice there's the error. So it doesn't always work every single time.

Read the full transcript

23:52In that case, sometimes I'll just scrape the one there and then just upload it. The other thing, too, is after you've created your agent, you have the ability to share it to your organization. You can either share it to the whole organization, you can share it to a subset of individuals, either as the group or individual user accounts.

24:11Jim Spignardo:So here's an interesting IT question for you related to that, which I truly don't know the answer, but I'm curious. Let's say that this agent is using a specific folder in my drive. And let's say that I share this with the entire organization, but some people do not have access to that folder on their personal logins, will the agent prevent them from seeing that information? Did Microsoft close that loophole? Or if I gave them access to the agent and the agent has access to a folder, you're going to get access to that folder even if you're not allowed to see that folder? Yeah. So if that content exists in N365, maybe that's your OneDrive or Teams or SharePoint, the agent can warn you that the people you're about to share with don't have access.

24:59And you can, if you have the privileges, right, you have to have the ability to assign permissions. You can do that as part of the agent creation. The thing you have to keep in mind is that if you do do that during the agent creation and you then remove the agent, it doesn't remove the permissions. You got it. If that content exists somewhere outside of M365, it can now just give you permissions to my C drive for instance but but it doesn't work the

25:26Jim Spignardo:other way around meaning if I let's say I do not assign permissions to the people who do not have permissions would they not be able to use the agent like what's going to happen then like would they be they wouldn't right got it okay so it does work this way it protects the data structure and access from a company perspective. Yeah, absolutely. Yeah. And, and, and so that's something you need to think about. If you go ahead and share it. And again, that they've just added that recently where the kind of similar to when you share a link and outlook, it will say, Hey, some people in this email may not have access.

26:03It's the same way. I would say some people might not have access. Do you want to forgive them access? That wasn't there before. So people were setting up agents and then people were going in and go, this doesn't work because Because they now access the pods where they were located. So it does still respect your permissions. Awesome. You can't get permissions if you don't have that privilege.

26:21Jim Spignardo:Got it. So I'm out here now in my agent catalog. And you can see all these agents that we have and bill. And what I want to do is pull up the RFP response bot that we actually have for our own organization. And so I do see that one right here, but I know I think I actually have a second one. So let me go ahead and type that in. Yeah, this is the newest one I have. So I'm going to go ahead and find that in my list. What I want to do is go in and edit that because I want to show you what's occurring behind the scenes. And so it immediately jumps to the configure tab. And you'll notice that similar instructions, although it's a little bit different because it has some things in here about tone and style.

27:04And I actually used the second method that I talked about to create this one, which was to collaborate with Copilot. and tell it what I wanted to do to build me the instructions, which I then brought into the gym. And so that's why I'm getting a little bit different outplay. I have things in here about compliance and ethics, parallel processing capability where you can handle multiple RFPs at the same time. We also have some limits and transparency, response optimization, and then continuous learning and feedback. You'll notice if I go down a little bit further here, this is where I have given access to these resources.

27:47So within our organization, I've given in access to our services SharePoint site, which goes in and talks about all the services and solutions that we can sell and position with a client. We also have information in our sales and marketing website, which probably is going to fill in a lot of those sales pitchy parts of the RFP. We also have a document that specifically talks about RFP response sections. This we built over time responding to RFPs, and it's essentially chunks of data within this Word document that typically get filled into an RFP. We also have a PDF about what are winning formats and strategies.

28:28We want to give it the ability to say, hey, when you create that first draft, make sure you're relying on this best practice knowledge about what a winning RFP looks like. We also gave it our location for all of our previous RFPs. And then we also gave it a couple PDFs for best practices for winning a proposal and then mapping your ideal RFP response. I have up here, allowed it to search all websites, which I think actually In hindsight, I'm going to turn off. And you notice that I do have the ability to use specified, only the specified resources. And over here, you can see my starter prompts, essentially.

29:10Jim Spignardo:So what I want to do at this point, and I've said before I can show you, this is where you would share it. And you can see anyone in your organization, specific users, it does give you a little bit of a blurb about permissioning. They'll respond with knowledge that each user has access to. Okay. So it is permission bound to the user unless you change it. So keep that in mind. So let's drop out of this and go directly into the agent. And one of the other things to be aware of, at least in the Microsoft ecosystem, is when I'm in a chat, they could be in a chat in any application or just general chat.

29:48If I want to call up an agent, I don't have to necessarily open up the agent directly. If I type in the ad symbol within the chat window, that is going to give me a list. And of course, I'm in an agent right now. So let me show you in a new chat. If I go in at the ad symbol, it's going to bring a list up of all the agents that are available to me to call up. So I can pivot any time into using an agent in a regular chat. Like I said, that works in any of the Microsoft applications as well. PowerPoint, Outlook, Word, Excel, you name it.

30:20Jim Spignardo:Two cool things about this. First of all, most people don't know that, and that's sad because it's a very helpful thing. So again, you can use this from anywhere, which is very helpful. But the other really interesting thing is it means you can build multiple agents for a single process. So let's think about the RFP for a second. You can build one agent that analyzes the RFP, another agent that analyzes the data in your company that aligns with the requirements of the RFP, and a third one that actually writes the proposal outline, and a fourth that writes the details for the proposal. Like you can do it this way.

30:53Jim Spignardo:The benefit of that, well, two benefits. One is you have more control over the process because the in-between steps, you can stop, go back, finesse, fine tune, et cetera, before you continue. But the second is you can get much more granular instructions for each and every one of the steps, which will mimic more what you're actually doing in real life. But then the reason that connects to what Jim said before is you can have a regular chat and then add the first agent and say, let's start with the research. Here are the RFP documents for this RFP, and then we'll do the research. And then he comes up with an output.

31:26Jim Spignardo:And then you add the second agent that now knows what happened in the conversation because it's the same context window. And this is how you can keep on going. So that add symbol is not just for being lazy instead of trying to find the agent somewhere. it also is very useful because you can use multiple of them in a single conversation. Yeah, absolutely. Good point. Absolutely. And here's the rule of thumb I usually put around agents. If you are in the process of building an agent and there's more than one primary task you want it to complete, it's a good chance you probably want to create another agent.

32:02We could definitely build this as multiple agents, although typically we found that with our users, this is the best process for them. But we have some examples that we're building one for our HR department right now. There's a sub-unit in that department, which is our talent acquisition department. And they said to us, we want to be able to answer questions like they have. And we said, no, we're not going to do that. We're going to basically just link to that agent when it gets to that topic and go, is there a question about talent acquisition? We will hand off to that agent so that their agent can answer.

32:35And so we're not duplicating effort in our organization either. All right. So I have my first, I have chosen the initial prompt here, which is the RFP analysis. I'm going to go ahead and click the plus button and I'm going to upload a synthetic or simulated RFP that I asked ChatGPT to create for me. It's a school district. Let me see if I can bring up. Oh yeah, I do have that. So this is what it looks like. It's a PDF file. It's pretty sparse. I know a lot of RFPs are a lot more detailed than this, but it created this fictitious school, Redwood Valley Unified School District, gave it an address, gave it an RFP number, proposal date, due date, demographics of the school, you know, the purpose, the current network environment, their data center, their objectives, the scope of work.

33:26So, I mean, it has all the elements you'd be looking for. Usually they're much more detailed than this, but for the purpose of this demonstration, this will do. So we now have the PDF for that RFP, and we'll go ahead and click the submit button. And now you'll notice what it's doing here. With Copilot now, because it has a model router, you can actually figure out whether it needs to think deeper or it can answer fairly quickly. So you'll notice, you'll see, it responded fairly quickly because it probably had a decent bit of information. So below is a structured RRP, read it, ready analysis, and draft response.

34:06If you want to reformat it into a full proposal, exec, and summary, or compliance matrix, you just got to let them know, right? So here's the key highlights, the purpose. My screen is frozen there for a moment. What's going on? There we go. We just got stuck for a second. Some of the gap risks and proposals are for the proposal considerations. This part here, it said for the RFP compliant, the content is structured so that it can be pasted directly into a proposal, which is cool. Keep in mind, it can actually put it right into a Word document as well. There's a little bit of an executive summary draft, then goes into ProArc's technical approach aligned to the RFP, talks about what we would do as it relates to that specific part of it, talks about the wireless network assessment, the security architecture review.

35:01It talks about any cloud and SaaS connectivity. Then it also talks about the deliverables. Here's our vendor qualifications. Again, this stuff actually came from stuff related to our teams internally. So, you know, in the PCI-E level network architect, we have multiple CISSP engineers. We have Azure and cloud network specialists on and on and on. And then it actually...

35:26Jim Spignardo:And again, for people, just a second, And for people to understand, the way it knows that is because you give it access to your company data through the relevant SharePoint folders that has this kind of information. So it's not making it up. It's actually pulling from the data that you gave it. And this is where the real magic happens, right? You need, going back to what Jim said in the beginning, you need to know which data it needs access to. It's exactly this. Like you need to plan ahead and say, I'm going to create a folder or a subfolder somewhere that has exactly the information this agent needs, no more nor less.

36:00Jim Spignardo:And I'm going to point it to that. And like you've seen from GM, this could be five different folders. It doesn't have to be one that has specific aspects of information that will help it execute what it needs to execute. And because we told it to only use this data, that's the only source of truth it's going to use, and hence it knows how to do these kind of things, down to the level of what certifications and how many people with those certifications exist in the company to be able to comply with the requirements of the RFP. Yeah, exactly, exactly. And it was even able to go down here when we started working on pricing models to know that we actually do penetration testing and access point lifecycle design.

36:39right so these are things that may not have been mentioned in the rfp but we can state that to the customer hey there's an optional add-on you can also do these things for you as well now goes through a compliance checklist right which basically um is checking the draft to make sure it actually addressed all of the elements of the rfp right so and he wanted to go through and say let me check my work let me ensure that all the things that are laid out there because i'll be honest, we have answered RFPs where there was a section that we thought we addressed, but to the client, they thought, well, you didn't address it to the extent that we thought you would.

37:18So if they're doing it this way, we get much more consistent responses and we get the AI to be able to check our work for us. And then down below, we get kind of these outstanding questions for finalization. So there might be some things that we want to additionally add to this. So the one is, it's asking us if we want to have a complete proposal in a PDF of Word format. Do you want a set of narrative sections to paste into an existing template? And or do you want a compliance matrix and executive summary only? You'll notice then I also get some suggested prompts based on the questions it's asking me.

37:59Do we want the narratives only or do you want to generate the compliance matrix and executive summary? What I'm going to ask it for is, and I didn't see this. Can we build out a task list and associated based timeline approach?

38:24Let's see what it gets me there. this is typically a lot of times what a customer wants to see in a in an rfp so this came out there and said okay assuming this kickoff date and we can adjust those if necessary uh we could complete by july 15th uh the recurrent recommended phased approach is aligned to a 60-day window phase one would be the project initiation it knows you know our project management philosophy because again Again, we've fed it documents and knows how we run our project management office and what that would look like. Down here, we have deliverables out of that phase one, which is the project plan, a documentation request log, and a stakeholder engagement schedule under the network infrastructure piece of this.

39:12Notice this information is coming right out of the RFP. I don't think we've shown you that, but there were some specs in here about the high school had a 10 gig network, the middle school had a 5 gig network, and so on. Again, the deliverables, again, the wireless heat mapping exercise we will be doing, even talking about which environments we're going to look at that typically have density issues. Phase four, we get into the cybersecurity, heart protection, compliance.

39:40Jim Spignardo:Yeah, I think the phases themselves are less relevant, but the clear thing is that it knows how to approach it from a systematic way, right? It knows how to read the RFP, understand the requirements, understand what the company knows how to do, and then put the two together into a very well-structured format. the other thing that I will say that I do a lot when it comes to these kind of things like when you're trying to write a really long document and usually a response on RFP is not going to be five pages it's not going to be 10 it's going to be 50 to 500 sometimes yes and the right way to do this is kind of like to follow the process that Jim defined so you start with an outline and then you go okay let's work on section 1.1.3 and then you start working on that with the AI and then once you get that, okay, let's go to 1.1.4.

40:32Jim Spignardo:And this way, because if you ask AI to write the full document, let's say it's supposed to be 150 page of answer, you're going to get six pages, sometimes 12. The only way to get it to dive to the level of details you need is actually to do the step-by-step process of let's create the outline, let's understand the components we need. Now let's start working on each and every one of the components separately. And as you do more of this, you will get a feel of what the level of granularity you need to impose versus what it will know how to do on its own. Yeah, absolutely. Yeah. And that's the problem.

41:09That extends to a lot of different types of collaboration that I do with AI. And it could set you in my section. You kind of work out the details, work out the kinks. You have it, analyze it over and over again and then say, okay, I'm happy with that section. Maybe copy that out, put it in a Word document and move on to the next section. And, you know, it sounds pretty labor intensive, but I will tell you it's been a lot less labor intensive than it was in the past for us. You know, if I think about what on average it would take and how many people it would take to be involved in an RFP, you know, it's probably no less than three people, usually four to five people over the course of 10 days putting all this information together.

41:57We recently responded to an RFP in less than a day and a half because we were able to pull all this information together so rapidly and get a good first draft. And then, like we always tell people, have a human review it and go through with it and say, OK, we don't like that section. This section reads a little inauthentic for who we are. And you can even say, hey, can you make this seem more on brand? And then we'll do that and we'll change it up for you. But, you know, the amount of time that it takes us to draft now is probably down by 75, 80 percent of what it used to take. And then, again, our win rate has dramatically grown up.

42:41We probably, again, we won about as many as we lost. I would say we're now closer to winning three quarters of our partner RPs. And sometimes it's not because of AI. It's because we're not qualified enough to do the work. or there was somebody already had some sort of unknown advantage over us that we didn't know.

43:00Jim Spignardo:Two things. One, a bit of an interesting add-on to what you just said, and the second is a question. So adding a little bit on, a lot of the work in the RFP is really evaluating whether the company actually has the expertise, the skills, the knowledge, the background, the past experience to actually win this. That by itself used to take days of work. Sure. And then you may get to the conclusion like, okay, hey, we're actually, we can't win this. Let's not bid. You already spent the two, three, four days, two weeks, depending how big the project is to get to that conclusion. Where now this part of it, if you built your data set correctly first in five minutes, you will know whether you should invest more time in this or not without investing any serious resources.

43:45Jim Spignardo:And the other thing is usually these resources are the most capable resources in the company. So it's not only you need to invest these two days, these are the two days who are the most senior project managers with the most experience with like, these are the people that can evaluate whether you can do this or not. These are the people you don't want to get out of their day job because they're the one that generally need the most amount of revenue to the company. The question that I have in the ChatGPT universe, when I do this, I use Canvas to write the answers. The benefit of Canvas is that it's a fully editable document that I can add text myself.

44:19Jim Spignardo:I can highlight text and ask AI to work with this and so on, which makes the iterative process of creating an outline and then working on 1.1, 1.1, 2.2, and so on, very easy to do. I don't believe that's possible in the co-pilot universe, but I'm asking about saying. Not to the same extent, but what you do have the ability to do is to, I'm looking here, you can actually send this to pages, right? And I'm not seeing that option right here, but if you send it to a page, the page does open up a canvas, which you can then edit things in and more easily copy from the chat window into that. The feature you're talking about with ChatTBT, yeah, it's create per coding too.

45:07You can see the changes being made while you're asking for the iterations.

45:10Jim Spignardo:So your best practices suggestion is working two windows or two monitors, one that has the chat, one that has a pages version of the first draft, and then you go back and forth. And the nice thing about the page, when you send something output to a page, is that after you're done editing it, there is a button in the top that says, send this to Word. So you can take all of that ongoing kind of workshop benching stuff and say, now I'm done, put it in Word, and we'll send it off for approval or last draft or last review by humans. Great stuff. Quick recap and summary of everything we did, and then let you say some final words.

45:52Jim Spignardo:First is you need to know which data you have, where you have it, what's applicable for what purpose. And again, now generalize it, forget about RFP for a second. That's true for any aspect of the business, right? So having a solid understanding of what information you have in your company, what of it is good versus not so good versus bad, labeling it correctly and putting it in places that will make sense to humans and agents was always true, but it becomes way more important right now. Because if you don't have that, everything that Jim just showed you is not possible because you won't have the 12, five folders and six documents that it gave the RFP agent to be able to do the things that it knows how to do.

46:39Jim Spignardo:So number one, you need to have your right data intact. Number two, as we said in the beginning, you need to figure out the use cases. And as we said, the right way to figure out use cases is things that can help you grow the business while hopefully saving you time. One or the other would still probably be a good option, but in this particular example, it does both. It reduces the effort and it generates more revenue. So it's a perfect fit to be something you want to build agents for. The next thing is really how you build the agents. And as Jim and I mentioned, the best way is to just have a conversation about it.

47:13Jim Spignardo:Just talk to the AI in a regular chat to say, this is what I'm trying to do. Here's the information I have. This is the goal that I'm trying to reach and just work iteratively and then in the end said, okay, now write me the instructions. And then the last thing is really, it's never really done, right? This gets you 90 % there, but they're like, oh, we should have added this. Go and add this. Like every time you learn something you didn't do before, you can go and add that additional thing to the agent. In many cases, I do this in the chat itself. So I'm like, oh, I would like the agent to also do this.

47:46Jim Spignardo:Can you add me a set of instructions to the current instructions that will add this new functionality capability, check whatever you want to do. And it will write you another paragraph or two in bullet points and will tell you exactly where to put it in. And you copy and paste it in the instructions to just keep making it better and better. And then like Jim said, you can share this with relevant people in the company so you're not the only one using it. The only really annoying thing that Microsoft did, but I understand they're trying to make money, is the other people need M365 licenses as well in order to use the agents that were created, which to me is really annoying.

48:20Jim Spignardo:Like it would have made sense. There is a little bit of a footnote to that, by the way. Okay, I'm curious. So if you do not want to license your users all up and still want to take advantage of agents, Microsoft does have a pay-as-you-go model where you now can buy token packs. And so if your agent is associated and sent out for the pay-as-you-go model, it's great for frontline workers field workers yeah they can use the agent every time they use it you get charged the penny per each message you can buy also now buy packs that are a discount so they can assign those as well and so now you're not in that model where i don't know if they're going to use 30 worth of copilot every month right yeah and now you have 300 employees i go So$30 is not a big deal.

49:10Jim Spignardo:$30 times 30 ,000, that starts being interesting. So that's awesome to know. I did not know that. Jim, this was absolutely fantastic. I'm sure people will learn a lot, both from the mindset as well and from this specific example. I think it's a very powerful example that, as I mentioned, even if you're not doing RFP work, you're probably writing proposals. So don't call it an RFP, call it customer requirements. And you go through the same exact exercise and you can do this. I can tell you that I haven't written a proposal on my own for at least two years. And I keep on upgrading and updating the process.

49:47Jim Spignardo:So the process that I have right now is way better than I had even a quarter ago. But it now writes better proposals than I ever did by a big spread, by a big spread. And it does it in about five minutes when it would have taken me two to three days. and so there's really zero reason not to do these kind of things that's all i'm saying it's there was the old joke you know in the in the in the project world of faster better cheaper pick two you don't have to pick anymore you can do faster better and cheaper true i didn't think of that yeah that's true absolutely i've heard that expression but yeah ai kind of jake puts turns on its head so yeah if people want to follow you learn from you work with your company what are the best ways to do that?

50:33Sure. I am very active in LinkedIn. I write about three articles a week, topics in AI and technology. So if you just search for Jim Spignardo, I noticed that I typed my

50:44Jim Spignardo:name in with my last name right on there. It's S-P-I-G-N-A-R-D-O. I'm the only Jim Spignardo on LinkedIn, probably the only one in the world. So you can find me there. My company is ProArc. so it looks like it's pronounced proarch but it's proarch p-r-o-a-r-c-h and we have all of our services listed there we just did a webinar yesterday similar exercise where we demonstrated building that hr agent so there's lots of free content on there that you can avail yourself of i'm also coming out i'm looking around my desk here coming out with a book soon an ebook that will be free to download. It's called the AI Turning Point, which really discusses how organizations have to fix what's wrong in their businesses to be able to take the best advantage of AI, both from a business process perspective, but also from a business mindset as well.

51:44Jim Spignardo:Awesome. Thank you so much. This was really well thought after and really well explained. So I really appreciate you taking the time and sharing with us. And thanks everybody who joined us live. I appreciate you spending the time with us and learning with us while we're doing this. Have a great rest of your day, everyone.

From the publisher

AI isn’t failing companies. Poor implementation is.

In this tactical, no-fluff session, you’ll learn exactly how to build AI agents that solve real business problems, from drafting winning RFP responses to eliminating internal knowledge bottlenecks.

We’ll walk through a real-world example of how a 500+ employee global organization built AI agents that reduced proposal effort by 80%, improved response quality, and transformed how teams access internal expertise. You’ll see what worked. What didn’t. And how better data discipline made all the difference.

Jim Spignardo, Director of Cloud Strategy & AI Enablement at ProArch leads AI adoption across a global Microsoft partner organization, overseeing AI governance, internal enablement, and real-world Copilot deployments. He’s built over 30 practical agents across sales, consulting, and operations — and he doesn’t just talk about AI strategy. He operationalizes it. At scale.

You’ll leave with a clear, step-by-step framework to:

  • Identify high-ROI AI agent opportunities
  • Structure and clean your data properly
  • Design effective instruction sets
  • Avoid common implementation mistakes
  • Decide when to use agents vs. notebooks/projects

About Leveraging AI

If you’ve enjoyed or benefited from some of the insights of this episode, leave us a five-star review on your favorite podcast platform, and let us know what you learned, found helpful, or liked most about this show!

More from Leveraging AI

All 330 episodes
278 | How To Build AI Agents: A Step-by-Step Playbook for Business Leaders with Jim SpignardoLeveraging AI · 52 min
Listen in VO