Meta AI director Rohit Patel leaves to take on Microsoft Office and Google Workspace
- ID
- 39991
- Status
- summarized
- Published
- 27 Oct 2026, 10:59 PM
- Fetched
- 27 Oct 2026, 11:50 PM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/10/27/meta-ai-director-rohit-patel-leaves-to-take-on-microsoft-office-and-google-workspace/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 5.0
- Created
- 27 Oct 2026, 11:50 PM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Rohit Patel, a director at Meta Superintelligence Labs who spent eight years on AI at Meta, has left to launch Ndoc, a startup pitched as an AI-native replacement for Microsoft Office and Google Workspace. Ndoc splits work into three tabs: Stage (slide decks, dashboards, simulations, mini apps), Narrative (analyses with numbered citations, generated figures and the reasoning behind the numbers), and Model (the underlying datasets and Python scripts). Colleagues can view a workspace without signing up, and users can pull up the Python script behind any generated document and ask the chat to explain which line produced a given formula.
Why it matters
The reusable idea here is not 'replace Office' — it's the Model tab: every AI-generated figure ships with the script and dataset that produced it, exposed to the reader rather than hidden. If your team already generates reports or dashboards with an LLM, that is a concrete design decision you can copy cheaply this week, and it directly answers the 'can I trust this number' objection you'll hit when pitching internal AI tooling. Also note the no-signup viewer path: Ndoc is treating read access for non-users as a distribution feature, which is worth considering if your product's value only lands when outsiders can open the output.
Discussion angle
Is 'show the Python script behind the number' enough for a team to trust an AI-built spreadsheet, or does verification only work for people who can read the code? Push the room on what a non-technical stakeholder would actually accept as proof.