SHURIQ • Intelligence Briefing • Issue No. 05

Four product names route every SAP services conversation in 2026. TruData’s site names none of them.

The four — Joule, BTP AI Foundation, RISE, GROW — anchor every Tier 1 GSI page and every named mid-tier specialist’s positioning. TruData’s truPath methodology delivers all four. The firm names none on its public surface. The structural cost of that silence is now visible.

TruData Solutions Editorial Brief — v0.4 Prepared for TruData Leadership Shur Creative Partners — May 2026

43% / 39%

SAP AI overtakes 2027 ECC deadline as #1 ERP-strategy driver

34,000

SAP customers using Joule across 35 solutions, 30–40+ agents, 2,400–2,500+ skills

7 / 7

Named SI peers that lead with at least three SAP product names

0 / 0 / 0

Named clients, quoted outcomes, quantified deltas across 9 TruData case studies

Letter from the Editor II

The 2027 ECC deadline has been demoted. As of Q1 2026, 43% of organizations cite SAP’s AI announcements as the lead external factor reshaping their ERP strategy — surpassing the deadline at 39%.^[1] Joule now spans 35 SAP solutions with 30–40+ specialized agents and 2,400–2,500+ skills, used by 34,000 customers.^[2] Clean Core has crossed from principle to mandate. BTP-first is table stakes. The category that TruData competes inside has standardized on a vocabulary the firm has chosen not to use. This brief is timely because the standardization happened; the choice not to follow it is no longer free.

ShurIQ reads TruData from the outside. Public-web evidence — 150+ sources, 9 named GSIs, 5 mid-tier specialists, SAP investor materials, OutSystems case archives, LATAM rate-card publications — combined with an InfraNodus knowledge-graph reading of the firm’s own discourse against the broader SAP services landscape (graph trudata-v04-editorial-brief-2026-05-04, 7 clusters, modularity 0.34). No transcripts. No interviews. The reading is third-party and methodological; this brief is intelligence, not consulting.

The brief does not score TruData’s marketing. It does not measure traffic, leads, or engagement. It reads the shape of the discourse: which clusters connect to which, which concepts carry weight, which words appear where the buyer is looking and which appear where the buyer is not. The findings are structural. The Action Set is editorial. The Score is a relative position, a reading of the firm’s standing inside its category.

The Reframe is one reading. The brief is the start of a conversation, not its conclusion. The Bridge names the question the brief leaves open. The Ask is what makes the next 30 days concrete. If the diagnostic reveals the silence on named SAP products is editorial discipline rather than drift, the brief reverses on its own terms — the move becomes naming the silence, deliberately and selectively, on TruData’s own terms. Either move is more articulate than the current state.

AI dethroned the deadline. 43% of orgs cite SAP AI as the lead ERP-strategy factor in 2026, surpassing the 2027 ECC migration cliff (39%) for the first time.
The category competes on named-product fluency. Every Tier 1 GSI and named mid-tier specialist surveyed leads with at least three of: Joule, BTP AI Foundation, Generative AI Hub, RISE, GROW. TruData’s discourse names none.
The methodology is registered. The methodology is not load-bearing. truPath™ (USPTO 99669810) sits in the smallest cluster of TruData’s discourse graph (5% degree, 4% betweenness). Named everywhere; structurally orphaned.
The wedge that should be TruData’s defense is held by Globant. RISE Expert Level + first SAP AppHaus in Argentina’s Southern Cone + 12-week S/4HANA migration accelerator. The LATAM-nearshore claim is no longer differentiated by geography alone.

— ShurIQ, Shur Creative Partners

TruData carries three legitimate edges — Clean Core, Multishore, Build-then-Run — and refuses to name the SAP products its methodology delivers. In a category that has standardized on named-product fluency, the firm whose methodology produces them has chosen the wrong silence. The work is rhetorical: TruData is the Unnamed-Product Firm, and the move is to name what the methodology already does.

The Reframe — Shur Creative Partners

The Reframe — Why this is the hinge VI

