Mayank Mathur (@MathurMnk) header
Mayank Mathur (@MathurMnk) profile picture

The pod is the new firm. Building Manthan — the aOS for it. Ex-Citi/MS IB London. Exited fintech founder. Vertical AI since 2017.

London
Joined August 2011
Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)Photo by Mayank Mathur (@MathurMnk)
1/ The 1000x Investor: what happens when you build an investment fund that never stops thinking? We built Manthan Intelligence — the AI-native engine for the upcoming Tavaga VC Fund. It analyses 25 companies/day, scores its own predictions, and rewires its own lenses.
1
1
2
173
1/ We almost deleted 907 real company websites yesterday. The "obvious" fix for a duplicate-records cleanup turned out to be based on a false assumption. Here's what caught it before it shipped.
1
45
5/ What we did instead: field-union merge, not delete. Keep the richer, more recent value on every field, every pair. Result: 3 independent precision checks (n=2,485 / 89 / 30) each scored 1.0000. Read-back against the pre-merge snapshot: 0 data loss. 15,500 to 14,442 records, verified.
1
7
6/ The lesson isn't "we cleaned a database." It's that the fastest fix was the one that would've quietly broken the asset. If you're running LLM-touched data pipelines: what's your pre-committed test before a bulk write happens, and would it have caught this.
5
1/ A third-grader just scored 5 on AP Calculus BC using zero LLMs — just a hand-encoded knowledge graph. This reframes the whole AGI-timeline debate. 🧵
1
34
5/ What's coming is hybrid: LLM for breadth, KG for precision. Both. The race to commodity single-modality ends this year.
1
4
Mayank Mathur retweeted
1/ Our weekly health check scans 3 fields for data-quality warnings. On 7 June it came back 0/0/0 — clean. It wasn't. Thread on the miss we found and haven't fully fixed yet.
1
1
4
28
1/ Our weekly health check scans 3 fields for data-quality warnings. On 7 June it came back 0/0/0 — clean. It wasn't. Thread on the miss we found and haven't fully fixed yet.
1
1
4
28
5/ Lesson: a self-healing loop is only as good as the agreement between what your writers emit and what your reader watches for. When those vocabularies drift quietly, the system doesn't fail loudly — it reports green.
1
5
6/ Fix isn't "widen the regex" blindly — some of those flags (insolvency proceedings) are legit business signals, not errors. Classify first, then converge the writers. Queued this week. Publishing the open defect now, not the tidy resolution later. getmanthan.com
8
1/ April: a routine audit of our knowledge graph's sector labels found a 58% error rate on one batch. An LLM was matching keywords to sectors, not checking what companies actually did. We fixed it. Then the same bug came back somewhere else — read on.
2
2
24
6/ The claim: this bug resurfaces in every new field we classify from text, because it's structural, not a one-off. It did — 7 Jul, a home-improvement retailer almost got tagged "hardware" (as in electronics) because its own hardware meant bathroom fittings. Same guard caught it.
1
8