Product URL analysis
Creates an initial understanding from the public product site.
AvailableProduct / Current state
A customer-discovery product in active development.
Seek analyses a SaaS product, looks for relevant public conversations, and explains why a small number may be worth reviewing.
BetaSource-firstHuman-reviewed
SEEK / OPPORTUNITY 04 Reviewing
HACKER NEWSProblem expressionJuly 2026
“We (that is to say my business partner and I) are building SaaS products, but we are really struggling to find enough users.”Read the original thread on Hacker News ↗
Quoted as published in “Ask HN: How do you do marketing in the age of slop?”. The layout around it is a mock-up of a Seek report.
WHY IT MATCHES
The author says, in their own words, that finding users is their problem: the problem this product helps investigate.
SUGGESTED NEXT STEP
Ask about their target customer and share a useful discovery framework before mentioning a product.
Product overview
Seek begins with product understanding, not keywords. It builds a structured picture of who the product is for, the problems it addresses and the language a potential user might use.
Results stay traceable so the founder can inspect the original conversation before deciding whether any next step is appropriate.
Current capabilities
Built, beta and planned.
Structured product profile
Maps ideal customers, pains, use cases and alternatives.
In betaPublic conversation discovery
Searches supported public sources for evidence matching the profile.
In betaIntent qualification
Separates active needs from weak mentions.
In developmentOpportunity report
Shows source, signal, relevance, explanation and next action.
In betaSaved opportunities
Keeps useful opportunities organised for later review.
PlannedAutomatic outreach
Not planned: Seek requires human judgment.
Not availableHow an opportunity is created
1. Product profile
Seek structures the audience, jobs, problems, use cases, buying language and known alternatives.
2. Signal discovery
Public conversations are searched with combinations of problem language, intent patterns and product context.
3. Qualification
Candidates are checked for intent, relevance, source quality and whether enough context exists to act responsibly.
4. Explanation
The source appears first, followed by Seek’s interpretation and a suggested next action.
Human validation
Seek supports judgment. It does not replace it.
During beta, products and results may be reviewed manually. Seek never posts, comments or messages anyone on your behalf. A person must read the source and decide whether contributing would genuinely help.
Known limitations
- A problem match does not guarantee buying intent.
- Public-source coverage is still limited.
- Product profiles can miss niche language without founder input.
- Older conversations may be useful for research but unsuitable for outreach.
- Relevance scores are guidance, not objective truth.