DataGlue
PRICING

Built around your business.
Priced to your scope.

For mid-sized and large organisations connecting customer data across teams and systems. Talk to us about your requirements for a tailored proposal.

Scope and price agreed before work begins. No per-seat fees.

A proposal for your organisation

Contact us

Your outcomes, source systems and implementation requirements shape the engagement.

  • Start with the decision and its business owner.
  • Map the systems and records it needs.
  • Agree the scope, delivery phases and price.

Platform access and implementation are discussed with our team. Bring your requirements to the conversation.

YOUR SCOPE · BEFORE THE BUILD

Know what we’re building before we begin.

One decision, its owner, the data behind it and how you’ll judge success. The architecture review gives you a clear view of what the build involves.

Priced to the outcome. Scope and price are agreed before work begins. No per-seat fees.

See what you keep

For a head start, see the starter kit for your industry: the systems and first outcomes we usually begin with.

Example engagement scope, agreed before work begins.
ENGAGEMENT SCOPEEXAMPLE
DECISION
Which steps come before a deal is signed?
OWNER
Head of revenue
SOURCES
  • CRM
  • WEBSITE
  • SALES CALLS
  • EMAIL
  • PAYMENTS
  • FORMS
  • ADS
SUCCESS
One answer leaders can check, row by row
FIRST RESULT
Live in your Glue Console
PRICE
Priced to the outcome
NO RATE CARD · NO PER-SEAT FEESAGREED BEFORE WORK BEGINS

A tailored proposal

What shapes the scope and price?

For a mid-sized or large organisation, the useful starting point is the decision, its systems and the work required to make the answer dependable.

Bring what you already know. The first conversation checks fit; the architecture review works through the detail. Scope and price are agreed before work begins.

Prepare a brief for your team
The decision and its definition
The first outcome, the person who owns it and the examples your team will use to check the answer. Matching rules and unresolved definitions affect the work involved.
The systems and the records
Source access, connection routes, available history, record volumes and how current the answer needs to be. We discuss the route for each source in your scope.
The people and the rollout
The teams using the result, who can approve source access and the phases you want to consider. Start with a defined use case and discuss additional scope separately.
Your operating requirements
Bring your data handling, security review, procurement, support and ownership requirements. Ask us to set out what is included and any dependencies before you proceed.
WHAT YOU KEEP · AFTER THE BUILD

What’s yours when we’re done. The Console, the joined records, your rules and your data.

The build ends with things your team owns, not a report we hand over. Keep asking, keep checking, and build the next outcome on the same records.

GLUE CONSOLE · OUTCOMESDEMO
DEAL SIGNED12 peopleSEE THE ROWS
  • SARAH CHENCall booked, Day 10 · Deal signed, Day 23CONFIRMED
  • MASKEDCall booked · Proposal sent · Deal signedCONFIRMED
  • MASKEDCall booked · Deal signedCANDIDATE
SHOWING 3 OF 12
Explore the Glue Console
WHAT YOU KEEP
  1. 01

    Your Glue Console.

    Open any count to see the records behind it. Findings rank what needs a decision. With Workspace AI on, ask in plain English and see what the answer read.

  2. 02

    One view of each customer.

    Your systems, joined around each person. Each link is marked confirmed, possible or in conflict. Only exact matches, such as the same email, join on their own.

  3. 03

    Outcomes in plain English.

    Each one shows how it counts, in plain English, and the records behind the number. The next outcome builds on the same records.

  4. 04

    Clean data, sent where you work.

    Where the build sets it up, new leads reach your CRM with their source and records reach your warehouse. Use outcomes in any AI tool, report or system you choose. Every send is logged, and a failed row can be retried on its own.

  5. 05

    Your source map and your rules.

    The map from the architecture review, plus your rules for ownership, privacy and quality: what Stick (our site script) collects and masks, and what counts as confirmed.

  6. 06

    Your data, with no lock-in.

    Your systems stay where they are. Your visits, activity and record matches export on request.

We connect what your decision needs. Some systems plug straight in; the rest join through your warehouse or our API. Check your systems: 148 listed, each with how it connects.

HOW AN ENGAGEMENT RUNS

Five phases. Each one ends with something your team can use.

