The Extension Economy Arrives at SAP's Door.

02 · Group AStrategic Lens

03 · Group BClient Profile — Who TruData is today

TruData Solutions is a ten-year-old, Carlsbad-headquartered, founder-led SAP specialist with a proprietary methodology, a seven-office multishore footprint, and a brand that under-articulates the position it already owns.

The company was founded in 2016. Public third-party sources place headcount at 51–200, revenue between $16M and $20M, and no disclosed VC or private equity backing. Offices span the US (Carlsbad HQ, Brooklyn), the UK (London), three LATAM nearshore centers (Costa Rica, Mexico, Panama), and an India offshore hub in Bengaluru. The delivery model is named explicitly on the site: US-led onshore, LATAM nearshore, India offshore — a three-tier multishore stack.

The methodology carries the brand. TruData's proprietary framework is truPath™, filed with USPTO under serial 99669810, described on site as a three-loop cycle (Optimize / Innovate / Operate) mapped to a five-phase sequence (Strategy → Design → Build → Test → Run). The language is consistent across every page: "Don't just migrate — evolve." Clean Core is the thematic anchor. BTP is cast as "the strategic engine for your digital evolution." Build-then-Run is the differentiation against ticket-based AMS vendors.

Leadership is visible but thin-bench. Six named executives appear across the About page and LinkedIn: Nevvar Hickmet (CEO, 25+ years SAP), Brad Dubé (CRO, ex-Google and SAP, named May 2023), Scott Redman (SVP Talent, 25+ years SAP), Sarvesh Chinnappa (VP Delivery, Application Modernization; Bengaluru lead), Eric McGee (VP Delivery, SAP Practice Lead, 20+ years), and Shyanne Yang (Director, Operations). CRO Brad Dubé is not yet featured on the current About page — a small branding signal worth correcting.

Partnerships anchor the go-to-market. OutSystems is the named low-code partner, with a published "4–7x faster than traditional coding" claim that positions OutSystems as the user-facing velocity layer on top of the SAP digital core. A 2019 partnership with Syniti exists for data-centric SAP work. No formal SAP PartnerEdge tier (Gold / Platinum / Services) is publicly asserted on the site itself, though industry reference treats TruData as a Gold-tier SAP Partner.

Nine anonymized case studies carry the proof layer. Sectors span pharma/biotech CRO, analytical science, executive search, premium paint and stain manufacturing, food and beverage, building materials, semiconductor, and film and television. Every client is described by descriptor rather than by name; there are no quoted executives, no named logos, no quantified outcomes. The case studies establish scope breadth. They do not yet establish outcome credibility.

04 · Group BMarket Context — The macro inflection

Four public shifts define the ground every SAP services firm will stand on through 2028.

The 2027 cliff. SAP mainstream maintenance for ECC ends 31 December 2027 — twenty months from the date of this brief. Roughly two-thirds of existing ECC customers still have not migrated to S/4HANA. A full ECC-to-S/4HANA migration still takes 18–36 months. Qualified consultant supply is contracting at the same time demand is compressing into a narrow window. The market is a supply-constrained stampede, not a cyclical buy-cycle.

SAP's bifurcated channel. Through RISE with SAP and GROW with SAP, SAP has consolidated its own tiered bundles (Base, Premium, Premium Plus) under SAP Cloud ERP Private and begun selling the infra-license-methodology stack directly. Every major system integrator now has a competing offering; some of the same firms (NTT DATA Business Solutions, Syntax) are simultaneously RISE partners and RISE competitors. SAP has quietly become a direct competitor to its own partner channel for the managed-services layer.

The Clean Core mandate. SAP's architectural direction is now explicit: no custom ABAP in the S/4HANA core. All extension, integration, and automation must move to the SAP Business Technology Platform. This is not a recommendation. It is the gating condition for upgrade-readiness and for Joule-era AI deployment. Firms that have been selling core customization as a service are watching that service evaporate. Firms that extend into BTP are watching their category expand.

Joule and BTP AI Foundation. Joule Studio went GA in Q1 2026. The platform is embedded in 35 SAP solutions, offers 40+ specialized agents, and exposes 2,400+ skills on BTP AI Foundation. SAP has started shipping for free agents and skills that the partner channel was previously paid to build. The response is a migration up-stack: partners who want to keep their margin move from infrastructure plumbing to domain-specific agents built on top of Joule and BTP AI Foundation. The firms that do not make that move will compete on price against free.

05 · Group CMethodology — How this brief was built

