Writing and content decision
Paperpal
A single developer can replicate a useful Google Docs grammar/paraphrase assistant in ~1 week using LanguageTool + an LLM, but cannot cheaply reproduce Paperpal’s claimed scholarly training/scale, institutional integrations, plagiarism/reference databases, or brand trust.
Visit website↗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.
What a replacement has to do
- Accept user text (Docs/web), run grammar/clarity/paraphrase checks via LLM or grammar engine, return suggested edits and alternative phrasings, apply edits in-document via editor plugin.
What it still won’t have
- Paperpal’s claimed training/curation on scholarly corpora (proprietary dataset)
- Trusted institutional integrations and enterprise access management
- Polished UX, editorial quality, and scale-tested accuracy
- Built-in plagiarism and reference databases
What remains hard
- Proprietary data
1M+ papers checked before submission
- Brand trust
Trusted by universities and publishers across the world
First-year cost
No published price
Paperpal does not publish a price we could read, so there is nothing to compare against. What building costs is below.
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 minimal Paperpal-like academic writing assistant with a Google Docs add-on and a small backend. Stack: Node.js/Express backend, TypeScript, React for the add-on sidebar UI, PostgreSQL for user records, and LanguageTool plus an LLM API (OpenAI or similar) for edits/paraphrases. In-scope features: Google OAuth install flow, Docs side panel to send selected text, backend endpoints to run grammar checks (LanguageTool) and paraphrase/edit suggestions (LLM prompts), structured suggestion responses (edits + alternatives), UI to preview and apply/accept/reject edits in the doc, logging, basic rate-limiting, and unit tests for backend endpoints. Out of scope: plagiarism database, institutional billing/SSO, large-scale analytics, offline/local model hosting, document storage beyond transient processing. Include error handling for API failures and timeouts, input validation, and automated tests covering core endpoints and the add-on flow.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Hard moats found in the evidence-3
- Evidence score57
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 · 5
Every page the run actually retrieved.
- official productPaperpal official product page
- official pricingPaperpal pricing
- official docsPaperpal for Google Docs
- open sourcelanguagetool-org/languagetool
- open sourcetheJayTea/WritingTools
Integrity checks
What held up, and what did not.
