Skip to main content

Project Knowledge

Project Knowledge (or "Know-how") provides the specific context Harmony’s AI needs to analyze your conversations accurately.

By adding your company’s unique terminology, product details, and internal definitions, you ensure that the generated insights are factual and aligned with your business goals.

Why context matters​

When you rely on a generic AI, it might get tripped up by your team’s unique way of talking, your company’s special nicknames, or even the names of projects your team uses every day. That’s where Project Knowledge comes in - it’s like giving the AI insider information.

With a little bit of context about your business, Harmony can start to truly understand who your competitors are, how your products or features are different from each other, or why your team says “the deal’s gone Gold” when talking about a special pricing rule.

If there’s jargon, abbreviations, or even casual shortcuts your team loves to use in meetings, adding them to Project Knowledge makes sure the AI keeps up and interprets everything just the way you intend.

If your Insights feel "generic," adding 2-3 paragraphs of specific Project Knowledge usually might help.

How to add Project Knowledge​

With Harmony, you can give each project its own unique “brain” by adding custom knowledge that’s tailored to that specific initiative. This way, the AI always has the right context at hand.

Getting started is easy. First, head over to the Insights area and pick the project you want to work with.

Next, open up the Configuration tab. Look for the area labeled Project Knowledge - that’s where all the magic happens. Click Edit, and you’ll see a spot where you can type in details that matter for your business: anything from company jargon to key product facts or special terminology your teams use.

Just type what’s important, hit Update to save, and Harmony will start using that knowledge right away when analyzing your conversations. It’s a simple way to help the AI think like a member of your own team!

What to include​

To get the most out of your Insights, consider including the following details:

  • Terminology and Jargon Define acronyms or technical terms used frequently by your customers or team. Example: "MQL refers to a Marketing Qualified Lead, which in our case must have a budget over $10k."

  • Product and Feature Names List your core products and specific features, especially those with common names that might be confused with general words. Example: "Our product 'Flow' is a workflow automation tool, not a reference to conversation flow."

  • Competitive Landscape List specific competitors and how customers typically refer to them. This helps the Competitor Analysis insight stay precise.

  • Pricing and Packaging Briefly explain your tiers (e.g., Solo, Plus, Max) and any "non-standard" deal structures your team is allowed to discuss.

How the AI uses this data​

When a meeting is processed, Harmony reads your Project Knowledge first. It then uses those definitions as a lens to interpret the transcript. When answering a Yes/No or Checklist insight, it checks the transcript against your definitions to make sure the answer is correct for your specific business.

Project Knowledge is private to your workspace. Harmony does not use this data to train public AI models.