OPF
← All posts

Sales

One sales pitch, every prospect

Build a pilot pitch once, then make the next prospect's version with a five-line patch.

A sales deck usually gets copied, renamed and hand-edited for every prospect. After a few rounds nobody knows which copy has the right prices. Here's the same job with one OPF source, a patch per prospect and a validator that checks both.

Video: building the pilot pitch and the next prospect's patch with the opf CLI.

The example is a pitch from Brightline Freight, a fictional regional carrier, offering a 90-day pilot to Acme Retail. Every name and figure in it is example data.

Start with one slide

These commands use the opf CLI from @openpresentation/cli 0.27.0, the version in the video. To run them without installing anything, put npx @openpresentation/cli@0.27.0 in place of opf:

sh
npx @openpresentation/cli@0.27.0 create deck.opf.json --title "Same-Day Lanes: a 90-day pilot for Acme Retail."
sh
opf create deck.opf.json --title "Same-Day Lanes: a 90-day pilot for Acme Retail."

That writes a valid deck in 242 bytes. Each later step is a small JSON Patch applied with opf edit -i: the problem, the offer, the proof, the plan, the pricing and the next steps.

sh
opf edit deck.opf.json -i --patch patches/04-chart.json

The chart is data, not a picture

The proof slide carries its numbers inside the deck, so a reviewer can read them in a pull request and an export can turn them into a native chart:

json
{
  "id": "on-time-chart",
  "title": "On-time rate in a comparable pilot (example data).",
  "tag": "Example data",
  "chart": {
    "type": "column",
    "data": {
      "columns": ["Month", "On-time %"],
      "rows": [["Jan", 82], ["Feb", 85], ["Mar", 88], ["Apr", 91], ["May", 93], ["Jun", 94]]
    },
    "dataLabels": true,
    "alt": "On-time rate rises every month of the example pilot, from 82% in January to 94% in June."
  },
  "caption": "Illustrative figures, not a real customer."
}
Live preview1 / 7

Loading preview…

The pricing slide is a table with the same shape: columns, rows and alt text.

The next prospect is a patch

Fernwood Market, another fictional company, needs the same pitch on different lanes. Five operations change the deck's name, its description, the title slide, the pricing rows and the pricing table's alt text:

json
[
  { "op": "replace", "path": "/slides/0/title", "value": "Same-Day Lanes: a 90-day pilot for Fernwood Market." },
  { "op": "replace", "path": "/slides/5/table/rows", "value": [
    ["Tacoma to Olympia", 4, "$3,900"],
    ["Tacoma to Yakima", 2, "$2,700"],
    ["Total", 6, "$6,600"]
  ] }
]

(The name, description and table alt-text operations are left out here; see the full file.)

sh
opf edit deck.opf.json deck-variant.opf.json --patch variant.patch.json
opf diff deck.opf.json deck-variant.opf.json --format text
text
10 changes (slides: 2 modified; metadata: 2)

You review what changed for this prospect, not a whole new file.

Check both, then hand off PowerPoint

sh
opf validate deck.opf.json deck-variant.opf.json --fail-on warning --format text
text
deck.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).
sh
opf convert deck.opf.json deck.pptx

The buyer gets an editable PowerPoint, and you keep the source for the next prospect.

Why it matters: the pitch lives in one reviewed file, each prospect is a small diff, and the validator catches problems before anyone opens PowerPoint.

CLI reference · PowerPoint is a handoff

Download the deck and the Fernwood patch. All names and figures in these examples are illustrative.