adamOne Services — SAP technical shop that also vibe-codes Fiori

Custom Fiori apps.
Vibe-coded. Honestly declared.

AOS is a SAP Technical Services practice — BASIS, ABAP, BTP. One of the things we build for you: bespoke Fiori apps, AI-assisted, and we say so out loud. You get the full source, every setup & activation guide, and a Basis/ABAP service list. No runtime lock-in.

// scope in one message: which landscape + what the app should do
The technical bench behind the build — we run the systems we deploy to.
BASIS · admin & ops ABAP · on-stack & Cloud BTP · side-by-side Fiori · vibe-coded
01 / Source
Full source, in Git. Yours to keep, fork, rebuild.
02 / Guides
Every setup guide. OData, roles, catalogs, tiles — documented.
03 / Basis/ABAP
We can activate it too. Same shop does the plumbing.
04 / No lock-in
No proprietary runtime. Standard SAP, standard transports.
Three landscapes, three products

Pick your landscape. It decides everything.

"Custom Fiori app" means something different on each SAP landscape — the tooling, the access we need from you, and what we can deliver. We scope this before a line of code.

On-Prem / PCE

Private Cloud & on-stack

Deployed to the ABAP repo, transported.
Tooling
  • ABAP Dev Tools (Eclipse / ADT)
  • Fiori Elements & freestyle UI5
  • Gateway OData · /IWFND/MAINT_SERVICE
  • STMS transport promotion
You provide
  • HTTPS 443nn + SAP GUI 32nn
  • Dev user + transport request
  • Developer key if the release still enforces it
Public Cloud S/4

S/4HANA Cloud, Public Ed.

No on-stack code — extend the clean core.
Tooling
  • ABAP Cloud — released APIs only
  • Key-user extensibility
  • SAP Build Apps / side-by-side on BTP
  • Consumes released OData / CDS
You provide
  • Communication arrangement + business role
  • API access only — no ports, no dev key
  • BTP subaccount if side-by-side
BTP

Side-by-side on BTP

Decoupled app, any backend.
Tooling
  • Business Application Studio (BAS)
  • CAP / RAP services
  • UI5 + MTA packaging
  • Work Zone / HTML5 app repo
You provide
  • BTP subaccount + entitlements
  • Cloud Connector to your backend
  • Destinations config
How you engage

From requirement to invoice.

Four moves to start, then the same milestones every time. The landscape only changes the middle — the tooling. Payment splits 50 / 50 around the work.

01
Message the scopeLandscape + what the app should do, on WhatsApp or email.
02
Approve & pay 50%We send the plan, access checklist, and price. You confirm.
03
Build & iterateWe develop and test in review loops with you.
04
Deploy, hand over, closePromote, deliver source + guides, final 50% invoice.
Requirement intakescope + landscape check
Which landscape?
On-Prem / PCE
ADT · SE80 · Fiori Elements
Gateway · STMS
Public Cloud S/4
ABAP Cloud · released APIs
SAP Build · BTP
BTP
BAS · CAP / RAP · UI5
MTA · Work Zone
50% upfront paymentwork starts
Development / test iteration↻ review loop with you
Deployment / promotiontransport · deploy · activate
Documentationfull source + setup guides
Closure + final invoicingremaining 50%
Packages · per project

Three ways to buy.

Every tier ships full source, setup guides, and a 50 / 50 split. Prices are per project — final quote depends on scope.

Starter

Low

$1,900per project · 50% to start
  • 1 custom Fiori app
  • 1 landscape
  • Full source + setup guide
  • Standard OData / CDS
  • No Basis/ABAP activation service
  • No BTP side-by-side
  • No post-go-live support
Choose Starter
Standard

Mid

$3,900per project · 50% to start
  • Up to 2 Fiori apps
  • 1 landscape
  • Full source + setup guides
  • Email support during build
  • No Basis/ABAP activation service
  • No BTP side-by-side
  • No post-go-live support
Choose Standard
// prices are launch placeholders — tune to your market. 50% on start · 50% on closure applies to every tier.
What lands in your hands

Everything, handed over.

Deliverables

</>
Full source in GitUI5 / Fiori Elements / CAP-RAP — no black boxes.
TR
Deployment packageTransport requests, MTA, or API activation — as the landscape needs.
DOC
Setup & activation guidesOData services, roles, catalogs, tiles, launchpad — step by step.
SVC
Basis/ABAP service listExactly what to activate — or we do it (Pro).

Engagement terms

To start50% upfront
On closure50% final
AI-assisted builddeclared
Runtime lock-innone
Source ownershipyours
Start a build

Tell us the landscape and the app.

One message is enough to scope it: which SAP landscape you're on, and what the Fiori app should do. We reply with the plan, access checklist, and price.

// vibe-coded, and we tell you so — full source, no lock-in, run by an SAP technical shop