TRV-2026-1904Certified recordPeer-reviewed

The role of AI robotics and marketing execution capabilities in B2B value realization and accumulation under technological uncertainty

Purpose This study aims to examine how artificial intelligence (AI) robotics capability is associated with customer value realization (CVR) and brand value (BV) in business-to-business (B2B) markets, and whether marketing execution capability (MEC) explains these relationships under technological uncertainty. Design/methodology/approach Drawing on the resource-based view and resource orchestration perspectives, this study uses unbalanced panel data from 234 Chinese B2B firms (2011–2022). AI-enabled robotics capa…

Business · The Trace — both readings · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

Among Chinese B2B firms, AI robotics capability's value potential is realized when firms can execute, coordinate and deliver AI-enabled offerings through marketing execution capability, raising customer value realization and brand value.

Current reading — problem

AI robotics capability alone shows no automatic direct association with customer value realization or brand value, and technological uncertainty weakens its link to marketing execution capability.

What this doesn’t fix

The evidence comes from Chinese B2B firms and uses patent data as the measure of AI robotics capability, and the findings are described as associations, so causality and generalization are not established.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1904, v1: “The role of AI robotics and marketing execution capabilities in B2B value realization and accumulation under technological uncertainty.” Truvace, 2026-10-19. /record/TRV-2026-1904 (accessed at citation time). sha256 b37cb920bc9417b7…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1b37cb920bc94…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1904 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.