Diff the customer promise against the system before the campaign ships.

Campaigns fail at the system boundary

Marketing locks the claim. Creative is beautiful. Checkout still cannot do split ship. Inventory truth disagrees with the storefront. Support has no script for the edge the campaign will create. The campaign ships anyway. Customers experience one promise; the systems deliver another.

That gap is not a messaging problem alone. It is an operating diff you can write down before spend commits.

This note gives you the TWIMCO Customer Promise Diff Sheet: side-by-side claims versus system capability, with a named fix-or-cut decision. It extends fulfillment-promise and checkout thinking into campaign readiness. It is not a customer status message matrix (copy for states)—it is whether the promise should ship at all.

TWIMCO built Paddle8’s fine-art auction house and marketplace, where post-transaction operations have to carry the promise past the bid. Use that delivery shape when campaigns touch inventory, shipping, payment, and support. Fulfillment-shaped work scopes under fulfillment operations or ecommerce delivery when the storefront is the surface.

A forthcoming studio helper may assemble claim rows from a brief; until then, fill the sheet by hand for one campaign.

Campaign calendars create artificial urgency. Urgency is not evidence of capability. If the sheet shows conflict and the calendar says “must ship Friday,” the honest move is narrow or cut—not silent heroics. Leadership can still choose residual risk; the sheet forces them to name who owns it and until when.

Treat the sheet as a gate on spend commit, not as optional color commentary after creative lock. Media buyers and agencies should see the fix-or-cut column. If they cannot, the conflict will resurface in customer care with your logo on it.

When SKUs are scarce or authenticated, under-claiming is often the operable choice. A narrower honest claim beats a broad claim the warehouse cannot defend on peak day.

Fields of the Customer Promise Diff Sheet

Claim row. Exact language marketing will use (timeline, availability, free return, “ships tomorrow,” authenticity, edition size, regional coverage). Quote it; do not paraphrase into softness.

System capability — checkout. Can checkout capture the claim (payment plans, gift options, restricted SKUs, geo limits)? Write yes / no / partial with the screen or rule an operator can open.

System capability — inventory. Does inventory truth support the claim at the volumes you expect? Note freeze rules and drift handling if two systems disagree.

System capability — shipping / fulfillment. Can carriers and warehouses meet the timeline and service level implied? Include cutoffs and exception paths.

System capability — support. Does support have a script, queue, and authority for the edge cases the claim creates?

Diff. One line: matches / partial / conflict. Partial means a conditioned claim could work; conflict means the claim as written cannot.

Fix-or-cut. Named decision: fix system before ship, narrow the claim, cut the claim, or accept residual risk with a named owner and expiry. Silence is not a decision.

The unreproducible asset is your filled sheet for a real campaign—the claim quotes and fix-or-cut decisions competitors cannot invent from “align marketing and ops.”

Write the sheet so a stranger could decide fix-or-cut from the evidence alone. If the inventory column says “probably fine,” rewrite it until it points at a screen, a rule, or an explicit unknown dated for resolution. Unknowns are allowed; vagueness is not.

When agencies or freelancers write claims, require they submit draft language to the sheet before media buy. Creative approval without an ops column is how beautiful conflicts ship.

How to run the diff session

Bring marketing, ops, support, and someone who owns inventory truth into one sitting. Walk each claim aloud. Prefer evidence over optimism: open the checkout rule, the inventory view, the carrier cutoff, the support macro.

Do not invent conversion metrics to win the argument. The sheet is about capability, not about projected lift. If leadership wants lift estimates, keep them in a separate memo that cannot override a conflict row.

Timebox fixes. A “we’ll fix it in sprint” without a dated owner is a cut deferral. If the fix cannot land before campaign start, the honest options are narrow or cut.

Watch for implied claims in imagery and influencer scripts—not only headline copy. A picture that implies next-day delivery is still a claim.

For marketplace sellers or consignors, include who owns the promise when inventory is not yours. Diff their capability too, or you advertise a promise you cannot fulfill.

Regional and channel variants deserve their own rows when capability differs. A claim that works domestically but fails internationally is a partial—or a conflict—if the campaign does not geo-fence the language. Write the geo rule into the claim row rather than hoping media buyers remember.

After the sheet: continuity and exceptions

A matched claim still needs exception paths. Pair the sheet with your fulfillment continuity map so checkout through customer message stays continuous when something fails.

When inventory drifts under campaign load, freeze rules belong in the inventory truth card—not as improvisation mid-campaign. Link the two artifacts.

Status copy after failure should not invent a new promise. If the campaign claimed X and the system failed, the message owns the failure; it does not silently rewrite X.

Archive filled sheets with the campaign brief. The next campaign inherits known conflicts instead of rediscovering them in customer care.

Returns and authenticity claims are especially sharp in marketplace and art commerce. If the claim implies a verification standard support cannot execute, cut or fund the standard before the campaign. Diff sheets prevent apology campaigns that were avoidable.

Partner and affiliate copy counts. If a partner can republish your claim, either bind them to the sheet’s fix-or-cut outcome or treat partner channels as out of scope in writing. Unscoped partners will ship the conflict you just cut internally.

Keep one sheet template per brand or channel family so vocabulary stabilizes. Renaming columns every campaign trains teams to argue about the artifact instead of the diff.

Failure modes the sheet catches

Hope as a plan. “Warehouse will figure it out.” Fix-or-cut refuses that blank.

Partial capability sold as full. Checkout can take the order; fulfillment cannot meet the timeline. Diff forces partial into the open.

Support surprise. New claim creates a ticket type with no owner. Support column catches it.

Metric theater. Projected lift used to override a conflict row. Keep lift out of the sheet.

These are delivery-shaped composites, not client telemetry. Use Paddle8 as a reminder that marketplace promises live or die after the transaction.

Put this into practice

1. Take the next campaign brief and quote every customer-facing claim onto the sheet.
2. Fill checkout, inventory, shipping, and support columns with evidence you can open.
3. Mark matches, partials, and conflicts; force a named fix-or-cut per non-match.
4. Block spend commit until conflicts are fixed, narrowed, or cut.
5. Scope fulfillment gaps under fulfillment operations and ground continuity in work like Paddle8.

Ship the campaign when the diff is reconciled—not when the creative is approved.