Two knowledge graphs, one stack-rank, and the ShurIQ Brand Power Score. Built from public sources only. No client-briefing data.

Graph 1 · Self-Discourse. A knowledge graph built from TruData's own site copy — every public page on trudatasolutions.com, every case study, every leadership bio, every services and partnership page. This graph surfaces how TruData narrates itself: the recurring concepts, the cluster structure, the gateway terms, the absences. Modularity 0.388, six clusters, built in InfraNodus on 2026-04-20.

Graph 2 · Industry Landscape. A second knowledge graph built from the competitive landscape corpus — analyst coverage, Tier-1 and mid-market specialist positioning, SAP's own RISE/GROW/Joule release notes, industry press on the 2027 cliff and Clean Core mandate. This graph shows the concept space the industry is moving through, against which TruData's self-narrative is read.

Stack Rank. Twelve SAP consultancies scored across the five Brand Power Score dimensions using the tech_services_v1 weight profile (Awareness 0.18, Trust 0.22, Mission 0.22, Differentiation 0.23, Loyalty 0.15). Public signals only: SAP Partner Finder, LinkedIn headcount, Gartner / Forrester / ISG positioning, published case studies. Every cell carries an [O] observation or [I] inference flag. The full instrument is the standalone stack-ranking tab.

Dual-graph + stack-rank is the ShurIQ method. The self-discourse graph shows how the subject narrates itself. The industry graph shows what the market is moving toward. The gap between the two — the silences, the mismatches, the opportunities the subject has not yet named — is the analytical material this brief is built from. The stack-rank positions the subject inside the competitive set the buyers actually shop.

06 · Group CLens of Analysis — Extension vs. Migration

One analytical frame holds the whole brief together: every SAP services claim, every gap, every action, reads through the question of where the money moves next.

For the last decade, SAP services revenue has concentrated in migration: the one-time transformation from legacy ECC to S/4HANA, paid for by a core-modernization project budget. That revenue remains large through the 2027 cliff. It is also the most commoditizing segment on the category: templates converge across firms, offshore labor arbitrage compresses pricing, RISE with SAP bundles the methodology directly.

The growing segment is extension: the continuous stream of post-migration work on the SAP Business Technology Platform — side-by-side applications, Datasphere unification, Fiori UX, Joule agent customization, industry-specific automation. Extension revenue is annuity-shaped, architecturally privileged by the Clean Core mandate, and structurally protected from RISE-bundled commodity pricing because the extension layer is where the customer's proprietary differentiation lives.

Every move in this brief is read through this frame. Firms that index on migration alone are watching their margin compress. Firms that index on extension are watching their margin expand. TruData's stance on the site is already extension-first ("BTP as the strategic engine for your digital evolution", "Don't just migrate — evolve"). The stance is correct. The execution volume is the gap.

07 · Group DDiscourse — How TruData narrates itself

Read across trudatasolutions.com, three themes recur on every page: Clean Core, BTP-first innovation, and Build-then-Run multishore. These are the concepts that shape the site's self-discourse. They are also the concepts that appear in the knowledge graph as the densest clusters.

Clean Core is the site's thematic anchor. Every services page references it: "Clean Core Architecture," "Clean Core principles from Day One," "keep your core clean while accelerating your digital evolution." The repetition is disciplined, not accidental. It positions TruData against the legacy SI playbook of core customization and attaches the brand to SAP's own architectural direction.

BTP carries the innovation narrative. The language treats BTP as the commercial engine, not the plumbing: "we treat SAP Business Technology Platform as more than just a platform, it is the strategic engine for your digital evolution." Four service areas anchor the BTP practice — Data & Analytics, Enterprise Application Development, Applied Artificial Intelligence, Modern Integration Services. The outcome claims (upgrade-ready, scalable, innovation-first) tie directly to the Clean Core mandate.

Multishore is the delivery-shape story. US-led / LATAM nearshore / India offshore, repeated across services pages, case studies, and the dedicated Multishore Delivery page. The framing is time-zone-aligned collaboration plus senior US accountability plus cost-efficient offshore execution. The OutSystems partnership adds a low-code velocity layer ("4–7x faster than traditional coding") that sits adjacent to the SAP digital core rather than inside it — consistent with the Clean Core stance.

What the self-discourse does not say matters as much as what it does. Three silences in TruData's own narrative map to three of the fastest-moving inflections in the industry: no mention of RISE or GROW with SAP anywhere in the site corpus, no named SAP AI products (Joule, Business AI, Generative AI Hub, AI Foundation) despite regular AI language, and no urgency framing around the 2027 ECC cliff despite Clean Core being the site's thematic anchor. These silences are the shape of the gap analysis that follows.

