My last post here was about what happens when one side of a skill swap delivers and the other side says it is not good enough. A few days later, in a thread under someone else's article about contract clauses for freelancers, the same problem showed up from the opposite direction. A commenter replied to me that pre alignment before writing a single line of code is the real fix for scope creep, and that pointing at what was agreed beats arguing in the middle of the work, every time.
I agreed, and I still do. But writing that reply made me notice something I had been skating past in my own product. The lock is not the hard part. The reviews are not the hard part. The hard part is getting two people to write the agreement down at the one moment when writing it down feels unnecessary, which is the beginning, when both sides are still friendly and neither of them wants to sound like they are preparing for a fight.
✍️ Why friendly beginnings resist writing things down
At the start of a swap, everything is warm. Someone loves your portfolio. You love their idea. The chat is full of exclamation marks. Suggesting deliverables, a deadline, and a revision count in that moment can feel like bringing a contract to a first coffee. It reads as distrust, even when it is really just clarity.
I recognise the feeling because I have been on both sides of it. As the person asking, I worry the other side will think I am difficult. As the person being asked, I catch myself thinking, do they not trust me? So both sides quietly skip it, each assuming the other is picturing the same job. That assumption is where scope creep is born. Not from bad people. From two friendly people carrying two slightly different versions of the same deal.
📝 What the Condition Card actually asks
In worXwap, the agreement step is called the Condition Card. It is not a legal document and it does not pretend to be. It asks four plain things before any work starts: what will be delivered, by when, how many revisions are included, and a short written brief of what is being asked for. The deadline is picked from 1 to 30 days. Revisions run from none to five. That is the whole form.
The point of keeping it small is that it has to survive the friendly beginning. A ten page contract would scare off exactly the moment it is meant to protect. Four fields can be filled in while the conversation is still warm, and filling them in together is itself a small test. If two people cannot agree on what the job is before it starts, that is useful information, delivered at the cheapest possible time.
🔄 The agreement goes back and forth, on purpose
One detail I changed my mind about while building this: the agreement is not written by one side and signed by the other. It bounces.
Here is the flow. One person sends a swap request. The other person receives it and writes the description of the deal, and they can adjust the details before submitting it. The first person then accepts it with a button, or edits it and sends it back. An edited deal has to be accepted by the other side again. The swap only starts when someone accepts a version without editing it.
So the final text is never one person's version imposed on the other. It is the version both people let pass. When a disagreement shows up later, neither side is pointing at their own notes. They are pointing at a text they both watched take shape.
🪞 The honest limit
Here is what a written agreement cannot do. It cannot make the work good. It cannot make two people read a sentence the same way, and it definitely cannot make someone deliver. If one side vanishes, the card just sits there, agreed and useless.
What it does is narrower and, I think, more valuable. It gives both sides the same text to point at. Most mid work arguments I have seen were not really arguments about the work. They were arguments about which memory of the beginning was the true one. A shared text ends that argument before it starts, and what is left is the real disagreement, the one about the work itself, which is at least a disagreement worth having.
An honest note, same as last time. worXwap is still tiny. Most of the people on it arrived because they were personally asked to try it, and plenty of them rarely open the app. The Condition Card has been argued about in threads like the one above far more than it has been stress tested by real swaps at scale. I would rather tell you that than pretend otherwise.
So let me ask the flip side of last time's question. When you start working with someone new, what do you actually write down, and how do you bring it up without making the beginning feel like a warning?
