CIRCUIT
Circuit
Log in

Enterprise · POS stays. The moment of capture moves.

Close the in-store identity gap.

Retail retention sits below 35%. Two in three guests never come back, and your tools cannot identify the ones who do.

Blocks are physical consent boxes for brand-led community programming.

Tap one to check in. The wall remembers. One-off attendees become regulars. The data is opt-in and first-party: who returns, which programmes work, who’s part of the community.

The most valuable customers are the ones who keep coming back.

The hardest part of retail is identifying them. A third of guests walk out as silhouettes. The friction at POS keeps the door shut on the people you most need to see.

POS opt-in · year on year
YearIn-store opt-in202252%202344%202438%2025 (run rate)31%

A third of guests walk out as silhouettes

The guest your CRM already knows.

Circuit puts a single tap target at the entrance to your event, class, run club, or store activation, and the guest who walks in becomes the guest your CRM already knows: identity, history, recency, frequency, plumbed into the CDP you already run. Hightouch, Klaviyo, Braze, or Salesforce Marketing Cloud.

Run club · 12 weeks
Sessions36
Distinct guests412
Bound to CRM321 · 78%
Returning ≥3147
Re-engagement queuedon cadence

Programming becomes the record.

The community programming your retention team is running becomes the record your acquisition team has been waiting for. After 100 writes it describes return rate, core-member status, cross-location attendance depth. Relationships no export reconstructs.

Programming · what surfaces
TeamSurfaceRetentionCohort dashboardsAcquisitionActivation listStore opsDoor viewBrandLoop story

Same record · four reading positions

Identity. Value exchange. Activation. In that order.

The sequence the loop runs on. Identify the guest at the door. Give them something for being known. Send the activation back to the store that captured them. Skip a step and the loop breaks.

The sequence · what runs where
SequenceWhat it isCircuitIdentityCapture at the doorBlock tapValue exchangeRecognition + Digital StubEmail · stubActivationSend to capturing storeRecord · dashboard

Skip a step · loop breaks

How the pilot runs.

  1. 01

    Days 1–30

    Deploy. Hardware installed at venue, store, or activation space. First event runs. Block taps captured at the door. No POS friction, no app download, no opt-in form.

  2. 02

    Days 31–60

    Integrate. Data flows into the CDP you already run. Recognition email goes out. Community engagement reports surface.

  3. 03

    Days 61–90

    Decide. ROI readout. Attendance frequency to LTV correlation, by venue, by guest. Expand to the rest of the estate, or end. Decided at 90.

Run club · Tue 18:30Door + CRM
MemberVisitCRML. Okafor6tier 2M. Schreiber4tier 1A. Vasquez2tier 1unknown1enrol?

Recency, frequency, event mix · per-member

Annual contract. Hardware and integration included.

Book a pilot conversation