08 · Group DTopology — Graph 1 self-discourse map

Visual companion → Viz Hub — Graph 1 topology visualization

The self-discourse graph surfaces six concept clusters, modularity 0.388 — focused but not dense. The dominant gateway concepts are sap, s/4hana, innovation, and build. Each structural gap in this brief bridges two of these clusters.

Top gateway nodes by betweenness: sap (BC 0.188), s/4hana (BC 0.187), innovation (BC 0.163), build (BC 0.132). These are the four terms every other concept routes through. A portfolio strategy that does not make a sharp claim about each of these four terms will fail the concept-space test.

09 · Group DStack Rank — TruData's position in the competitive set

Standalone instrument → ↑ Full industry stack ranking — same five-dimension diagnostic in §10 applied to the full twelve-company peer set, with per-dimension scoring rationale and public-source evidence for every cell.

Twelve SAP consultancies ranked by Brand Power Score composite using the tech-services weight profile. Public signals only. TruData sits at rank #11 with a 56.7 composite.

Read across the stack: TruData's near-peer band is Syntax (65.3), NIMBL (59.7), TruData (56.7), Bowdark (50.6). The gap to NIMBL is 3.0 composite points — closeable inside a six-month concerted program. The gap to Syntax is 8.6 points — a twelve-to-eighteen-month ambition. See the standalone stack-ranking instrument for the per-dimension rationale on every cell.

10 · Group EBrand Power Score — The diagnostic

Visual companion → Viz Hub — Brand Power Score viewport

Five-dimension composite for TruData Solutions. Vertical: tech services. Weight profile: tech_services_v1 (Awareness 0.18 · Trust 0.22 · Mission 0.22 · Differentiation 0.23 · Loyalty 0.15). Each strategic action in §16 names the dimension it addresses.

Per-dimension rationale

• Awareness 38 O · Limited analyst coverage. Low SERP presence for "SAP BTP consulting," "SAP mid-market," "S/4HANA implementation partner." Small LinkedIn and press footprint vs. peers. Third-party review platforms (G2, Gartner Peer Insights, TrustRadius) show effectively no TruData presence.
• Trust 58 O · SAP Gold / PartnerEdge. Multishore delivery cited. Nine case-study descriptors visible on site (no named logos, no quoted executives). Leadership tenure ~15–25 years per bio. Founded 2016. No disclosed VC / PE backing; appears founder-led.
• Mission 60 I · Clear BTP-first + S/4HANA + mid-market POV. truPath™ methodology named and trademarked (USPTO serial 99669810). Clean Core language consistent across pages. POV is coherent but not category-defining in the way Deloitte's Kinetic Enterprise or Accenture's reinvention narrative are.
• Differentiation 66 I · Multishore LATAM/India model plus mid-market BTP focus is distinctive vs. large SIs. Under-articulated in public materials but legitimately distinct. Most Tier-1 SIs avoid the true mid-market. Most nearshore LATAM shops do not have full SAP depth. TruData sits in a narrow real lane.
• Loyalty 58 I · Repeat-client signals present (one analytical-science client appears in two different case studies). Managed services book size not publicly disclosed. Build-then-Run positioning implies retention but the retention rate is not published.

11 · Group EStructural Gaps — The named tensions

Three gaps surface from Graph 1, each bridging two clusters that TruData's self-narrative does not yet connect.

Gap 1 · Delivery Model ↔ Data & Analytics

The Delivery Model cluster (25%) is the largest in the graph. The Data & Analytics cluster (11%) is the smallest. The multishore story carries the narrative weight; the data-unification / AI-readiness story does not. TruData's site states the outcome — "AI-ready data foundations that deliver trusted insights" — but does not name the products (Datasphere, BTP AI Foundation, Joule) and does not tie the multishore model to the specific practice of delivering data-unification work across time zones. The bridge is implicit in every services page; it is not built explicitly anywhere.

Gap 2 · Delivery Model ↔ Customization Strategy

The Customization Strategy cluster (13%) captures the "SAP Surround" positioning — externalizing customization onto OutSystems to protect the Clean Core. The Delivery Model cluster is where the multishore labor runs. The two clusters do not meet in the self-discourse: TruData does not say which tier of the multishore stack does the OutSystems work, which does the BTP side-by-side extension work, and which does the AMS run state. The practice exists; the operating model behind the practice is not legible to the buyer.

