Meera ran operations for a small company that sold handmade stationery online, and in the spring she took a call that she believed had settled everything. The vendor, a freelance developer her colleague had found, agreed to rebuild the checkout page, connect it to the courier’s tracking and finish before the festival-season rush. She hung up pleased. Six weeks later the team discovered that “finish” meant something different to each side, and the lesson they took from it is the subject of this case study: put the agreement in writing the same day, in a few plain lines.
The call that felt complete
The conversation had been warm and efficient. The developer said the work would take “a few weeks”. Meera said that sounded right. He mentioned that the courier integration might need “a bit of extra effort” depending on the courier’s interface, and she said they would deal with it when they got there. Both of them used the word “launch” several times. Neither defined it.
Afterwards Meera told her team the checkout would be live by the first week of October. The developer, as it later emerged, had been thinking of a version ready for testing by then, with launch to follow after the team’s review. Two reasonable people, one phrase, two timelines. In the company’s weekly notes, the only record was a line reading “checkout rebuild: vendor confirmed, October”.
Where the drift showed up
By mid-September the team started asking about progress, and the answers did not match their expectations. The developer sent a preview link and said the remaining items were “minor”. Meera’s colleague Arjun, who handled customer messages, saw that the tracking links were not yet connected and asked when they would be. The developer replied that the integration had been described as possibly needing extra effort, and that it would be billed separately.
Nobody in the exchange was dishonest. Each could point to something said on the call that supported their view, and each remembered the call a little differently. The company lost nearly a week arguing about who had promised what, and the argument itself did more damage than the delay, because it turned a working relationship into a contest of recollections. Arjun said later that he spent more energy trying to reconstruct a phone call than he would have spent writing a four-line message.
What the team changed
After the project was rescued, with a revised plan both sides accepted, Meera sat down with Arjun and a colleague from accounts to work out a small habit. They called it the recap note, and the rules fit on a sticky note.
- Send it within a few hours of any call that settles scope, cost basis, dates or responsibilities.
- Write three things: the deal as both sides understood it, the date each step is due, and the fallback if anything shifts.
- End with an invitation to correct: “Tell me if I have this wrong.”
- Save the thread under the project name so that anyone can find it later.
The first test came a month later, when the same developer was asked to adjust the product pages. This time Meera finished the call and wrote: “Thanks for today. As agreed, you will update the product page layout and deliver a test version for our review. We will give feedback within the window we discussed, and if the courier changes its interface, any extra work will be quoted before you start.” The developer replied within the hour with one correction: he wanted feedback to be consolidated into a single message, not scattered across several. Meera agreed, and the correction went into the thread.
Why a short recap beats a long contract for small jobs
Meera’s team did not abandon formal paperwork. For larger commitments, they still use proper documents prepared with advice. The recap note fills a different gap: the many mid-sized arrangements that are too small for a formal agreement and too important to leave to memory. Three features make the short form effective.
- Speed. A note sent the same day captures the call while recollections still agree. A formal document drafted a fortnight later tends to capture a negotiation, not a conversation.
- Tone. A friendly recap does not feel adversarial. A heavy document can make a small vendor wary and slow the work down.
- Correctability. Because it ends with an invitation to fix errors, a recap converts a possible dispute into a thirty-second reply.
The team also noticed a side benefit that surprised them. Writing the note forced Meera to notice vagueness in her own head. Twice she started a recap, realised she could not say what “done” meant, and rang the vendor back to ask before sending. That was a better moment to discover the gap than six weeks later.
Lines worth including in a recap
Over the following quarter the team refined what a useful recap carries. Keep it conversational, but cover whichever of these applied to the call:
- The deliverable in one sentence, written the way a stranger would understand it.
- The basis for pricing, such as fixed amount or time-based, and what falls outside it.
- The date by which each side owes the other something.
- What counts as finished, for example “ready for our review” versus “live for customers”.
- What happens if a date or condition changes, and who tells whom.
These lines are arrangements, not advice about law or accounts, and the team was careful to keep them that way. If a question touched on contract wording or on how an expense should be treated in the books, they took it to a professional. For the bookkeeping side, Meera’s company eventually used a directory of chartered accountants that can be searched by city, speciality and whether consultations are held remotely or face to face to start looking for someone suitable, and she sent the shortlisted firms a recap of the first call too.
How the habit connected to their wider planning
The change did not stay confined to vendor work. When the team revisited its plans for the year, they found the same pattern in internal discussions: decisions made in meetings and remembered differently afterwards. The planning ideas in a piece on mapping out digital growth step by step fit naturally with the recap habit, since any plan is only as useful as the agreements underneath it. Similarly, the thinking in a guide to picking suitable technology for a business reminded them that tools do not remove ambiguity; people do, by saying plainly what they expect.
Arjun began sending recaps after calls with courier staff and packaging suppliers. Within a season, the team reported fewer awkward conversations that started with “I thought we said”. They did not eliminate disagreement, and they would not claim to have, but the disagreements became about real differences in needs, not about whose memory was better.
What to take from the story
A few lessons carry beyond one stationery company.
- Words like “launch”, “done”, “soon” and “a few weeks” mean different things to different people. A written line pins them down.
- The cheapest moment to resolve ambiguity is the afternoon of the call.
- Invite correction. The reply you get is the agreement; your note is only the draft.
- Match the weight of the paperwork to the weight of the commitment, and do not skip the light form just because a heavy one exists.
The sticky note is still stuck to Meera’s monitor, curling at one corner. It carries three words: deal, date, fallback. Her team sends the note almost without thinking, and the October disaster has become a short story they tell new hires, usually just before handing them the call-recap snippet and asking them to try it after their first vendor conversation.
