Why is POS or CRM access non-negotiable?

Because the claim we make is a revenue claim. Without ticket-level attribution we could show you behavior rates and no proof that changing them changes anything, which is exactly the position mystery shopping is in.

Do you write anything into our system of record?

Not to transactions, deals or clinical records. Optional writes exist only for LMS learning items and CRM follow-up flags, and only when a customer enables them.

Our POS is a bespoke system with no API. Is that fatal?

No. Scheduled secure file exchange at ticket level is sufficient. We scope this in the first integration session.

What if we cannot integrate before the pilot starts?

Capture can start earlier, but the cohort clock starts when transaction data is flowing. Otherwise the readout at day 45 has behavior movement and no outcome to attach it to.

Platform · Integrations

Live

Behavior data is only useful next to the transaction.

Six categories, with what Gaincraft reads, what it writes, and why each one matters for measurement.

Book a demo See our subprocessors

POS or CRM access is a condition of every pilot. LMS integration is available but never a dependency.

What we connect to, stated plainly.

POS and retail ERP

Gaincraft reads: Tickets, line items, discounts and associate attribution, at transaction level.
Gaincraft writes: Nothing to the transaction record. Gaincraft never writes to your books.
Why it matters for measurement: This is what turns a behavior rate into a dollar figure. Without ticket-level attribution, a missed second-item offer cannot be valued.

CRM and clienteling

Gaincraft reads: Customer history, appointment records, assigned associate and open follow-up tasks.
Gaincraft writes: Coaching outcomes and follow-up verification flags, where you want them.
Why it matters for measurement: It lets Gaincraft check whether a promised call actually happened, rather than treating the promise as the outcome.

DMS for automotive

Gaincraft reads: Deal jackets, gross, F&I product attach and salesperson assignment.
Gaincraft writes: Nothing to the deal record.
Why it matters for measurement: Gross erodes inside a negotiation nobody hears. Deal-level data is how that erosion is tied to a specific behavior in the showroom or the F&I office.

Practice management for optical

Gaincraft reads: Exam and dispensing records, second-pair and lens-upgrade outcomes.
Gaincraft writes: Nothing to the clinical record.
Why it matters for measurement: Attach rate is the whole economic question in optical, and it only becomes measurable next to the dispensing record.

HRMS for rostering

Gaincraft reads: Shift schedules, seat and zone assignment, joiners and leavers.
Gaincraft writes: Nothing.
Why it matters for measurement: The roster is how Gaincraft identifies a speaker without voiceprints, and how shift-aware arming knows when a device may capture.

LMS for delivery

Gaincraft reads: Course completion and curriculum structure.
Gaincraft writes: Daily coaching prompts, clips and behavior assignments as learning items.
Why it matters for measurement: It puts coaching where habit already lives. LMS integration is available but never a dependency — the loop works without it.

The one hard requirement

POS or CRM access, at associate and ticket level, for the pilot period. Attribution is impossible without it. A program that cannot be measured becomes a program that gets cancelled on a feeling, so we do not start one.

In practice

How integration actually goes

Integration scoping is the first working session of a pilot, not an afterthought. We map three things: how a ticket is attributed to an associate, how the roster maps to physical seats, and how the retention window is enforced on both sides.

Most of it is read-only. Gaincraft does not write to your transaction, deal or clinical records, which keeps the security review narrow and keeps your systems of record authoritative.

Where we do write — coaching items into an LMS, follow-up flags into a CRM — it is optional, scoped, and switched on only because a customer asked for it.

Technical detail

The technical detail, in plain language

Access method: API where one exists, otherwise scheduled secure file exchange. Read-only credentials wherever the integration does not need to write.
Granularity required: Associate and ticket level for the pilot period. Store-level aggregates are not sufficient to attribute a behavior to an outcome.
Pilot condition: POS or CRM access is a condition of every pilot. Attribution is impossible without it, and we do not run programs we cannot measure.
LMS posture: Available, never required. If your LMS is where associates already go every morning, we deliver there; otherwise we use your existing messaging channel.
Data minimisation: We take the fields needed for attribution and nothing else. Customer personal data is not required for behavior measurement.
Security review: Subprocessors are published, a DPA is available, and residency can be set to US or India.

FAQ

Questions we get asked

Send us your stack and we will scope it.

Bring your POS, CRM and HRMS names to the call. We will tell you what the integration session looks like.

Book a demo Read the pilot playbook