The inbox
Intro threads, founder updates and data room links, spread across 400 emails and three people's inboxes.
For investment teams
Your fund's judgment, on one record.
Every deal leaves a trail: intro emails, a data room, IC debates and the reasons you passed. Mobtasks keeps that trail on one record. AI coworkers screen decks and work the data room against your checklist, cite every source, and wait for the deal partner before anything goes to a founder.
Deal walls built in Untrusted files screened Sources on every answer Runs on your machines
The problem
The fund's best asset walks out the door.
Pattern recognition is what a fund sells to its LPs. Today it lives in inboxes, memo drafts and partners' heads. When a principal leaves, the reasons behind hundreds of decisions leave too.
The memos
IC_memo_draft3.docx is on a desktop. The IC debate that changed the decision is in nobody's notes.
The why
“Why did we pass on Ledgerly?” Only the principal who ran the deal knows, and they left in March.
Across the deal
From inbound deck to LP question.
One channel per deal. Agents do the reading and the matching. Your people decide at every step that matters, and every step lands on the record.
01 · Screen
Every inbound deck, against your thesis
A Monday pipeline screens each new deck against the thesis and drafts a one-page note per company. Your review is a stage, so nothing passes it by itself.
02 · First look
What do we already know?
Search by text and by meaning across every past deal, memo and IC thread. Answers name their sources and come only from deals you may read.
03 · Diligence
The data room, against your checklist
Sync the data room to the deal folder. The agent screens every file first, then matches the room to your checklist and lists the gaps, with questions for the founders.
04 · Investment committee
Memos that cite their sources
The memo cites the cohort file, the customer call and the deal you passed on. The IC debate stays in the thread, next to the memo it changed.
05 · Founders
Nothing leaves without a partner
Questions and documents for a founder wait for the deal partner's approval, in the workspace or in Slack. The record keeps who approved what.
06 · Portfolio
One channel per company
Board decks and monthly updates stay with each company. A pipeline drafts a summary of each update for the partners' meeting.
07 · LPs
Answer the LP's question
When an LP asks why you led a round, the record holds the memo, the IC thread, the approvals and the files they cited.
08 · Memory
Judgment becomes the playbook
Scribe turns IC debates into the fund's positions, such as how you judge churn at Series A. Every line points to its source, and a partner promotes it.
What you get
Built for how a fund runs its deals.
The deal channel holds the data room, the questions, the answers and the sign-offs. The fund's playbook grows from them.
Diligence against your checklist
Ask in the deal channel. The agent matches every checklist item to a file and lists what is missing: churn, the signed cap table, IP assignment.
Answers that cite sources
Every answer names the file, the IC note and the earlier deal it used, so you can check it before it goes in a memo.
Deal walls
An agent reads as the person who asked. A deal you cannot open stays out of its context and out of its answers.
The deal partner signs off
Anything sent to a founder waits for the deal partner. Approve in the workspace or in Slack. Routine reading runs without approval.
The data room, synced
Memos, models and trackers open in the deal. A folder on your Mac syncs both ways, and a conflict keeps both copies.
Know what diligence costs
See agent spend per accepted memo and per deal, across every agent and model.
Plan your team in plain words
Describe your fund. Review the team it proposes.
Chief of Staff asks up to three questions, then proposes AI coworkers and channels. You edit or untick each role before anything is created, and every new agent starts restricted.
An example team for a Series A fund. Your proposal follows the work you describe.
- Screening AnalystScreens inbound decks against the thesis and drafts a one-page note.
- Diligence AnalystWorks the data room against your checklist and lists the gaps.
- Memo WriterDrafts IC memos with a source for every claim, for the deal team to edit.
- Portfolio AnalystSummarizes portfolio updates for the partners' meeting.
The record
Everything lands on one record.
Every message, run, file change and approval is one event on an append-only record. It shows who did it, person or agent, what was approved and by whom.
- 09:15 · #deal-quillohuman
Maya asks Diligence Analyst to check Quillo's data room against the Series A checklist
- 09:17 · screening · data roomgate
1 file held. A PDF with hidden instructions is quarantined before the agent reads it
- 09:19 · run · Maya's MacBook Proagent
Diligence Analyst matches 64 files to the checklist. 41 of 44 found, 3 gaps
- 09:24 · threadhuman
Maya answers: use the cohorts to June, and ask for July
- 09:38 · gate · questions to foundergate
Questions parked. Sending to Quillo's CFO waits for the deal partner
- 09:40 · approvalhuman
Ben approves. The record keeps who approved, and the questions as sent
Why we passed, years later
Search the record for a company and find the memo, the IC thread and the reasons, even after the principal who ran the deal has left.
An answer for every LP question
Every decision links to the files, the debate and the approvals behind it.
Know what diligence costs
See agent spend per accepted memo and per deal, across every agent and model.
Before you trust it with a deal
Questions your partners will ask.
A fund holds founders' data under NDA. This is how Mobtasks handles it.
Where do the agents run?
On your own machines. A local worker runs each agent, and model credentials stay on that machine. They never pass through our servers.
Who can see a deal?
Only the people you give access, signed in through your SSO with two-factor codes. An agent reads as the person who asked, so a walled deal stays out of its answers.
What if a deck hides instructions?
Untrusted files are screened before an agent reads them. An injection attempt is quarantined, and the run waits until the screen finishes.
What did the agent see?
The Run Inspector shows every byte of context the platform added to a run, and lists each workspace read the run made.
What can an agent do alone?
What its permission preset allows: Supervised, Standard or Autonomous. Risky actions park until a person approves, and the record keeps the decision.
Can we audit it, and leave?
The record is append-only and sealed with your workspace's own key. Export the whole workspace at any time, or delete it.
Private beta
Run one live deal through Mobtasks.
Bring one deal in diligence and your checklist. We'll set up the team with you during the private beta.