Gap 3 · Data & Analytics ↔ Customization Strategy

The smallest cluster and the third-smallest cluster sit far apart on the graph. This is the gap that matters most for the extension economy. Data & Analytics is where Joule-era AI plugs in. Customization Strategy is where the domain-specific agents live. A firm that bridges the two — data-unification feeding domain agents running on BTP AI Foundation — owns the next wave. TruData has the building blocks but does not yet tell the story.

12 · Group EGap Analysis — What the gaps mean commercially

Why the Delivery-Model ↔ Data-Analytics gap is the SAP Signavio-adjacent story

SAP Signavio — the process-mining and transformation-suite product set — is increasingly the gate to RISE engagements. Buyers are told to run Signavio before they commit to a transformation scope; analyst coverage treats Signavio positions as prerequisite. A firm with a named Signavio practice can front-load engagements with process discovery. A firm without one arrives after the business case has been built. TruData's site has no Signavio mention. The delivery-model engine exists; the data-analytics diagnostic layer that feeds it does not. Named together — multishore Signavio practice, global coverage, fixed-scope process-mining engagements — this gap closes inside a single content-plus-partnership quarter.

Why the Delivery-Model ↔ Customization-Strategy gap is the operating-model legibility problem

Mid-market buyers evaluating SAP partners read for two things: the methodology, and the operating model behind the methodology. TruData's methodology — truPath™ — is clearly named. The operating model — which tier does what, at which phase, with what handoff to AMS — is not. Syntax's Compass publishes an explicit phase-plus-tier map. Rizing's Wipro-backed delivery does the same through scale. TruData's multishore is named; the multishore playbook for a BTP extension engagement specifically is not published. Closing this gap is a single internal document translated into site copy: which tier runs Signavio discovery, which tier runs S/4HANA migration, which tier runs BTP extension build, which tier runs AMS — and on what clock.

Why the Data-Analytics ↔ Customization-Strategy gap is the Joule-era opportunity

Joule Studio shipped 40+ agents and 2,400+ skills in Q1 2026. The commodity of agent-building is now SAP's, not the partner's. The margin lives in domain-specific agents built on top of Joule and BTP AI Foundation — for pharma CAPEX governance, for building-materials data consolidation, for executive-search compensation modeling. TruData's case studies show the verticals (pharma CRO, analytical science, exec search, building materials); the domain-agent POV for those verticals is not yet articulated. The firm that names a "Joule-first mid-market extension practice" this quarter owns the vocabulary for the next three years. The firm that does not names it in 2027 behind three competitors.

What breaks if these gaps go unclosed

The commodity S/4HANA migration market is where TruData currently lives commercially. That market is price-compressing through the 2027 cliff. After 2027, the money moves to extension. A firm that has not made its extension-layer claim by late 2026 is competing against Joule for free on the low end and against Syntax or Rizing with published methodologies on the high end. The remediation cost in 2028 is an order of magnitude greater than the build cost in 2026. The gaps are not rhetorical. They are the difference between a firm that compounds on annuity revenue and a firm that re-earns each engagement from scratch.

13 · Group ECompetitive Lens — Who has solved which problem

Visual companion → Viz Hub — Competitive Lens viewport

Seven peers across five dimensions. Reads as: who has solved which problem already, and where the white space sits.

Read across TruData's row: the methodology is strong, the multishore is strong, the BTP stance is strong. Two dimensions are low: AI / Joule POV (the positioning language exists but the product names do not) and RISE Validated Partner (status is not confirmed on the site). Those two are exactly the two dimensions where NTT DATA BS and Rizing have already moved. The competitive position reads as a content-and-credentialing gap, not a capability gap.

14 · Group FReframe — The hinge claim

Visual companion → Viz Hub — Extension Economy viewport

The SAP services market won the last decade on migration. The operative question was: how do we get the customer from ECC to S/4HANA before 2027. Every RFP was scored on it. Every SI trained its staff toward it. The 2027 cliff concentrates that question into a twenty-month stampede.

This is not a rhetorical move. It is a category-level read backed by four public signals: SAP's own Clean Core mandate forcing every custom ABAP line out of the core and onto BTP; Joule's Q1 2026 GA shipping 40+ agents and 2,400+ skills that commoditize agent-building for free; RISE with SAP's consolidation of bundled migration SKUs under SAP Cloud ERP Private, which prices the core commodity migration directly; and the industry press consensus that commodity S/4HANA implementation is price-compressing as templates converge across SIs.

