Skip to content
Cardon Digital

Cardon Digital

A growth-systems practice
for wineries in Valle de Guadalupe and Ensenada.

We build the system a winery runs on (harvest, lots, tanks, lab results, vintage comparison, weather data, sales and bookings) and keep it running, with an assistant that answers questions from the winery's own records. Around that system we run the marketing that fills the tasting room, the club and direct sales. One senior team, flat fees, and the client owns what we build.

Built to hold water

Open a demo
ProduccionHospitalidadRestauranteAll of it together

Each demo runs on a made-up brand, with no signup and no password. Each button opens the live demo in a new tab, with that module switched on.

Where it stands today

Six things that are true in almost every winery we walk into.

None of them is about working harder. They are all about a record that was never kept in one place.

Weather per section, on the same clock as the fruit.Cabernet, section 4illustrative view

The Brix and total acidity a lab sheet carries, over what the section's own sensor records. Drag across either graph and both read the same day.

Day 45 from veraison

Brix
23.6°Bx
Total acidity
5.9g/L
Daily high
28°C
Daily low
14°C

Drag across the graph, or use the arrow keys.

  1. 01

    The record is spread across four places.

    Field notebooks, tank cards, lab sheets and a spreadsheet somebody keeps. Gathering them takes longer than the decision they were meant to inform.

  2. 02

    Past vintages are out of reach.

    Three harvests ago is a box of paper. The Cabernet's total acidity in the two weeks before pick, 2023 against this year, takes an afternoon or never gets answered.

  3. 03

    What worked cannot be repeated.

    Without a comparable record there is no way to rebuild what was actually done, so each vintage starts again from memory.

  4. 04

    Sales and hospitality run on tools that never talk.

    Bookings, the club, the shop and distributors: four subscriptions, no single view, and follow-up that arrives late or not at all.

  5. 05

    The reporting lands too late to act on.

    Hours of manual work over the numbers, and by the time the report exists the month it describes is already closed.

  6. 06

    The software market is not built for you.

    The specialist winery systems all come from somewhere else. vintrace and InnoVint publish no price at all: you ask a salesperson for it. Commerce7 publishes its own in seven currencies and none of them is the peso, and its entry plan is capped to direct sales in the United States and Canada. None of them issues a CFDI, and an expense without a CFDI is not deductible. On the Mexican side, CONTPAQi and Aspel invoice correctly and their catalogues carry no winery product at all: they do not know what a lot, a tank or a vintage is.

What we build

Three modules. You buy the ones you run on.

Produccion is the record of what you grew, made and sold. Hospitalidad is every booking from every channel in one calendar. Restaurante is the point of sale, from the waiter's phone to the cash cut. Each one is a whole system on its own, and each one is sized to the operation in front of it.

01

Produccion

The record of the harvest, the cellar and the sale

The vintage is real and the record of it is not.

Weights arrive on a phone, lab results live in a notebook, tank movements are remembered rather than written, and the commercial side sits in a different file again. By the time anyone asks how this year compares with the last three, the answer has to be rebuilt from memory and from four exports that disagree.

Produccion is the winery's own record of what it grew, made and sold, dated and attributed, with the comparison, the report and the assistant built on top of it. One record, and every question answered from it.

Lots and tanksillustrative view
L-12 · Cabernet · T4Brix 24.4

What is built, by size

At S, the entry build
  • Production record: schema, ingestion for the first two sources, and the core views, weights, lots, tanks, lab, barrel and bottling, dated and attributed
  • Vintage comparison: any measure plotted against days post-veraison, this year beside prior years
  • Commercial record: tasting room visits, club members, direct sales and distributor orders, next to production
  • Historical vintage load: one prior vintage brought in from digital sources the winery already holds
  • Monthly report generator: the plain-Spanish monthly report built from live data, with a delta section
  • The assistant: grounded question answering over your own records, with an audit log and a refusal when the record does not hold the answer
  • Training and handover pack: role-scoped Spanish documentation, recorded walkthroughs, credential handover and a competence check
M adds
  • Two more data source connectors, each mapped and validated
  • A second historical vintage
L adds
  • A third extra data source connector, for five or more sources in total
  • Prior vintages up to four seasons back
  • A prediction or classification model tuned to house standards, harvest readiness or quality
  • Finance workflow automation on your reporting
Also available
  • An existing ERP integrated into the data-system features
  • More than one production site

The sizes

