SAASPOCALYPSEverdict #GRAMMARLY-B510
scanned 2026.05.04 · 14:35
subject of investigation

grammarly.com

AI writing assistant & grammar checker
verdictCONTESTED
wedge score
47
/100
wedge thesis

The door is vertical distribution: Grammarly is a horizontal tool for everyone, which means it's a mediocre tool for any specific niche — a focused writing assistant for, say, legal, medical, or developer docs would own a segment they can't serve well.

real walls — pick your flank·ship in 8 weeks·run for $24.00 + usage
the doorregulatory
wedge

where the walls are.

methodology →
the door

no regulatory wall — SOC 2 doesn't count.

watch out

their distribution is fortress-grade — they own their brand SERP end-to-end.

capital
5.0/10
investment the incumbent had to make
why this scoremedium confidenceGrammarly's capital moat is moderate. They have a large engineering org, dedicated teams for painful integrations...

Grammarly's capital moat is moderate. They have a large engineering org, dedicated teams for painful integrations (Word, Google Docs), and significant brand/marketing spend. However, the core product is software — there's no inventory, payments risk, or heavy compliance infrastructure. The main capital barrier is the sustained investment in maintaining fragile editor integrations and a browser extension across a constantly shifting landscape of third-party apps. An indie builder can replicate the core product cheaply, but keeping up with integration breakage at scale requires headcount.

  • Grammarly maintains a dedicated team for MS Word and Google Docs add-in integrations, which break frequently on updates — this is an ongoing capital commitment, not a one-time cost.
  • 40 million users implies significant infrastructure spend for low-latency suggestion delivery at scale, though the wedge competitor would start small.
  • No evidence of heavy compliance teams, regulated duties, or proprietary physical infrastructure — capital moat is primarily headcount and integration maintenance.
technical
6.0/10
depth of the underlying engineering
why this scoremedium confidenceThe technical moat is real but not a fortress. The hard parts — sub-200ms perceived latency at keystroke speed,...

The technical moat is real but not a fortress. The hard parts — sub-200ms perceived latency at keystroke speed, stable content-script injection across dozens of constantly-changing third-party apps (Gmail, Notion, Slack, Google Docs, Word), and a robust suggestion engine that avoids false positives — represent genuine engineering depth. However, LLMs have commoditized the core NLP/grammar logic that was Grammarly's original technical differentiator. The remaining technical moat is in the integration surface area and latency engineering, both of which are solvable by a skilled small team, just slowly.

  • Achieving <200ms perceived latency with LLM calls requires aggressive debouncing, streaming, and edge deployment — non-trivial but documented techniques.
  • Browser extension content script injection into arbitrary third-party pages without breaking their UI is described as 'fiddly but well-documented' — real friction, not a fortress.
  • Google Docs and Word add-in APIs are 'painful, poorly documented, and break on updates' — Grammarly has a dedicated team; an indie builder does not.
network
2.0/10
users compound users
why this scorehigh confidenceGrammarly is a single-player productivity tool. There is no meaningful network effect — one user's presence does not...

Grammarly is a single-player productivity tool. There is no meaningful network effect — one user's presence does not make the product more valuable for another user. There is no marketplace, no social graph, no UGC corpus that compounds with user growth, and no multi-sided liquidity. The free tier drives distribution but not network effects. A niche competitor does not need to overcome any network to win a vertical segment.

  • Grammarly is a horizontal writing assistant — individual users derive value independently, with no interaction between users that creates network value.
  • No marketplace, partner/app ecosystem, or social graph features are described or evident in the product.
  • 40 million free users represent distribution scale, not a network effect — losing one user does not degrade the product for others.
switching
4.0/10
stickiness of customer data + workflow
why this scoremedium confidenceSwitching costs are moderate but not high. Users accumulate personal dictionary entries, custom style rules, and...

Switching costs are moderate but not high. Users accumulate personal dictionary entries, custom style rules, and writing statistics over time, but none of this is deeply trapped — it's exportable or recreatable. The main switching friction is behavioral: Grammarly is embedded in the user's browser and workflow across every writing surface. Uninstalling and replacing it requires conscious effort and retraining muscle memory. For enterprise/team plans, there may be admin-configured style guides and team settings, adding some organizational friction. But there's no deep data lock-in or approval chain.

  • Personal dictionary, custom style rules, and writing stats create mild lock-in but are not deeply non-exportable.
  • Browser extension embedded across all writing surfaces (Gmail, Notion, Slack, docs) creates behavioral/workflow lock-in — replacing it means changing a habit, not just a tool.
  • No evidence of deep ERP-style integrations, approval chains, or migration complexity that would make switching painful at an organizational level.
data
7.0/10
proprietary data accumulates over time
why this scoremedium confidenceThis is Grammarly's strongest moat axis. Years of behavioral data from 40 million users — what suggestions were...

