Start with one minimal DRGT-to-HubSpot audience handoff, one personalised voucher campaign and a secure browser-based QR redemption experience. No production POS integration. No app requirement. DRGT stays in control of gaming data throughout.
Skip to business case
Decision document — internal review
See the options
Recommendation
Decision needed
Why change
Recommended path
Decision needed
Value at stake
Investment frame
Time to first value
Confidence
Recommended
Decision document — internal review
Casino 2000 × HubSpot
Start simple. Prove the voucher loop. Expand with evidence.
One dinner-voucher journey — DRGT selects, HubSpot communicates, the guest accepts without an app, the venue redeems by QR, and the result returns to one shared view.
Select the preferred scenario (phase one on 12 or 36 months, or full scope on 36 months), name a legal and information-security reviewer, and authorise Bonana to scope implementation. These three decisions unblock all subsequent design and delivery work.
Commercial review September 2026 Target
Go to decisionExecutive summary
The case in three decisions
Casino 2000 contacts selected guests too infrequently. Each campaign requires manual DRGT exports, file transfers and follow-ups across separate systems. Acceptance and redemption are invisible to marketing until someone checks. The casino loyalty card is legally restricted to casino use, so cross-venue rewards require a different path.
Run one deliberately simple voucher journey first. DRGT selects the audience, HubSpot sends the offer, the guest accepts on any browser without installing an app, the venue redeems by QR and the result returns to HubSpot. This is the minimum that proves the loop and generates evidence for every later decision.
Casino 2000 will review three commercial scenarios in September. To unblock implementation, the team needs to select a scenario, name the legal and information-security reviewers, and authorise Bonana to run a discovery and scoping workshop.
Executive check
The decision in one minute
More frequent, measurable guest engagement across casino, restaurant, hotel and events — with one closed feedback loop and a platform that can grow without replacing DRGT or violating the loyalty-card boundary. Value magnitude is directional until the first campaign baselines are captured.
Three scenarios are under review: phase one on a 12-month or 36-month term, or a broader scope on 36 months. HubSpot licence, seat count and Bonana implementation cost will be confirmed after scenario selection and partner scoping. No figure is stated here because no scenario has been selected.
After the September scenario review and legal/security sign-off, Bonana can scope and begin implementation. The first live campaign is a target that follows those gates — not a committed date until the review is complete and the partner scope is agreed.
The voucher journey is demo-validated on portal 51693900 with real Casino 2000 brand, a Keyring incentive schema and a live QR redemption flow. DRGT's role and the loyalty-card constraint are confirmed customer facts. Production feasibility depends on partner, Lightspeed and legal/security validation.
Strategic case
Why change
Three confirmed friction points prevent Casino 2000 from running frequent, measurable cross-venue campaigns today.
What is true today
DRGT qualifies and selects guests for campaigns, but the selected audience must be manually exported and imported into a separate communication tool before any message can be sent.
Why it hurts
Campaign preparation is time-consuming and limits how often marketing can send offers. Errors or delays in the manual handoff create gaps in communication.
What follows
Confirmed
Fewer campaigns reach qualifying guests than DRGT analytics and the team would support. Retention and re-engagement opportunities are missed each cycle.
What is true today
Offer acceptance and point-of-sale redemption are tracked in separate places, if at all. Marketing cannot see whether a voucher was used without a manual follow-up.
Why it hurts
There is no single view of whether a campaign worked. Accepted offers and redeemed vouchers generate no automatic feedback to the system that issued them.
What follows
Confirmed
Marketing cannot measure campaign effectiveness, close the offer lifecycle or use redemption outcomes to improve the next campaign.
What is true today
The casino loyalty card is legally restricted to casino use and cannot be used to earn or redeem points at restaurants, bars, the hotel or events.
Why it hurts
Guests with high gaming value cannot be recognised and rewarded at other Casino 2000 venues through the existing loyalty mechanism, limiting the cross-venue relationship.
What follows
Confirmed
A separate, complementary channel is required for non-casino recognition. Without one, the business cannot use its guest relationships across its full estate.
Outcomes
What success changes
The first scope targets three outcomes: one for guests, one for the operations team and one that justifies the platform investment.
Guests receive and use a personalised cross-venue reward without installing an app
TargetTodayGuests receive no personalised cross-venue digital offer from Casino 2000. The loyalty card is casino-only by legal constraint.
FutureA DRGT-selected guest receives a personalised dinner voucher by email, accepts on any smartphone browser, and presents a QR at the venue. No app required. The experience works on any device.
MeasureVoucher acceptance rate and redemption rate per campaign. Baselines set in the first live campaign; no prior data exists to establish a target in advance.
The marketing team runs a complete offer cycle from one place
DirectionalTodayCampaign execution spans DRGT exports, file transfers and a separate communication tool. Redemption status is not visible without a manual chase.
FutureMarketing issues the campaign in HubSpot, monitors the funnel — selected, sent, accepted, redeemed, expired — in one view, and uses the redemption outcome to plan the next offer.
MeasureCampaign preparation time per cycle (current process described by the team as time-consuming; exact baseline to be agreed before the first campaign). Number of campaigns run per quarter before and after automation.
The first campaign generates the evidence base for every subsequent platform decision
TargetTodayNo redemption data, cross-venue digital engagement baseline or measurable outcome from a digital channel exists.
FutureAfter the first live campaign, Casino 2000 has acceptance rates, redemption data and an operating record to inform the Lightspeed production integration decision, the retention policy and the scale-up investment case.
MeasureEvidence record: voucher-funnel data quality, redemption-return reliability, team operational assessment and readiness signal for the next phase decision.
Recommendation
What is in the decision
The first scope is deliberately minimal. Everything else is gated behind what the first campaign proves.
Now
- One DRGT-to-HubSpot audience handoff via validated CSV exportThe customer confirmed a minimal CSV handoff rather than a live API for step one. This keeps DRGT in control and removes the API dependency from the first delivery gate.
- One personalised dinner-voucher email campaign in HubSpotThe dinner-voucher journey is the agreed proof case. One campaign validates the full loop before any expansion decision is made.
- Keyring voucher lifecycle: issue, accept by browser QR, redeem by staff scan, return status to HubSpotKeyring provides the no-app acceptance, QR redemption and feedback return in one layer. It is demo-validated on portal 51693900.
- HubSpot voucher funnel view: selected, sent, accepted, redeemed, expired or non-redeemedThe marketing team needs a single status view. The funnel is the primary measurement output from the first campaign.
- Consent, data-retention and GDPR controls for the voucher audienceConsent and GDPR are explicit customer criteria and a legal/security review gate. These must be designed and approved before the first live send.
Later
- Automated or API-based DRGT data transportCadence, format, secure transfer method and operational ownership need to be agreed with Bonana and Casino Operations. A phase-two decision after the CSV route is validated.
- Production Lightspeed F&B point-of-sale integrationThe exact Lightspeed product family and series are unknown. Production integration cannot begin until the family/series, API entitlement and scanner flow are confirmed.
- Mews hotel system connectionHotel-stay data adds valuable cross-venue context. Include after the F&B loop is proven and the hotel use case is scoped with Bonana.
- Events and entertainment venue coverageEvents were discussed as a possible first-scope addition but were not confirmed. Include after F&B proof and once the events-venue operations are validated.
- Multi-language campaign and acceptance pagesFrench, German and English requirements for the first communication are still to be confirmed. Language expansion follows once the English-first loop is proven.
Out of scope
- Replacing DR Gaming Technology as the gaming system or gaming-analytics sourceDRGT is explicitly the confirmed gaming source and segmentation engine. HubSpot is the communication and offer-lifecycle layer, not a gaming platform.
- Using casino loyalty points at non-casino points of saleThe casino loyalty card is subject to a stated legal constraint that prevents cross-POS points collection or redemption. This boundary is not changed by this scope.
- Requiring guests to install an app for any part of the voucher journeyThe customer explicitly required that guests do not need to install an app. Browser-based QR acceptance is the confirmed model.
First outcome
How it works
The first campaign follows six steps. Each has a defined owner and a visible handoff point.
- 1
DRGT selects the campaign audience
Casino Operations uses DRGT to identify qualifying guests — by visit behaviour, gaming activity or segment. DRGT is the qualifying and segmentation source; no gaming behaviour data travels with the handoff.
Recorded outcomeA validated audience list with Player/Unique ID, identity fields, campaign identifier and offer validity period is ready for export.
- 2
Casino Ops exports a minimal CSV to HubSpot
The phase-one transport is a minimal CSV export. Fields include Player/Unique ID, first name, last name, email address, campaign identifier and validity period. Duplicate detection and consent checks run before the campaign activates.
Recorded outcomeContacts are created or updated in HubSpot. The audience is ready for the campaign with consent confirmed.
- 3
HubSpot sends the personalised voucher email
Marketing runs the campaign from HubSpot. The guest receives a personalised invitation with the offer details and an acceptance link. Only consenting contacts within their validity period receive the message.
Recorded outcomeDelivery, open and click rates are visible in HubSpot from the moment the send begins.
- 4
Guest accepts on any browser — no app required
The acceptance link opens in the guest's browser. Keyring records the acceptance, generates a QR code and displays it in the browser wallet. The guest can return to this page at any time during the validity period.
Recorded outcomeAcceptance is recorded in HubSpot and the voucher status updates from sent to accepted.
- 5
Staff redeems the voucher by scanning the QR
At the venue, a staff member opens the redemption page on a phone or browser and scans the guest's QR. Keyring validates the code, prevents duplicate redemption and confirms the result. No dedicated hardware required for phase one.
Recorded outcomeThe voucher is marked redeemed in Keyring. The result returns to HubSpot and the funnel record updates from accepted to redeemed.
- 6
HubSpot closes the loop and prepares the next decision
Marketing reviews the complete funnel — selected, sent, accepted, redeemed, expired and non-redeemed — in one HubSpot view. Redemption data, acceptance rate and funnel shape become the evidence base for the next campaign and for the Lightspeed integration decision.
Recorded outcomeThe first campaign cycle is complete. The evidence register for all subsequent platform decisions is open.
Operating model
Who runs the loop
The phase-one operating loop crosses four functions. Each owns a defined stage; the handoff between them must be explicit and agreed before launch.
System landscape
Roles, not assumptions
Five systems are involved across the proposed scope. Validation status reflects the current evidence boundary.
DR Gaming Technology (DRGT)
ConfirmedThe gaming system of record. Owns player identification, gaming analytics, segmentation and campaign qualification. Supplies the audience for every HubSpot campaign. Not replaced or extended in this scope.
DirectionExports minimal audience CSV to HubSpot (phase one). Direct API transport is a later decision after the CSV route is validated.
HubSpot
ProposedCommunication, campaign orchestration and voucher lifecycle visibility. Receives the audience from DRGT, sends the personalised offer, tracks acceptance and redemption, and hosts the funnel view for marketing. HubSpot Professional is a working assumption; tier and entitlement to validate with Bonana.
DirectionReceives DRGT audience data; sends personalised email; records Keyring voucher acceptance and redemption events
Keyring
ProposedThe voucher-layer application. Issues the digital voucher, serves the browser acceptance page (no app required), validates the staff QR scan, prevents duplicate redemption and returns the confirmed result to HubSpot.
DirectionIssues vouchers triggered by HubSpot campaign; redemption confirmation returns to HubSpot lifecycle record
Lightspeed (F&B point of sale)
LaterThe restaurant and beverage point-of-sale system. Lightspeed is confirmed as the vendor; the exact product family and series are not yet known. Production integration with Keyring is not part of phase one and must not be assumed until the family, API entitlement and scanner flow are confirmed.
DirectionPhase one: none. Later phase: to validate once product family and API access are confirmed.
Mews (hotel)
LaterThe hotel property management system. A HubSpot connection incorporating hotel-stay data into cross-venue personalisation is a later-phase possibility after the F&B loop is proven.
DirectionPhase one: none. Later phase: hotel-stay signals to HubSpot for cross-venue personalisation.
Value case
How value will be proven
Four value mechanisms are identified. Campaign effort savings and redemption economics are directional because no current baseline has been confirmed. ROI is not calculated: implementation cost, quantified benefit and the selected scenario are all outstanding inputs.
Campaign cycle time — from audience qualification to first email sent
Directional- Baseline
- Not captured. The team described the current manual process as time-consuming with multiple handoff steps.
- Target
- To be set with the marketing team once the first automated cycle is completed and timed.
- Unit / period
- Hours per campaign
- Method
- Time log of the current manual process compared to the first automated run. Owner: Marketing and Casino Operations, agreed before launch.
Voucher acceptance rate — offers sent that the guest accepts
TBC- Baseline
- No comparable digital campaign has run. No prior acceptance-rate data exists.
- Target
- To be established after the first campaign. External hospitality benchmarks exist but are not used as customer forecasts.
- Unit / period
- Percentage of vouchers sent
- Method
- HubSpot voucher funnel: accepted ÷ sent. First live campaign result becomes the baseline for all subsequent campaigns.
Voucher redemption rate — accepted offers that are redeemed at the venue
TBC- Baseline
- No prior cross-venue digital redemption data exists.
- Target
- To be established after the first campaign.
- Unit / period
- Percentage of accepted vouchers
- Method
- HubSpot voucher funnel: redeemed ÷ accepted. Redemption confirmation arrives automatically from Keyring.
Guest dataset for cross-venue personalisation
Directional- Baseline
- Currently zero cross-venue digital guest interactions are tracked in a shared system.
- Target
- After step one, Casino 2000 will have a growing, consent-gated guest dataset that can support Lightspeed integration scoping, Mews personalisation and event segmentation.
- Unit / period
- Consented contacts with at least one recorded cross-venue voucher interaction
- Method
- Assessed after the first campaign: dataset size, consent coverage, data quality and readiness for the next integration decision.
Economic case
Options considered
Three paths are available. One is recommended as the best balance of simplicity, evidence and platform value.
Continue as today
Keep DRGT as the only campaign tool; continue manual exports and communication through separate systems. No HubSpot investment.
BenefitsNo change in cost or process. No new system, partner or legal/security review required.
Trade-offsCasino 2000 continues to under-contact qualifying guests. The cross-venue redemption gap remains. No feedback loop is created. The loyalty-card constraint is not bridged for restaurant, hotel or event guests.
Phase one — minimal voucher loop (recommended)
One DRGT CSV handoff, one HubSpot campaign, Keyring voucher lifecycle and browser-based QR redemption. No production POS integration. Available on 12 or 36-month terms.
BenefitsProves the end-to-end loop with the lowest possible implementation risk. DRGT stays in control. No app required. The first campaign data informs every subsequent decision — Lightspeed, Mews, retention, scale — without committing to those decisions now.
Trade-offsRequires Bonana for implementation, a legal/security review and a GDPR-compliant operating design before launch. Does not immediately solve the F&B POS feedback gap — that requires a later Lightspeed integration. The CSV handoff is a manual step until the API transport is designed in a later phase.
Full scope — communications, F&B and events (36 months)
A broader scope covering restaurant, events and hotel across a wider set of HubSpot hubs, including production Lightspeed and Mews integration.
BenefitsDelivers more of the cross-venue platform vision in one commercial decision. Avoids a mid-term scope-expansion conversation once the team is confident in the platform.
Trade-offsCannot be scoped or priced until the Lightspeed product family, API entitlement, Mews integration design and events-venue requirements are all confirmed. Higher upfront and recurring cost. Higher implementation complexity while the platform and the team are both new to the tools. The customer explicitly asked for step one to be as simple as possible.
Management case
Risks and mitigations
Five risks require active management before or during implementation.
Lightspeed product family and series are unknown. Restaurant K-Series is an unconfirmed working hypothesis. Production POS integration design cannot begin until the exact family, API entitlement, scanner behaviour and accounting representation are confirmed.
Ask Casino 2000 to identify the Lightspeed product: app name, Back Office URL, enabled Web Extensions and scanner hardware. Run a Web Extension UAT only after confirmation. Phase one is independent of this decision.
Bonana has been introduced as the implementation partner but its discovery scope, responsibilities and commercial agreement are not confirmed. Implementation cannot be baselined or priced without a partner scoping workshop.
Authorise Bonana to run a discovery workshop immediately after scenario selection. Agree scope, responsibilities and delivery timeline before contracting begins.
Legal and information-security reviewers have not been named. Recorded objections include US subprocessors, AI/data use, third-party access, vendor reliability and data retention. None of these can be closed without a named reviewer and a formal review process.
Name the legal and security reviewers as the first commitment after scenario selection. Share the DPA and data documentation immediately. Do not deploy to production without a written legal review outcome.
No quantified baseline for campaign effort, voucher economics or redemption rate exists. Without a baseline, the investment cannot be compared to a return and the success threshold for the first campaign is undefined.
Log the steps and time in the current manual campaign cycle before the first automated run. Define the minimum acceptable acceptance and redemption rate as a go/no-go criterion with the marketing team and Bonana before launch.
A feature-heavy or technically complex solution will undermine team confidence. Casino 2000 stated explicitly that the discussion became too complex and that step one must be as simple as possible.
Restrict phase-one delivery strictly to the agreed minimal scope. Present only the phase-one journey at the September walkthrough. Keep architecture and expansion discussion for a separate session after commercial sign-off.
Delivery
Plan and ownership
The delivery path is gated by the September review. No milestone below is a commitment until scenario selection, partner authorisation and legal/security decisions are made.
Commercial scenario review — team reviews three proposals and selects a scenario
ProposedSeptember 2026
Dependency / exit criterionCustomer team available after August period
OwnerCasino 2000 (Sandra, Marie, Joffrey) / HubSpot (Bas, Willem)
Legal and information-security reviewers named; DPA and data documentation shared with them
ProposedSeptember 2026
Dependency / exit criterionScenario selection
OwnerCasino 2000
Bonana discovery workshop — scope, responsibilities, implementation cost and timeline agreed
ProposedSeptember / October 2026
Dependency / exit criterionScenario selection and Bonana formally authorised
OwnerBonana / HubSpot / Casino 2000
Legal and security review complete; data handling and retention design signed off
TBCOctober 2026 (target)
Dependency / exit criterionReviewers named; documentation reviewed
OwnerCasino 2000 legal/security (reviewer TBC) / HubSpot
General management approval and contract signed
TBCOctober / November 2026 (target)
Dependency / exit criterionLegal review and Bonana scope complete
OwnerCasino 2000 general management / HubSpot deal owner
Phase-one build: HubSpot configuration, Keyring setup, CSV import validation, consent and retention design, staff redemption flow tested end-to-end
TBCAfter contract (target)
Dependency / exit criterionContract signed; baseline measurement plan agreed before the first send
OwnerBonana / Casino 2000 Marketing / HubSpot
First live campaign: one DRGT-selected audience, one dinner voucher, full redemption loop from send to HubSpot confirmation
TBCAfter build (target)
Dependency / exit criterionBuild complete; legal approval granted; staff trained and redemption controls tested
OwnerMarketing and Casino Operations
Decision
Select the preferred commercial scenario (phase one on 12 or 36 months, or full scope on 36 months), authorise Bonana to run a discovery and scoping workshop, and name the legal and information-security reviewers. These three decisions unblock all implementation, legal and partner-scoping work.
After the September scenario review, HubSpot will walk through the selected option, Bonana will run a discovery workshop to scope implementation, and the named legal/security reviewers will receive the DPA and data documentation. General management approval and contract signature follow those three gates.
Confirm the review dateQuestions
Frequently asked questions
Is HubSpot replacing DR Gaming Technology?
No. DRGT remains the gaming system of record, the source of player data and the segmentation engine. HubSpot receives only the fields needed to send the campaign and track the voucher lifecycle. Detailed gaming data stays in DRGT and the data warehouse.
Does the guest need to install an app to use the voucher?
No. The guest accepts the voucher on any smartphone browser using the link in the email. Keyring serves the acceptance page and QR code without requiring an app download. Staff validate using a phone or browser — no dedicated hardware is required for the phase-one experience.
Why can the casino loyalty card not cover restaurant or hotel rewards?
Casino 2000 confirmed a legal constraint: the casino loyalty card cannot be used to earn or redeem points at restaurants, bars, the hotel or events. The voucher and QR model proposed here provides a complementary cross-venue recognition channel that does not use or modify the casino-loyalty mechanism.
What happens to non-redeemed or expired vouchers?
The final retention rule is an open question requiring legal/privacy review. During the demo, expired and non-redeemed vouchers are hidden from the default guest view without deleting the record. The decision on whether to retain, anonymise or delete them after the validity period will be confirmed as part of the GDPR and legal/security review.