01
You send us the problem
Which application is underused, and what specifically goes wrong. A screenshot and two paragraphs is plenty to start.
See the work
Most consultancies show you slides.
We cannot publish client deployments — they sit inside live systems under confidentiality. So instead of describing the craft, this page demonstrates it. Everything below is real, running in your browser right now.
A purchase requisition, mid-process.
A form on a system nobody enjoys using. Step through the guidance the way one of your users would — including the Deciding which users see which guidance, based on attributes like role, tenure, region or licence type. Get it wrong and everyone sees everything, which is how guidance becomes noise people learn to dismiss. decision that stops it annoying everyone else.
my-company.s4hana.ondemand.com
Create Purchase Requisition
General information
CC-4420-EU
Select…
Search supplier…
14.09.2026
Items
Save as draftSubmit for approval
1/4
Start where the work stalls
The requisition form is where users abandon. Guidance opens on the field that causes it, not on a welcome message nobody reads.
2/4
Validate before submission, not after
A guardrail overlay checks the cost centre against the account assignment while the user is still in the field. The data problem is prevented, not reported.
3/4
Automate the lookup
Rather than sending the user to a second system for the supplier code, an ActionBot retrieves it from the backend and writes it into the field.
4/4
Segment who sees this
This flow targets requisitioners in their first 90 days. Experienced users see a Smart Tip instead — the same content, a tenth of the interruption.
- 01
Start where the work stalls
The requisition form is where users abandon. Guidance opens on the field that causes it, not on a welcome message nobody reads.
- 02
Validate before submission, not after
A guardrail overlay checks the cost centre against the account assignment while the user is still in the field. The data problem is prevented, not reported.
- 03
Automate the lookup
Rather than sending the user to a second system for the supplier code, an ActionBot retrieves it from the backend and writes it into the field.
- 04
Segment who sees this
This flow targets requisitioners in their first 90 days. Experienced users see a Smart Tip instead — the same content, a tenth of the interruption.
The vocabulary
Six element types. Choosing between them is the job.
A walk-through where a tip would do is an interruption. A tip where a guardrail is needed is a data problem you will meet again downstream. Most of the craft is in this choice, not in the building.
- Smart Walk-ThruSequenced
- A process with several steps that users get wrong in a consistent order.
- Smart TipContextual
- One field, one recurring misunderstanding. The lightest possible intervention.
- LauncherEntry point
- Guidance the user should be able to summon rather than be interrupted by.
- ShoutOutAnnouncement
- A change users must know about before they next attempt the task.
- ActionBotAutomation
- The user knows what to do and it simply takes too long. Retrieve, prefill, submit.
- GuardrailValidation
- Bad input that becomes a data problem downstream. Catch it at the point of entry.
The offer
We build one on your system, free.
The demo above runs on a mock screen. The useful version runs on yours — which is what we do before any engagement is agreed, at no cost and with no obligation.
02
We look at the actual screens
A 30-minute call on your system. We are looking at how it renders, what it exposes for identification, and where the work genuinely stalls — not at your slide deck.
03
We build it
A working solution in your environment, typically within a week. Not a mockup and not a recording of somebody else's system.
04
We show you how it was built
Including the decisions and the trade-offs. If you take that knowledge and build the rest in-house, that is a fair outcome.
The obvious question is why we would give away the work. Because it is the fastest honest way to establish whether we are any good, and because a proof of concept that does not impress you has told us both something useful early.
Bring us a system that isn't being used.
Send us the application and the problem. We'll build a working proof of concept on your real screens and walk you through how it was built. No charge, no obligation.