What Is a Contract, Really?

On the messy human process nobody builds around, and why it's the root of everything.

Think about what system in your life works the same way in 2026 as it did in 1999. Your phone? Your car? All fundamentally transformed.

But for deals, we're using the exact same disconnected systems. Email. Spreadsheet. Approval doc. Contract. Redline. PDF. Folder.

I lived this at Religion of Sports, Delta Rae, Akin Gump, and the FTC. Entire afternoons hunting for "AGREEMENT_FINAL_v4" across email threads and Google Drives. Different industries, same tax.

Manual data entry. Version control. "Just following up." Reconstructing what was agreed to 2 weeks ago because the conversation happened across 3 different threads. And after all that coordination you've reached a signed deal, and you've accomplished nothing of what you set out to do. The entire purpose behind the deal, the work, hasn't even started yet.

AI is accelerating creation. The infrastructure hasn't moved.

Production timelines are collapsing. More content means more deals. And we're trying to do this with 1999 infrastructure: tools built for one Super Bowl ad, not one Super Bowl ad plus 300 creator deals simultaneously. We need to transact at the pace of creation.

Two and a half years building Basa. One question kept coming back: what actually is a contract?

A contract is structured data derived from a messy human process.

The deal is a process. The document is just a step in it.

Every tool in this space starts at the document. DocuSign, Ironclad, Evisort: they all receive the contract after the process that created it. If you only solve the document, you've improved one step in a process that was broken long before it got there and broken long after.

The mess starts before you even know if someone wants to work with you.

Outreach goes out: email, DMs, WhatsApp depending on the industry. Did it land in spam? Did they open it and move on? Is the creator interested or just slow? You don't know. So someone follows up. Then follows up again. The creator hasn't signed the NDA yet, which was the condition for sharing the campaign details they need to decide if they're even interested.

"Just following up" starts here. Before there's been a single substantive conversation.

Only once 2 parties have established they want to work together does the negotiation begin. Every message narrows uncertainty. The creator asks for $15k. You come back at $8k. You settle at $10k with a 30-day exclusivity window. Usage rights get debated. A kill clause gets added. 60 to 80 messages for a single creator, and that number doesn't include everything that came before it.

That negotiation is where the intelligence lives. The rate isn't just "$10k." It's $10k negotiated down from $15k, for this creator category, at this moment, where this term held and that one didn't. That context is what makes it intelligence rather than just a number.

And after the contract is signed: did they deliver? On time? What did the content actually perform? Would you work with them again and at what rate?

The full arc is outreach, interest, NDA, negotiation, contract, delivery, performance, payment. The document shows up somewhere in the middle. When you flatten all of that into a PDF, you keep the number and lose everything that makes it useful. Every deal starts from scratch. Nothing compounds.

DocuSign starts when you hand it a document: the outreach, the negotiation, all of it happened elsewhere. Ironclad manages the document through its lifecycle: redlines, approvals, storage. Evisort goes furthest, using AI to extract intelligence from contracts after the fact. But it's working backward. The context that actually matters — what was asked for, what got negotiated away, what this counterparty looks like after years of deals — was never in the document to begin with. All 3 start after the process. You can't fix that by building more sophisticated tools on top of it.

The terms stay alive.

My co-founder Ryan: every other tool in this space is document-based. The deal's intelligence — who asked for what, what got negotiated away, what the history with this counterparty looks like — that context never makes it into the document.

Basa is term-based. We capture each term as it gets negotiated, with its full context, and keep it alive through the lifecycle of the deal. The contract still gets generated. But the terms behind it stay useful.

The contract still governs. It's the legally binding record, with the full history of how you got there: every version, every signature, every step, preserved. Your legal team's templates, their language, their contracts. Sign through DocuSign, Ironclad, or whatever you use today. That doesn't change.

A contract is structured data. And structured data has to come from somewhere: from the outreach, the back-and-forth, the negotiation, the human process that precedes any document. If your tool starts after that process, you're managing the residue.

Basa works alongside DocuSign, Ironclad, and Evisort. If you're already using them, nothing changes. We connect to whatever document workflow you have today and add the layer those tools were never built for.

Legal sets parameters once. Deal teams operate within them.

Every contract has 2 types of terms belonging to 2 different teams. Business terms: rate, deliverables, scope — commercial decisions owned by the deal team. Legal terms: confidentiality, liability, indemnification — policy decisions owned by legal. Those decisions should be made once, not relitigated on every deal.

In most organizations both live in one Word doc. Which means as soon as a contract goes to legal, you're on their calendar, not yours. What in-house lawyers hate is a high volume of small deals with basic redlines they've resolved a hundred times. What deal teams hate is being blocked on legal for terms that should've been pre-decided. Both problems come from the same place: the architecture doesn't separate what belongs to each team.

Legal sets parameters once. Deal teams operate within them. The $500 creator deal doesn't need a lawyer. The $10 million partnership does. The right infrastructure knows the difference.

Your data. Your teams generated it.

Your New York team's rate negotiation with a creator in LA. Your London office's deal history across EMEA. The agency you worked with in São Paulo last quarter, negotiating on your behalf. Different cities, different offices, sometimes different agencies, all generating intelligence about your business that currently dies at the edge of whoever collected it.

A new team member inherits nothing because there's no system that carries what the last person knew.

What's the gap between initial ask and final agreed rate? Which usage rights terms show up in your best-performing campaigns? What does your full history with a counterparty look like before you start a new negotiation?

That intelligence exists. It's yours. It's just scattered across inboxes and PDFs right now.

The complexity is the human behavior underneath the technology.

Two parties with different incentives, different information, different constraints, trying to reach an agreement. The agent who goes quiet for a week is managing a client who has cold feet. The brand pushing hard on exclusivity has a competitor relationship they can't talk about yet. The creator who hasn't signed the NDA has been burned before and wants their manager to review it first.

None of that is in the document. None of it ever will be. And no technology is going to navigate it for you.

Technology can eliminate the rest: the filing, the following up, the copying between systems, the searching for what was agreed to 6 months ago. That's the infrastructure tax — the negative-value work nobody does because it produces value, but because the systems make it unavoidable. If you're spending 30 percent of your time on it, that's 30 percent you're not spending on the work that actually requires being human.

The work that actually requires being human is different. Reading between the lines. Deciding whether a rate reflects the market or reflects desperation. Building the relationship that makes the next deal easier. That work can't be automated without losing something real.

Basa doesn't have AI in the product yet. The infrastructure problem doesn't require AI to solve. It requires rethinking what a contract is, how deal data flows, and what gets captured versus what gets lost. Fix that first. Then AI has something real to work with.

Making human decisions at AI speed means giving humans back the time the infrastructure tax has been stealing, so the judgment and the relationship work get the attention they deserve.