The Reframe rests on a single observable fact and a single causal claim. The fact: every Tier 1 GSI and every named mid-tier specialist in the SAP services category leads its public surface with at least three named SAP products — Joule, BTP AI Foundation, Generative AI Hub, RISE, GROW. TruData’s public discourse names none. The claim: the gap is not an absence of capability. truPath™ is registered (USPTO 99669810). The OutSystems partnership is real. The BTP work is being delivered. The capability ships; the vocabulary that earns category attention does not.

The original Inarticulate Firm framing was diagnostic — it named the symptom. The Reframe goes one layer down to the cause. The firm refuses to name the products. The cost of that refusal is now visible in the graph: three discourse rails that do not connect, a methodology that ranks 6 of 7 in influence, and a competitive landscape that routes around TruData because TruData is not in the rooms where SAP services buyers choose vendors. The remaining sections demonstrate the move. They describe what breaks in the structure as long as the firm keeps the silence in place.

Numbers Spine — The evidence base VII

Eight anchors. Each carries an inline citation tracing back to a primary source. Subsequent sections reference these values without re-citing.

[1]	43% / 39%	Orgs citing SAP AI as the top external factor reshaping ERP strategy in 2026 (43%) — surpassing the 2027 ECC deadline (39%). First time AI is in front. The dethrone.^[1]
[2]	34,000 · 35 · 40+ · 2,400+	SAP Business AI scale, Q1 2026: 34,000 customers, 35 solutions, 30–40+ agents, 2,400–2,500+ skills (source variance across SAP News Q1 2026 release and SAPinsider Apr 2026). Joule is shipping for free what BTP services partners used to bill custom-built. The commoditization.^[2]
[3]	4× – 60×	Scale gap of TruData (~250 multishore est.) vs peer GSIs by SAP-published GSSP certified-individual ranges. Accenture & IBM 15,000+; Capgemini & Deloitte 10,000–15,000; Wipro 5,000–10,000. The selection-set fact.^[3]
[4]	17,000	ECC customers projected still on legacy in 2027 at the current migration rate. The supply-constrained migration window.^[4]
[5]	0 / 0 / 0	Named clients / quoted outcomes / quantified deltas across TruData’s nine published case studies. The evidence density gap.^[5]
[6]	0.34 / 0.72	InfraNodus modularity (medium-low, “too focused”) and top-hub betweenness for sap (5× the next concept). The structural fingerprint of fragmentation.^[6]
[7]	USPTO 99669810	truPath™ trademark application — USPTO serial 99669810, filed February 2026 (intent-to-use, awaiting examination). Most US mid-market SAP shops do not have a federally filed methodology trademark. The asset that exists.^[7]
[8]	~$16–20M / 51–100	Third-party revenue estimate / employee count (Crunchbase / PitchBook / LinkedIn). Site shows 7 offices and “global” footprint — the scale signals contradict.^[8]

The Inflection — Why this is the moment VIII

Three reads of the inflection. The dethrone, the commoditization, and the evidence-density bar — each one sets the price of staying silent through 2027.

The dethrone is real. SAPinsider’s 2026 ERP Migration and Transformation Benchmark put AI in front of the 2027 deadline as the top external factor reshaping ERP strategy. The buyer who routed conversations through migration cost in 2024 now routes them through AI capability. The category vocabulary moved with the buyer. Joule, BTP AI Foundation, Generative AI Hub, SAP Build — these are the words that surface in vendor short-lists. A firm that pitches “AI-Ready by Design” in a market that asks “which Joule scenarios have you shipped” is answering a question no one is asking.

The commoditization is the second-order effect. SAP itself is now shipping for free what BTP partners used to bill as custom AI extension work. A Field Service Management agent that delivers 12.5% increase in dispatcher productivity. A Catalog Optimization Agent that cuts translation time 70%. An SAP Concur expenses agent with 30% reduction in preparation time. The platform is eating the boutique work from above — and the firms still standing in that lane are the ones that publish, in named SAP product vocabulary, what they uniquely deliver beyond what Joule ships out of the box.