Size is set per module, so an operation can be M on one and S on another.

S
One production site, one brand, one or two data sources, no more than about 20 lots. For a grower: one ranch, one or two sources, up to about 30 blocks.
M
Several lots and varietals, the tasting room and direct sales in the record, three or four data sources, an existing site that needs real changes. For a grower: two or three ranches, three or four sources, deliveries to more than one buyer.
L
Multi-origin, five or more data sources, a model and finance workflow automation.

Who it is for

Winemakers and grape growers. A grower gets a different feature set at the same rates, built around blocks, applications, irrigation and deliveries to buyers instead of tanks, barrels and a bottling line. It is another set of features, not a cut-down one.

The grower set
  • Vineyard block record: blocks, varietals, rootstock, planting dates and area, with every field event dated and attributed
  • Maturity and phenology curve: sampling results plotted against days from budbreak, this season beside prior seasons
  • Delivery and buyer record: loads by block and buyer, weights, sugar and pH at reception, price terms and payment status
  • Applications and compliance log: sprays and doses, pre-harvest intervals, who applied, the evidence a certification audit asks for
  • Irrigation and water register: irrigation events and water use, captured by hand when no controller exposes data
  • Historical season load: one prior season brought in from digital sources the grower already holds
  • The report generator, the assistant, and the training and handover pack, the same as the cellar set

A weather station or an irrigation controller is read as a data source when it already exposes its data. When it does not, the register is kept by hand. We do not buy, install, own or warrant hardware, and no quote carries a device that was not checked at the Diagnostico.

On Produccion we organise data, control and automation. We do not build a winery's sales. There is no version of this module that carries a site, conversion tracking or an ads build; those attach to Hospitalidad and to Restaurante, which are the modules that sell a thing a guest books.

Open the Produccion demo
02

Hospitalidad

Every booking in one calendar, and the day the property works from

Four channels, four calendars, and one room.

The bookings land in as many places as there are channels, the arrivals for tomorrow are counted by hand, housekeeping is told by phone, the guest who came last season is a name somebody half remembers, and the revenue by channel is a spreadsheet rebuilt at the end of every month.

Hospitalidad puts every booking from every channel into one calendar, with the day view the property actually works from, the state of each unit, the guest kept between stays, and occupancy and revenue that reconcile. One calendar, and a day that is already counted when it starts.

Master calendarillustrative view
U1 · 1-3Direct3 nights

What is built, by size

At S, the entry build
  • Unit and stay record: units, stays and guests, the schema every other feature reads, dated and attributed
  • Two channel feed connectors: each booking channel read into normalised stays, deduplicated, with a freshness stamp
  • Master calendar: units by days, each stay coloured by channel, month navigation, usable on a phone
  • Day view: arrivals, departures, units occupied tonight and cleanings pending, on one screen
  • Unit status board and housekeeping phone view: unit states, cleaning tasks generated from departures, marked done from a phone
  • Guest record: notes and stay history attached to the guest, kept between stays
  • Occupancy and revenue by channel: nights sold over nights available, revenue by channel and month, with the count of stays still missing an amount shown
  • Monthly report generator, the assistant, and the training and handover pack for host, housekeeping and admin
M adds
  • A third channel feed connector
  • Direct booking capture: an enquiry or booking path captured straight into the stay record and tracked
  • Channel manager connector: replaces the read-only feeds, bringing guest names, amounts and webhooks with it
  • A prior season loaded from channel exports the property already holds
L adds
  • A fourth channel feed connector
  • A second prior season loaded
Also available
  • Tasting room and event booking capture: visits, tastings and events booked into the same record and tracked, from M
  • Automated follow-up on direct bookings, repeat guests and the wine club, from M
  • A brochure or booking site wired to the stay record and to tracking, in Spanish and English
  • Conversion tracking and GA4, owned by you
  • A Google Ads build at any size, with its monthly management from M

The sizes

S
Up to 6 units, up to 2 channels, one property, no channel manager.
M
7 to 20 units, up to 3 channels, one or two properties, a channel manager or a direct booking path.
L
21 to 40 units across more than one property, 4 or more channels, a channel manager, direct booking and ads.
Above 40
Not a client we take. A property that size has a property management system, a revenue manager and a procurement process, and it is better served by them. We say so in the Diagnostico rather than quoting work we would not do well.

Who it is for

