The founder problem
Competitor movement creates anxiety because founders have to answer quickly: did someone beat us, validate our market, change the standard, weaken our story, or create a new customer objection?
The useful answer is not a generic market summary. It is a product-specific comparison tied to your Product ID, claims, evidence roadmap, and buyer conversation.
What to compare first
- Intended use and claim boundary.
- Customer, procedure, workflow, and buying trigger.
- Technology and physical or software role.
- Jurisdiction and public authorization or licence clues.
- Product-code, classification, and comparator buckets.
- Safety-history and recall clues, with limitations.
- Evidence claims that appear stronger, weaker, or not publicly supported.
The direct-competitor test
A product is not a direct competitor simply because it sounds similar. It has to compete for the same buyer decision, workflow slot, claim, budget, or evidence story.
That is why the review should keep several labels: direct competitor, adjacent comparator, substitute workflow, enabling technology, future roadmap threat, or not currently relevant.
What the report should produce
| Output | Why it matters |
|---|---|
| Source ledger | Keeps the review from relying on rumor or a single announcement. |
| Same / different matrix | Shows whether the products really compete around the same job. |
| Claim-boundary note | Flags overclaiming risk and evidence-roadmap implications. |
| Founder action brief | Turns the signal into customer, investor, partner, or board talking points. |
What TrueMedDevice can prepare
TrueMedDevice can prepare a competitor movement review for one Product ID: signal summary, public source ledger, same / different matrix, reliability notes, open questions, founder impact brief, and next-action options.
Source ledger
What it can tell you
Public FDA database families for cleared, approved, classified, recalled, and postmarket device records.
What it cannot decide
Whether a competitor's device is directly substitutable, commercially stronger, clinically superior, or a valid predicate.
What it can tell you
Device names, product codes, device classes, and generic category clues used by FDA.
What it cannot decide
Whether two products share the same intended use, claim boundary, evidence burden, or commercial buyer.
What it can tell you
How TPLC combines public premarket, recall, and adverse-event information by product code and why counts can change.
What it cannot decide
Adverse-event rates, product quality, market share, or direct safety comparison between products.
What it can tell you
Active Canadian medical device licences for Class II, III, and IV devices, with licence and manufacturer context.
What it cannot decide
Whether a licensed product is commercially successful, equivalent to your product, or relevant to your intended Canadian positioning.
Frequently asked questions
Can public FDA records prove that a competitor is better?
No. Public FDA records can show authorization, classification clues, summaries, recalls, or adverse-event reports. They do not prove commercial success, clinical superiority, or direct substitutability.
What if the competitor has no public FDA record?
The review can still capture company announcements, trials, patents, distributor materials, conference signals, and customer claims, but the confidence level and limitations should be explicit.
Is this a regulatory report or a market report?
It is a Product ID strategy review. It uses regulatory and public evidence to support founder-level market, investor, customer, and partner questions without making regulatory determinations.
What is the first useful deliverable?
A short competitor impact memo with source ledger, same / different matrix, claim-boundary implications, and the next three questions to review before changing the sales or investor story.
Need to know if a competitor signal matters?
Send the product signal and the Product ID you are protecting. We can scope a source-backed competitor impact memo before you rewrite your sales or investor story.