Seller Context helps Dealtree understand your product, your market, and the type of stakeholders who may be involved in your deals. When you add your Product Name, Product Category, and Product Description, Dealtree uses that information as context while generating account intelligence. This helps the platform create recommendations that are more relevant to what you are actually selling.Documentation Index
Fetch the complete documentation index at: https://docs.dealtree.io/llms.txt
Use this file to discover all available pages before exploring further.
Why Seller Context Matters
Different products have different buying processes. For example, a sales intelligence product may involve sales leaders, RevOps, SDR managers, account executives, founders, and procurement teams. A technical infrastructure product may involve CTOs, engineering leaders, security teams, developers, and technical evaluators. A consulting service may involve founders, department heads, finance leaders, operations teams, and executive sponsors. Seller Context helps Dealtree understand which people may matter most for your specific product or service.How Dealtree Uses Seller Context
Dealtree may use Seller Context when generating:- Buying committee recommendations
- Stakeholder role analysis
- Action Plan tasks
- Multi-threading recommendations
- Stakeholder-specific actions
- Deal risk suggestions For example, if your Product Category is Account Intelligence Platform, Dealtree may look for stakeholders related to sales, revenue, RevOps, GTM, founders, and leadership roles. If your Product Category is Cybersecurity Software, the relevant stakeholders may be different, such as security leaders, CTOs, IT teams, compliance teams, and procurement.
Impact on Buying Committee Mapping
Seller Context helps Dealtree understand who may play which role in the buying process. It can affect how Dealtree identifies roles such as:- Economic Buyer
- Champion
- End User
- Technical Buyer
- Blocker
- Procurement or Legal For example, if your product is mainly used by sales teams, a Head of Sales or VP of Revenue may be more likely to appear as an economic buyer or strong influencer. If your product requires technical approval, a CTO or engineering leader may be more relevant as a technical buyer.
Impact on Action Plan Recommendations
Seller Context also affects the tasks generated in the Action Plan. If Dealtree understands what you sell, it can recommend more useful next steps. For example, the Action Plan may suggest that you:- Validate budget ownership with the right leader
- Ask your champion for an introduction to a specific role
- Schedule a technical fit discussion with the technical buyer
- Confirm procurement or legal involvement
- Prepare role-specific messaging based on stakeholder priorities
- Investigate possible blockers connected to your product category Without clear Seller Context, the recommendations may become too generic.
Best Practices
To get better intelligence from Dealtree:- Use a specific Product Category
- Write a clear Product Description
- Mention who your product is for
- Explain the problem your product solves
- Include the main outcome customers expect
- Update your Seller Context when your positioning changes For example, instead of writing: We help companies grow. Write something more specific: We help B2B sales teams generate org charts, map buying committees, and create multi-threaded action plans to close complex deals faster.
Important Notes
- Seller Context improves the relevance of Dealtree’s recommendations.
- Clear product information can lead to better buying committee and action plan outputs.
- If you update Seller Context, consider regenerating the buying committee or action plan for important accounts.
- Seller Context does not replace your own sales judgment. It gives Dealtree better information to work with.
- Vague or outdated Seller Context may reduce the quality of account intelligence.