PAIN TRIGGERS
Existing AI detectors and checks are easily bypassed and unreliable.
Current writing tools like Google Docs do not detect or prove human creation.
SaaS· academic journalsPain 8.00/10WTP 8.0/10Market 8.0/10Validation 8.0Confidence 72%May 13, 2026
HumanTrace: Real-Time Keystroke Provenance for Human-Authored Documents
No reliable way to prove text was human-composed after creation; post-facto detectors are consistently bypassed, fracturing trust in documents.
academiaai-poweredcompliancecontent-creationdevtoolseducationjournalismproductivitysaasverification
1
STAGE 01 · PROBLEM
Is the problem real?
CANONICAL PROBLEM
It is impossible to reliably detect whether text was AI-generated or human-composed after the fact.
FREQUENCY
Limited repetition signal.
INTENSITY
Users explicitly describe existing tools as bloated/overkill and mention workaround behavior.
EVIDENCE
Show HN: Truly Typed – A writing app for the AI era
42
Show HN: Truly Typed – A writing app for the AI era
42
Show HN: Truly Typed – A writing app for the AI era
42
Show HN: Truly Typed – A writing app for the AI era
42
2
STAGE 02 · CUSTOMER
Who feels this pain?
TARGET USERS
academic journalsUniversity Integrity Officers And Academic Writers
University admins and students/journalists who must prove written submissions are genuinely human-authored rather than AI-generated for grading, publication, or credibility.
Context
Verify and prove that written documents contain genuine human-authored content, especially for academic, journalistic, or professional sharing.
Explicitly stating 'I typed this myself' at the end of posts or documents.
Current Workarounds
Manually adding 'I typed this myself' disclaimers
Using easily bypassed AI detectors like Turnitin or GPTZero
Relying on honor codes or vibe checks with no proof
3
STAGE 03 · MARKET
Where's the gap?
EXISTING SOLUTION GAPS
AI detectors are bypassable and do not consistently distinguish human from AI text.
Google Docs and Microsoft Word do not track or prove how content was actually created (typing vs. generation).
No reliable way to verify provenance of text after creation.
OPPORTUNITY & VALUE
Why Now
Strong repeated emphasis on unreliability of all existing detection methods across academic and media contexts.
Value Proposition
Creation-time behavioral provenance instead of unreliable post-generation linguistic detection; impossible to fake without matching live typing patterns.
Product Direction
A secure writing app/extension that records keystroke sessions in real-time, generates tamper-proof provenance certificates (timestamped + behavioral hash), and allows easy verification by recipients.
4
STAGE 04 · BUSINESS
How does it make money?
MONETIZATION
$19/moPer writer or per institution seat
Model
SaaS subscription
WILLINGNESS TO PAY
Institutions already pay for Turnitin and similar tools due to integrity crises; writers explicitly seek proof mechanisms as disclaimers fail and trust erodes. Signals show urgent need for verifiable alternative to bypassable detectors.
5
STAGE 05 · EXECUTION
How do you ship it?
MVP PLAN
“Prove your text is human-authored at creation time.”
A secure writing app/extension that records keystroke sessions in real-time, generates tamper-proof provenance certificates (timestamped + behavioral hash), and allows easy verification by recipients.
Core Features
Real-time keystroke capture in browser editor
Tamper-proof session certificate with PDF export
Simple verifier link for recipients (schools/journals)
Basic anti-spoofing (focus time, deletion patterns)
Weekly Roadmap
1
W1-W2
Core real-time editor and certificate generation working for single documents.
- •Build browser-based editor with keystroke logging
- •Implement session hashing and basic certificate JSON
- •Add PDF export with QR code verifier
2
W3-W4
Anti-spoofing and shareable verifier complete.
- •Add focus time, deletion pattern detection
- •Build public verifier web page
- •Session tamper detection (hash chain)
3
W5
Internal testing and first user onboarding.
- •Recruit 5-10 academic beta testers
- •Polish UI/UX and export formatting
- •Basic usage analytics dashboard
4
W6
Public launch ready with initial paid conversions.
- •Stripe integration for subscriptions
- •Launch post in r/academia and writer forums
- •Document 1-2 case studies from betas
Launch Strategy
Target r/academia, r/professors, university tech procurement lists, and writer communities on X/Reddit
RISKS & ASSUMPTIONS
Top Risks
Detector arms race continuation
Sophisticated users may still try to game live recording; behavioral spoofing needs strong anti-cheat.
Integration friction with existing workflows
Writers prefer Google Docs/Word; forcing a new editor risks low adoption.
Privacy concerns on keystroke data
Recording sessions raises data sensitivity issues especially for institutions.
Verification trust
Recipients must trust the certificate format without established standards.
6
STAGE 06 · DECISION
Should you build it?
NEED A CLEARER CALL?
Run an Investment Memo to get a structured Go / No-Go verdict, competitor landscape, unit economics, and a 90-day validation roadmap for this opportunity.
Generate an investment memoWhat this score means
This opportunity scores well above the median for ideas surfaced by MonetScope, with a validation sub-score of 8/10 against 4 independently sourced evidence signals. A "strong" rating in this band typically means the pain signal is consistent and recurring across multiple discussions, but one of the three pillars (severity, willingness to pay, or competitor weakness) is somewhat softer than top-tier opportunities. Founders evaluating this should focus customer discovery on the softest pillar first — confirming the gap before committing engineering time to a build.
Why this matters for SaaS founders
It sits at the intersection of "academia", "ai-powered", "compliance", which makes it relevant to a specific subset of founders rather than a generic horizontal opportunity. SaaS opportunities at this stage tend to win on the strength of their initial wedge — a single workflow that the target user runs every week, where the existing solution is either spreadsheets, a clunky incumbent feature, or a manual process they hate. The build cost is moderate; the distribution cost is everything. The MonetScope pipeline surfaces this category alongside other saas signals, which is why it appears here rather than in a generic "trending ideas" feed.
Scores are derived from real forum discussions across Reddit, Hacker News and X, weighted by evidence volume and signal quality. How scoring works
Frequently asked questions
Is "HumanTrace: Real-Time Keystroke Provenance for Human-Authored Documents" a real validated startup idea or just an AI-generated suggestion?
MonetScope does not generate ideas from a language model's imagination. Every opportunity on this site is anchored to specific source posts and comments from real public discussions — typically on Reddit, Hacker News, or X — where actual users describe the pain in their own words. The AI's role is structuring, scoring, and grouping those signals into a navigable opportunity, not inventing the problem.
How recent is the underlying data for academia?
MonetScope's spider pipeline runs continuously and surfaces opportunities as new evidence accumulates. The "Updated" date in the header reflects the most recent re-scoring of this specific opportunity. Most saas opportunities visible in the public catalog draw from discussions in the last 30-60 days; older signals are de-prioritized because user pain shifts faster than most founders assume.
What's the difference between "overall score" and "validation score"?
Overall score is a composite across six dimensions — pain, urgency, willingness to pay, market size, defensibility, and execution ease — designed to give a single number for triage. Validation score is narrower: it asks "how cleanly does the same signal repeat across independent sources?" An opportunity can score high on overall but lower on validation when one or two large discussions dominate the evidence; conversely, validation can be high on a smaller-overall idea where the signal is consistent but the addressable market is modest.