Sales
Change the terms, not the deck
Revise a renewal’s seats, term and discount with one guarded JSON Patch, then review every dependent change.
A renewal proposal changes when the customer comes back with different terms. More seats, a longer commitment, a discount: each one affects more than a single cell. Keep the proposal as an OPF file and the counter-offer as one patch, so the reviewer can see whether the totals, timeline and ask still agree.
This Renewal Proposal is from Tidewater Software to Harborline Logistics: fictional companies, example data. Every slide visibly labels its figures as example data: the title slide says it in the subtitle, and slides 2–7 include “Example data” in their titles. The final slide also says “All numbers are example data”. This is a negotiation over the same renewal, rather than a new prospect’s version of a pitch.
Start with the proposal
The commands use the published opf CLI from @openpresentation/cli 0.27.0, the version installed by the video pipeline. To run them without a global install, use npx @openpresentation/cli@0.27.0 in place of opf:
opf create deck.opf.json --title "Tidewater Software: Renewal Proposal for Harborline Logistics"Slide 1 introduces the proposal and adds the subtitle “Fictional companies, example data”. The recording grows that starter with one JSON Patch per slide, applied with opf edit -i. For example, this command adds the terms slide:
opf edit deck.opf.json -i --patch patches/04-terms.jsonRecap the year, then show usage
Slide 2 gives three example outcomes: on-time dispatch rose from 90% to 96% (six percentage points), operations saved 240 hours over the year, and support tickets fell from 200 to 150 (25%). These are illustrative figures, not customer results.
Slide 3 shows active seats by quarter. The bar chart keeps its labels and values in rows, so the export can draw the chart from data:
{
"id": "active-seats",
"title": "Active seats by quarter (Example data)",
"tag": "Example data",
"chart": {
"type": "bar",
"data": {
"columns": [
"Quarter",
"Active seats"
],
"rows": [
[
"Q1",
80
],
[
"Q2",
95
],
[
"Q3",
110
],
[
"Q4",
120
]
]
},
"dataLabels": true,
"alt": "Example data: active seats Q1 80, Q2 95, Q3 110, Q4 120."
}
}Loading preview…
The Q4 value is 120 active seats. That is past usage; it stays at 120 when the proposal later changes to 150 seats.
Keep the annual terms together
Slide 4 is a table of the original renewal terms. The term line says one year, billed annually. Multiplying 120 seats by $300 per seat per year gives a $36,000 annual subtotal. The multi-year discount is 0%, or $0, leaving an annual total of $36,000:
{
"id": "renewal-terms",
"title": "Renewal terms (Example data)",
"subtitle": "1-year term, billed annually",
"tag": "Example data",
"table": {
"columns": [
"Line item",
"Annual terms"
],
"rows": [
[
"Seats",
"120"
],
[
"Price per seat per year",
"$300"
],
[
"Annual subtotal",
"$36,000"
],
[
"Multi-year discount",
"0% = $0"
],
[
"Annual total",
"$36,000"
]
],
"alt": "Example data: 1-year term, 120 seats at $300 per seat per year; annual subtotal $36,000, multi-year discount 0% = $0, annual total $36,000."
}
}Slide 5 lists what’s included: a dispatch planning workspace, operations reporting and exports, role-based access controls, and customer success and support. There are no additional quantities or prices to reconcile there.
Slide 6 lays out the timeline: sign by Dec 15, start the renewal on Jan 1, and onboard new seats during January. Its signing detail repeats the seat count and term. Slide 7 asks for approval of 120 seats on a one-year term at $36,000 annually, a signer and billing contact, and the signed proposal by Dec 15.
With all seven slides in place, format and validate the deck:
opf format -i deck.opf.json
opf validate deck.opf.json --fail-on warning --format textdeck.opf.json: 0 findings (0 errors, 0 warnings, 0 info). Checked: syntax, schema, references, accessibility, content, layout (estimated).The counter-ask is one guarded patch
Harborline asks for 150 seats on a two-year term with a 10% multi-year discount. The unit price stays at $300 per seat per year: 150 × $300 = $45,000, with a $4,500 annual discount and a $40,500 annual total. The table continues to show annual amounts.
The patch begins by testing that the old seat count is still “120”. It updates the terms, the table’s alt text, the signing detail on slide 6 and the approval ask on slide 7:
[
{
"op": "test",
"path": "/slides/3/table/rows/0/1",
"value": "120"
},
{
"op": "replace",
"path": "/slides/3/subtitle",
"value": "2-year term, billed annually"
},
{
"op": "replace",
"path": "/slides/3/table/rows/0/1",
"value": "150"
},
{
"op": "replace",
"path": "/slides/3/table/rows/2/1",
"value": "$45,000"
},
{
"op": "replace",
"path": "/slides/3/table/rows/3/1",
"value": "10% = $4,500"
},
{
"op": "replace",
"path": "/slides/3/table/rows/4/1",
"value": "$40,500"
},
{
"op": "replace",
"path": "/slides/3/table/alt",
"value": "Example data: 2-year term, 150 seats at $300 per seat per year; annual subtotal $45,000, multi-year discount 10% = $4,500, annual total $40,500."
},
{
"op": "replace",
"path": "/slides/5/timeline/0/description",
"value": "Confirm 150 seats on a 2-year term."
},
{
"op": "replace",
"path": "/slides/6/bullets/0",
"value": "Approve 150 seats on a 2-year term at $40,500 annually."
}
]This snippet is a JSON Patch (RFC 6902); the JSON Patch guide explains the operations and the guard that stops an edit when the starting value has changed.
Save it as counter-ask.patch.json, then write the revised deck and review the diff:
opf edit deck.opf.json deck-variant.opf.json --patch counter-ask.patch.json
opf diff deck.opf.json deck-variant.opf.json --format text8 changes (slides: 3 modified)
…
~ slide #4 "Renewal terms (Example data)" (id renewal-terms)
~ subtitle "1-year term, billed annually" -> "2-year term, billed annually"
~ table.rows[0][1] "120" -> "150"
~ table.rows[2][1] "$36,000" -> "$45,000"
~ table.rows[3][1] "0% = $0" -> "10% = $4,500"
~ table.rows[4][1] "$36,000" -> "$40,500"
~ table.alt "Example data: 1-year term, 120 seats at $300 per seat per y…" -> "Example data: 2-year term, 150 seats at $300 per seat per y…"
~ slide #6 "Renewal timeline (Example data)" (id renewal-timeline)
~ timeline[0].description "Confirm 120 seats on a 1-year term." -> "Confirm 150 seats on a 2-year term."
~ slide #7 "Next steps (Example data)" (id next-steps)
~ bullets[0] "Approve 120 seats on a 1-year term at $36,000 annually." -> "Approve 150 seats on a 2-year term at $40,500 annually."That is the real diff shown in the recorded session: eight changes across three slides. The standalone ellipsis marks lines the recording leaves out. The test operation changes nothing, so it adds no diff entry. The dates, the included features and the year-one figures stay as they were. Both the visible terms and the table’s alternative text now describe the same counter-offer.
Validate the revision, then export it
opf validate deck.opf.json deck-variant.opf.json --fail-on warning --format textdeck.opf.json: 0 findings (0 errors, 0 warnings, 0 info). Checked: syntax, schema, references, accessibility, content, layout (estimated).
deck-variant.opf.json: 0 findings (0 errors, 0 warnings, 0 info). Checked: syntax, schema, references, accessibility, content, layout (estimated).opf convert deck-variant.opf.json deck-variant.pptxEvery command shown here exited 0 in the recorded session. No command needed to be omitted for lack of support. The customer can receive the editable PowerPoint while the OPF source and patch preserve the proposal and its revision.
Why it matters: the counter-offer has one reviewable change set. A reviewer can check the annual arithmetic alongside the text that repeats it, and the starting-value guard prevents applying the same patch after the seat count has already changed.
CLI reference · One sales pitch, every prospect
Download the deck and the renewal counter-ask patch. All companies and numbers are fictional examples.