We launched on Reddit and it crashed our app. 🫠

I had assumed Reddit wasn't where our audience was. So I posted at midnight and went to sleep.

My expectations were low. I had assumed that:

• Reddit isn't the place for enterprise AI
• The post wouldn't get visibility since AI is a contentious topic in SAP subreddits

What actually happened was that we received so much traffic that our app was down for 3 hours. 😅

What I learned:

1️⃣ Make it ridiculously easy to try your software

I didn't lead with fancy efficiency numbers. Just "here's what the tool does" with a link to try it for free, no login required.

There's so much noise in the AI market right now. Even if you're an early entrant in your category, there's a good chance people have been burned by an AI promise before.

If you add any friction, (say a signup button), they'll decide you probably won't work for them, and will readily move on with their day.

The only thing that cuts through is letting them experience it themselves.

2️⃣ Do staggered launches. Don't blow everything on one big moment. Spread it out.

3️⃣ Launch everywhere. It's typical startup advice, but harder to actually practice than it sounds.

Now, on to celebrating that we're the #1 post on r/ABAP today 🎉

Yesterday, we opened up free access to our SAP Change Request agent for everyone who requested it earlier.

The response has been amazing! So we're expanding access limits and squashing a few bugs we found along the way.

Claude Opus 4.5 was released yesterday and is claimed to be "the best model in the world for coding," so I was curious how it performs in ABAP development.

So I asked both Opus 4.5 (the newest model) and Sonnet 4.5 (the previous model by Anthropic) to create an ALV report for sales order analysis using traditional ABAP. See the complete prompt in the attached document.

My first impressions:

1. Table selection: Both models hallucinated incorrect tables on their first attempt. Opus 4.5 self-corrected after one prompt; Sonnet 4.5 needed two.

2. Syntax errors: Both models produced syntax errors initially. Opus 4.5 fixed them after one prompt; Sonnet 4.5 took five attempts.

3. Scope discipline: Opus 4.5 produced only what was requested. Sonnet 4.5 added unrequested features and documentation, increasing output length and review time.

Overall:

-> Opus 4.5 reached an error-free solution in 3 iterations; Sonnet 4.5 took 7. -> Opus 4.5's leaner output made its first attempt ~50% faster to generate.

This was a simple, quick test. I'm planning to try more complex scenarios next. Stay tuned.

Excited to share an early preview of ChromaSQL, a new SQL-like language that helps ABAP developers access SAP’s tribal knowledge in a few seconds instead of wading through SE11/SE84 and stacks of notes. 🎉

Say a business user asks you to tighten credit limit checks at order entry. Instead of manually digging through your SAP system chasing BAdIs, tables, and all the related artifacts one by one, you just type what you’re after: “credit limit check enhancement.”

SELECT id, distance, metadata.object_type
FROM sap_artifacts
USING EMBEDDING (TEXT 'credit limit check enhancement')
TOPK 5;

That one query runs a vector search across your SAP knowledge base and hands back the top five hits with similarity scores. You learn about:

• BAdI implementations like ZSD_CREDIT_CHECK,
• Tables (VBAK, KNKK) you need to regression test,
• CDS views with related logic,
• Even past transports you might have forgotten.

Now you can decide:

• which enhancements to review,
• what downstream integrations (credit exposure reports, for example) could break, and
• exactly what to drop into your change spec or automated checks.

Result: Less time wasted digging through SE11/SE84, fewer missed dependencies, and a clearer rollout plan for every change request.

We’re putting the final polish on the release right now.