See What Can Still Change — Free

Why this exists

A wedding is bought as one thing and contracted as a dozen.

A venue, a caterer, a florist, a photographer, a band, a rentals company. Six businesses, six agreements, six sets of totals and dates — signed months apart, by two people who have never done this before and will never do it again.

Nobody ever puts them together

Not the couple, who may have signed them one at a time across a year. Not the venue, which knows its own contract. Not the planner, if there is one, whose job is the day rather than the paperwork. What a couple has committed to can be scattered across the PDFs and inboxes it arrived in, and planning a wedding does not by itself make a moment to sit down and open them together.

So the budget spreadsheet stops being true somewhere around the fourth deposit and never recovers. It is nobody’s fault. It is what happens when one purchase is made of a dozen separate ones and the only person with visibility into all of them is the one with the least practice at it.

We expected to find villains. We did not.

The obvious version of this business is catching a vendor out, and it is the version we started with. Then we read real wedding paperwork. Wedding vendors are small businesses working from standard contracts, and a duplicate charge is the best thing we can find for you — not the thing to plan on. We have not measured how often one is there, so this page does not tell you.

The harder problem is not the arithmetic on any one invoice. It is that the arithmetic across them may never have been done — what is committed against what is quoted, what is paid against what remains, which deadline closes next, and what each contract says happens if something changes. That is worth having whether or not there is a single error in the pile.

Why a machine, and why this one

Reading forty pages of contracts and tying figures back to the line that produced them is exactly the sort of work a person does badly at eleven at night and software does without getting bored. That is the whole of our advantage, and it is why the discipline that matters here is not cleverness but traceability: a figure is meant to enter your plan only when it can be pointed at the sentence in your own document that it came from, and shown to you beside it so you can check that it was.

It is not, however, the same every time. The same document read repeatedly at one version of our code produced materially different numbers of findings, so treat your plan as one careful reading rather than the definitive one.

We measure that rather than assert it, and we measure the harder question too — what we miss.

In the 2026-08-21 evaluation run, at revision 2c6c6a7, this product surfaced 25 of 411 independently selected actionable items on a fixed 31-document corpus. Of 106 substantive claims it emitted, 97 were fully supported by the source, 9 were partially supported or materially overstated, and 0 were wholly unsupported.

  • Proven money issue: 0 of 29
  • Timeline or conflict: 0 of 32

What this number is not. It is not population accuracy, not savings recall, not whole-order accuracy, not an F1 score. It describes one run, at one revision, over one fixed set of documents:

  • One fixed corpus of 31 documents, not a representative sample of real orders.
  • One stochastic run. The same document read five times at one revision returned between 43 and 177 facts.
  • Documents were read one at a time, so rules requiring two vendors could not fire.
  • Recall and source support use asymmetric truth sets; no F1 is reported.
  • Key overlap is a lower bound: the frozen recall key is not assumed exhaustive for predictions.

The readiness page breaks that down by category, including the two that came back at zero.

And then we stay for the wedding

Reading the contracts was where this started. It is not where it stops. The same plan becomes the place the wedding is run from: a checklist dated off your day, your budget against what your contracts commit, the guest list your guests fill in themselves, the seating, the light at your venue on your date, the words you will say, the music, the letters sealed until the anniversary, the album your guests add to, and a keepsake of the whole day. Nothing in it is invented; it is built from your paperwork and what you and your guests put in.

How we get paid, in full

You pay us $79, once, after you have seen a summary of what we found and a complete list of what your plan contains. What we find never changes what you pay. Each figure is counted under our published rules. That is the entire business model.

No vendor pays us anything. There is no commission, no referral fee and no kickback from any venue, caterer, planner, florist or photographer, and no vendor can pay to appear in your plan or to stay out of it. We do not sell your documents, your email address or anything derived from them.

It matters that those two paragraphs are the same paragraph. A service paid by the people it reports on cannot tell them the uncomfortable thing. We are paid by you, after you have seen what we found and what your plan contains — not on a promise about them.

What we will not do

Who is accountable

Wedding Remedy is operated by Eltherion, LLC, at 851 NE 1st Ave, Miami, FL 33132 — a registered company with an address you can look up, rather than a brand name and a contact form. If a figure in your plan is wrong, if the writing is careless, or if you think we have overreached, the support address reaches a person, not a queue.

We have not launched, and we would rather say so here than have you work it out later. What is built, what is not, and what we cannot do well yet are all listed on one page. That page exists instead of a wall of five-star reviews, and it will keep existing after we have some.

See what can still change — free

5 questions · No card · We never contact your vendors