How Midly works

From handshake to signed —
without the chaos

Eight stages. One thread. See exactly how Midly moves a deal from creation to close.

Scroll to explore
1 Stage one

A deal starts.
So does the contract.

The deal owner creates a deal in Midly — names the counterparty, sets the deal type, and adds a deal brief: agreed deviations from standard terms, who approved them, and any context the team needs. That brief travels with the contract through every stage.

Deal Owner
Deal created Counterparty linked Deal brief captured Approved deviations noted
Draft — MSA_v1.docx
AI Draft
Master Services Agreement 2s ago
1. Scope of Services. Provider shall perform the services described in each Statement of Work ("SOW") executed by the parties hereunder…

§2. Payment Terms — §3. IP Ownership — §4. Confidentiality…
Generating clause 14 of 20…
2 Stage two

Company template or
counterparty paper. Your call.

The deal owner picks from company-approved templates already configured by the admin — NDA, MSA, SOW, Order Form. Or uploads the counterparty's paper to work from their draft. Either way, the contract is in the editor in seconds.

Deal Owner
Admin-configured templates Or upload their paper In editor instantly
3 Stage three

Insights that
know your deal.

Midly surfaces role-based insights — commercial flags for deal owners, legal risk for reviewers, portfolio exposure for admins. And it reads your deal brief. If a flagged clause matches an approved deviation, Midly tells you — so you're not chasing false alarms.

Deal Owner Reviewer Admin
Deal owner: commercial flags Reviewer: legal risk Admin: portfolio view Brief-aware — approved deviations acknowledged
Legal Finance Ops
Hey — got the contract. Taking a look now.
10:02 AM
Great. Section 4 is the one to focus on — we built in some flexibility on payment schedule.
10:04 AM
Noted. Our legal team flagged §8.2 — indemnification scope. Can we cap that?
10:11 AM
Sure — I'll send a redline.
10:13 AM
4 Stage four

Address it yourself.
Or escalate it.

The deal owner works through flagged areas — pushing back on terms, proposing edits, leaving internal comments for the team. Comment threads keep discussion organized and in context. Anything that needs legal review gets escalated with one click.

Deal Owner Reviewer
Address commercial flags Escalate to reviewer Threaded comments Internal + counterparty
5 Stage five

Context travels with
every escalation.

When the deal owner escalates an item to a reviewer, the deal brief goes with it — approved deviations, who signed off, and the full comment thread. The reviewer always knows what was agreed before the contract was drafted, not after.

Deal Owner Reviewer
Brief attached to escalation Comment threads included No lost context Reviewer sees the full picture
Clause Analysis
High Risk
§8.2 Indemnification — uncapped liability
Review
§12 Governing Law — conflicts with HQ state
Note
§5 IP assignment — broader than standard
OK
§4 Payment Terms — within playbook
Suggested redline: "…provided, however, that each party's indemnification obligations shall not exceed the total fees paid or payable under this Agreement in the 12-month period preceding the claim."
6 Stage six

The reviewer sees
exactly what needs them.

When something is escalated, the reviewer is notified. They see only the flagged items — not the full deal history. They review inline, mark items resolved, and return it to the deal owner. No email. No version confusion. Full audit trail.

Reviewer
Escalated items only Inline feedback Returned to deal owner Audit trail
7 Stage seven

Send it out.
Get it back cleaner.

The deal owner sends the contract to the counterparty via a secure Midly link — no email attachments. The counterparty approves, requests changes with redlines, or declines. All feedback lands back in the same deal thread.

Deal Owner Counterparty
Secure review link Approve / redline / decline Feedback in-thread No attachments
Signature Status
Sarah Chen · VP Sales ✓ Signed 2:14 PM
Marcus Reid · CFO ✓ Signed 2:31 PM
Jordan Blake · Counterparty ✓ Signed 3:07 PM
Fully Executed · Mar 14, 2026
Renewal
Mar 14, 2027
Contract value
$240,000
Repository
Executed
MSA — Acme Corp Mar 14, 2026
ESIGN
2 of 2 parties signed
Renewal alert
Mar 14, 2027
Contract value
$240,000
Stored · Indexed · Monitored
8 Stage eight

Close the deal while
you're closing the contract.

Terms resolved. Both parties sign with ESIGN-compliant e-signatures inside Midly. The executed contract is stored, indexed, and monitored — with expiration alerts and renewal reminders. The deal is done.

Deal Owner Counterparty
ESIGN compliant Both parties sign Auto-stored Expiration alerts
Ready to close faster?

Your next deal
closes in Midly

Stop managing contracts in email. Start closing deals like you actually have a system.

No credit card required · Free plan available · Setup in 5 minutes