“are there any testimonials of companies/people using this product? how much does it cost? what's the average deal size? would like to learn more about the GTM/sales side of things there”
27 evidence rows gathered as of 10 September 2026 across testimonials, pricing and packaging, organization signals, and developer distribution — spanning generaltranslation.com, GitHub, podcast indexing, job pages, and third-party developer trackers. Average deal size is not disclosed anywhere publicly; the $25K–$100K enterprise ACV band below is an underwriting estimate, not a fact.
Single-source caution: more than half of the directly useful pricing and testimonial rows are company-owned or company-curated pages; Theo’s long walkthrough disclosed GT as a sponsor. No independently verified ROI, deployment size, spend, or before/after metrics were found.
The PLG-to-enterprise wedge
Hover a stage for the evidence behind it. Width narrows from free developer entry to hand-closed enterprise contracts; the dashed band is estimated, not observed.
Cursor’s head of engineering calls GT “an incredible product, we are users at @cursor_ai” — but the quote lives on GT’s own enterprise page. generaltranslation.com
The Starter plan is $0/month with unlimited users, projects and languages, 5M free platform credits, then pay-per-workflow usage on input tokens; Enterprise is custom-priced with SLAs and forward-deployed engineers. generaltranslation.com
A job listing shows about 8 employees and no sales, marketing or customer-success openings — enterprise deals are almost certainly founder- and engineer-led. builtin.com
The “no enterprise customer has ever churned” claim appears on one Duke career-hub posting and is not independently verified. careerhub.students.duke.edu
Testimonials: real names, mostly curated venues
Andrew Milich — Head of Engineering, Cursor
“General Translation is an incredible product, we are users at @cursor_ai”
Public logo claims: Cursor, Ramp, Mintlify, Profound, Partiful, ClickHouse — and Cognition on hiring pages. High-quality names, but logo proof only: no case study quantifies spend or deployment size.
Unlimited users, projects and languages; 5M free platform credits to start
Then pay-per-workflow usage billed on input tokens; varies by workflow, file format and context; agent workflows priced separately generaltranslation.com
An en-GB usage page states $1 per 1,000 input tokens plus $0.02 per 1,000 input tokens per 1,000 context tokens — a regional page; the current US page exposes the formula without a clean rate table
Enterprise — custom pricing
Custom integrations and workflows, custom SLA, forward-deployed engineers, enterprise support generaltranslation.com
Shared translation context, glossaries and prompts across every project and content source generaltranslation.com
No public minimum, annual commitment or contract price found. Older $5/month and $500/month tiers are gone
Average deal size: unknowable publicly — an estimate, clearly labeled
No contract values are disclosed. Inferring from custom pricing, FDE labor, SLA and security packaging, startup-heavy logos, an ~8-person team, and no visible sales hiring: likely enterprise ACV of roughly $25K–$100K, with ~$50K a reasonable central assumption; strategic FDE-heavy deployments could exceed $100K. Self-serve accounts likely spend near zero to low thousands a year, so a blended average across all accounts would be far below enterprise ACV and not meaningful. Sensitivity at $50K ACV: 10 enterprise customers imply $0.5M enterprise ARR, 25 imply $1.25M, 50 imply $2.5M — before self-serve usage. These are not actual customer counts or ARR.
Sales motion: engineering-led, not a scaled sales organization
Inference from public pages: the target user is the developer (open-source TypeScript/React stack, CLI/npm install, free API key, docs and influencer sponsorships as top of funnel); likely economic buyers are engineering and product leaders, developer-experience/platform teams, and localization leaders. GitHub showed ~954 stars and 28 forks when captured, with third-party snapshots around 988–1.1K — early but visible developer awareness. Careers pages describe a “lean team” hiring engineers in San Francisco; no AE, SDR, marketing or CS roles were found, so closing likely rests on founders and forward-deployed engineers. Named customers cluster among developer-first, high-growth software companies — a strong wedge, and a potentially narrow initial ICP.
Diligence checklist
Paid versus pilot or logo-only customers, and number of enterprise contracts
Median and average ACV; renewal terms and net revenue retention
Usage gross margin and FDE utilization
Sales cycle and conversion from open source / free tier to paid
Customer concentration and pipeline coverage
All 27 evidence rows
Type
Subject
Evidence
Metric
Source
Shaped evidence set: 27 rows captured as of 2026-09-10 covering testimonials, pricing/packaging, GTM/organization and developer-distribution signals for General Translation. Metrics are as printed on each source page (GitHub stars/forks, employee counts, plan terms); ACV and ARR figures in the estimate section are underwriting assumptions, not observed data. Long quotes truncated in the table for space; each row links its source.