Skip to content

About

The same problem in five different costumes.

I have spent eighteen years on the customer side of enterprise technology. The technology keeps changing. What decides whether it lands has not.

01The long view

I started in data warehousing in 2000, which means I have spent my whole career on one problem wearing different clothes.

The first version was getting data into one place at all — a senior developer role at Silicon Laboratories in Austin, then data warehouse content development at SAP Labs, then a data warehouse and data quality program at Boeing. Boeing taught me the thing that has held up ever since: a technically correct model nobody trusts is worth nothing.

The second version was making that data legible. At Accenture I led a cross-functional team of eleven turning a client’s legacy reporting into SAP Analytics across logistics, procurement, and finance. The piece of work from that period I still bring up is a distributor-spend solution that freed up to 20% of the client’s distributor capital, which went back into sales promotion. It was not a sophisticated model. It answered a question nobody had previously been able to ask.

Then HANA arrived and speed changed which questions got asked. At IBM I owned analytics architecture and the commercial side of delivery — cost structures, deliverable tracking, risk, RFP responses — and won and delivered implementations at Honda Motors, VSP, and Abbott. After that came cloud, and migration stopped being a project and became the transformation itself. Back at SAP I led analytics delivery for utilities clients under MaxAttention through their S/4 journey, drove mass on-premise-to-cloud migrations on HANA, and established a Cloud Database and Integration practice that still contributes recurring revenue.

Since 2022 I have owned an $18M portfolio of enterprise SAP cloud accounts end to end — deployment, adoption, renewals, expansion. Which brings me to the fifth version, and the one I find genuinely thrilling.

I implemented SAP Joule and guided customers through rolling out Joule Agents. A real share of my week now goes to questions that did not exist three years ago: how agents orchestrate, what they are permitted to ground on, where a human stays in the loop, what the blast radius is when one of them is confidently wrong. I delivered a Snowflake Cortex engagement connecting SAP data to LLM-powered analytics. I ran the workshops that moved PI onto BTP Integration Suite and BW onto Datasphere — the unglamorous prerequisite for all of it.

The pattern I have now watched five times is the same. The capability shows up, everyone is impressed, and then it sits there. What moves it is someone who can hold both ends at once — the architecture and the business case — and who is still in the room at the QBR when it is time to prove the number. That is the job I have. After eighteen years it is the most interesting version of it I have had.

Gireesh Malhotra, Customer Success Senior Manager at SAP
Gireesh MalhotraPalo Alto, CA
02Platform shifts

Five platform shifts

Every one of these arrived as a capability story and turned into an adoption problem. The bands are industry eras and overlap because real eras do. The bars beneath them are my own dates.

Industry era

  • Data Warehouse20002007Get the data into one place.
  • Enterprise BI20052013Turn it into numbers people will act on.
  • In-Memory · HANA20112018Speed changes which questions get asked.
  • Cloud & S/420162024Migration stops being a project and becomes the transformation.
  • Business AI · Agentic20222026Capability is abundant. Adoption is the constraint.

My dates

  • 2000 — 2009SAP · Deloitte · HPEarlier Career — Consulting
  • Oct 2009 — May 2014AccentureSAP Enterprise Solution Architect
  • May 2014 — Nov 2016IBMAnalytics Delivery Architect / Manager
  • Jan 2017 — Mar 2022SAPAnalytics Delivery Lead — Utilities
  • Apr 2022 — PresentSAPCustomer Success Senior Manager
03How I work

Five things I hold to

  1. 01

    The data layer sets the ceiling

    An agent is only as good as what it can ground on. Re-platforming PI to Integration Suite and BW to Datasphere is not preparatory work that delays the AI project — it is the AI project, arriving early.

  2. 02

    Guardrails before autonomy

    Before an agent gets to act, I want to know its blast radius, its approval threshold, what it is allowed to read, and who sees the audit trail. Autonomy earns scope; it does not start with it.

  3. 03

    Value has to survive a CFO

    A use case that cannot be instrumented is a use case that will not be renewed. I build the measurement into the design, then bring it to the QBR and the Balanced Scorecard as evidence rather than narrative.

  4. 04

    Nothing goes live without a cutover plan

    Eighteen years of go-lives teaches one thing reliably: the technology is rarely what fails. Test strategy, change management, training, and cutover sequencing are where programs are won.

  5. 05

    Escalations get owned

    When a critical situation lands, the customer needs one person accountable for the path to resolution — aligned with the account team and the implementation partner, not routing between them.

04Credentials

Education

  • MBA

    Durham University Business School

    United Kingdom

  • Machine Learning

    University of California, Berkeley

    California

  • Advanced Project Management

    Stanford University

    California

  • Bachelor of Engineering

    Nagpur University

    India

Recognition

  • Best Customer Engagement
  • Zero Critical Defect Delivery
  • Pat on the Back (multiple)

The full record — roles, engagements, and platforms — is on the résumé page, which is built to print cleanly.