The evidence-density bar is the third read. The figure pinned at Anchor 5 sits against a comparison set that has been busy. Hexaware published a 75% TCO reduction across 11 European countries for a print-tech client. IBM published a 150,000-user RISE migration. Capgemini published $1.4M savings and 30% ticket reduction with named outcomes. The evidence density gap is a publishing decision, the cost of which compounds every month the comparison set keeps shipping artifacts and TruData does not.

See the discourse graph — Viewport 01: Network Explorer

Structural Gaps — Five named breaks XI

Five gaps promoted from the discourse graph. Each names two clusters that should bridge in TruData’s public surface and currently do not. The connection is the diagnosis; the prose under each card is the consequence; the bridging concept is the move that closes it.

Critical · Severity 9

Innovation runs on one rail. The engine runs on another.

Bridges · Digital Innovation (BTP / AI / Clean Core / data) ↔ Delivery Model (multishore / nearshore / LATAM / India)

TruData says BTP/AI/Clean Core in one place and US-led / LATAM nearshore / India offshore in another. The graph shows minimal co-occurrence between the two vocabularies. The “AI-Ready by Design” promise and the multishore wedge are running on parallel rails. The buyer reading the site cannot answer the only question that earns the wedge: what specifically does the multishore engine produce on the BTP/AI layer that monolithic-onshore or pure-offshore cannot? The geography needs to do work on the AI layer specifically — the buyer sees no evidence that it does.

Bridging conceptTime-zone-aligned BTP engineering. Concrete artifacts of the LATAM team building AI/BTP extensions during US business hours, with India running 24/7 hardening behind them.

Critical · Severity 9

The named products are missing. So is the room.

Bridges · Digital Innovation (BTP / AI / Clean Core) ↔ Market Tiering (RISE / GROW / partner-tier / SI-vocabulary)

TruData’s discourse never names Joule, BTP AI Foundation, Generative AI Hub, RISE, or GROW. Every Tier 1 GSI and every named mid-tier specialist surveyed leads with at least three of those product names. The graph shows the disconnect as structural: the AI/BTP cluster does not co-occur with the partner-tier vocabulary. This is the structural fingerprint of the Reframe. TruData publishes in clusters where buyers do not route their vendor decisions; buyers route through the named-product / partner-tier vocabulary, and TruData is silent there.

Bridging conceptJoule-grade, mid-market. Explicit naming of SAP’s actual AI products with TruData’s mid-market tier as the qualifier — Joule rollout for the firm too small for Accenture and too complex for a reseller.

Notable · Severity 8

Methodology is named everywhere. Nowhere is it load-bearing.

Bridges · Brand Methodology (truPath / case / brand) ↔ everything else

truPath™ should be the spine of the graph — it is TruData’s only proprietary asset and a federally filed trademark. Instead it sits in the smallest, weakest cluster (5% degree, 4% betweenness) connected mainly to case and advantage. The methodology word lives in the brand cluster but does not carry the build / run / optimize / innovate / operate vocabulary into the rest of the discourse. Methodology is named, but not load-bearing. This is what “slogan, not structure” looks like in graph form.

Bridging conceptA diagrammed truPath with the 3-loop frame mapped to the 5 phases mapped to specific deliverables — every phase node carrying a representative artifact (architecture readout, BTP extension repo, hypercare runbook, AMS continuous-innovation backlog).

Notable · Severity 8

Build-then-Run is a claim. The corpus does not show the handoff.

Bridges · Business Transformation (s/4hana / build / run / trudata) ↔ Delivery Model (multishore / India / execution)

TruData’s most concrete differentiator against ticket-taking AMS is Build-then-Run — the claim that the same shore, same team, same architects who build the system also operate it. The graph shows Build-then-Run as a mindset and Multishore as a model, with the path between them — which shore builds, which shore runs, what hands off when — rhetorical rather than structural. The claim is high; the proof is missing.

Bridging conceptContinuity engineering. Specific roles, ratios, and handoff rituals that survive the Transformation→AMS transition. A diagram of one LATAM lead architect carrying forward into AMS Year 1 makes the bridge concrete.

