Meet Jordan. The AI Deal VP inside every mandate.
Jordan is not a chatbot and not a product sold to the client. It is the proprietary intelligence engine developed by Mainhattan Labs UG (haftungsbeschränkt) and used inside AILPA mandates: mandate state, buyer rationale, evidence, meeting packs, approvals, follow-up, and escalation, all handed to a senior advisor for judgment.
Today
Advisor control room
Morning brief
Buyer movement, open risks, stale approvals
Meeting pack
Questions, posture, source-backed talking points
Diligence queue
Four answers ready, one needs judgment
Memory update
Buyer objections captured for future mandates
A live mandate memory, not a chat thread.
Mandate state
Phase, documents, blockers, approvals, buyers, materials, risks, and open decisions in one governed memory.
Evidence ledger
What is known, what is missing, what is assumed, and which claims are ready to leave the firm.
Operating rhythm
Morning briefs, stale-item sweeps, meeting prep, post-call follow-up, and decision queues.
Buyer intelligence
Longlist, shortlist, rationale, exclusions, conflicts, engagement, and lessons from prior behavior.
Advisor drafts
Emails, follow-ups, meeting notes, seller updates, questions, and recommendations ready for review.
Approval boundary
No send, release, self-approval, negotiation, or valuation call without human authority.
The operating rhythm before, during, and after every important conversation.
Most of the value is quiet: noticing what changed, preparing the next room, turning conversation into structured work, and making the few human decisions easier to make.
Before the day starts
Jordan prepares the mandate brief.
Evidence readiness, approval queues, buyer movement, materials progress, open tasks, risks, and decisions waiting for an advisor are summarized before the day starts.
Before a meeting
Jordan prepares the room.
Attendee context, open issues, recent decisions, source-backed talking points, likely objections, and the questions an advisor should ask are assembled in one brief.
During and after
Conversation becomes structured memory.
Where configured and disclosed, notes or transcripts become decisions, tasks, risks, follow-ups, and facts for advisor review.
When work is needed
Jordan routes the work to departments.
Evidence, financials, buyer intelligence, communications, materials, and QA return typed work with sources, limits, and a recommended next action.
When judgment is needed
Jordan escalates instead of pretending.
Missing evidence, disclosure risk, valuation-sensitive points, conflicts, and external actions are surfaced to the advisor with a clear recommendation.
The output is a controlled deal room, not a stream of prompts.
- Q3 revenue bridge, by segmentAnswered
- Customer concentration analysisAnswered
- Working capital normalisationAnswered
- Key employee contracts, summarisedDrafting
- IP assignment, one gap to confirmNeeds you
- 02:14Screened 1,240 new companies across 6 markets
- 03:40Found 3 new strategic buyers, added to the shortlist
- 04:55Refreshed the valuation with today's comparables
- 06:10Drafted answers to 9 diligence questions for your review
- 07:30Left a one page summary at the top of your inbox
Jordan coordinates work. It does not pretend to do everything itself.
Work moves through bounded departments, narrow tools, source requirements, QA, and approval gates.
Human advisor
Trust, strategy, negotiation, approval
Jordan
AI Deal VP
Carries the mandate state, prepares the room, routes work, drafts follow-ups, and escalates what needs judgment.
Evidence & Diligence
Separates what is known from what is assumed.
Financial Analysis
Makes material numbers traceable to a source.
Buyer Intelligence
Builds the buyer universe with a reason for each name.
Communications
Drafts the firm voice for advisor approval.
Materials
Turns evidence into inspection-ready work product.
QA / Risk
Challenges claims before they leave the firm.
Every useful answer carries its proof.
The output is only useful if an advisor can inspect it. Jordan's work is expected to show sources, assumptions, gaps, and the decision it wants a human to make.
Evidence
Claim tied to a source document.
Analysis
Number checked against the workbook.
Material
The point enters the buyer story.
Approval
Advisor approves before release.
Jordan proposes. A human advisor decides.
Does not negotiate
Jordan may prepare positions, but it does not negotiate with buyers, sellers, lenders, or advisors.
Does not send externally
Drafts and recommendations require human approval before release.
Does not approve itself
Materials, buyer movement, valuation-sensitive language, and releases remain approval-gated.
Does not set valuation strategy
It can analyze, compare, and highlight questions. A human advisor owns the judgment.
Does not become a partner
Jordan is proprietary infrastructure, not a separate legal entity or public partner of the firm.
Does not generalize confidential facts
Mandate-specific confidential information stays inside the mandate boundary.
The fastest way to understand Jordan is to put it against a real mandate.
We can talk through how Jordan would prepare the evidence, buyer universe, meeting rhythm, and approval path around your company or advisory process, within the mandate terms and confidentiality controls agreed for that situation.