
Lexigramrevenue
Natural Language Processing (NLP) SoftwareRedwood City, CaliforniaFounded 2014
Shut downLexigram is a former Natural Language Processing (NLP) Software company based in Redwood City, founded in 2014.
Lexigram revenue
Lexigram has not published its revenue. GetLatka estimates it at about $399.1K a year (October 2023).
All 2 revenue readings, with sources
| As of | Revenue | Source |
|---|---|---|
| Apr 2021 | $332.6K | – |
| Oct 2023 | $399.1KEST | GetLatka estimate |
– source not recorded
Lexigram CEO, founders & employees
Manuel Salvadores founded Lexigram in 2014 and led it as CEO. Lexigram had 1–3 employees (October 2024, LinkedIn).
- Manuel SalvadoresFounder & CEO
All 9 headcount readings, with sources
| As of | Employees | Source |
|---|---|---|
| Oct 2024 | 3 | |
| Oct 2024 | 1 | |
| Dec 2023 | 3 | |
| Oct 2023 | 4 | |
| Dec 2022 | 1 | |
| Dec 2022 | 3 | |
| Oct 2022 | 4 | |
| Dec 2021 | 4 | |
| Apr 2021 | 5 | – |
Lexigram FAQ
Is Lexigram still in business?
No. Lexigram has shut down.
What was Lexigram's revenue?
GetLatka estimates Lexigram's revenue at about $399.1K a year (October 2023). The company hasn't published its own figure.
How many employees does Lexigram have?
Two counts from October 2024, according to LinkedIn, put Lexigram's headcount at 1 and 3.
Who founded Lexigram?
Manuel Salvadores founded Lexigram in 2014.
Browse Natural Language Processing (NLP) Software
Categories
- All Natural Language Processing (NLP) Software companies, ranked
- Clinical Decision Support
- Data Science and Machine Learning Platforms
- Healthcare Analytics Software
- Health Care Software
- Machine Learning Software
- Other Analytics Software
- Text Analysis Software
- Best Artificial Intelligence Software
- Best Vertical Industry Software
- Best Analytics Tools & Software
- All industries
How this page is sourced
8 from public sources · 1 estimate. Founder figures link to the second they were said; public figures name their source; estimates are marked EST and say whose they are. Not financial advice.
Updated Oct 30, 2026Data disclaimerReport a correction