The Clean Core mandate is the mechanical driver. It is not a design preference. It is the gating condition for upgrade-readiness and for Joule-era AI deployment. Every line of custom ABAP in a production S/4HANA system is a line item that must move to BTP. The partner who moves the line wins the next engagement. The partner who doesn't watches it get moved by someone else.

Joule and BTP AI Foundation move value up-stack. The margin leaves agent-building (free with SAP) and concentrates in domain-specific agents — pharma CAPEX governance, building-materials data reconciliation, exec-search compensation modeling — built on top of Joule's foundation. This is the extension economy's top layer. TruData's case-study portfolio spans exactly these verticals. The vocabulary does not yet exist on the site.

truPath™ is already positioned for the extension economy, not for migration. Read the three-loop framing on trudatasolutions.com: Optimize (the Build) — migrate to S/4HANA while stripping legacy debt, Innovate (the Extend) — activate Datasphere and embed agentic AI, Operate (the Run) — transition seamlessly into AMS. The middle loop is where the money is going. The site narrates it clearly. The market has not yet heard it at sufficient volume.

Every gap, every competitive read, and every action that follows demonstrates this reframe. Read that way, the brief is coherent. Read any other way, it is a list of tactical moves.

15 · Group FConflict Map — Where the reframe collides with current narrative

The reframe does not align with three of the market's default narratives. Each conflict has to be named and handled, or the reframe reads as a pitch rather than a reading.

Conflict 1 · RISE templates say the core is the product

SAP's own RISE and GROW playbooks center on the core-migration bundle as the primary commercial motion. Analyst coverage, SAP field sales, and hyperscaler co-sell all speak the language of "move to S/4HANA Cloud." The reframe says the core migration is a price-compressing commodity and the money moves to extension. That contradicts SAP's primary sales motion. Handling: position the extension layer as the follow-on to RISE, not as an alternative — "RISE is the core, truPath™ is the extension economy." Same customer, larger lifetime value, distinct motion.

Conflict 2 · Commodity SI pricing assumes migration is the engagement

The current mid-market RFP script scores vendors on "how fast can you migrate us and at what cost." The reframe says the migration is the loss-leader and the extension practice is the account. This contradicts the buyer's purchasing muscle memory. Handling: publish a BTP extension playbook that ships separately from the migration scope. Make the extension engagement a distinct, fixed-scope, premium-priced product that starts at migration go-live and runs on its own clock.

Conflict 3 · Offshore-first pricing absorbs nearshore margin

The Tier-1 offshore model (TCS, Infosys, Wipro-via-Rizing) prices mid-market work off Indian labor arbitrage. The reframe — multishore with explicit LATAM nearshore — costs more per hour than offshore-first. This contradicts the lowest-bid procurement default. Handling: price the LATAM tier on data-sovereignty, time-zone overlap, and USMCA advantage, not on per-hour cost. Signavio discovery, Joule agent design, and data-migration governance are the three workstreams where time-zone overlap and data-sovereignty commands a premium that offshore cannot match. The India tier runs scale commodity; the LATAM tier runs the premium extension surface.

16 · Group FStrategic Action Grid — The recommendation vector

Four moves, ordered by leverage not difficulty. Each names the Brand Power Score dimension it addresses and the structural gap it closes.

Sequencing. Move 4 funds the analyst visibility that Moves 1–3 need to carry. Move 1 (Signavio) defines the practice that every downstream engagement now front-loads. Move 2 (Joule-first branding) claims the vocabulary that the next three years will be priced on. Move 3 (LATAM as extension IP) is the commercial overlay. If only one can run first, run Move 4 — the credentialing moves unlock the top-of-funnel for everything that follows.

17 · Group GPartnership Model — Swim lanes

This brief is diagnostic. The next step is the engagement that turns the diagnostic into a joint agenda. Two lanes, named explicitly.

We do togetherThe 30-day commitment

Thirty days of joint discovery on Move 4 — the BTP Extension Playbook and RISE Validated Partner credentialing path. Scope: engagement product architecture, SKU pricing, RISE application timeline, analyst-relations sequence. At day 30, a shared go / refine / park decision. If we do not earn the engagement, we walk with a joint brief TruData can use internally, our cost.

18 · Group GConfidence Ledger — What we stand behind

Every load-bearing claim in the brief, ranked by confidence. The reader should apply their own skepticism in exactly the rank order below.