A useful competitor profile is a maintained decision record: current enough to guide action, historical enough to explain change, and explicit about what the team still does not know.
Most competitor profiles begin as research projects. Someone gathers a company description, product list, audience, pricing, funding, strengths, weaknesses, and screenshots. The document looks complete on the day it is shared. Then a plan changes, a page disappears, a new offer appears, and nobody knows which fields are still dependable.
A living profile solves a different problem. It holds the team's current working view of one relevant competitor, keeps the observations behind that view, and shows how confidence changed. Its value comes from careful maintenance, not from the number of fields filled in.
Define the job before designing the profile
Start with the decisions the profile should support. A product team may need to understand public capability movement. Sales may need current positioning, buyer objections, and known packaging. Marketing may need audience language and recurring themes. Each use creates a different freshness requirement and proof threshold.
Confirm the company is worth maintaining before building its record. The guide to finding and validating competitors separates direct competitors from search competitors, substitutes, and adjacent companies. Record that relationship in the profile. A company can be strategically relevant without competing in every product, segment, or deal.
Profile rule: Every maintained field needs a decision use, a source, a scope, a last verified date, an owner, and a condition that causes another review.
Build the profile as four connected records
Treat the profile as a small state system. Four record types keep durable facts, dated evidence, interpretations, and gaps from being flattened into one confident company summary.
1. Current fields
Current fields hold the team's accepted working view: official identity, competitor relationship, public positioning, named audiences, maintained products, observed packaging, markets, and other facts the team repeatedly uses. Each value carries its scope and last verification. “Starts at $79” is incomplete without the plan, currency, billing period, region, and date.
2. Dated observations
An observation records what a source showed at a particular time. A new enterprise landing page, an updated integration document, or an unavailable product belongs here before it changes the profile's accepted view. Keep the source URL, observed date, captured wording or value, and the exact entity, product, plan, or market involved.
3. Standing interpretations
Interpretations connect several observations to a useful working view. Label them as interpretations, list the supporting and conflicting evidence, state confidence, and name the decision they affect. “Public positioning increasingly addresses enterprise logistics teams” can be a sound interpretation. “Enterprise revenue is growing” needs evidence that public positioning cannot provide.
4. Unknowns and open questions
Unknowns stop assumptions from quietly becoming fields. Capture what is missing, why it matters, which evidence could answer it, who owns the next check, and when the question should be closed. An unknown that does not affect a decision can be retired instead of becoming permanent research debt.
| Record type | Example | Allowed action |
|---|---|---|
| Current field | Verified official domain | Reuse until its freshness or event trigger requires another check |
| Observation | Enterprise page appeared on August 12 | Append with source, date, scope, and review state |
| Interpretation | Enterprise logistics has become a public positioning theme | Revise confidence as aligned or conflicting evidence arrives |
| Unknown | Customer adoption of the enterprise offer | Keep open, define suitable evidence, or retire if it has no decision use |
Choose the minimum fields the team can keep current
A profile should be smaller than the research archive behind it. Begin with fields that support recurring decisions and expand only when a real use appears.
- Identity: official name, domain, legal entity when relevant, and aliases that could cause entity confusion.
- Relevance: direct, indirect, substitute, search, or adjacent relationship, including the segments where it applies.
- Customer and problem: audiences and use cases the competitor currently claims to serve.
- Positioning: the current public promise, category language, and meaningful proof points.
- Offer: active products, services, plans, and documented capabilities within the maintained scope.
- Commercial state: observed public pricing and packaging with every comparison condition preserved.
- Market scope: named regions, industries, channels, or company sizes relevant to the team's decisions.
- Evidence state: source, observation date, last verified date, confidence, contradictions, and open questions.
- Maintenance state: owner, review interval, event triggers, recent changes, and the next decision affected.
Financial estimates, broad feature matrices, executive biographies, social counts, and every historical announcement should not be default fields. Add one only when the team has a lawful, suitable source and a repeated decision use. Otherwise keep the material in the evidence archive or leave the question open.
Keep the profile separate from the archive and battlecard
The profile is the maintained state. The evidence archive holds the source material and dated observations that justify or challenge that state. A battlecard is a narrower enablement view designed for a particular sales or customer conversation. Combining all three creates a long document that is difficult to verify and easy to use outside its intended scope.
| Artifact | Primary job | Typical content |
|---|---|---|
| Living profile | Maintain the accepted current view and its decision-relevant history | Scoped fields, interpretations, confidence, unknowns, owners, and triggers |
| Evidence archive | Preserve the material needed to reproduce or challenge a profile change | URLs, captured text or values, dates, source notes, observations, and contradictions |
| Battlecard | Help a named team handle a recurring customer-facing situation | Approved comparison points, discovery questions, objection guidance, and escalation paths |
Link each battlecard statement back to a current profile field. Link each material profile field back to its evidence. When a field becomes stale, the dependent battlecard point should be reviewed too. This lineage keeps a convenient sales summary from outliving the research behind it.
Access should follow the artifact's purpose. Raw customer notes, licensed datasets, personal information, and restricted documents may need tighter handling than an approved profile summary. Preserve source and access restrictions when material is transformed. The competitive intelligence ethics framework covers collection, handling, use, escalation, and recordkeeping.
Create a baseline without pretending it is complete
A baseline is the accepted starting state for future comparison. Verify the official identity and relationship first. Then collect the minimum current fields from sources appropriate to each claim. The competitive intelligence source guide explains how to choose an anchor, corroboration, context, and contradiction without counting repeated delivery routes as independent evidence.
Date the baseline, identify the reviewed source set, and mark fields as verified, provisional, disputed, unknown, or outside scope. “Unknown” is a valid value. An empty cell is ambiguous: it can mean missing research, no public information, an irrelevant field, or a forgotten update.
Absence rule: Failing to find a page, feature, product, or claim does not prove it is absent. Record the checked sources, date, and coverage limits before using absence in an interpretation.
Use explicit write operations when evidence changes
Maintenance becomes safer when reviewers choose a specific operation. This preserves history and prevents a fresh observation from overwriting a better-supported current field.
| Operation | Use it when | What to preserve |
|---|---|---|
| Append observation | A source shows a new or changed item that has not passed the field's proof threshold | Source, captured value, date, scope, and reviewer |
| Update current field | Suitable evidence establishes a new current value within the field's scope | Prior value, effective or observed date, and reason for the change |
| Revise interpretation | Aligned, conflicting, or broader evidence changes the working explanation | Earlier interpretation, confidence movement, and evidence considered |
| Change confidence or scope | The value remains useful but applies more narrowly or with less certainty | Original boundary and the new limitation |
| Open or close a question | A decision-relevant gap appears or receives a sufficient answer | Owner, answer threshold, evidence, and closure reason |
| Retire a field | The field no longer supports a decision or cannot be maintained responsibly | Last accepted value and retirement rationale |
Never erase a prior value merely because a current page differs. A page can be personalized, regional, temporarily unavailable, or caught during a rollout. Append the observation, check comparability and coverage, then update the field when the evidence satisfies its rule.
Resolve disagreement at the field boundary
Two sources can both be accurate inside different boundaries. A US pricing page may differ from a UK page. Documentation for an enterprise plan may describe a capability missing from a starter plan. A current sales note may report a negotiated offer that does not change the public-price field. Compare entity, product, plan, region, currency, channel, customer type, date, and definition before marking either source wrong.
If the conflict survives normalization, keep both records visible. Narrow the current field, lower confidence, or mark it disputed. Assign a reviewer and specify the source or event that could resolve it. A profile that shows a material disagreement is safer than one that selects the most convenient value and hides the rest.
Apply a higher threshold to interpretations and claims of absence than to a directly observed field. Several aligned observations may justify a bounded positioning interpretation. Silence across an incomplete source set cannot establish that a product, audience, or initiative has ended.
Give each field its own freshness contract
One “last updated” date for the whole profile hides stale fields. Identity may remain stable for years. Public pricing can matter within days. Buyer objections may need review after a defined number of qualified deals. Set freshness at field level.
| Contract element | Question |
|---|---|
| Maximum age | How old can this value be before a decision must treat it as stale? |
| Calendar review | Which daily, weekly, monthly, or quarterly check is proportionate to its use? |
| Event trigger | Which observed event forces a review before the calendar date? |
| Proof threshold | What source and corroboration are needed to change the field? |
| Coverage requirement | Which products, regions, plans, or channels must be checked before drawing a conclusion? |
| Owner | Who reviews the field and records the decision? |
Useful triggers include a new product announcement, a verified public price event, a documentation change, a new audience page, a cluster of buyer-reported objections, or a contradiction in an authoritative source. The competitor analysis framework can help connect those observations to a question and available action.
Run a maintenance loop that ends in a decision
- Collect new items from the approved source portfolio and manual research paths.
- Resolve the company, product, market, and time scope before attaching an item.
- Classify the item as a repeated fact, new observation, contradiction, or irrelevant noise.
- Apply one profile write operation and preserve the previous state.
- Review any interpretation or unknown affected by the change.
- Notify the decision owner only when a defined threshold or trigger is met.
- Record the action taken, the outcome to watch, and the next review condition.
The weekly competitor content review workflow provides a practical review rhythm. The competitor tracking spreadsheet template offers a lighter starting structure when a dedicated profile system is unnecessary.
Worked example: update OrbitSail without overstating the signal
LoomCrest and OrbitSail are hypothetical software companies. LoomCrest's baseline says OrbitSail publicly positions its operations product for growing ecommerce teams. The field is supported by the home page, product page, and current customer stories. Its next calendar review is one month away.
A new enterprise logistics page appears. The reviewer appends an observation with the URL, date, copied audience language, and page scope. The page triggers an early positioning review, but it does not immediately replace the current field. One landing page cannot establish a durable company-wide shift, adoption, commercial success, or strategic intent.
Two weeks later, current documentation adds enterprise administration and security material. The navigation now routes enterprise visitors to the same offer, and a current customer page describes an enterprise logistics use case. The reviewer checks that the pages belong to the same product and market. These independent source roles satisfy the profile's threshold for a public-positioning update.
| Profile action | Recorded result |
|---|---|
| Update field | Public positioning now includes enterprise logistics teams within the verified product and market scope |
| Preserve history | The earlier ecommerce-growth positioning remains in the change record and may still apply |
| Revise interpretation | Confidence increases that enterprise logistics is a sustained public theme |
| Keep unknowns open | Customer adoption, enterprise revenue, rollout breadth, and management intent remain unknown |
| Set next trigger | Review after a packaging change, additional customer evidence, a contradiction, or the next calendar date |
The profile gives LoomCrest a defensible current view and a visible change history. It does not turn a pattern of public evidence into facts that the sources cannot support.
Use Content Radar as an evidence input, not the profile owner
Content Radar can help organize selected inputs to a living profile. Supported direct RSS, Atom, and public sitemap sources can add discovered items to Articles. User-supplied Google Alerts RSS and supported manual discovery paths can add Candidate URLs for review. Teams can also keep manually selected URLs in their research flow.
Product Monitoring is separate. For compatible public Shopify, WooCommerce, and structured custom stores, later checks can produce supported product, same-known-currency price, and availability events within documented limits. Those events can trigger a field review. They do not establish cross-store product equivalence, promotion mechanics, demand, or strategic cause.
Content Radar does not generate competitor profiles, maintain profile fields, score confidence, draw conclusions, or produce executive reports. Source health reflects the last known collection attempt and does not prove complete coverage. A reviewer still applies the source standard, chooses the write operation, and owns the decision record.
Review profile health by sampling material fields and reproducing their current values from the linked evidence. Track stale decision-critical fields, unresolved contradictions, overdue questions, and updates with no named owner. Field count and document length are poor substitutes for this maintenance test.
Profile review checklist
- The competitor relationship and decision use are explicit.
- Every current field has a source, scope, last verified date, and owner.
- Dated observations remain separate until they meet the field's change rule.
- Interpretations show support, contradiction, confidence, and decision relevance.
- Unknowns have an answer threshold, next action, or retirement decision.
- Prior values remain available after an update.
- Freshness and event triggers operate at field level.
- Coverage limits are checked before absence or silence affects a conclusion.
- The latest review ends with an action, owner, and next trigger.
Keep profile evidence ready for review
See how Content Radar organizes selected public publishing and compatible ecommerce signals that can feed a human-maintained competitor profile.