Skip to main content
A powerful Value Framework includes dozens of use cases covering different industries, personas, and value drivers. Tags are how you keep this library organized and discoverable. Without tags, sellers face decision paralysis: “Which of these 40 use cases matter for this healthcare CFO?” With smart tagging, AI suggests exactly the right use cases based on deal context, and sellers can quickly filter to what’s relevant.
Think of tags as your use case filing system. Good tags turn a overwhelming library into a curated selection that feels tailor-made for each deal.

Why Tags Matter

Tags solve three critical problems:

1. Discovery Efficiency

When creating a business case, sellers need to find relevant use cases fast. Tags let them filter by industry, persona, or value category instead of scanning an entire library.

2. AI Relevance

Minoa’s AI uses tags to suggest use cases based on deal context. If you tag a use case “Healthcare” and “CFO,” it’ll surface when sellers work healthcare deals or present to finance leaders.

3. Library Organization

As your Value Framework grows, tags provide structure. New team members can navigate your library logically instead of guessing which use cases apply to their deals.
Well-tagged use cases lead to better AI suggestions, faster business case creation, and more relevant value quantification.

Common Tag Categories

Most companies organize tags into a few standard categories. You can create custom categories that fit your business, but these are the most common:

Industry Tags

Categorize use cases by the industries they best serve:
  • Healthcare
  • Financial Services
  • Manufacturing
  • Retail
  • Technology
  • Professional Services
Industry tags help sellers working vertical-specific deals quickly find relevant value stories and proof points.

Persona Tags

Tag use cases by the buyer role that cares most about this outcome:
  • CFO / Finance
  • CTO / IT
  • VP Operations
  • Head of Sales
  • Compliance Officer
  • Customer Success Leader
When sellers know their champion’s role, persona tags surface the use cases that resonate with that stakeholder.

Value Category Tags

Group use cases by the type of business outcome:
  • Cost Reduction
  • Revenue Growth
  • Risk Mitigation
  • Efficiency Improvement
  • Quality Enhancement
Value category tags help sellers match use cases to the buyer’s strategic priorities.

Product or Solution Tags

If you have multiple product lines, tag use cases by which solution delivers the value:
  • Platform Core
  • Analytics Module
  • Integration Suite
  • Professional Services
This helps sellers building product-specific business cases or presenting tiered offerings.
Start with industry and persona tags. These deliver the biggest impact on AI suggestions and seller efficiency. Add other categories as your library grows.

Creating and Managing Tags

Setting Up Tag Categories

Before creating individual tags, define your tag categories. These are the groupings (Industry, Persona, Value Category) that organize your tags.
1

Navigate to Tags

Go to SettingsValue FrameworkTags. This section is available to workspace admins.
2

Create a tag category

Click “New Category” and give it a clear name like “Industry” or “Buyer Persona.” Add a description to help your team understand when to use tags from this category.
3

Add tags to the category

Within each category, create individual tags. For an “Industry” category, you might add Healthcare, Financial Services, Manufacturing, etc.
4

Apply tags to use cases

As you build or edit use cases, add relevant tags. Most use cases get 2-4 tags across different categories.
Once your tags are created, they’re available across your entire Value Framework and inform AI suggestions.

Tag Naming Best Practices

  • Use buyer-friendly language – “Financial Services” not “FINSERV_VERTICAL”
  • Be specific but not overly narrow – “Mid-Market” is better than “501-1000 Employees”
  • Stay consistent with terminology – Pick “Head of Sales” or “VP Sales,” not both
  • Avoid redundancy – Don’t create “Healthcare” and “Health Care” tags

Multi-Tagging Use Cases

Most use cases deserve multiple tags across different categories. For example: Use Case: “Reduce Time Spent on Financial Reporting”
  • Industry: Financial Services, Healthcare
  • Persona: CFO, Controller
  • Value Category: Efficiency Improvement, Cost Reduction
  • Product: Analytics Module
This multi-dimensional tagging ensures the use case surfaces in multiple relevant contexts.
There’s no limit to how many tags you can apply to a use case. Tag liberally—better to over-tag than leave relevant connections undiscovered.

Using Tags as a Seller

When sellers create business cases, tags appear in the use case selection interface:

Filtering by Tags

Sellers can filter the use case library by any tag:
  • “Show me use cases tagged Healthcare”
  • “What use cases work for CFOs?”
  • “Which use cases drive Risk Mitigation?”
Filters can combine across categories: “Healthcare use cases for CFOs focused on Cost Reduction.”

Browsing Tag Groups

The use case selection interface groups use cases by tags, making it easy to explore:
  • See all Healthcare use cases together
  • Browse by persona to find stakeholder-specific value
  • Filter by product line when building solution-specific business cases
Learn more about how sellers choose use cases when creating business cases.

Managing Your Tag Library

Keeping Tags Current

As your business evolves, your tags should too:
  • Add new tags when entering new markets or launching products
  • Consolidate redundant tags if you’ve created similar tags with different names
  • Retire unused tags that no longer apply to your value framework
  • Update use case tagging as positioning or target audiences shift
Review your tag library semi-annually. Look for patterns—if sellers keep filtering for something you don’t have a tag for, create it.

Tag Usage Insights

Monitor which tags are most commonly used:
  • Frequently used tags indicate strong product-market fit in those segments
  • Rarely used tags might indicate gaps in your use case library
  • Missing tags that sellers ask about reveal opportunities to expand

Best Practices

Industry and Persona tags deliver the most value immediately. Add more categories as your library grows and patterns emerge.
Use industry names buyers use (“Financial Services”) not internal codes (“FINSERV”). Think like a seller, not a product manager.
Under-tagging makes use cases hard to discover. Over-tagging dilutes relevance. Aim for 3-5 tags across different categories.
Sellers know how they think about deals. Ask them how they’d naturally categorize use cases, then build tags that match their mental models.
Create simple guidelines for your team: “Use Persona tags for buyer job titles” or “Industry tags should match Salesforce industry picklist values.”
Create sample business cases for different buyer scenarios. Verify that AI suggests the use cases you’d expect. Adjust tags if not.

Common Questions

Most companies use 3-5 categories: Industry, Persona, Value Category, and optionally Product Line or Company Size. Start with fewer, add more as needs emerge.
Tag creation is typically restricted to admins to maintain consistency. Sellers can suggest new tags through feedback channels.
Updating a tag name automatically updates it everywhere it’s used. All use cases with that tag reflect the new name immediately.
No. Some use cases are universal and don’t need industry tags. Others are product-specific and don’t need persona tags. Tag what’s relevant, not exhaustively.
Each use case variant can have its own tags. A Healthcare variant of a use case gets Healthcare tags; an SMB variant gets SMB tags. This ensures AI suggests the right variant for each deal.
While you can’t directly import tags, we recommend aligning your tag names with CRM fields (like Industry picklist values) for consistency across systems.

Setting Up Your First Tags

Ready to organize your use case library? Here’s where to start:
  • Identify your 2-3 most important tag categories (likely Industry and Persona)
  • Create 5-10 tags within each category
  • Review your existing use cases and apply relevant tags
  • Test AI suggestions by creating sample business cases
  • Gather seller feedback on whether suggested use cases feel relevant
  • Refine tags based on what’s working and what’s missing
  • Document your tagging guidelines for the team
With a well-tagged use case library, your sellers will spend less time searching and more time having conversations that matter.