This is Grammarly's strongest moat axis. Years of behavioral data from 40 million users — what suggestions were accepted, rejected, ignored, and in what contexts — constitutes a proprietary training and evaluation corpus that an indie builder cannot replicate. This data has been used to train and fine-tune their own models (GrammarlyGO). The feedback signal at scale (accept/reject per suggestion type, per writing context) is genuinely non-replicable from a standing start. However, LLMs trained on internet-scale data partially erode this advantage for general grammar, and a niche vertical competitor would be building a different, smaller dataset anyway.

  • 40 million users generating accept/reject signals on grammar and style suggestions over many years is a proprietary behavioral data flywheel.
  • Grammarly has used this data to train GrammarlyGO and their own suggestion models — the corpus is actively used for model improvement, not just logged.
  • An indie builder starting today has zero of this behavioral feedback data and cannot purchase or scrape an equivalent.
regulatorydoor
1.0/10
real licenses, not SOC 2 theater
why this scorehigh confidenceThere is no meaningful regulatory moat. Grammarly is a writing assistant with no regulated duties — no HIPAA...

There is no meaningful regulatory moat. Grammarly is a writing assistant with no regulated duties — no HIPAA obligations (they process text but are not a covered entity or BAA holder in the clinical sense), no financial licenses, no KYC/AML, no money transmission, no PCI obligations. SOC 2 compliance is mentioned implicitly by enterprise positioning but SOC 2 alone is explicitly low per the rubric. A niche competitor in legal or medical writing would face the same absence of hard regulatory barriers — the domain knowledge is a product challenge, not a licensing one.

  • No evidence of HIPAA BAA obligations, financial licenses, KYC/AML, money transmission, or clinical EHR data handling.
  • Writing assistant category has no inherent regulated duties — processing user text does not trigger financial or healthcare licensing requirements.
  • SOC 2 is the likely compliance posture for enterprise sales, which the rubric explicitly scores as low.
distribution
8.0/10
brand SERP grip, knowledge graph, news flow
take

the blunt take.

Grammarly has 40 million users and a free tier, which means the mass market is already spoken for. The wedge isn't "better grammar checker" — it's "grammar checker that actually understands what I'm writing about."

A legal writing assistant that knows contract language, or a developer-docs tool that doesn't flag technical jargon as errors, would have a real reason to exist. Grammarly's horizontal model is its distribution strength and its product weakness simultaneously.

cost

cost of competing.

what they charge
Pro plan
$12
/ member/mo (billed annually)
$30/mo if billed monthly
annual:$144
what running yours costs
01 · Vercel Pro (SSR + edge for extension backend)$20.00
02 · Supabase free (user accounts, settings)$0.00
03 · OpenAI / Anthropic API (grammar + rewrite calls)??? — scales with usage
04 · Resend free (transactional email)$0.00
05 · Chrome Web Store developer fee (one-time, amortized)$2.00
06 · Cloudflare R2 (document storage, light)$1.00
07 · Domain$1.00
08 · Sentry free (error tracking)$0.00
TOTAL / mo$24.00 + usage
▸ break-even:immediately for Pro — $12/mo vs ~$30/mo est_total means a single paying user covers your infra. At free tier, never.
build

what you're up against.

2 weeks browser extension scaffolding · 2 weeks LLM prompt engineering for vertical domain · 2 weeks editor integrations (VS Code, Google Docs) · 2 weeks billing + onboarding polish
easy
medium
hard
nightmare
01
easy
Core grammar/spell check UI
Inline underline + suggestion popover. TipTap or CodeMirror handles the heavy lifting.
02
easy
User auth + settings persistence
Supabase Auth + a settings table. Standard CRUD.
03
medium
Browser extension content script injection
Injecting into arbitrary third-party pages (Gmail, Notion, Slack) without breaking their UI is fiddly but well-documented.
04
medium
Domain-specific prompt engineering
Getting an LLM to reliably flag issues in legal/medical/dev prose without false positives requires careful few-shot tuning and eval sets.
05
hard
Latency at keystroke speed
Grammarly's inline suggestions feel instant. Achieving <200ms perceived latency with LLM calls requires aggressive debouncing, streaming, and edge deployment.
06
nightmare
Deep editor integrations (MS Word, Google Docs native)
Google Docs and Word add-in APIs are painful, poorly documented, and break on updates. Grammarly has a dedicated team for this. You do not.
stack

their position.

detected signals· measured
frameworkNext.jscdnCloudFront
recommended stack · inferred
inferNext.js 15 (app router + API routes)inferChrome Extension Manifest V3 (content scripts)inferOpenAI API (GPT-4o-mini for speed/cost balance)inferSupabase (auth + user prefs)inferTipTap (standalone editor view)
rivals

who else has tried this.

option A
LanguageTool (self-host)
Open source, runs locally, no API costs. Lacks LLM rewriting but covers grammar/spell check solidly.
option B
ProWritingAid
Cheaper than Grammarly Pro, deeper style analysis, niche-friendlier. Skip the build if your users just need this.
option C
ChatGPT / Claude with a system prompt
A well-crafted system prompt for your vertical beats Grammarly's generic suggestions for domain-specific writing today.
compare

similar scans.

same shape - different moat
ready to wedge in?
Get the wedge plan. Cancel some plans.
▸ generated with love, by a heartless robotverdict v2.5 · saaspocalypse.dev