Properties with rooms, cabins or casitas, from a six-unit house up to forty units across more than one property. A winery with rooms, a tasting room and events belongs here too: this is the module that owns bookings and guests.

How the channel read works, said plainly. At the entry build we read each channel's calendar, so guest names and amounts are captured by hand until a channel manager is contracted, and the count of stays still missing an amount is shown on the occupancy view rather than hidden. The system never writes back to a channel. The cleaning task is generated from the departure date, and who cleans is the property's own arrangement.

Open the Hospitalidad demo
03

Restaurante

From the waiter's phone to the cash cut

The order is written twice and the night is counted at midnight.

The order goes on a pad, then onto a ticket, then into a till. The kitchen works from paper and shouting. A table waits for a bill that has to be added up by hand, and a split one waits longer. At close, the cash is counted against a number nobody can rebuild, and the comps and cancellations are whatever people remember.

Restaurante is the point of sale: the order is born on the waiter's phone, travels to the kitchen screen, is paid at the table with the bill split and the tip kept apart from the sale, and the day closes with a cut that reconciles. Written once, at the table, and counted as it happens.

Table mapillustrative view
123456789
Table 1Seated2 covers

What is built, by size

At S, the entry build
  • Menu, categories and modifiers: the menu tree, modifier groups and prices, with 86 marked from any phone and gone from every phone at once
  • Order taking on the waiter's phone: by table and by seat, grouped by course, line notes, live subtotal
  • Send to kitchen and course firing: a line or a whole course sent, sent lines locked, the waiter fires the next course
  • Kitchen screen: queue oldest first, capture time, elapsed minutes, table and waiter, colour and text thresholds, bump and recall, and a warning when it loses sync
  • Table map and host screen: zones and real table shapes, covers, arrival time, occupancy minutes, state and turn time
  • Checkout with split and tip: whole bill, by seat, evenly between several or by amount, with the tip stored apart from the sale
  • Cash and card recorded by hand: works on day one with no third party, cash received and change, card written down as taken
  • Invoice request capture: RFC, razon social, regimen fiscal, uso de CFDI and email captured on the ticket
  • Cancellations and comps log: every one with its reason and who authorised it, listed one by one
  • Daily summary and cash cut: sale by category, hour and waiter, covers, average ticket, tips, the ten best sellers, opening float, declared cash and the difference
  • Monthly report generator, the assistant, and the training and handover pack for waiter, kitchen, host and admin
M adds
  • Station split: bar, hot and cold queues, with an expediter view over all three
  • Payment link and QR connector, on the restaurant's own provider account
  • Table reservation seating: the day's reservations by hour, with a seat button that opens the table session
  • The menu and prior sales loaded from an export the restaurant already holds
L adds
  • Card payment reconciliation: the day's card sales matched to the provider's transaction report by our own reference, gross reported against the deposit net of commission and tax
Also available
  • A brochure or booking site wired to the record and to tracking, in Spanish and English
  • Conversion tracking and GA4, owned by you
  • A Google Ads build at any size, with its monthly management from M

The sizes

S
Up to 12 tables, up to about 80 covers a day, one station, up to 4 phones and one kitchen screen.
M
13 to 30 tables, up to about 200 covers a day, two or three stations, up to 10 phones and two screens.
L
31 to 60 tables, above 200 covers a day, three or more stations plus an expediter, more than 10 phones and three or more screens.
The tie-breaker
Covers a day decides when the tables and the devices point at different sizes, because what the month costs to run tracks service volume rather than furniture.

Who it is for

Owner-run dining rooms, from a twelve-table room up to sixty tables and three or more stations. One branch: a group running several is not what this module is built for, at any size.

Payments and invoicing, stated exactly. Cash and a card recorded by hand work from day one, with no third party involved, because a restaurant that cannot write down that a table paid by card has not bought a point of sale. Where the restaurant has its own payment provider account and can issue its own credentials, a payment link and its QR at the table is a connector quoted on top, one per provider, and the bill turns paid only when an authenticated status query returns the completed state. The invoice request is captured on the ticket; the stamping is done by your own invoicing provider and we never imply otherwise.

What this module does not do

Named here rather than discovered later: guest self-service ordering by QR, ingredient inventory and recipe costing, our own CFDI stamping, physical card terminals, thermal ticket printing, happy-hour price rules, payroll and tip distribution, and more than one branch.

Open the Restaurante demo
The seven combinations

One, two or three, and what the bridges add.

