ZAMBO.

Direct answer

Agreed on the call. Denied later. Here is the way out.

A phone call feels clear while you are on it. Both sides hear the same number, say the same yes, and hang up thinking the deal is done. Weeks later the invoice lands and the memory changes: that price was never agreed, or it was only an estimate, or someone else was supposed to approve it. You cannot replay the call. What you can do is rebuild what was agreed from everything both sides did next, and then close the gap so the next agreement is decided on a record before the work starts.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 25, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.

Step 1. Write down your account of the call today, while it is fresh

Before you contact the client again, write your own note of the call: the date, who was on it, the price stated, what the price covered, the start date, and the exact words of agreement as you remember them. Date the note itself. A note written the week of the dispute is weaker than one written the day of the call, but a clear note written today still beats a memory argued from in a month. This note is for you and for anyone who later has to judge the dispute. It is not the proof on its own, and you should not present it as proof. It is the spine everything else hangs on.

Step 2. Collect the trail both sides left after the call

Agreements leave footprints. Look for what happened in the days after the call: the follow up message where you restated the price, any reply that did not object, the client sending you files, logins, or a start date, the deposit request, the first deliverable they commented on as if the job was live. Each item is small. Together they answer the only question that matters: did both sides behave as if a deal at that price existed? A client who sent the materials, set the kickoff, and reviewed the first stage will have a hard time explaining that no agreement was ever made. Gather the trail in date order and keep the originals, not screenshots of screenshots.

Step 3. Send one recap message and ask for a plain answer

Now put it in one short message: on this date we spoke, the price agreed was this, covering these deliverables, and work started on this date with these items from you. Then the key sentence: if any of that is wrong, tell me which line, in writing, today. You are not asking them to confess. You are giving them one clean chance to point at a specific disagreement instead of a general denial. A reply that corrects a detail but not the price is close to a confirmation of the price. Silence after a clear recap, while the work continues to be used, also speaks. What does not help is a long argumentative thread. One recap, one request for a plain answer, then you act on whatever comes back.

Step 4. Invoice against the acted on agreement, with the trail attached

Invoice the agreed price for the work actually delivered, and attach the dated trail: your call note, the recap, and the items showing both sides acting on the deal. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show what a decided state looks like when it is kept properly:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

An accepted record, 4 of 4 steps checked, decided_by client, release_hint ok_to_release, is an agreement state nobody has to reconstruct from memory later: the decision, the decider, and the date are all on it. A pending record, 5 of 5 steps checked and release_hint hold, is the honest opposite: checked work still waiting for a decision. Your invoice packet aims at the first shape using the materials you have: the price, the dates, and the conduct that followed the call, in one place the client and anyone else can open.

Step 5. Decide what the denial is really about before you escalate

Three different problems hide inside the same sentence. Sometimes the client genuinely remembers a different number, and the trail settles it in one exchange. Sometimes the person on the call agreed beyond their authority, and the denial is their company correcting them; then your trail matters most, because you relied on their yes in good faith and started work they accepted. Sometimes the denial is a price negotiation wearing a memory costume, and it arrives only after the work is delivered and in use. Name which one you are in before choosing a tone. The first needs the recap. The second needs the packet sent to the person who can actually decide. The third needs a payment date and a firm, flat restatement, not another round of justifying the price.

Step 6. Make the next agreement a decision on a record, before work starts

The permanent fix is small: after any call where terms are agreed, the agreement goes on a record the client opens and accepts before the first hour of work. Price, scope, start date, and the name of the person accepting, in one place, decided with a date. It takes minutes and it feels almost too simple, right up until the first time a memory changes and the record simply answers. If a client will not accept the recap of what they just agreed on a call, that refusal is itself information, and it arrives before you have done the work instead of after. Believe it early and price the risk or walk away.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove what was said on a phone call, does not decide whether a verbal agreement is binding where you work, and cannot make a client honor a price. The call note, the recap, and the trail of both sides acting on the deal are what a claim stands on. This page is general information, not legal advice.

Frequently asked questions

My client agreed to the price on a phone call but now says they never agreed. How do I prove what was agreed?

You prove it from conduct, not from the call itself. Write your dated note of the call today: the price, what it covered, who was on the call, and when work was to start. Then gather the trail from the days after: your follow up restating the price, the client sending materials or a start date, the first deliverable they reviewed as if the job was live. Send one recap message listing the date, the price, and the scope, and ask them to name any line that is wrong, in writing, today. Invoice the delivered work at the agreed price with that trail attached. A client who acted on the deal for weeks has to explain the conduct away, and that is a much harder argument than denying a conversation.

Is a verbal agreement worth anything, or did I need it in writing?

In many places a spoken agreement on price and work can count, and in many places certain kinds of deals must be in writing, so the honest answer depends on where you are and what was agreed. What is true everywhere is the practical side: a spoken deal you cannot show is an argument, while a spoken deal followed by written recaps, acted on by both sides, is a record. You do not need to win the legal theory today. Send the recap, build the trail, and get the next agreement accepted in writing before work starts. For a large amount or a flat refusal, a short consultation with a local lawyer is money well spent. This page is general information, not legal advice.

What if the client says the person on the call had no authority to agree?

Then the question becomes what you reasonably relied on. If the person held themselves out as your contact, set the start, sent the materials, and accepted the early work, your trail shows a deal being run by their side, not invented by you. Send the packet to the person who can decide now, keep the tone flat, and pause further work until the price is confirmed by someone whose yes counts. Going forward, the acceptance step names the decider: the record shows who accepted, so an authority argument has to start from a named decision, not from a fog about a call.

Should I keep working while the client disputes what was agreed?

Pause new work, protect what exists. Continuing to deliver into a price dispute grows the amount at risk and weakens your position, because it tells the client the denial costs them nothing. State the pause plainly: work resumes when the price for the work so far and the next stage is confirmed in writing. Deliver nothing new, but keep every record, message, and file exactly as it stands. Most authority and memory disputes resolve quickly once the client understands the project is stopped at a dated line, with the delivered part invoiced and documented.

How do I put an agreement on a record the client actually accepts?

Close every stage, starting with the agreement itself, as a handover the client opens: the terms, the steps that ran, the saved results, and a place to accept, with the decision, the decider, and the date kept on the record. When the work runs through Zambo, every step carries a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and new users get 20 free calls per day, then they upgrade when the job needs more. For $0.99, put the next job on that footing and let the acceptance state answer the memory questions before they start: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related