A guided tour · 12 beats

Your best consultant can't sit at every desk.
Their playbook now can.

CSPeach is an AI consultant for SAP teams. It does the whole job a senior ABAP developer does — not just the typing. Here's what that means, and why it's different from everything else you've been shown.

01 / 12
A day on a SAP team

Coding is the smallest part of the day.

Before a line is written, someone reads the spec and finds what's missing, designs the objects, estimates the effort, checks it's clean-core ready. After, someone reviews it, writes the tests, traces the 6 p.m. dump, and builds the transport without breaking production.

The sequence of real SAP work

Typing the ABAP is maybe 20% of it. The other 80% is judgment.

02 / 12
What everyone else sells

AI that just generates code.

It lives in your IDE. It writes ABAP on request — and even when it writes a whole method, it stops at the code. It touches exactly one box on that strip. It doesn't know your estate, your spec, your transport, your clean-core debt, or last night's dump.

What a code generator actually touches

Faster code. Same bottleneck.

03 / 12
Why teams stay slow

The bottleneck isn't keystrokes. It's the senior.

Every SAP team has one or two people whose judgment everyone queues for. Is this design right? How long will it take? Is it safe to transport? Will it survive S/4? That knowledge lives in their head — so juniors wait, seniors firefight, and the playbook never leaves the room.

Junior Junior Mid Mid
The senior every decision routes here ⟶ everyone waits
04 / 12
A different kind of tool

Not just a code generator. A consultant — at every step.

CSPeach is 35 skills, each one a senior's playbook for one part of the job. It lights up the whole strip, not one box — and it carries the same rules a senior consultant would apply themselves.

What CSPeach covers · one skill (of 35) shown per phase

05 / 12
35 skills · grouped by the job they do for you

The skills, and the day they give you back.

Understand

Walk into unfamiliar ABAP and grasp it in minutes — not days of tracing where-used lists.

/abap-radar/abap-explain/abap-document/abap-handover/abap-impact

Plan & design

Decide before coding — the missing questions, the object list and sequence, an estimate with real risk ranges, and a plan that holds across sessions.

/abap-spec-gap/abap-plan/abap-design/abap-data-model/abap-estimate

Build & modernize

Clean-ABAP by default — scaffold a RAP stack, modernize legacy reports, refactor to OO, all on your release level.

/abap-generate/abap-rap/abap-modernize/abap-refactor/abap-segw/abap-eml/abap-enhance

Review & quality

Senior-grade review, unit tests, performance and clean-core checks on every change — before it ships, not after.

/abap-review/abap-atc-fix/abap-test/abap-performance/abap-cloud-check/abap-preflight

Upgrade & migrate

Estate-wide S/4 readiness and upgrade remediation in hours — scan, fix with rollback, verify, and sign off.

/abap-cca/abap-migrate/abap-upgrade-scan/abap-upgrade-fix/abap-upgrade-verify/abap-transport-analysis

Operate & fix

From a 6 p.m. short dump to a verified fix and a clean transport — incident to delivery in one flow.

/abap-incident/abap-dump-analyze/abap-dump-triage/abap-transport
06 / 12
How it works

It asks before it builds.

01

It asks the questions a senior would ask — before touching anything.

02

It plans the whole thing — and waits for your yes.

03

Then it executes one safe step at a time, verifying as it goes.

07 / 12
For a whole project — not just a task

It plans the project — and picks up where it left off.

Real SAP work spans days and many sessions. /abap-plan lays out the whole project as phases, runs one phase per session in a focused, bounded context, and carries the state forward in a single plan envelope — so no one has to re-brief it tomorrow.

plan envelope · @sales-credit.plan — state persists across every session
Session 1Spec gapsdone ✓
Session 2Designdone ✓
Session 3Data modeldone ✓
Session 4Buildnow ▶

Create it from a goal or a spec-gap envelope · resume the next day with --resume · one phase per session keeps context tight and cost low.

Every session moves the project forward. Nothing gets re-explained.

How it reaches your SAP

From your laptop, straight to your system.

How CSPeach connects A developer on their laptop talks to CSPeach in plain language. CSPeach reasons with an AI model — Anthropic, OpenAI, or the team's own key — and reads and writes the SAP system only through audited ADT calls from the laptop, under ten Forge Rules. AI PLANE YOUR SAP LANDSCAPE ADT REST only · your code stays here AI model Anthropic · OpenAI …or your own key (BYOK) You & your team cspeach CLI · plain English on your machine CSPeach 35 skills 10 Forge Rules runs on your machine Your SAP ECC · S/4HANA snapshot · ATC · transport plain English reasons ADT REST every write: audited & reversible

You talk to it in plain language. It reasons with an AI model — ours, or your own key. It touches your SAP only through audited ADT calls, from your own machine — snapshot, syntax check, ATC, transport, every time. See the full architecture →

08 / 12
Why it compounds

Each phase feeds the next. The project explains itself once.

Each skill hands off to the next — spec-gap feeds design, design feeds the build, the same scope drives CCA and the upgrade. That context lives in a shareable, versioned envelope your whole team can open and review without a login — not locked inside one person's chat history.

spec-gap-v1.cspeach.json
   design-v1
     estimate-v1
       cca-assessment-v1
         upgrade-scan-v1
           upgrade-report-v1

No phase ever asks your team to explain the project again.

09 / 12
Safe on a real system

It doesn't just suggest. It can act — safely.

This is what separates a consultant from a chatbot. CSPeach writes directly to your SAP system under ten Forge Rules it cannot break — so a manager can trust it on a productive system, not just a sandbox.

R1No blind generation. Ask the missing questions first.
R7Snapshot before every write. Always a way back.
R8No batch without a plan you approved.
R9Transport isolation. Clean, traceable change.
R10Verify after every write. Syntax → ATC → activate.
Automatic rollback from the snapshot on any failure.

Every change leaves an audit trail in its own transport.

10 / 12
What changes for your team

Every desk moves like your best desk.

Before

  • One senior is the bottleneck for every decision
  • Juniors stall, waiting for review
  • The playbook lives in one person's head
  • Multi-week projects lose the thread between sessions
  • Upgrades drag on for quarters
  • Last night's dump eats the morning

With CSPeach

  • That senior judgment, at every desk
  • Juniors ship senior-grade work
  • The playbook lives in the tool — shared
  • A living plan carries the project across sessions
  • Estate readiness in hours
  • Dumps triaged straight to a fix

Same team. Senior-level output. That's the superpower.

11 / 12
On the roadmap

And we're just getting started.

CSPeach already covers the back-end delivery lifecycle, live today. Next, it grows toward the rest of the SAP surface — the front end, your landscape, your standards.

In progress

Freestyle Fiori

Fiori Elements already comes free from RAP. The hard part is freestyle SAPUI5 — custom views, controllers and controls. CSPeach will generate those: the front end your business actually asked for.

On the roadmap

BTP deployment lane

Run CSPeach through your own BTP wrapper — XSUAA, Destination, Cloud Connector — governed entirely by your landscape.

On the roadmap

Customer playbooks

Your naming, your standards, your patterns — baked into every skill for your team, with no forks to maintain.

These are on the roadmap — not released yet. Everything in the lifecycle you've just seen is live today.

Get started

See what your team could do.

One CLI, one viewer, 35 skills. From the first spec gap to the final transport — a senior ABAP consultant, at every desk.

CSPeach © Cremencing Solutions · Home · GitHub

12 / 12