Learning and careers decision
The Read Time, LLC
A capable developer can recreate the core RSVP reader and basic PDF/TTS flows (prior art exists for RSVP), but reproducing the polished cross-site extraction, Chrome store reputation, and ongoing paid features is non-trivial and would take multi-week effort, so building a narrow replacement is realistic while matching the full paid product is harder.
Visit website↗$7.95/mo
$95/yr
Read off the official pricing page.
$100one-off90 h to build
$20/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 4 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All The Read Time, LLC alternatives, with the arithmetic →
What a replacement has to do
- Load page or document -> extract text -> render RSVP stream at chosen WPM -> optionally play synced TTS -> store user settings.
What it still won’t have
- Chrome Web Store listing reputation and existing user ratings
- Polish edge-case handling and cross-site extractor rules accumulated by the vendor
- Priority support and ongoing feature rollouts bundled with Plus
- Mobile apps or native OS integrations (if vendor provides them)
What remains hard
- Brand trust
Rated 4.9 in the Chrome Web Store
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 4 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a Chrome WebExtension + small backend that replicates a minimal ReadTime Plus: stack: React for popup/options, plain WebExtension APIs (manifest v3), pdf.js and epub.js for document text extraction, Web Speech API with fallback to a paid cloud TTS (expose REST proxy on Node/Express), Stripe for one-seat Plus billing, and S3 for uploaded files. Core features in scope: (1) content extraction from arbitrary pages; (2) RSVP renderer with configurable WPM, chunk size, fonts and themes; (3) TTS playback synced to RSVP with play/pause/seek; (4) PDF and ePub upload/import and parsing to plain text; (5) local settings persistence and a Stripe-gated Plus flag enabling PDFs/ePubs and unlimited TTS. Out of scope: mobile apps, analytics/dashboard for multiple users, advanced extraction heuristics for every site. Require error handling for extraction/parsing/TTS failures, unit tests for parsing and RSVP timing, and end-to-end tests for extension install and basic flows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- Price verified on pricing page+3
- Evidence score63
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productThe Read Time — product
- official pricingReadTime Plus — pricing
- open sourcepasky/speedread (prior art)
Integrity checks
What held up, and what did not.