Buy the modules you run on. A bridge is only built when both of the modules it joins are bought, and it is quoted on top of the two.

  1. On its own

    Produccion

    The record of what you grew, made and sold, the vintage comparison, the monthly report and the assistant over your own cellar.

  2. On its own

    Hospitalidad

    Every channel in one calendar, the day view the property works from, the unit board, the guest kept between stays and revenue by channel.

  3. On its own

    Restaurante

    The order on the phone, the kitchen screen, the table map, the table paid with the bill split, and a day that closes with a cut.

  4. One system

    Produccion and Hospitalidad

    One system and one login for both, and the shared service base is priced once whichever modules you add it to. The tasting room, the events and the club are still booked in Hospitalidad, and those visits already sit in Produccion's own commercial record on its own.

  5. The bridge

    Produccion and Restaurante

    The house wine list reads live from the cellar by vintage and varietal, so what the dining room offers is what the cellar actually holds. It reads only: the cellar record stays the cellar's.

  6. The bridge

    Hospitalidad and Restaurante

    Charges from the restaurant post to the room, and a guest's table booking shows on their stay, so the host sees the guest and the stay sees the table.

  7. The bridge

    All three

    Both bridges at once, under one system: the guest arrives, books a table, charges dinner to the room and drinks a wine the cellar knows by vintage, while the tasting room visit still sits next to the season that produced it.

The service base is charged once whatever the mix, and a module added to a client we already serve is a smaller build than the same module bought alone, because the training, the assistant frame, the report and the environment are already standing.

What it costs

Every module has a published entry price.

Setup pays for the build and you own it. The monthly fee pays to run it. End the service and nothing moves between accounts: we promote you to owner, hand over the payment method and remove our access.

Where each module starts

What each module starts at, and what that buys.

To implement
  • Restaurante$4,260 USD
  • Hospitalidad$3,120 USD
  • Produccion$2,760 USD
Every month
  • Restaurante$710 USD
  • Hospitalidad$680 USD
  • Produccion$640 USD

Each monthly is the shared base, charged once per client, plus that module's run cost.

Restaurante

Close the day with the cash already counted.

Twelve tables, one station, four phones, one kitchen screen.

To implement$4,260 USD

Every month$710 USD

bought on its own

The complete build

  • Menu, categories and modifiers
  • Order taking on the waiter's phone
  • Send to kitchen and course firing
  • Kitchen screen
  • Table map and host screen
  • Checkout with split and tip
  • Cash and card recorded by hand
  • Invoice request capture
  • Cancellations and comps log
  • Daily summary
  • Cash cut
  • Monthly report generator
  • The assistant over your own records
  • Training and handover pack
What moves it up
More tables, stations or covers a day move it up, to 60 tables.
Worth knowing
Cash and a card written down work from day one. A payment link is a connector on your own provider account, quoted on top, one per provider, and your own invoicing provider stamps the invoice.
Open the Restaurante demo

Hospitalidad

Fill the rooms two calendars left empty.

A six-unit property on two booking channels.

To implement$3,120 USD

Every month$680 USD

bought on its own

The complete build

  • Unit and stay record
  • Booking channel connector x 2
  • Master calendar
  • Day view
  • Unit status board and housekeeping phone view
  • Guest record
  • Occupancy and revenue by channel
  • Monthly report generator
  • The assistant over your own records
  • Training and handover pack
What moves it up
More units, more channels or a channel manager move it up, to 40 units.
Worth knowing
The entry build reads each channel's calendar, so names and amounts are typed in by hand until a channel manager is contracted.
Open the Hospitalidad demo

Produccion

Know what you grew, made and sold.

One production site, one brand, two data sources, one prior vintage.

To implement$2,760 USD

Every month$640 USD

bought on its own

The complete build

  • Production record
  • Vintage comparison
  • Commercial record
  • One historical vintage loaded
  • Monthly report generator
  • The assistant over your own records
  • Training and handover pack
What moves it up
More sources, more origins, more prior vintages, a model or finance automation move it up.
Worth knowing
A grape grower gets a different set at the same rates: blocks, applications, irrigation and deliveries.
Open the Produccion demo

The demos run on an invented brand, in a new tab.

An entry price only moves up, never down: more sources, more units, more tables, more vintages, a connector, a second module. Below that build there is no system, only a report. The Diagnostic sets the final quote.

More than one module

Two modules, or three.

