Skip to main content
Every piece of work in Plomo lives inside a deal. When you start a new M&A engagement, you create a deal, and from that moment everything related to that target company — its documents, its classification taxonomy, your Copilot conversations, and your CIM draft — is organised and isolated within that single workspace. Nothing leaks between deals, and only the collaborators you invite can see its contents.

​
What’s inside a deal

A deal is more than a folder. It’s a structured workspace that ties together every stage of due diligence, from the first information request to the final deliverable.

​
Deal lifecycle

A deal moves through three natural phases as your engagement progresses.
1

Setup

You create the deal, give it a name, and optionally paste in the target company’s website. You upload your information request (or use Plomo’s standard sell-side template), and Plomo extracts the deal taxonomy automatically. Invite your collaborators before documents start flowing in.
2

Active

Documents are being uploaded — either directly by your team or by the target company via a share link. Plomo classifies each file against the taxonomy in real time and updates coverage as items are matched. You can open Copilot at any point to ask questions about the documents received so far.
3

Review

The bulk of the document set has arrived. You review classifications, resolve any items that need manual attention, chase outstanding coverage gaps, and begin drafting the CIM. The deal remains fully searchable throughout this phase.

​
Deal isolation

Plomo is designed so that deals never bleed into one another. Each deal has its own:
  • Document storage — files uploaded to one deal are invisible to every other deal.
  • Taxonomy — the category structure is specific to this engagement; changes you make don’t affect other deals.
  • Copilot context — when you open Copilot inside a deal, the AI can only reference documents from that deal. It will never surface content from a different engagement.
  • CIM workspace — drafts and generated sections are stored per-deal and cannot be shared across deals.

​
Access control

Each deal maintains its own membership list. You choose who to invite, and only those collaborators can open the deal, view its documents, or interact with Copilot. If someone isn’t on the list, they see nothing — not even the deal name. You can invite additional team members at any time from the deal’s Collaborators panel. To let the target company upload documents directly, generate a share link from the deal settings. Recipients who follow the link can upload files into the deal without needing a Plomo account. Their uploads are classified automatically, just like files your team uploads directly.
Use the share link when you want the target company to self-serve their document upload. You keep full control — you can revoke the link at any time from the deal settings.

​
Deal name and metadata

When you create a deal you provide:
  • Name — a label for the engagement (e.g. “Project Falcon”). This is encrypted at rest and never visible outside your collaborator group.
  • Website (optional) — the target company’s domain. Plomo stores this for company context; it does not affect taxonomy extraction or document classification.
Deals are encrypted end-to-end. Deal names, filenames, and the full content of every document are encrypted with a per-deal key managed by Plomo’s key management service. Even Plomo’s infrastructure cannot read your deal data without your session credentials.