The estate you just bought brings its own club list
How do we fold an acquired winery's club, tasting room and sales records into the rest of our estates?
Figures and rules on this page apply to
United States
Working somewhere else? The shape of the problem usually travels. The deadlines do not.
What this looks like
The deal closes and the estate keeps selling. Its club ships from its own list. Its tasting room rings sales on its own till. Head office asks how many new members also belong to another club in the group. Nobody can say without a week of spreadsheets.
The numbers
Every figure here is someone else’s. Check them.
- 8,785wine businesses reporting to the federal alcohol tax bureau (TTB) in 2025
- 9,703the same count in 2023, the peak year, so nearly a thousand fewer two years later
- 15%drop in cases shipped direct from wineries to US consumers in 2025, the worst year since the report began in 2010
- +11%rise in the average price per bottle shipped direct in 2025, so each lost member costs more
Why it happens
It is not a people problem.
Each estate keeps its records correctly, in its own terms. One calls a member a club member, another a subscriber, another an allocation customer. The same person can sit on three lists under three spellings. Wines, club tiers and shipping rules are coded differently too. The fields line up. What they mean does not.
Why your current software has not fixed it
Because it was never built to.
The usual plan is to move every estate onto one club and sales system. That takes a year or more, and the estate cannot stop selling meanwhile. Club software ships wine and takes payment well. It was not built to decide that two records are one person. So the join is done by hand, again, at every acquisition.
Intelligence, plumbed in
A member saved as 'Bob & Sue Miller, Napa' at one estate and 'Robert Miller' at another can be matched, with a reason shown.
We build the layer that says what each estate's records mean, then read every estate through it. Underneath it: a connector, one agreed meaning per field, and a test set scored on your own records.
How we make AI survive real data-
Connectors -
A semantic layer -
Evals you can check
However hard, whatever it is
A newly bought estate is one example. Bring the records that never quite join up.
We wrote this for wine groups because buying estates is how many of them grow. The same approach fits any business adding sites that sell direct.
-
01 We sit with you
Days where the work happens, not a workshop in a meeting room. We watch the job get done and write down the shortcuts nobody wrote down.
-
02 We read everything
Your data, your rules, your vendors and their documentation, and the published research on your sector. We report what is actually in there.
-
03 We break it to first principles
Not which tool fixes this. What is actually causing it, taken apart until we reach the piece that cannot be divided further.
-
04 Then we build
Weeks, not quarters. By this point we are not guessing what to build, and guessing is the thing that makes projects long.
What we build
Specific enough to argue with.
Four mechanisms, not four features. Each one is a thing that happens on its own, every day, whether or not anyone remembers to run it.
-
Club lists, till sales and order history read from each estate as they are, with nothing switched off.
-
One agreed meaning for member, tier, wine and site, held above every estate's own systems.
-
A daily view of club and direct sales by estate, including members who belong to more than one club.
-
A newly bought estate joined to the same view in weeks, before its members notice any change.
How you would know it worked
Numbers in your own reporting, not ours.
- Days from closing to seeing the new estate's members in the group view.
- Share of new members matched to existing customers without a person checking each one.
- Club cancellations at the new estate in its first two shipments after the sale.
Straight answers
Where a model is involved, it is scored against your own records first. Accuracy per source, not one flattering average.
The questions this raises
-
We plan to move every estate onto one club system. Why do this first?
The move needs the same matching of members and wines anyway. Doing it first gives you the group view now and makes the move shorter.
-
Will the new estate's members notice anything?
No. Their club, their shipments and their tasting room stay as they are. The change is in what head office can see.
-
What about records kept in spreadsheets or on paper?
They are common at smaller estates. They are read and matched like any other record.
Where the figures come from
We did not make these up, and you should not take our word for them.
Also in agriculture & food
The traceability deadline moved to 2028, and nothing else changed
Congress directed the FDA not to enforce the food traceability rule before July 2028. The records the rule asks for are still not being produced, and the extension does not produce them.
ProblemEvery customer wants its own spec sheet, and a person writes each one
Ingredient and seasoning makers sell blends made for one customer. Each customer then asks for a specification, an allergen list and a label in its own format.
The meaning is not in any schema
Two systems agree on the field and disagree on what it means.
The rule lives in a document, or in what one site has always called something, or in a habit nobody wrote down. Joining the data is the easy half; agreeing what it means is the half that is actually the work.
- Behavioral healthOne in four facilities still run on paper, and there is a reason
- Accounting & consultingAn eight-hundred-billion-dollar quarter built on hours recalled from memory
- Senior livingNobody wants a sixth dashboard
- Skilled nursingEvery building reports. Nobody can see the portfolio.
- ManufacturingEvery plant you add keeps its own production record
Consent rules, site vocabulary, what an hour counts as. Wherever two systems agree on a field and not on what it means.Describe the disagreement.
Joining a new estate is a question of meaning, not a system migration.
We build the layer that says what each estate's records mean, then read every estate through it.
See everything we build-
Software -
Hardware -
Ways of working -
Whole ventures
Is this happening to you? Tell us the size of it.
Twenty minutes. We will tell you honestly whether the numbers justify doing anything about it.