Notable · Severity 7

AMS is sold as innovation. The graph shows it as ticket-taking.

Bridges · Managed Support (managed_services / application / development) ↔ Digital Innovation (btp / ai / data)

TruData claims AMS is “different — outcome-based, continuous innovation, not ticket-taking.” The AMS cluster (the smallest in the graph at 6% degree, 2% betweenness) is graph-distant from the Innovation cluster. Innovation-as-a-Service appears as a phrase rather than a connected concept. The corpus does not show AMS producing innovation. This is the credibility gap on the most-quoted AMS claim.

Bridging conceptQuarterly innovation backlog (governed). Make the AMS-innovation feedback loop a named ritual — cadence, governance body, measurable output (extensions shipped per quarter, business-case-validated AI use cases lit per quarter).

See the gaps in motion — Viewport 02: Gap Radar

Competitive Lens — The seven-by-seven view XIII

TruData read against three Tier 1 GSIs (Accenture, Deloitte, Capgemini), two mid-tier specialists (LTIMindtree, Hexaware), and one LATAM-native (Globant). Seven dimensions selected from the graph readout — the dimensions the graph shows TruData competing on.

Dimension	TruData	Accenture	Deloitte	Capgemini	LTIMindtree	Hexaware	Globant
Named-AI-product depth	Generic only (“agentic AI”, “AI-ready”)	Joule co-eng. + myConcerto + ADVANCE	Joule + boost + Brownfield+ + Selective Trans.	ADMnext + Renewable Enterprise + Mistral AI	Topaz for SAP S/4HANA + 55+ ready-to-deploy GenAI	Amaze® + named platform-led model	G>SAP + RISE Expert Level + AppHaus
RISE / GROW partner status	None visible	Premium Supplier	Premium Supplier (May 2024)	Co-founded BTP Partner Advisory Council	Leader, ISG SAP Ecosystem 2025 RISE	Leader + Rising Star, mid-market 2025	RISE Expert Level + Gold
Methodology legibility	truPath™ named, undiagrammed	myConcerto + ADVANCE diagrammed	Kinetic Enterprise + 4 pillars diagrammed	ADMnext four-track frame	Reimagine + Reimagination Studio	Amaze® + platform-led rhythm	G>Audit360 + G>Launch S4 (12-week)
Multishore narrative	“US-led + LATAM + India” — generic	75,000+ practitioners; LATAM + India CoEs	26,000+ professionals; multi-region delivery	LATAM presence via acquisitions	9,000+ SAP experts; global delivery	Mexico (Monterrey, Saltillo)	First SAP AppHaus in Argentina; 36 countries
Mid-market wedge specificity	“Mid-market” generic	ADVANCE: orgs up to $5B	Generalist enterprise	Generalist	Mid-market + enterprise	“Platform-led” mid-market US healthcare/mfg	Cross-vertical digital
Build-then-Run continuity	Mindset claim, no proof	Ongoing managed services + named clients	boost + AMS continuum	ADM-as-regenerative + 30% ticket reduction	25–30% process efficiency benchmarks	“Migration as managed rhythm” — concrete	12-week S/4HANA migration claim
Evidence density	0 / 0 / 0 across 9 case studies	50+ Pinnacle Awards, named clients	Pinnacle 2016/17/18/20/21, named clients	Capgemini-Mistral named partnership	Tricentis Partner of the Year 2025	75% TCO reduction (named client outcome)	3-5x productivity (named)

What the table makes visible is the dimension TruData has the most permission to claim — Multishore narrative concreteness — and how that claim collapses when read against Globant. Globant has 25+ years of SAP, the SAP AppHaus in Argentina’s Southern Cone, RISE Expert Level, and a published 12-week S/4HANA migration accelerator. The wedge that should be TruData’s structural defense is held by a digital-native firm with a stronger LATAM SAP credential. Every other dimension on the table is held by an entrant that names its products. The pattern is consistent: the SAP services category competes on named-product fluency, named-client outcomes, and diagrammed methodology. TruData competes on slogan, mindset, and method-by-claim. The Reframe is editorial commentary in only the narrowest sense; it is the only honest reading of where the firm actually sits in this table.

