We first noticed Dxdec because a reader forwarded us a single diagram. It was a clean, labeled map of how wedding vendor deposits move through card processors, and it made an abstract subject feel manageable. That reader, an anonymous wedding planner we will call M., had been running a side project: helping small bridal businesses compare payment fees. She was not a finance person. She was a planner with a spreadsheet and a growing pile of confusing vendor contracts.
What follows is a post-mortem of that project, assembled from her notes and our own follow-up. It is not a product review. It is a timeline of a real planning problem, the decision points that shaped it, and the numbers that came out the other side.
The starting problem: three contracts, zero clarity
In January, M. was comparing three payment processors for a 12-vendor bridal collective. Each contract ran 14 to 20 pages. Each promised lower rates, faster settlement, or better fraud protection. None of the documents explained how a $1,200 deposit actually traveled from a couple's card to a florist's account. M. could compare headline percentages. She could not compare the mechanics underneath them.
Her first instinct was to ask a friend in accounting. That friend explained the basics over a 40-minute call, then sent a link to Dxdec. M. spent the next evening in the diagram explainers, tracing how authorization, clearing, and settlement fit together. The value was not new information. It was ordered information. For the first time, she could see where each processor's fee actually attached to the flow.
Timeline: from one diagram to a decision memo
Week 1 — Mapping the payment path
M. rebuilt the processor flow as a one-page diagram for her vendors. She marked three decision points: interchange, processor markup, and monthly gateway fees. That single page replaced a 90-minute meeting. Two vendors said they had never seen their own contract explained in plain language.
Week 2 — The energy grid detour
Then a different problem surfaced. The collective shared a rented event space, and the electricity bill had jumped 22 percent in one quarter. M. suspected the venue's demand charges, not usage. She used the same explainer approach to unpack energy grids: generation, transmission, distribution, and the demand component that punishes short spikes. She pulled 12 months of interval data and found that two Saturday load-ins were driving the spike. Shifting setup by 90 minutes cut the projected demand charge enough to save roughly $310 per quarter.
Week 3 — Market mechanics and the pricing question
The third thread was pricing. Bridal vendors in the collective were raising rates unevenly, and no one could explain why. M. applied the market mechanics explainers to build a simple supply-and-demand picture for peak-season Saturdays. The diagram showed what the group had felt but not articulated: 9 available dates, 14 vendors competing for them, and a price ceiling set by couples' comparison shopping. The group used that picture to agree on a shared peak-season rate floor instead of guessing individually.
Week 4 — The decision memo
M. delivered a 4-page memo with 3 diagrams. The collective chose the middle processor, not the cheapest one, because the flow map showed the cheapest option added two extra settlement days. For a business built on deposits, two days mattered more than 0.4 percent.
Obstacles and what nearly derailed it
- Jargon creep. Early drafts used terms like "interchange" and "demand ratchet" without defining them. M. rewrote every label as a plain-English question.
- Data gaps. The venue would only release 12 months of utility data, not 24. The team treated the shorter window as a limitation, not a blocker.
- Group politics. Two vendors resisted a shared rate floor. The market mechanics diagram gave them something neutral to argue about instead of each other.
Measurable results
Five months after the memo, the collective reported: payment processing costs down 11 percent, projected venue energy costs down about $310 per quarter, and a written peak-season rate floor adopted by 11 of 14 vendors. M. also estimated the memo saved her 6 hours of repeated explanation, because the diagrams did the talking.
None of these numbers are dramatic. That is part of why we find the case useful. The project did not require a consultant or a new software subscription. It required decoding dense material into pictures that busy people could actually use. Dxdec describes its own mission as decoding curated knowledge for the curious, and this project is a fair test of that claim: 3 obscure topics, 4 weeks, and a planner who started out unable to read her own contracts.
If you are planning a wedding or running a small bridal business, the transferable lesson is not about processors or demand charges. It is that the confusing parts of your operation usually become manageable once someone draws the flow. You can explore the explainer library and its diagram-first approach at the Dxdec knowledge hub, where dense subjects are unpacked one diagram at a time. We will keep following small projects like M.'s, because they tend to produce the most honest evidence about what actually helps.