Negotiation memory for transactional teams

Drop in the other side's markup. Vellcite reads every change, finds how your firm answered the same ask in past deals, and drafts the reply — accept, counter, or stet — with the precedent cited beside it.

Drop in their markup. Vellcite answers clause by clause.

  • 01What did we give on liability caps to logistics clients?
  • 02Show every super-cap we agreed above £5m.
  • 03Has Halden's counsel accepted a mutual indemnity before?

How a markup
becomes a reply.

/read

Their markup, sorted before you open it.

Vellcite compares the new draft against your last turn, not just against the last version someone saved. Every change is classed as substantive, commercial or cosmetic, and anything your firm has never been asked for comes first.

Twenty-eight typo fixes don't need a partner. They're accepted in one batch, and logged.

/recall

Your firm's answers, not the internet's.

For each change that matters, Vellcite searches your closed deals: the executed versions, every turn in between, and the emails that explained them. It shows how often the position held, and where it finally landed.

It reads iManage, NetDocuments and SharePoint where they already sit. Ethical walls come with them.

/reply

A reply the partner can sign.

Vellcite drafts the response markup and the issues list together. For each change it accepts, counters with the language that closed before, or stets: restores your wording and says why. Every line cites its source.

Nothing goes out until a lawyer sends it. Vellcite drafts; your team decides.

The answer is already
in last year’s deal.

Firms remember in people. The associate who ran the Ostrava closing knows what the other side dropped at 2 a.m., until she moves to another team. Vellcite keeps that memory with the documents, where the next deal can read it.

  • 01

    It cites. It doesn’t guess.

    Every suggestion links to the clause it came from: the deal, the turn, the lawyer who agreed it. Where your firm has no precedent, Vellcite says so, and leaves the clause to you.

  • 02

    Nothing leaves the matter.

    Walls and permissions carry over from your document system. A deal you can’t open is a deal Vellcite won’t quote to you. Your documents never train a shared model.

  • 03

    The playbook, checked against what happened.

    The playbook says what you’d like. The closing sets say what you got. Vellcite shows both, side by side, so the playbook can catch up.

  • 04

    A lawyer signs every word.

    Vellcite reads, recalls and drafts. It never sends, accepts or files anything on its own, and every change it proposes waits for a person.

One markup, one morning.

A Tuesday in a pilot team · times are real, names are not

  1. 09:12

    Their markup lands

    Draft 4 from opposing counsel. 64 pages, no cover note.

  2. 09:13

    Vellcite has read it

    41 changes, 6 that matter, 1 the firm has never seen.

  3. 09:40

    Associate reviews

    Keeps four suggestions, rewrites two, adds a note on §1.1.

    Sam Arden, associate

  4. 10:05

    Partner signs off

    Reads the issues list, not the whole draft. Approves.

    Dana Hale, partner

  5. 10:20

    Reply is out

    Same morning. The other side expected it on Thursday.

68%

of counterparty changes answered from the firm’s own precedent

3.4h

saved per markup turn on a mid-size commercial contract

0

replies sent without a lawyer’s approval

Questions.

What is Vellcite?

Negotiation memory for transactional lawyers. When the other side sends a markup, Vellcite reads every change, finds how your firm answered the same request in past deals, and drafts the reply with the precedent cited beside each point.

Where does the precedent come from?

From your own closed matters: executed agreements, the drafts exchanged on the way, and the emails that explained them. Vellcite connects to iManage, NetDocuments and SharePoint and reads them in place. Nothing is copied into a shared corpus.

Does it replace our playbook?

No. Vellcite reads your playbook as the firm’s stated position and your deal history as the record of what actually closed. Where the two disagree, it shows you both, which is usually the most useful thing on the page.

How are ethical walls handled?

Vellcite inherits permissions from your document system, user by user. If you can’t open a matter, Vellcite can’t cite it to you, and it can’t mention that the matter exists.

Does it train on our documents?

Your documents are indexed for your firm only and are never used to train a shared model. Data stays in the region you choose: UK, EU or US.

What happens when there’s no precedent?

Vellcite says so. The change is marked “new to us”, moved to the top of the list, and left for a lawyer, with the relevant playbook section attached if there is one.

Who is it for?

Commercial, technology and finance teams that negotiate the same kinds of agreements many times a year, in firms of 30 to 1,500 lawyers and in-house teams with a real deal archive.

How does a pilot work?

Eight weeks, one practice group, your real matters. We connect a slice of your archive in the first week, and you judge Vellcite on live markups from the second.

Let it stand.
Or know why it can’t.

Vellcite is in pilot with a small number of commercial teams in London and New York. Tell us what you negotiate most, and we’ll set one up on your own matters.