April 24, 2026 — a day I‘ll remember for a while. SAP‘s d-com event landed in Pune at the stunning Westin Hotel, Koregaon Park, and I had the privilege of being part of it — not just as an attendee, but as a volunteer apprentice alongside the FRE Pune team.

Starting the Day as a Volunteer

There‘s something different about experiencing an event from the inside. As part of my apprentice role, I got to interact with employees before the sessions even began — helping with software installations on desktops that would be used for the hands-on labs. If someone was stuck, I was there. It was a great way to break the ice, meet people early, and genuinely be useful before the day got going.

The Hands-On Lab: Vibe Coding with Cline + MCP Servers

The hands-on lab I participated in was a highlight of the day — building an application using Cline with MCP servers, driven entirely by a prompt.

If you haven‘t tried this yet, it‘s hard to describe the feeling when you type a prompt and watch an agent do the heavy lifting — discovering files, editing configs, generating code, asking you only when it needs a decision. It‘s what I‘d call vibe coding: you stay in control, the agent does the work.

What I walked away with is a clearer understanding of where I add the most value in this new world. The real skill isn‘t just writing code — it‘s knowing what you want, articulating requirements clearly, and validating that what comes out is correct. Once I have that clarity, the speed and intelligence of tools like Claude CLI and Cline become genuinely powerful. I‘d already been working this way, but d-com made it feel more tangible and exciting than ever.

Most hands-on participants got a bottle with the SAP logo — and I was one of the lucky ones. Always a win.

Our Demo: From Manual Onboarding to AI Agents

Vinay and I demo'd our work on SDK adoption at Demo Pod 02 — a session titled “From Manual Onboarding to AI Agents: How We Automated BTP Service Adoption.”

Here‘s the problem we set out to solve: integrating 16 BTP Fabric SDK business services across 100+ applications meant 2–4 hours of repetitive manual work per service, per app — editing mta.yaml, configuring IAS, writing boilerplate, every single time. That‘s 200+ engineer-hours of work that looks almost identical every time you do it.

Our answer: a multi-agent framework built on LangGraph + MCP, driven through Cline in VS Code.

We built 4 agents:

• Extensibility Agent — full CAP extensibility onboarding in 10–15 minutes, including IAS config and portal registration
• Import/Export Agent — annotating CAP entities for data portability with a loop-based annotation menu
• Event Handler Agent — pick one of 7 proven patterns, get code generated instantly
• Temporal Agent — previews every file change before writing, rolls back automatically on failure

The key design choice: patterns + LLM, not pure LLM. With 12–16 known services, encoding expert knowledge into YAML skill files means consistency, lower latency, fewer tokens, and no silent mistakes. The framework handles orchestration, pause/resume, checkpointing, and rollback — you just bring the domain knowledge.

The numbers: ~95% time reduction. 3–10 minutes per service, down from 2–4 hours. 200+ engineer-hours saved across 100+ applications. 

9+ more agents are planned. Same architecture, different domain knowledge.

Demo pod speakers got a shirt. I'll take it.

A Session That Caught My Eye: Act As for HANA DB

One session that genuinely caught my attention was on “Act As” for HANA DB. It felt familiar — FRE has a similar concept in the works, though for a different use case. Seeing the parallels and the differences in how “Act As“ is applied across contexts was a great reminder of how the same pattern can serve very different purposes depending on the domain.

The Pune Vibe

There‘s something special about the Pune office. It‘s smaller, which means almost everyone knows everyone — and that kind of familiarity creates a really warm energy at an event like this. I got to meet folks from the Supplier Management team I don‘t usually cross paths with, and those conversations were genuinely enjoyable.

Post-Event: The DJ Party

Let‘s be real — the post-event DJ party was awesome.

Tons of fun, great energy, and a perfect way to wind down after a packed day. These moments of connection outside the sessions are just as valuable as what happens inside them.

Shoutout 🙌

A massive thank you to the FRE Pune team for making this happen — it was a pleasure being part of this with you all:

And a special thank you to Harsh Verma and Krishna Bussu for sponsoring the trip — this experience wouldn‘t have been possible without your support.

What I'm Taking Away

D-com 2026 reinforced something I‘ve been learning on the job: the most important thing in AI-assisted development isn't the tool — it's the quality of your thinking. Clear requirements, solid validation, and business understanding are what turn a prompt into something production-ready.

And honestly, d-com didn‘t just inspire me — it pushed me to act on it immediately. While still in Pune, with a few inputs and suggestions from colleagues, I built a basic Q&A agent using Claude CLI and Cline in just a few hours. That‘s exactly the spirit of SAP‘s “All in on AI” motto in action — it‘s not a solo effort, it‘s everyone contributing, sharing, and building together.

Once I was back in Bengaluru, I shared it with colleagues for feedback. Those conversations helped me see what could be improved, and I‘ve been iterating on it since. It‘s a small example of exactly what d-com was preaching: just start, collaborate, get feedback, and make it better. The loop is faster than ever when the tools are this good.

The tools are getting faster and smarter. So the best investment I can make is in getting sharper on the what and the why — and letting Cline, Claude CLI, and the agents handle the how.

Also: Kullad chai from the hotel. A small touch, but a memorable one. 🍵

Thanks to everyone at d-com 2026 Pune for making it a day worth writing about.

#SAPdcom #SAP #AIAgents #VibeCoding #FRE