For each phase: what happens, who does what and what you have at the end. The build starts only once the scope and price are agreed.

  1. Phase 1: Book a call

    Bring one question.

    WHAT HAPPENS

    Talk it through with the people who would build it. We find where its data lives today.

    WE DO
    Ask how the decision is made today and which systems hold each piece of it.
    YOUR TEAM DOES
    Bring the question and the names of the tools behind it. No access needed yet.

    AT THE END, YOU HAVE

    • Where your data breaks
    • The first decision worth building
    • A straight answer on fit
  2. Phase 2: Architecture review

    Map every source behind it.

    WHAT HAPPENS

    We sit with the teams closest to the decision. We map where its data lives, where it disagrees and where it goes missing, then show you what it looks like glued together.

    WE DO
    Map each source and show the decision glued together.
    YOUR TEAM DOES
    Bring the people who know the systems. Name who owns the decision and how you’ll judge success.

    AT THE END, YOU HAVE

    • One decision, written down, with its owner
    • A map of every source behind it
    • The scope and price, agreed before work begins
  3. Phase 3: Build together

    We connect the pieces.

    WHAT HAPPENS

    Our team finds the records that matter and joins them into one view of each customer. Records join only where they clearly match. Your systems stay where they are.

    WE DO
    Connect your systems, join the records and show why each match was made.
    YOUR TEAM DOES
    Open access to the systems. Set the rules for ownership, privacy and quality.

    AT THE END, YOU HAVE

    • The data behind your decision, joined
    • Every match marked confirmed, possible or in conflict
    • The source on every recorded step
  4. Phase 4: Go live

    Your first result, ready to use.

    WHAT HAPPENS

    We take the first result live in your Glue Console. Open any count to see the records behind it. With Workspace AI on, ask in plain English and see what the answer read.

    WE DO
    Take the first result live in your Glue Console.
    YOUR TEAM DOES
    Check the records behind the answer, then decide.

    AT THE END, YOU HAVE

    • Your first result, live
    • Counts that open to their records
    • Answers that show what they read
  5. Phase 5: Keep building

    The next outcome reuses what you built.

    WHAT HAPPENS

    We roll out in phases, each measured against the outcome. Each new outcome starts from the systems and matches you already have.

    WE DO
    Build the next outcome with you.
    YOUR TEAM DOES
    Own the decision and choose what comes next.

    AT THE END, YOU HAVE

    • A Glue Console your team keeps
    • A shared record you can keep asking
    • Each phase measured against the outcome

The call is about fit. Any build is a separate engagement, priced before work begins.

QUESTIONS

Straight answers before the call. On pricing, your scope, data and implementation.

Your setup, your questions.

Bring them to the call. That’s what it’s for.

Getting started

What happens after I book?
We reply to the email you gave us to set a time. On the call, you talk the decision through with the people who would build it. We find where its data lives today and give you a straight answer on fit. If it fits, the next step is an architecture review.
Do we need a data team, a warehouse or clean data first?
No. Messy data is where we start. If your CRM history isn’t in a warehouse yet, getting it there is part of the build. A dedicated team does the gluing. Your team names the decision and decides.
What happens in an Outcome Build?
We start with one decision and how you’ll judge success. We map every source behind it, join the records only where they clearly match and take the first result live in a Glue Console your team keeps. The next outcome builds on the same joined records. Think of it as a data team, without hiring one.
How long does a build take?
It depends on the decision and the systems behind it. You get the scope and the plan before work begins. The build runs in phases, each measured against the outcome.

Data and trust

Do we have to move our data?
No. Your systems stay where they are. We connect what the decision needs: natively where we can, through your warehouse or our API where we can’t.
Which kinds of systems can you connect?
Stick captures activity on your site and web app. Booking and email platforms, your CRM, Postgres, webhooks and our REST API can contribute the records behind an outcome. App installs, store visits, drive-through orders and car park events can join when your systems record them. Before we promise a joined-up journey, we check what each source records, what consent covers and which details link people.
How do you match people across systems?
On details you already trust: emails, accounts and customer IDs. Website profiles that share an email merge on their own. CRM records never join a profile silently. Each link is marked confirmed, possible or in conflict.
What does Stick collect, and what does it leave out?
Stick records visits, forms, clicks and page speed on your site, served from your own domain, and reads ad click ids from the landing page URL. It skips password, card, government ID and health fields, and session replay masks what people type, by default. Consent modes, masking and an on or off switch for each signal sit with you, with an audit trail.
Where does our data sit, and who can see it?
In DataGlue’s cloud, with roles, an admin audit log and API keys limited to what each one needs. Records can also be copied into your own warehouse, where an Outcome Build sets that up.
What happens if we leave?
Your data stays yours. Your visits, activity and record matches export on request. Whatever an Outcome Build already copies to your warehouse stays there.