See what is missing — Viewport 04: Negative Space Topology

Structural Advantage Score XV

46.5 / 100

Composite SAS — Five dimensions, equal weight

The composite is held back by two of the five dimensions. Named-AI-Product Fluency (37.5) and Evidence Density (42.5) carry a combined 16.0 of a possible 40.0. Both dimensions share a single cause: real engagements and real BTP/AI capability that TruData has not named on the public surface. The recovery move — three named-product audit memos — lifts both dimensions from a single editorial decision.

Named-AI-Product Fluency

37.5 20%

Methodology Legibility

55.0 20%

Evidence Density

42.5 20%

Mid-Market Wedge Specificity

47.5 20%

Multishore Concreteness

50.0 20%

Named-AI-Product Fluency 37.5 / 100

TruData claims “AI-Ready by Design” while the public corpus never names Joule, BTP AI Foundation, Generative AI Hub, SAP Build, RISE, or GROW. Every Tier 1 surveyed names at least three. The Present score is 10 because TruData’s AI vocabulary is generic; the Opportunity is 65 because the underlying capability appears real (truPath, BTP partnership, OutSystems integration), it is just unnamed. Closing this dimension is the single highest-yield move on the composite.

Methodology Legibility 55.0 / 100

truPath™ exists as a federally filed trademark (USPTO 99669810, filed Feb 2026, application pending) — the asset most mid-market shops do not have. Present is 35 because the methodology is named, the loops are described, and the cycle is articulated. Opportunity is 75 because the methodology is not diagrammed: no phase-by-phase artifact map, no role-by-deliverable table, no public reference architecture. The named competitors win this dimension because they show the shape; TruData has the slogan.

Evidence Density 42.5 / 100

The lowest Present score on the table (5). Across nine published case studies: zero named clients, zero quotes, zero quantified outcomes, zero deployed user counts, zero dates. Compare to Hexaware’s 75% TCO reduction (named print-tech client), IBM’s 150,000-user RISE migration, Capgemini’s $1.4M savings + 30% ticket reduction with named outcomes. The Opportunity is 80 because the engagements presumably exist — TruData is delivery-led — they simply have not been written as evidence. The fix is editorial, not capability.

Mid-Market Wedge Specificity 47.5 / 100

TruData’s site uses mid-market as a generic word. The category has fragmented: SMB (sub-$500M revenue, GROW with SAP territory), upper mid-market ($500M–$5B, the ADVANCE-by-Accenture lane), and divisional/subsidiary work inside Fortune 1000 (where TruData’s case studies actually live). Present is 25 because the firm has not yet declared which of these three it serves. Opportunity is 70 because picking one band and making it explicit — “the firm too small for Accenture and too complex for a reseller” — is a positioning move that costs zero capability and gains category clarity.

Multishore Concreteness 50.0 / 100

The wedge that should be TruData’s structural defense. Present is 30 because the multishore claim (“US-led + LATAM nearshore + India offshore”) is real but unparameterized — no public role splits, no time-zone work assignment, no retention metrics, no AI/BTP-specific tasking. Opportunity is 70 because the geography is genuinely advantageous and the LATAM tailwind (USMCA, time-zone overlap, AppHaus precedent) is structural. The fix is to make geography do work on the AI layer specifically — Time-zone-aligned BTP engineering, more than generic nearshore. Globant holds this claim today; TruData can take it back by naming what the LATAM team actually builds.

The Broken Edge

Named-AI-Product Fluency × Evidence Density. Combined contribution: 16.0 of a possible 40.0. The two lowest-Present dimensions form the structural drag on the composite. The 5/100 on Evidence Density and the 10/100 on Named-AI-Product Fluency are independent in framing but share a cause. TruData has the engagements; TruData has the BTP/AI capability. Neither is named. The single editorial move that lifts both is to name what the firm has done to which named SAP product for which named client.

Recovery Move

