How Claude Projects Can Strengthen Software Asset Management Teams

Software Asset Management (SAM) teams work with a significant amount of context. License entitlements, publisher agreements, renewal schedules, audit correspondence, normalization rules, Effective License Position (ELP) methodologies, and discovery data often live across multiple systems and repositories.

Finding and applying that information can take time, especially when teams are managing multiple publishers and increasingly complex software environments.

Claude Projects can help bring that context closer to the work.

Projects are not a replacement for a SAM platform or established SAM processes. Instead, they can provide an AI-enabled workspace that helps teams organize knowledge, accelerate analysis, and create more consistent outputs across everyday SAM activities.

A quick note on scope: This article focuses primarily on Projects within Claude.ai, Anthropic’s web, mobile, and desktop interface. Claude’s Cowork environment offers additional workflow and automation capabilities, which we cover later.

What Is a Claude Project?

A Claude Project is a dedicated workspace designed around a specific topic, workflow, or body of knowledge.

Within a Project, teams can provide reference materials and instructions that Claude can use across conversations. Rather than providing the same background information every time a new conversation begins, teams can establish a more consistent foundation for how Claude supports a particular workflow.

For SAM teams, that could mean creating a Project around a publisher, renewal, licensing analysis, or another recurring area of work.

The result is less time rebuilding context and more time applying that context to the work at hand.

Where Projects Can Add Value to SAM

One of the most practical applications of Projects is creating a centralized knowledge base for the information that supports SAM analysis.

Depending on the use case and an organization’s AI governance requirements, a Project could include materials such as:

• Publisher licensing documentation
• Entitlement information
• ELP methodology guidance
• Audit response templates
• Discovery gap documentation
• Software normalization standards
• Internal governance documentation
• Renewal and contract information

With the appropriate context available, Claude can help teams analyze information, summarize documentation, draft materials, identify questions, and work through complex licensing scenarios more efficiently.

Consider a team managing IBM licensing. Instead of providing the same background on its PVU methodology every time it begins an analysis, the relevant methodology and guidance can already be available within the Project.

The same approach can be applied across publishers and workflows.

For teams managing platforms such as ServiceNow SAM Pro or Flexera, Projects can also support the work surrounding the technology. CMDB documentation, discovery remediation processes, normalization standards, and internal procedures can provide useful context when creating analyses, documentation, or recommendations.

The SAM platform remains the system supporting the program. The Project helps teams work more effectively with the information and processes around it.

Building an Effective SAM Project

A strong Project starts with a focused use case and clear governance.

Use clear, descriptive file names.
As the knowledge base grows, clear naming makes it easier to identify and reference the right information. A file named Oracle-ELP-Methodology-2026.pdf, for example, provides considerably more context than methodology_final_v3.pdf.

Create specific Project instructions.
Define how Claude should approach the work. A SAM team might instruct it to identify assumptions, reference applicable documentation, follow an established ELP structure, or distinguish between confirmed information and areas requiring additional validation.

Start with a focused use case.
Rather than immediately building a Project for the entire software estate, consider starting with one publisher, renewal, or recurring workflow. This makes it easier to evaluate the output and refine the approach.

Direct Claude to the relevant source material.
When appropriate, reference specific documents in your prompts. Asking Claude to evaluate a question based on a particular agreement or methodology can help keep the analysis grounded in the right context.

Keep information current.
AI-assisted analysis is only as useful as the information supporting it. Agreements, entitlements, methodologies, and other reference materials should be reviewed and updated as the environment changes.

And, as with any enterprise AI use case, organizations should ensure that the information provided to AI tools aligns with their security, privacy, contractual, and internal governance requirements.

Creating Greater Consistency Across SAM Teams

Projects can also help teams establish a more consistent way of working.

For organizations using Claude plans that support shared Projects, teams can work from common instructions, reference materials, and methodologies. Instead of each practitioner approaching an analysis differently, the Project can provide a shared foundation for how information is evaluated and outputs are structured.

That consistency can be particularly valuable for activities such as:

• ELP analysis
• Renewal preparation
• Publisher research
• Executive reporting
• Audit and compliance support
• SAM process documentation

Projects can also complement Claude Skills.

A useful way to think about the two is that Projects provide context, while Skills provide repeatable process.

For example, a Project might contain the agreements, entitlement information, methodology, and internal guidance for a publisher. A Skill could then provide a standardized workflow for creating an ELP summary, renewal brief, or other recurring deliverable.

Used together, they can help teams move from individual AI interactions toward more structured and repeatable AI-enabled workflows.

A Practical Place to Start

Organizations do not need to redesign their SAM program around AI to begin exploring the potential value.

Start with one clearly defined workflow.

Choose a publisher, recurring analysis, or deliverable that requires teams to repeatedly gather the same information. Build a Project around that use case, provide the relevant approved documentation, establish clear instructions, and test the outputs.

Then evaluate the results.

Where did the Project save time? Where did additional context improve the output? Where did the instructions need to be more specific? And, importantly, where should human expertise and validation remain central to the process?

That iterative approach can help organizations identify where AI meaningfully improves SAM workflows without introducing unnecessary complexity.

For organizations managing increasingly complex software environments, the objective remains the same: improve visibility, strengthen governance, and enable more informed decision-making.

AI workspaces such as Claude Projects can provide another way to support that objective by helping SAM teams spend less time finding and rebuilding context and more time applying their expertise.

Beyond Projects: Automating Recurring SAM Workflows

Projects can support knowledge and context, but some SAM workflows also involve repetitive operational tasks.

Claude’s Cowork environment extends the use case further by supporting more automated workflows. Depending on the available capabilities and connected systems, teams can explore recurring activities such as renewal pipeline summaries, discovery gap reporting, ELP status updates, or standardized operational reporting.

For SAM teams that regularly spend time gathering the same information and assembling similar reports, these capabilities are worth evaluating alongside Projects.

The opportunity is not simply to automate more work. It is to determine where AI can reduce repetitive effort while keeping SAM expertise, governance, and validation at the center of the process.

Anglepoint’s SAM Technology Services team helps organizations get more value from their SAM technology and the processes that support it.