Case study · FujitsuEnterprise · SAP
May 2022 to Feb 2024Frontend lead, team of three03 / 04
May 2022 to Feb 2024Frontend lead, team of three03 / 04
All clients
Fujitsu
Leading three developers into a from-scratch SAP dashboard
An internal SAP administration dashboard built from zero: stack selection, domain architecture and the proof of concept that won the budget.
Enterprise · SAPMay 2022 to Feb 2024
What changedMeasured before
and after3 outcomes
in production02
and after3 outcomes
in production02
What changed
(01)−70%Time to complete core SAP tasks3× faster than legacy
(02)ApprovedPoC won funding for the full project
(03)3Developers led end to end
The processWhat we walked into
and what we didFrontend lead, team of three03
and what we didFrontend lead, team of three03
What we
walked into
- SAP administrators completed core tasks through long multi-screen legacy flows with heavy manual steps.
- There was no frontend architecture, no conventions and no shared component library to build on.
- Stakeholders wanted evidence before funding a full rewrite.
- Requirements arrived incomplete and contradictory between backend and product.
What we
did
- (01)Selected the tech stack and defined the domain architecture, folder conventions and review standards the team worked to.
- (02)Produced wireframes and Material UI specifications for the core administration flows.
- (03)Built the proof of concept around the three highest-frequency tasks and instrumented time-to-complete against the legacy flow.
- (04)Ran requirement refinement sessions with backend and product, and converted the outcomes into tickets for the team.
- (05)Led day-to-day work for three developers: task breakdown, code review and technical decisions.
StackReactTypeScriptSCSSMaterial UI
Now an agentThis playbook runs
on every commit1 agent
in the fleet04
on every commit1 agent
in the fleet04
What we did by hand,
the fleet now repeats
The agents below now run the checks, measurements and fixes from this engagement on every repository they connect to.

Next stepGains Audit
Fixed price, fixed scopeTwo weeks
One repository05
Fixed price, fixed scopeTwo weeks
One repository05
Find out what
slow costs you.

Start with a two‑week audit.
We connect the fleet to one repository for two weeks. You get a ranked list of gains in euros and the first pull requests, already open.