AI

Which AI model does it use?
Ask AI in the Glue Console runs on one model that we set up and run for you, so there’s no model to pick and no key to bring. It works once Workspace AI is on. If your team already works in its own AI tools, we can bring the context into them as part of an Outcome Build.
Will it make up numbers?
It shows its work: every step shows what it read. Every count in Outcomes opens to the records behind it, so your team checks before acting.
Why not connect our systems straight to an AI assistant?
Connectors give access. They don’t decide which records are one person, or which of three definitions is right. An assistant that reads one system answers with confidence and misses the rest. We do the gluing with you. Then your team asks in the Glue Console. Ask AI reads visits, forms, bookings and emails, and Outcomes count the CRM steps with the records behind them.
Can our own tools read the glued data?
For profiles, events and sessions, yes, through our REST API. Records can also be copied into your warehouse, where an Outcome Build sets that up, and your other tools read them there.

Cost and fit

What does it cost?
Contact us for a tailored proposal. We price the engagement around the outcomes, source systems and implementation scope your organisation needs. Scope and price are agreed before work begins, with no per-seat fees. The first conversation is about fit; any build is a separate engagement.
Do you publish standard plans or a self-service price?
No. We work with mid-sized and large organisations whose systems and implementation requirements vary. Contact us to discuss platform access, the build and the scope of a proposal for your business.
How do we discuss ongoing support and additional work?
Bring your support, rollout and future outcome requirements to the scoping conversation. Ask us to set out the work included in your proposal and any additional scope before you proceed.
Who should be involved in scoping an implementation?
Start with the person who owns the business decision and someone who understands the records behind it. For the architecture review, involve the relevant source-system owners and your data or engineering team. Bring privacy, security, procurement and support requirements early so we can discuss them as part of the proposed scope.
Can we start with one team or outcome?
Yes. Begin with one decision, the sources it needs and the people who will use the answer. Agree how that first result will be checked before expanding the scope. Additional sources, outcomes and rollout phases are discussed with your team and priced before the work begins.
What should we check before expanding the rollout?
Agree the outcome definition, source timing and examples that should or should not qualify. Check the records behind the count, including uncertain matches and missing data. Then use the result in the meeting or workflow it was built for and review it with the person responsible for that decision.
Is DataGlue a service or software?
Both, on purpose. The Glue Console is the platform. Our architecture review is the service: our team maps how your systems fit together, then connects them to it. Use the Console on your own (access is by invitation), or have our team take the first result live with you.
Is this only for sales and marketing?
No. Start wherever one decision is worth real money: revenue, sales, customer service, operations, leadership or AI. The channels behind it come along: call results, the CRM, email, forms, bookings and payments. Support and product data join through your warehouse or our API, as part of the build.
We already have a CDP, a reporting tool or an agency. Do we replace them?
No. Keep them. Each does its own job well. We glue the records one decision needs, and your systems stay where they are. Bring their reports to the call. They show us where the numbers disagree.
Who is it right for?
Mid-sized and large organisations with customer records spread across teams and systems, and a recurring decision that those records need to support. A useful first scope has a business owner and source records your team can check. If one existing tool already answers the question reliably, start by using that capability.
What is the closest comparison?
One shared map of your customers and your business, with many sources joined into it. Some call this an ontology. A dedicated team builds it with you. With Workspace AI on, your team asks it in plain English. Not another dashboard, and not another report.
YOUR NEXT STEP

Let’s scope the right engagement.

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.

  1. Contact us

    Send a few details. We reply to set a time.

  2. Talk it through

    With the people who would build it. No access needed.

  3. 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 do architecture reviews: a deep look at how your systems fit together. Bring the decision your team is stuck on.
Ankit PaliwalFounder, DataGlue