Publish three named-product audit memos — one truPath loop each (Optimize / Innovate / Operate) — each anchored to a quantified outcome on a named SAP product (Joule / BTP AI Foundation / RISE). This is the single move that, executed once, lifts the broken edge from 16.0 to a projected ~28.0, raising the composite from 46.5 to a projected ~58.5. The work is editorial and disclosure, more than engineering.

See dimensions in motion — Viewport 03: Structural Advantage

Action Set — Five moves TruData owns XVI

Five actions, each closing a named SAS dimension. Sequencing: actions 01 and 03 are unlock moves — lowest cost, highest lift on the broken edge. Sequence them first.

Name the products.

Replace generic AI / BTP / cloud language with the specific SAP product names the methodology already delivers. Joule on the truPath Innovate loop. BTP AI Foundation on the AI extension page. RISE / GROW on the migration pages. SAP Build wherever low-code shows up. Where the firm holds a partner credential (PartnerEdge tier, OutSystems certification), display it. Where it does not, name what it does instead. The cost is editorial; the move is verbal precision.

Closes → Named-AI-Product Fluency

Diagram truPath as artifact.

Convert the three-loop / five-phase methodology into a single diagrammed page. Each phase carries one named deliverable (architecture readout, BTP extension repo, hypercare runbook, AMS continuous-innovation backlog). Each role carries a named seniority and shore. The diagram replaces the cycle metaphor with a load-bearing schematic. Production cost: one designer + one architect, two weeks.

Closes → Methodology Legibility

Re-author three case studies with named clients and quantified outcomes.

Pick three engagements TruData has actually delivered. Get the client release. Write each as: client name + sector + before-state + truPath loop activated + named SAP products / BTP services used + measured outcome (cycle time, TCO, user count, downtime reduction, revenue effect). Three is enough to move the dimension; nine generic studies have not.

Closes → Evidence Density

Declare the mid-market band that’s yours.

Pick one of the three mid-market sub-categories — SMB / upper mid-market / divisional Fortune 1000 — and name it explicitly on the homepage and the services pages. Specify revenue band, headcount band, complexity profile. The line that was: “a high-performance nearshore delivery model” becomes: “the firm for the [revenue band] manufacturer too small for Accenture and too complex for a reseller.” The wedge becomes findable.

Closes → Mid-Market Wedge Specificity

Publish the multishore role-allocation matrix.

Replace “US-led + LATAM nearshore + India offshore” with a named role-by-shore matrix specific to BTP / AI work. Lead architect: LATAM, daytime US. Solution architect: US-onshore, client-facing. BTP developer: LATAM, time-zone-aligned. Hardening / 24/7 ops: India. AMS continuity: same LATAM team that built. Show the AppHaus equivalent — what the LATAM team produces on the AI layer that India alone or onshore alone cannot.

Closes → Multishore Concreteness

Sequencing Actions 01 and 03 are unlock moves — they cost the least and lift the broken edge most. Sequence them first. Actions 02, 04, and 05 are 30–60 day production work and stack on top.

What we ask of you in the next 30 days — access, one decision, one introduction. The Score lifts from 46.5 to 58.5 on those three.

The Ask — Shur Creative Partners

The Ask — A 30-day diagnostic window XVII

30-Day Diagnostic

A 30-day Unnamed-Product Firm diagnostic. Shur runs it. TruData provides access and one decision.

Five named-product audits across the truPath loops. One audit per loop pair: (Optimize · Clean Core × S/4HANA) · (Optimize · Clean Core × ECC migration) · (Innovate · BTP × Joule) · (Innovate · BTP × Generative AI Hub) · (Operate · AMS × continuous innovation backlog). Each audit is a 4–6 page memo: what TruData has actually shipped under the loop, what named SAP product was involved, what outcome was achieved, what is publishable. Production: 5 memos × ~6 hours each. Access required: 30-minute interview with the engagement lead per loop.
One mid-market wedge framing session. A 90-minute working session with the CRO + CEO + Head of Delivery to pick one of the three mid-market sub-bands as the firm’s declared territory. Output: one paragraph + one number for the homepage and the services pages. This is the move that closes Mid-Market Wedge Specificity in 90 minutes.
One introduction. Shur introduces TruData to a RISE or GROW Validated Partner peer who is ahead on naming — Birlasoft, Hexaware, or NTT DATA Business Solutions. The peer call is on the record: 45 minutes, structured questions, what they did to earn the partner designation, what the cost was, what the lift was. Shur observes; TruData asks. The intelligence transfers regardless of whether TruData pursues the badge.

