Opportunities › Translation management for distributed teams › Proposed app
Larkspell
Translation workflow for dev teams: translators, review and Git sync
- Score
- 56
- confidence 42
- Evidence
- 1
- items on the page
- Rivals
- 0
- named in sources
- First version
- 35 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2009
- Mature market · AI estimate
ScreensConcept
Desktop app: Developers push strings from repos, translators work in a browser editor, and reviewers approve pull requests—all text-heavy coordination work. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Project progress
Release in 5 days82%
- German
About this appAI proposal
Larkspell keeps every language of your app in one place. Developers push source strings from their repo, translators work in a simple browser editor, and reviewers approve changes before they go back as a pull request.
It is built for small software teams shipping web apps and SaaS products to several markets, including teams that want to keep data on their own servers. Roles are flexible, so a team can use in-house translators, outside agencies or both.
Instead of spreadsheets and emailed files, every string has a status, an owner and a history. You can export everything at any time, so you are never locked in.
- Tagline
- Every language, one calm workflow.
- Voice
- ClearPracticalCalm
- Why this name
- Lark is a songbird, a nod to voices in many languages, and spell hints at words. Two plain parts, easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Git sync
Pull source strings from your repo and send approved translations back as a pull request. Common JSON, YAML and PO formats.
No member yet
Per-language workflow
Set your own steps for each language: draft, review, approve. Use a lighter flow for small markets.
No member yet
Translator invites
Invite outside translators to chosen languages only. They see strings, context and comments, never your code.
No member yet
Context for every string
Attach notes, screenshots and character limits to a key so translators stop guessing.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#1F3D36Deep Moss · primary#F6F3ECPaper · surface#1B2421Ink · text#E0793ALarkspur · accent#8FB5A3Sage · data
Typography
Aa
Larkspell
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Every language, one calm workflow.
PricingAI proposal
The material gives no competitor prices. Tiers are a starting point to test, following the monetization idea of team size, languages and self-hosted support.
Open
Free
- 1 project
- 2 languages
- 3 members
Team
$39 a month
- Unlimited members
- 10 languages
- Git sync
- Review workflow
Scale
$99 a month
- Unlimited languages
- API access
- Priority support
Self-hosted
$1200 a year
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Users invite others. Developers invite outside translators and reviewers into their project. Translators who also work for other software teams see the tool and may suggest it to them.
- Do they become customers?
- Translators are mostly users, not buyers. Test whether freelance translators bring in their client teams, and whether those teams start paid projects.
- First customers
- Teams of 3 to 15 developers at small SaaS companies localizing a web app into 3 to 8 languages, led by an engineering manager.
- Where to reach them
- GitHub and open-source forums: Share a free sync tool and guides on localizing web apps in project discussions and issues.
- Developer communities: Post practical write-ups on i18n workflows on Hacker News, Reddit and dev.to.
- Direct outreach: Contact engineering leads of SaaS teams that list several languages on their sites.
- First milestone
- Ten teams run a real project through Git sync and five pay for the Team tier within 60 days.
Why people already pay for this
- VerifiedGitHub repository gained 2132 stars in 2776 days
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · File parsingParsers for JSON, YAML, PO, XLIFFNeeded to read and write the string files teams already use.
- This app · Git integrationGitHub and GitLab app APIsPull source strings and open pull requests with approved translations.
RisksAI inference
- CommercialOpen-source and established translation tools may already satisfy teams; Larkspell needs a clear edge in price or workflow flexibility.
- TechnicalMany file formats and framework conventions (plurals, placeholders) cause subtle sync bugs.
- PlatformDepends on GitHub and GitLab APIs and app review; changes could break Git sync.
- CommercialSelf-hosting adds support load and may reduce hosted subscriptions.
- DataSource strings may be confidential before launch; access controls and hosting location must be trusted.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.