Short answer: To prepare source material for EntityMesh, gather the approved facts your public knowledge system should rely on: product definitions, buyer questions, support answers, onboarding notes, policies, proof, comparisons, glossary terms, pricing constraints, and review owners. EntityMesh can structure and draft from this material, but public pages should be approved before publication.
EntityMesh works best when the source material is clear.
It can diagnose gaps, structure answers, build pages, and prepare infrastructure.
But it should not invent the truth of the business.
That truth needs to come from approved source material.
What counts as source material?
Source material is anything the business can stand behind.
It can include:
- Product descriptions.
- Service descriptions.
- Existing website pages.
- Sales call notes.
- Support tickets.
- Onboarding docs.
- FAQ answers.
- Policy pages.
- Pricing rules or constraints.
- Integration lists.
- Case studies.
- Customer proof.
- Reviews.
- Comparison notes.
- Founder or subject-matter expert explanations.
The goal is to separate approved knowledge from assumptions.
Start with product and category definitions
Before building a Support Hub, clarify:
- What does the company do?
- What is the product?
- What category does it belong to?
- Who is it for?
- What does it replace?
- What terms should be used consistently?
- What terms should not be used?
This is the foundation for the Auth Graph.
Run the free EntityMesh scan to identify which definitions and answer gaps need attention first.
Collect repeated buyer and customer questions
EntityMesh uses questions as infrastructure inputs.
Collect questions from:
- Sales calls.
- Support tickets.
- Customer success notes.
- Onboarding calls.
- Chat transcripts.
- Search queries.
- Reviews.
- Community posts.
- AI prompt monitoring.
Then group them by Question Architecture: Who, What, When, Where, Why, How, proof, trust, comparison, strategy, and systems questions.
Gather proof before making claims
Proof should be available before claims are published.
Useful proof can include:
- Case studies.
- Screenshots.
- Process examples.
- Public pages.
- Schema validation.
- Customer quotes where approved.
- Third-party references.
- Measured findings.
- Diagnostic outputs.
If a claim is not proof-grade, label it carefully. The Public Proof Package explains how to separate Proof-Grade, Directional, and Not Yet Measured claims.
Identify what should stay private
Not all source material belongs in a public Support Hub.
Keep private or review carefully:
- Customer-specific details.
- Private account data.
- Security-sensitive procedures.
- Legal advice.
- Custom pricing.
- Unannounced roadmap.
- Internal strategy.
- Unsupported performance claims.
Source material can inform the build without becoming public.
Assign review owners
Approval is part of the EntityMesh operating loop.
Before drafting begins, identify who can approve:
- Product claims.
- Pricing language.
- Policy explanations.
- Legal-adjacent content.
- Support answers.
- Technical details.
- Comparison language.
- EntityAgent knowledge.
Who approves EntityMesh content? explains the review model.
Format source material for a faster build
The material does not need to be polished.
It should be organized enough to use.
A practical folder structure:
- 1Product and category definitions.
- 2Buyer questions.
- 3Support questions.
- 4Onboarding and process notes.
- 5Proof and examples.
- 6Policies and constraints.
- 7Competitors and comparisons.
- 8Terms to use and avoid.
- 9Review owners.
This gives EntityMesh a cleaner starting point.
Run the free EntityMesh scan before preparing a full source packet if you need help prioritizing what matters first.
Frequently asked questions
What source material does EntityMesh need?
EntityMesh needs approved product facts, customer questions, support answers, proof, policies, comparisons, terms, and review guidance.
Does source material need to be polished?
No. It can be raw notes, call summaries, ticket exports, or internal docs as long as the facts can be reviewed and approved.
Can EntityMesh create content without source material?
EntityMesh can identify likely gaps and draft structures, but public claims should be grounded in approved source material.
Who reviews the source material?
The client should assign review owners for product, support, legal-adjacent, pricing, proof, and policy claims.
How does source material help EntityAgent?
EntityAgent answers from approved EntityMesh knowledge. Better source material creates a stronger approved retrieval layer.