The growth of SAP consultancies depends on proof and visibility. When teams deliver outcomes and share the story, reputations spread, decision-makers pay attention, and larger programs follow.
Even if these award winning projects are interpreted as examples of best practice, endorsed by SAP themselves, these are still valuable stories for those seeking to expand SAP consultancies.
The 2025 Pinnacle Award winners showed to a clear pattern: BTP as the build zone, AI in production, S/4HANA kept clean, and results that customers could verify. Those stories marked where the market moved and gave other firms a practical compass, or a bar to surpass, so in this article from IgniteSAP we take another look at the projects and features that were considered “award-winning”, as a source to emulate in consultancy growth.
SAP named nineteen winners and twenty-eight finalists across twenty-four categories in April 2025
The program’s purpose emphasized customer value, measurable growth, and simplification on current SAP technology, so each recognition tied back to adoption and outcomes rather than brand size or reputation. That context matters because it reframes praise as patterns other firms can actually study and use.
So what were the project themes highlighted by SAP in the awards this year?
Cloud ERP momentum was notable in Sales Success tiers for enterprise, midmarket, small enterprise, and partner-led territories, and through a RISE with SAP Methodology category that spotlighted clean-core delivery.
Business AI split into an award for a customer use case and another for an AI cloud application, which pushed partners to ship production scenarios on BTP instead of stopping at pilots.
BTP appeared again through Extensibility and Clean Core and through Data and AI Growth, which signaled that upgrade-safe extensions and consumable services sat at the heart of modern projects.
Customer Success Management stood on its own and valued lifecycle performance after go-live. Industry-focused and solution-centric categories, including SAP Store and Partner Solution Success, recognized repeatable IP with references and sales traction.
With that backdrop in mind, the rest of this article from IgniteSAP interprets those award-winning projects and initiatives as a strategy that any consultancy can run.
Accenture won RISE with SAP | Sales Success and Sustainability, which signaled strength in cloud ERP deal conversion and live sustainability programs. Public material around the win pointed to readiness for SAP Green Ledger, SAP Green Token, and SAP Sustainability Data Exchange, backed by reference-able work. A practical path others can take starts with a small sustainability reference library: publish one product carbon footprint case, one supplier-token trace, and one SDX data-share pattern with named sponsors and dates. That packet gives sales teams proofs that map to the Sustainability category while RISE deal hygiene drives the Sales Success outcome.
Capgemini won SAP Business AI | Partner Innovation – Customer AI Use Case, which meant a production scenario on SAP BTP with measurable impact and a verifiable customer story. Event communications and later notes around work with foundation models in regulated sectors reinforced that focus on governed routes.
Other consultancies can also create a one-page AI dossier per vertical: name the process owner, show the model path through AI Core or Generative AI Hub, record data lineage, and publish a pre/post cycle-time graph with a sponsor quote. One dossier per industry turns “AI capability” into proofs buyers can check.
delaware won Customer Success Management and was a finalist for Partner Industry Innovation, which placed the firm’s strength in lifecycle value after go-live with visible momentum in industry IP.
A firm seeking the same outcome can set a quarterly adoption review as a standing rhythm and publish three numbers per account: active users by role, feature adoption by module, and a one-step expansion plan with an owner, then request a short sponsor note after each review. This creates an auditable trail that mirrors the category.
Deloitte won RISE with SAP Methodology and Delivery Quality, which pointed to stage-gates tied to value and predictable outcomes. Method notes described how value hypotheses moved from discovery into post-go-live measurement through Cloud ALM.
To emulate that, build a slim RISE guide that maps business cases to gate checklists, assigns owners, and records time-to-value at each milestone. Keep artifacts short so sales can preview the cadence during final calls.
PwC won SAP BTP | Data & AI Growth, which recognized partners that expanded adoption of BTP data and AI services across the customer journey. Alliance pages listed named solution assets (CSRD.AI Manager and ESG Reporting Manager among them) which gave the award concrete footing.
A BTP consumption ledger is a move that others could use: list services per account, quarter-by-quarter usage, and two named references per service. Add a brief explainer for each solution that states the business problem, the BTP services in use, and the adoption curve.
Tenthpin won Partner Industry Innovation, which rewarded partner IP that complemented SAP’s industry scope with references and live customers. Company materials highlighted a Life Sciences focus near regulated processes.
A usable template for boutiques is a small vertical pack: two process maps that sit near audit points, one validation note that explains controls, and two public case briefs with dates and outcomes. That pack turns specialist knowledge into repeatable deals and supports future submissions in industry categories.
Every firm that wants to compete at this level needs a house style for architecture, delivery, and measurement. The architectural style starts with a clean core, because upgrade cadence and change control depend on it.
That means ABAP Cloud or CAP for extensibility, Integration Suite for standard interfaces, and a clear rule that custom work lives outside the digital core unless a risk case is documented and approved. A small design authority can keep this simple by issuing short extension cookbooks, reviewing pull requests on sensitive objects, and publishing a monthly ratio of in-core versus extension-layer changes. This ratio gives leaders a fast read on drift and makes later upgrades less painful.
Delivery style comes next, because good ideas stall without stage-gates and clear roles. A RISE playbook helps here, since most modern ERP journeys now flow through it. The playbook should connect business cases to Cloud ALM checkpoints so value hypotheses turn into tracked outcomes. Gate names can stay plain: scope freeze, fit-to-standard complete, integration proven, data ready, security signed, go-live approved, value measured. Each gate gets a short checklist and one owner.
Measurement ties the two together. A compact dashboard works best, and it should travel from pre-sale to run without translation. Deployed ACV, time-to-value, active users by role, BTP consumption by service, and AI usage by scenario form a solid spine. Clean-core conformance can sit on the same page as a simple percentage. Customer-side health adds net retention, feature adoption, and expansion by business unit. These numbers speak to reviewers, buyers, and delivery leads in the same language.
Award juries favored AI use cases that named the task, ran on BTP services, and produced an outcome a customer could verify. That gives consultancies a pattern they can copy.
Start by scouting three processes with frequent handoffs, clear text input, and measurable cycle time. Service ticket triage, procurement exceptions, or maintenance notes are common choices. Pick one process owner who can sponsor a live trial and one data owner who can clear access to the required records.
Then write a one-page brief that captures input sources, the model route through AI Core or Generative AI Hub, decision boundaries, and expected outcome in minutes saved or errors prevented. Build the scenario with a simple toggle that switches back to the prior path so the sponsor can compare. Run a two-week shadow period, publish the usage graph, and ask the sponsor to sign a short reference. That small packet (brief, toggle, graph, quote) turns a demo into evidence and makes the path repeatable across accounts.
Several winners showed that packaged IP still moved the market, which means firms gain by treating one repeatable capability like a product.
This does not need a large team. It needs a clear scope, a tiny backlog, and a route to market. Start by analyzing the last five projects in one vertical and pull out the two features your teams rebuilt each time.
Pick the feature with the simplest data model and the highest business value, then draft a three-release plan: an MVP that runs for one pilot customer, a version that supports upgrades and observability, and a version that meets SAP Store requirements.
Write a two-page service policy that covers support windows, response times, and patch cadence, because buyers read those pages before they ask for a demo. Price the first version based on saved effort when compared to bespoke build, and ask the first buyer to sign a short case note at the first renewal. That sequence builds a real asset without starving delivery teams.
The Customer Success Management category rewarded partners that grew value after go-live, and that pattern gives firms a simple play they can copy.
Create a quarterly review with three parts: adoption by module or feature, business outcomes tied to the original case, and a forward plan for one expansion step. Keep the meeting short and bring one page of graphs and one page of notes, then ask the sponsor to sign the page that records the plan.
Over time this practice produces a library of references with dates, names, and numbers that future buyers and reviewers can check without long calls.
Firms that want to move quickly can use a short horizon to build habits that stick. In the first thirty days, define the clean-core rules in a three-page note, appoint two reviewers from different teams, and open a simple mailbox where architects can send tricky cases.
In the same month, shortlist two AI scenarios using the one-page brief format and confirm data access with named owners. In the next thirty days, stand up a Cloud ALM project for one large program and load the gate checklist so the cadence starts to live in the tool. In the same window, draft the MVP backlog for one product idea and meet two clients who might pilot.
In the final thirty days, ship the first AI scenario to a small user group with a toggle, hold the first quarterly adoption review at one live customer, and publish light notes from both meetings on your internal wiki.
Sales Success categories rewarded signed cloud commitments tied to business cases, which means the sales process needs a tight link to delivery.
The simplest tweak is to add a value hypothesis to every proposal that names the outcomes, the gates that will measure progress, and the timeline for the first check. Invite one delivery lead to the last sales call to confirm the plan, and invite the future sponsor to the first gate review during the sale. After go-live, circle back with a short note that records time-to-value and the next outcome.
Guardrails keep the clean-core promise honest as projects scale. A living API catalog helps, because teams see available interfaces before they reach for custom exits. A naming convention for extension apps and packages keeps code discoverable across teams and years. A short policy for change freezes before upgrades keeps everyone on the same calendar. A biweekly clinic where architects review tough cases in public cuts decision time and helps younger staff learn pattern choices without long documents.
The work above depends on a few roles working in concert. RISE program leads hold the cadence and keep value tied to gates. BTP solution and integration architects place change in the right layer and watch for creeping modifications. Signavio transformation leads make sure process discovery feeds design rather than sitting in a separate deck. Data and AI engineers take responsibility for model routes, observability, and privacy controls.
These roles prosper when the firm publishes a clear certification plan and when managers create pairs across senior and mid-level staff for each capability. A small enablement team can coach on proposal structure, case write-ups, and reference management, which keeps stories consistent even as teams rotate across accounts.
There is no shortage of inspiration in the SAP services market, but the SAP Pinnacle Awards in 2025 provided a genuinely useful insight into the leading edge of SAP consulting.
If we extract one message, it is that a common path forward uses one house style for clean-core work on BTP, one production AI scenario per flagship account, a steady cadence of lifecycle metrics, and one productized industry solution with paying users and a support plan.
Industry awards are sometimes derided as merely marketing exercises, but if you are a part of an SAP consultancy looking to grow as SAP’s innovation roadmap advances, keeping track of what others are doing and working out how to integrate award-winning practices into your firm is a great resource to help guide strategic decisions.
Keep track of what your peers are engaged in and emulate the initiatives that are most relevant to your organization, and you will find new areas to expand and deliver even better value for your customers.
Contact IgniteSAP if you are looking to fill project gaps with skilled SAP experts, build an award-winning internal team, or to hire top SAP leadership for your company.
Why Growth Rate Is the Wrong Metric for Judging an SAP Employer
How to Identify the Ceiling in Your Current SAP Career Path
