Building an agent-native deal workspace inside Matrix

Part of the Matrix company OS series.

Corporate finance work is a useful test for a company operating system because every engagement crosses the same difficult boundaries.

There is structured deal data, but the work does not fit neatly into a generic CRM. There are sensitive documents in OneDrive. Client and investor communication runs through email. Every mandate follows a recognizable process, but each has different counterparties, deadlines, documents, and judgment calls. Colleagues need a shared view without losing individual ownership.

The usual answer is a collection of spreadsheets, folders, inboxes, and templates. AI gets added one task at a time, while the coordination layer remains manual.

An agent-native deal workspace would make the deal—not the spreadsheet row or chat session—the durable unit of work.

This post is a product blueprint informed by customer discovery. It describes where Matrix can go; it does not claim that all of these enterprise features are available today.

Start with a deal object, not a generic contact database

A heavy CRM is often designed around sales activity. A corporate finance team needs a lighter operational record around the mandate itself.

The core record might include:

• mandate type and stage,
• client entity and key contacts,
• internal owner and working team,
• counterparties or investor universe,
• milestones and next decisions,
• connected OneDrive folder,
• relevant email threads,
• KYC status and exceptions,
• document set and latest approved versions,
• activity and approval history.

Structured fields make the pipeline filterable. The workspace around those fields carries the actual work.

That distinction matters. Replacing Excel with another grid does not solve the problem. The product becomes useful when a stage change can create tasks, attach the right template, wake an agent, or ask an owner for missing information.

Create every mandate from a template

A project template should be executable company knowledge.

It can define:

• default stages and milestones,
• folder structure,
• required documents,
• KYC checklist,
• recurring tasks,
• document templates,
• agent skills and instructions,
• approval rules,
• reporting cadence,
• naming conventions.

When a new mandate opens, Matrix creates the workspace, plan, roles, and source connections from that template. The team starts with the firm's operating method rather than a blank project.

Templates must also be versioned. An active deal should record which version created it, while administrators can decide whether later policy changes must propagate to existing workspaces.

Keep OneDrive authoritative

For a Microsoft-centered firm, OneDrive and SharePoint should remain the document system of record.

Matrix can connect a selected deal folder, track changes through Microsoft Graph, index supported content for authorized retrieval, and materialize files when an agent needs to work with them. The technical design is explored in turning OneDrive and Google Drive into agent working memory.

The workspace should always point back to the authoritative file and version. Generated work begins as a Matrix draft. After review, Matrix writes it to an approved destination and records the resulting OneDrive item and version.

That keeps the integration legible:

• source files stay where company policy expects them,
• agents receive only workspace-scoped context,
• reviewers know which versions were used,
• approved outputs return to the company folder,
• permissions remain tied to Microsoft identity.

Turn email into project activity without copying the whole inbox

Email automation should be owner-aware and thread-specific.

A user can connect Outlook with delegated access and associate selected threads, contacts, or mailbox folders with a deal. Microsoft Graph supports message change notifications and the creation of drafts as well as sending mail. A cautious first workflow should stop at a draft.

For example:

1. A relevant inbound message is detected.
2. Matrix links it to a deal using explicit rules and known participants.
3. The workflow updates the activity timeline.
4. An agent identifies promised actions or missing responses.
5. The relationship owner receives a proposed follow-up.
6. Approval creates an Outlook draft.
7. Sending remains the employee's action until policy allows otherwise.

The system should not indiscriminately scrape every employee mailbox into a common index. Access follows the employee, the workspace includes selected context, and any broader company mailbox automation requires administrative consent and clear policy.

Make document automation evidence-driven

Many professional-services documents are highly reusable without being fully generic.

A robust document workflow separates:

• fixed company language,
• approved template structure,
• structured deal data,
• sourced facts,
• calculated values,
• agent-generated narrative,
• reviewer edits.

Every generated section should know which category it belongs to. Fixed legal language should not be casually rewritten. Facts should link to source records. Calculations should preserve inputs. Narrative can be drafted by an agent but remains visibly generated until reviewed.

This allows high automation without pretending that the final document is low-risk. The useful target is not “AI writes 85%.” It is “the system assembles the repeatable 85%, exposes the variable 15%, and routes both through the right review.”

Treat KYC as a controlled workflow, not an autonomous verdict

KYC is an attractive automation target because it involves repetitive collection, classification, extraction, and follow-up. It is also a poor place for vague claims.

The Financial Action Task Force recommendations cover customer due diligence and record keeping, but concrete obligations depend on jurisdiction, institution, transaction, and professional advice. Matrix can support operations around the process without declaring that a customer is compliant.

A bounded workflow can:

• detect new documents in an approved folder,
• classify document types,
• extract selected fields with confidence indicators,
• compare the set against a configured checklist,
• flag expired, duplicate, unreadable, or missing material,
• propose a follow-up request,
• organize reviewed files into the expected structure,
• preserve source, reviewer, and action history.

A designated person remains responsible for deciding whether the evidence is sufficient and what regulatory action follows.

GDPR principles reinforce the need for purpose limitation and data minimization: personal data should be collected for specific purposes and limited to what is necessary. In product terms, a KYC agent should not gain open-ended access to every identity document the company has ever received.

Give colleagues one operational view

The workspace home should answer four questions:

1. Where is this deal now?
2. What changed recently?
3. What is blocked or at risk?
4. What needs a person's decision?

A useful view could include:

This is where the shared workspace model becomes concrete. A partner can review status without reading every thread. An associate can see the exact exception to resolve. A new team member can enter an active mandate without reconstructing it from inbox history.

The agents are attached to responsibilities

Instead of one universal deal bot, the workspace can assign specialized agents:

• Intake agent: checks that the workspace and folder structure are complete.
• KYC operations agent: classifies evidence and maintains the checklist.
• Document agent: assembles drafts from approved templates and sources.
• Follow-up agent: prepares owner-reviewed email drafts.
• Reporting agent: produces a periodic status report.
• Coordinator agent: monitors the plan and surfaces exceptions.

Each agent receives different sources, tools, and action policy. Specialization makes permissions and evaluation clearer than giving one agent access to everything.

A practical first release

The first release should prove one mandate workflow end to end:

1. Create a deal from a template.
2. Connect one OneDrive folder.
3. Import or enter the lightweight deal record.
4. Generate the project plan and checklist.
5. Track document changes.
6. Draft one recurring report.
7. Route it to an owner for review.
8. Store the approved version and complete activity history.

Email follow-ups and KYC classification can follow once the permission, review, and audit model works reliably.

This is how we think Matrix grows from a cloud computer for agents into a company OS built on existing tools: one complete, accountable workspace at a time.

The opportunity extends beyond M&A. Legal matters, consulting engagements, recruiting searches, audits, and complex sales processes share the same shape: a structured record surrounded by files, communication, plans, judgment, and repeated work.

The deeper implementation paths are a lightweight agent-native CRM, safe email follow-up agents, evidence-driven document automation, and AI-assisted KYC operations.