Outcome at day 30 TruData has five named-product memos ready to publish, one declared mid-market band, and one peer benchmark on the partner-designation move. The Structural Advantage Score lifts from 46.5 to a projected 58.5. The Reframe holds, with evidence behind it.

Bridge — The open question XVIII

What does TruData’s pipeline look like when every other firm names the products it serves? Is there a tier of buyer who actively prefers vendors that don’t lead with vendor logos — and if so, is that a position TruData can defend by naming, deliberately and selectively, on its own terms?

Shur Creative Partners · May 2026

Appendix — Glossary, sources, methodology XIX

Glossary

Reframe: A single conceptual move that shifts the frame inside which a question is asked. One Reframe per brief. The body of the brief demonstrates the move rather than deriving toward it.
Structural Advantage Score: Composite 0–100 score across five equally-weighted dimensions. Each dimension splits 50/50 between Present and Opportunity. The broken edge is the dimension pair that holds the composite back.
Structural Gap: Two clusters in the discourse graph that should bridge in the public surface and currently do not. Severity scored 1–10 by the size of the bridging clusters and the strategic cost of the absence.

Graph Metadata

Graph Nametrudata-v04-editorial-brief-2026-05-04

Modularity0.34

Clusters7

Top BC Nodesap · 0.72

Sources150+

Build Date2026-05-04

Top concepts by betweenness: sap (0.72), data, solution, service, migration, cloud, customer, btp, s4hana, rise. The top hub sap sits 5× the next concept — the structural fingerprint of fragmentation flagged at Anchor 6.

Source Index

1	SAPinsider 2026 ERP Migration and Transformation Benchmark, Apr 2026 — sapinsider.org — 43% AI / 39% deadline
2	SAP News, Joule scale — news.sap.com Jun 2025 (34,000 customers) · Joule 35 solutions / 40+ agents Apr 2026
3	SAP Global Strategic Services Partner certification ranges, Nov 2024 — SAP GSSP Cert PDF
4	CIO / Gartner ECC migration projection, Jun 2025 — cio.com — 17,000 ECC holdouts
5	TruData Solutions case studies (public surface, retrieved 2026-04-20) — trudatasolutions.com/case-studies
6	InfraNodus knowledge graph `trudata-v04-editorial-brief-2026-05-04` — modularity 0.34, 7 clusters, top BC sap 0.72. Built 2026-05-04 from TruData’s public corpus + named SI peer surfaces.
7	USPTO trademark database — truPath™ serial 99669810
8	Third-party firmographic estimates — Crunchbase, PitchBook, LinkedIn (51–100 employee LinkedIn band; specific count ~35–50 per Prospeo / Exa pulls; ~$16–20M revenue est.). Compared against TruData’s site-claimed 7-office, “global” footprint.
9	SAP Q1 2026 + Q4 2025 results — SAP Investor Relations (RISE / GROW signings)
10	Competitive lens sources — Accenture myConcerto / ADVANCE · Deloitte Brownfield+ · Capgemini ADMnext · LTIMindtree ISG Leader 2025 · Hexaware 75% TCO case · Globant SAP / RISE Expert

Disclosure

This brief uses public-web evidence only; no internal TruData data, transcripts, or post-call analyses were used. All numeric claims trace to the Numbers Spine and the Source Index above. Discourse graph constructed from TruData’s public corpus plus the named SI peer surfaces, retrieved 2026-04-20 through 2026-05-04. The Reframe is testable against pipeline data Shur does not have; the Bridge surfaces the question whose answer redirects the editorial move.