Start from a kit. Not a blank page.
Each kit names the systems we connect first, the first three outcomes and what you keep. Our team starts from the kit and adapts it to your systems.
Priced to the outcome. Scope and price are agreed before work begins. No per-seat fees.
5 KITS · ONE PER INDUSTRY
- 01Sales & service businesses3 OUTCOMES · 4 SYSTEMS
- 02E-commerce3 OUTCOMES · 4 SYSTEMS
- 03Retail & malls3 OUTCOMES · 4 SYSTEMS
- 04Hospitality3 OUTCOMES · 4 SYSTEMS
- 05Logistics3 OUTCOMES · 4 SYSTEMS
A starting scope, adapted to the systems you run.
A starting scope, not a template. Our team adapts every kit to your systems.
Kits are how our team starts a build. They are not a ready-made setup inside the Glue Console. Swap any system for one you run. Change any outcome to fit your question.
Who it's for
The business it fits, in one line.
Systems we connect first
Named as sources. Each links to how it connects.
The first three outcomes
Written as rules DataGlue can count, in plain words.
What you have after
What your team keeps when the build is done.
KIT 01OUR CORE
Sales & service businesses
For sales-led businesses that win clients through calls, proposals and signed contracts.
SYSTEMS WE USUALLY CONNECT FIRST
Your website
Visits, forms and UTM tags, recorded by Stick on your own domain.
Ad platforms
The ad click ID on each landing page. Spend by campaign through your warehouse.
Booking
Discovery calls and review meetings, as they are booked.
CRM
Contacts, proposals, signed contracts and renewals.
FIRST THREE OUTCOMES
EXAMPLE RULESPricing read, then a call booked
Pricing page viewed, then discovery call booked within 30 days, for the same person.
See which visits turn into conversations, and where those visitors came from.
Proposals still waiting
Proposal sent, and no contract signed yet, for the same client.
Your team follows up while the proposal is still fresh.
Clients who came back
Contract signed, at least 2 times in the last 365 days, for the same client.
See where your returning clients first came from.
Your event names, windows and matching are agreed in the build.
AFTER THE BUILD, YOU HAVE
One history per client. Website visits, ad clicks, bookings and CRM records, joined only where they clearly match.
Three outcomes, live. Counted in your Glue Console. Each count opens to the records behind it.
The path to each contract. The visits and calls recorded before each signature, in the order they happened.
A Glue Console your team keeps. Build the next outcome on the same records. With Workspace AI on, ask in plain English.
KIT 02
E-commerce
For online stores that want more first orders to turn into repeat orders.
SYSTEMS WE USUALLY CONNECT FIRST
Your store
Orders, refunds and customer accounts. Storefront visits come in through Stick.
Ad platforms
The ad click ID on each landing page, so each visit keeps its campaign.
Email
Recorded opens and clicks on the messages you send.
KlaviyoMailchimpCustomer.ioMore in Email and marketing automation
Support desk
Tickets and the orders they mention.
FIRST THREE OUTCOMES
EXAMPLE RULESAd clicks that became orders
Visit from a paid ad, then paid order within 7 days, for the same customer.
See which campaigns bring paying customers, not just visits.
Repeat customers
Paid order, at least 2 times in the last 45 days, for the same customer.
Know who already buys from you before the next message goes out.
Kept after a return
Item returned, then paid order within 30 days, for the same customer.
See which customers stay after a return.
Your event names, windows and matching are agreed in the build.
AFTER THE BUILD, YOU HAVE
One history per customer. Visits, orders, returns, messages and tickets, joined only where they clearly match.
Three outcomes, live. Counted in your Glue Console. Each count opens to the records behind it.
Refunds stay visible. Returns and refunds sit on each customer's record, beside the reorder.
A Glue Console your team keeps. Build the next outcome on the same records. With Workspace AI on, ask in plain English.
KIT 03
Retail & malls
For stores and shopping centres that want to know their regulars, at the till and online.
SYSTEMS WE USUALLY CONNECT FIRST
Tills and POS
Receipts, items and the loyalty card used at the till.
Loyalty
Members, points and the rewards they use.
Your online store
Product views and online orders. Visits come in through Stick.
Cameras and footfall
Visit totals by store. A plate links to a member only with consent, such as loyalty parking.
People and footfall countersNumber plate recognition (ANPR / LPR)More in Cameras and footfall
FIRST THREE OUTCOMES
EXAMPLE RULESBrowsed online, then bought in store
Product page viewed, then in-store purchase within 30 days, for the same member.
See which online browsing ends at the till.
Your regulars
In-store purchase, at least 4 times in the last 30 days, for the same member.
Know your regulars before they reach the till.
Back after a reward
Reward used, then in-store purchase within 7 days, for the same member.
See whether a reward brings people back.
A purchase counts for a member when their loyalty card is used. Your event names, windows and matching are agreed in the build.
AFTER THE BUILD, YOU HAVE
One history per member. Till receipts, loyalty and online visits, joined through the member's loyalty account.
Three outcomes, live. Counted in your Glue Console. Each count opens to the records behind it.
Counts stay counts. Footfall describes a place, not a person. It never joins a member's record.
A Glue Console your team keeps. Build the next outcome on the same records. With Workspace AI on, ask in plain English.
KIT 04
Hospitality
For restaurants, bars and hotels that want guests to come back, and to be known when they do.
SYSTEMS WE USUALLY CONNECT FIRST
Reservations
Bookings, covers and guest records.
Tills and POS
Bills, dishes and drinks.
QR ordering
Table orders, with a guest ID where the guest gives one.
Loyalty
Check-ins, points and the rewards guests use.
FIRST THREE OUTCOMES
EXAMPLE RULESGuests who book again
Bill paid, then new booking within 30 days, for the same guest.
See which guests book again after a visit.
Your regulars
Bill paid, at least 3 times in the last 30 days, for the same guest.
Know your regulars before they sit down.
Booked again after a reward
Reward used, then new booking within 14 days, for the same guest.
See whether a reward brings a booking.
Your event names, windows and matching are agreed in the build.
AFTER THE BUILD, YOU HAVE
One history per guest. Bookings, bills, table orders and loyalty, linked by loyalty number or booking email.
Three outcomes, live. Counted in your Glue Console. Each count opens to the records behind it.
Anonymous orders stay anonymous. A shared table never makes every guest at it the same person.
A Glue Console your team keeps. Build the next outcome on the same records. With Workspace AI on, ask in plain English.
KIT 05
Logistics
For carriers and delivery teams that want to see a late run before the account review.
SYSTEMS WE USUALLY CONNECT FIRST
GPS and telematics
Vehicle positions, arrivals and route IDs.
Temperature sensors
Readings and breaches, with vehicle or shipment IDs.
Delivery and dispatch
Scheduled drops, scans and signatures, sent from your delivery app.
CRM
Customer accounts, contracts and logged complaints.
FIRST THREE OUTCOMES
EXAMPLE RULESLate runs that became complaints
Late delivery, then complaint logged within 7 days, for the same account.
Your account manager can follow up with the delays and complaint in view.
Accounts with repeat delays
Late delivery, at least 2 times in the last 14 days, for the same account.
See which accounts feel the delays before the contract review.
Signed for, then disputed
Delivery signed for, then dispute raised within 7 days, for the same order.
Open each dispute to the scans and signature behind it.
A late delivery is one your delivery app records as late. Your event names, windows and matching are agreed in the build.
AFTER THE BUILD, YOU HAVE
One view per account. Runs, scans, sensor readings and complaints, joined through delivery and run numbers.
Three outcomes, live. Counted in your Glue Console. Each count opens to the records behind it.
Vehicles keep their own records. Runs, vehicles and orders keep their own identity. People join only through a shared ID.
A Glue Console your team keeps. Build the next outcome on the same records. With Workspace AI on, ask in plain English.
A kit saves you the blank page. Your systems and your question shape the rest.
How a kit becomes your build. The same three steps as every engagement.
Bring one question.
Pick the kit nearest your business, or start from the question alone.
We glue the systems behind it.
We swap any system you don't run for one you do, and fit the outcomes to your question.
Your team, tools and AI act on the answer.
The first outcomes go live in your Glue Console, and every count opens to its records.
Every kit is scoped to your systems. Priced to the outcome. Scope and price are agreed before work begins. No per-seat fees. See how an engagement runs
One open route for results. Results leave through a signed webhook to any compatible HTTPS endpoint. Read results through our API, ask from an AI assistant that supports MCP, or export on request.
No kit for your industry? Bring the question anyway.
Real estate, financial services, defence and mining builds start from your question and a map of your systems.
Bring the question your team is stuck on.
Talk it through with the people who would build it. You’ll leave with a straight answer on fit.
The call is about fit. Any build is a separate engagement, priced before work begins.
Book a call
Send a few details. We reply to set a time.
Talk it through
With the people who would build it. No access needed.
Hear if it fits
A straight answer. If we’re not the right team, we’ll say so.
We don't do sales calls. We take a deep look at how your systems fit together. Bring the decision your team is stuck on.