The second module is a smaller build: the training, the assistant, the report and the environment already stand.

  • The shared service base is charged once, whatever the mix.
  • On the build the largest module goes at full price, the second 10 percent off, the third 12 percent off.
  • A line inside a mix can sit below what that module costs alone, because it is priced on the hours actually built.
The seven combinations

What each combination costs at the entry size.

Most expensive first, and every row is the complete build of each module it names.

The colours key the monthly blocks only. Each row's build bar draws in a shade of its own, outside these four.

The seven combinations at the entry size
What you buyTo implementEvery month
Restaurante, Hospitalidad and ProduccionPriced on the hours actually built: Restaurante at full price, Hospitalidad 10 percent off, Produccion 12 percent off.To implement$8,320 USDEvery month$950 USD
Restaurante and HospitalidadPriced on the hours actually built: Restaurante at full price, Hospitalidad 10 percent off.To implement$6,620 USDEvery month$850 USD
Restaurante and ProduccionPriced on the hours actually built: Restaurante at full price, Produccion 10 percent off.To implement$6,090 USDEvery month$810 USD
Hospitalidad and ProduccionPriced on the hours actually built: Hospitalidad at full price, Produccion 10 percent off.To implement$4,940 USDEvery month$770 USD
RestaurantePriced on the hours actually built: Restaurante at full price.To implement$4,260 USDEvery month$710 USD
HospitalidadPriced on the hours actually built: Hospitalidad at full price.To implement$3,120 USDEvery month$680 USD
ProduccionPriced on the hours actually built: Produccion at full price.To implement$2,760 USDEvery month$640 USD

Each bridge is quoted on top of these figures, and only where both of the modules it joins are bought: the restaurant bridge and the wine list wired to the cellar.

Worked example

A winery with six rooms and a restaurant.

All three at their entry size, ranked by build price: Restaurante at full price, Hospitalidad second, Produccion third.

The three modules together, at their entry size
To implementEvery month
Together$8,320 USD$950 USD
Bought separately$10,140 USD$2,030 USD
What that saves$1,820 USD$1,080 USD

This line is what this configuration costs, priced on the hours it takes, and it sets no floor.

The monthly service fee

What the monthly fee pays for.

One shared part per client, plus one run cost per module. This is the shared part.

  • Hosting, monitoring and backups
  • The assistant's provider account, paid by us
  • Care, corrections and the calls they need
  • A weekly call and WhatsApp
  • The monthly report and its readout
  • Your invoicing and account admin

Each module adds its own run cost: its feeds, its corrections, its part of the report and the assistant.

Paying a year up front

A year in one payment costs less.

Twelve months paid at the start cost less than twelve payments: one invoice a year costs us less than twelve. Service fee only, never setup and never ad spend. The paid year runs to its end: stop halfway and there is nothing more to invoice and nothing to refund. The system stays on until the anniversary and you can leave there. Your quote carries the figure.

Ads and content

Google Ads management and content attach to Hospitalidad and Restaurante.

Neither attaches to Produccion: there we organise data, control and automation, and we do not build a winery's sales. Content from the entry size, ad management from the middle size up. Ad management is inside the monthly fee, never as a share of what you spend, and both are quoted on top of the figures above.

Terms

The terms.

  1. Setup is half on signature and half on acceptance.
  2. The signature half can go in three monthly payments at no extra cost.
  3. The service fee runs month to month, paid in advance, 30 days notice either way.
  4. Leave inside the first twelve months and we invoice the part of the build the service fee was funding, less one twelfth per month paid. How much depends on the configuration, and your quote states it.
  5. All prices are plus IVA. Your ad budget goes straight to Google, never through us.
  6. We quote and invoice in Mexican pesos. Dollar figures are rounded conversions, so a dollar column can sit a few dollars off its sum.
Start here

The Growth Diagnostic

Which modules, at which size, and what gets built first is what the Diagnostic answers before anybody quotes anything. Ten working days going through your data, your bookings, your floor and your numbers as one system.

Get the free Growth DiagnosticOther ways to reach us

Free. No retainer, no obligation. If the memo shows work worth doing, we propose the build and you decide.

Day 1. A working session over the operation you actually run, module by module.
Days 2 to 9. We dig: the sources, the channels, the floor, the measurement and the numbers behind the numbers.
Day 10. The memo lands: what is true, what is broken, and which module earns its place first.
Free and unattached. Use it with us or without us. If we build, the price is agreed at the start and you own the result.