What we're building next.

Live, on-demand S/4HANA data inside FSA — read-through, snapshot into FSA, and write-back to S/4 with concurrency checks and a conflict dialog. One client covers OData V2 and V4, so it works either side of SAP's own migration. Ships with 13 curated mapping templates and a discovery API for everything else. It runs on your own SAP BTP subaccount, with your credentials, over your network path.

Calls to S/4 carry the technician's own authorisations rather than one shared service account, via OAuth, SAML bearer or principal propagation. Writes are opt-in per entity at the engine, so it cannot write anything you did not allow.

Turn any screen — or a whole category of screens — into its own installable FSA extension in one click. One deployment behind it, never one per screen. 18 outlet placements plus the Shell home screen, short install links, and revoke, reactivate or delete per install without touching the others.

The same products and screens inside the FSA mobile Web Container, and as an installable app on the device. Five products on the shell, pinned single-product mode or a curated subset, and minted screen extensions on mobile too.

Licences can be capped by the number of people who actually use them, over an activity window. One person is one seat across laptop, phone and a second browser; someone who stops using it quietly releases their seat; nobody working is ever evicted mid-session. If our licensing service is unreachable, users are let in.

Export every screen design to one bundle and import it into another company — dev to test to production. A read-only preflight reports collisions, renames, missing references and S/4 dependencies before anything is written, then you choose create, overwrite or skip per screen. The bundle carries the user-defined-object definitions with it, so a restore can create the ones the target tenant is missing.

S/4 Live, Warranty Checker, Stock Checker, Service Report Compiler, Checklist Manager, Attachment Renamer and QR Labels. Each installs from a single permanent link with no setup, and each is unlocked by its own entitlement on your licence.

Standard reports, user-defined-object screens, SAP document screens and fully custom screens — designed by your own power users, no code and no deployment cycle. Screens can also scope themselves automatically to the record whose tab they are opened in.

A report block can read live from S/4 alongside FSA objects and user-defined objects in the same screen. Blocks that carry a date can merge into one chronological stream — the view behind an equipment history page.

Export a master file, edit it, upload it back: rows are classified as create, update or skip, reviewed before anything runs, and the whole import can be undone in one action. Failed rows come back as their own CSV. Files survive Excel — European separators, umlauts, leading zeros and no formula injection — and a whole report exports as one workbook with a sheet per table.

Ask a list for what you want in plain language, explain a field, explain an SAP error, get a mapping suggested from your own metadata, generate a template, and have a screen checked for broken bindings. Every tool passes three independent switches — the engine, your tenant, then the individual screen — and each layer can only narrow the one above it. Error explanations answer from a curated knowledge base first, which needs no AI at all.

The equipment-history pattern applied to business partners: FSA service history alongside S/4 sales orders, invoices and credit status, in one chronological view. The starter screen exists; the remaining work is the S/4 side, where credit-status availability differs by system.

Photograph an equipment nameplate, have the serial and model read off it, review what was extracted, and fill the FSA equipment record from it. Specified end to end; the largest piece not yet started.

The equipment timeline ships today as something you configure. Next is shipping it as a starter template you install, the timeline presentation in the other designers, server-side filtering on S/4 columns, and 'open in S/4' links straight from a row.

Natural-language filtering works on record lists and document lists today. Next it reaches report screens' driver bars and the search-help lookups, so the same sentence works wherever you are.

Paste an email or a note and have the fields filled in, with every value shown for review before anything is saved. Designed, deliberately not built — the review step is what makes it safe, and it needs a real workflow to design against.

See your active licences, entitlements and renewal dates, and request a renewal without emailing anyone. Worth building when issuance volume justifies it; today a person answers the same question the same day.

Seven products exist because customers named seven specific problems. The eighth will come the same way — tell us what your technicians work around every day.