Memorandum of Understanding

Once two companies decide to try something together, getting to a signed contract normally takes months. Legal review runs, the commission split gets argued over, and each side has to clear budget approval internally.

The trouble was that during those months no document existed. Two people exchange emails saying they're excited to move forward, then walk back into their own companies where those emails carry no weight at all. Asking to pull two engineers off other work for three months, with nothing to point at but a counterpart's email, rarely gets approved.

Staff changes make it plainer. Six months of discussion living only in one person's head starts over from zero when that person leaves, because the successor has no record of what was already settled and no way to tell which parts are still open. More partnerships dissolve this way than are ever signed.

A memorandum of understanding (MOU) exists to fill that gap. It's light enough that legal review takes weeks rather than months, and it still leaves a document to hold up internally when asking for budget and people. Nothing about it commits either company to spend money. The near-absence of binding force isn't a weakness here — it's exactly why the document can be produced quickly.

What belongs and what is deliberately left out are both fairly settled. There are usually five blocks.

1. Purpose — two or three sentences on why the two companies are joining up. Something at the level of "improve customers' document workflow by connecting both products."
2. Scope — a list of what will be done together. This is where you separate joint marketing from technical integration from introducing each other's products to your customers.
3. Roles — who takes what, stated at the company level. Headcount and time commitments are rarely spelled out.
4. Term and renewal — typically one year, auto-extending absent objection. Leave an MOU open-ended and you end up with a live commitment nobody remembers making.
5. What is binding — naming which clauses carry legal force and which don't. This block is the one most often omitted, and omitting it plants the dispute.

What usually stays binding under block five is two things. One is confidentiality, and if a non-disclosure agreement (NDA) was signed earlier, this is just a line pointing at that document. The other is the clause naming which jurisdiction's law governs a dispute.

What stays out is equally clear. Amounts, commission rates, firm delivery dates, and penalties do not go in. The moment they do, legal review becomes as heavy as it would be for the real contract, and the whole point of producing a fast document has been lost. Those terms belong to contracting practice and get handled at the next stage.

Many companies add one more line: the date by which drafts of the real contract will be exchanged. Without it, MOUs get signed and the contract never follows, which happens more often than anyone plans for. The line costs nothing to write and gives both sides a date to point at when the discussion goes quiet.

The side that proposed the partnership usually drafts it — a business development lead or the founder writes, and legal reviews. At Pagedeck's size there's no in-house counsel, so it goes to outside advice, where the shorter clause list makes both the cost and the turnaround far smaller than for a full contract.

Readers split three ways.

The other company's legal team reads the binding clauses and little else. Their job is to establish what this document forces their company to do, and once they see that the answer is almost nothing, they move on quickly.

Executives on both sides read scope and roles, checking that what's written matches where each company is headed. This is also where an MOU quietly gets narrowed — a scope written broadly enough to cover four kinds of cooperation tends to come back with three of them struck out.

The person who actually uses the document most is the operator who has to ask for budget and people. They carry it in and say the partner company has agreed to this, so a developer is needed this quarter. Which is why roles written too vaguely produce a document that is useless where it matters most.

"Let's sign the MOU now and do the contract after legal review."

The direction is agreed; the terms can be negotiated later.

"Keep that out of the MOU. Put it in and review takes two months."

Adding money or penalties changes what kind of document this is.

"We signed an MOU and then never heard from them again."

Nothing binding was created, so no obligation followed.

That was the situation when Pagedeck agreed to become an integration partner with an accounting software company, connecting the two products. Both founders agreed on direction, but the revenue split stalled for two months because each side calculated it differently.

Grace chose to sign the MOU first. It carried purpose, scope, and roles with the money left blank, plus a line committing both sides to exchange contract drafts within eight weeks. On the strength of that document Theo started the integration work, and the commission negotiation ran separately across those eight weeks. Without the MOU, engineering would have sat still until the split was settled, and the two months already lost would have become five.

The most common mistake is reading an MOU as a kind of contract. Signatures appear, company seals go on, so it looks like one. But most of its clauses carry no legal force, so if the other side does nothing the next day, there is almost no basis for a claim. Mistaking it for a contract causes two failures at once: teams commit people and schedules against it and absorb the cost alone when the partner walks, or they try to pack every term into it and spend as long as a real contract would have taken.

The other mistake is treating the signing itself as the achievement. There's a photo and a press release, so something appears to have happened. What's actually worth checking is whether contract drafts moved within three months and whether anyone on either side was staffed to the work. Start counting signed MOUs as a result and the team drifts toward partners who are easy to sign, and a year later none of them has produced revenue.