Walk into any well-run company and you’ll find the machinery of coordination humming. Engineering has its tracker. Sales has its CRM. Documents live in a workspace someone actually curates. Ask where any piece of internal work stands, and someone can pull it up in seconds.
Now ask where the integration with your partner company stands — the one that’s supposed to ship next month. Someone forwards you an email thread. Someone else has a spreadsheet, last updated three weeks ago. The real answer lives in the memory of two people, one on each side, who have never met.
This isn’t a failure of discipline. It’s a failure of geography. Every tool your company runs was bought by your company, for your company, and its jurisdiction ends precisely at the company line. The work that crosses that line — the handoffs, the blockers, the decisions, the documents both sides need to be reading the same version of — lands in the one place that requires no permission from anyone: email. Email is where cross-company work goes because email is the last neutral territory left. It is also the worst possible system of record: no state, no ownership, no memory beyond what individuals hoard in their inboxes.
The guest-seat trap
The obvious fix has been tried thousands of times: invite the other company into your tools. Add them as guests in your Slack, your Jira, your Notion.
It fails, and it fails for a structural reason, not a usability one. In every shared board with guest seats, one company is the host and the other is the guest. The host chose the tool, configured the workflow, controls the permissions, and — crucially — keeps the data. The guest is visiting. When the project ends, or the relationship sours, or someone in IT runs a security review, the guest’s access disappears, and with it their entire record of what happened. Imagine signing a contract where only one party keeps a copy.
Guests behave accordingly. They under-invest in the host’s tool because it isn’t theirs. They keep their real notes elsewhere. They confirm things by email “just so we have it on our side.” The shared board becomes a partial mirror of the truth, and everyone is back to double bookkeeping — now with the added illusion that a system of record exists.
Neutrality isn’t a feature you can add to someone else’s tool. It’s a property of who owns the ground you’re standing on.
Neutral by construction
What the joint layer needs is a system of record owned by neither side’s toolchain. Neutrality here isn’t a tone of voice; it’s architecture, and you can check for it.
Both companies see the identical view — the same scoreboard, the same open items, the same clocks. Not a filtered “external view” of one side’s internal tool; the same screen. Obligations are symmetric: a handoff moves from Proposed to Accepted to In progress to Delivered to Confirmed, and the response clock ticks against whichever side owes the next move. A blocker names the company doing the blocking, and escalation is automatic and even-handed — the counterpart hears about it at 24 hours, the other side’s workspace lead at 48, no matter who raised it. Decisions are proposed by one company and signed off by the other, and the record is append-only: a decision can be superseded, never edited. Nobody’s admin can quietly rewrite history, because nobody is the admin of the truth.
And when the work ends — joint work always ends, which is another way it differs from internal work — both companies walk away with the same complete record: a portable export, an accountability snapshot, the open items, a written summary. Two copies of the contract. The workspace itself goes read-only, a closed record either side can revisit at no cost for as long as they need it.
Only the joint layer
There’s a discipline hiding in this design that matters as much as the neutrality: the joint layer should own only the joint layer.
Every tool wants to grow. The temptation, having built the shared space, is to pull each company’s internal work into it too. That would be a mistake, and companies would rightly refuse. Your internal standup, your team’s half-formed tasks, your candid assessment of the partner’s velocity — none of that belongs on shared ground. The right shape is a narrow one: each side keeps its own tools and its own private lane, and promotes work to the shared board deliberately, one way, when it becomes a commitment to the other company. The shared table is not the kitchen. Both companies keep their kitchens.
This narrowness is also what makes neutrality economically possible. Nobody has to rip anything out or make their partner adopt their stack. One side opens a workspace, and the invited company never pays — because if joining the neutral ground cost money, it wouldn’t be neutral ground. It would be a toll booth.
The pattern is old. When two parties who don’t fully trust each other need to transact, they don’t meet in one party’s living room. They use an escrow agent, a notary, a land registry — an institution whose entire value is that it belongs to neither of them. Software ate the inside of the company decades ago. The space between companies is still governed the way it was in 1995: by email, attachments, and someone’s memory.
That space is where the work you can least afford to lose actually happens. It deserves a home that neither side owns and both sides trust — one that knows how to close the door properly when the work is done.