I bring SAP Business One to the web, and AI to SAP Business One. Six years of .NET and Angular, a team of six led through a rescued bank project, and today web client extensions and an MCP prototype at Boyum IT.
Fig. 0 · B1UP Web Designer, click to deploynot to scale
6years of .NET and Angular
6developers led at HyperTeam
30+workflow statuses in a bank system
~10 sfrom edit to live preview
Selected work
3 sheets
Each sheet covers the problem, what I built and the decisions that mattered. No client code or internal details.
Sheet 01 · Boyum IT · 2025–B1UP Web Designer
Team of two · I owned the technical foundation
Customizing a SAP Business One web client screen used to be developer work: build an extension in VS Code, find controls with SAP's inspector, package an .mtar, then install it per company. We turned that into a Chrome side panel where admins point, click and deploy.
Reaching inside SAP's page. The web client is a SAPUI5 app, and Chrome's isolated content scripts can't see its JavaScript objects. I built a page bridge that runs inside SAP's own context and talks back through tagged messages with request IDs and timeouts.
A picker that survives SAP's markup. A click resolves from the HTML element to the UI5 control to the B1 widget's stable GUID, through layered fallbacks for labels, read-only fields, group headers and table columns.
Live preview without installing. I found that the web client can load extension files from a debug server, so the backend generates them on the fly. An admin sees changes in their own tab within about 10 seconds; everyone else keeps the installed version.
One-click deploy. The backend generates the UI5 project, builds the .mtar and installs it through the Extension Manager's API, with a Playwright fallback. Each company now gets its own extension, which fixed one company's customizations leaking into another.
Angular rewrite. I rebuilt the side panel from plain TypeScript in Angular on Boyum's component library, working through every screen with a designer.
Only the page bridge can see SAP's controls; only the backend touches the database and the Extension Manager.
result
Tested heavily by colleagues before release, with great feedback from consultants, partners and customers. Customizing a screen no longer needs a developer.
Sheet 02 · Boyum IT · 2025–Print & Delivery for the web client
Front end and backend, end to end
Print & Delivery, Boyum's add-on for previewing, emailing and saving business documents, only existed for SAP's desktop client. I built the web version: an Angular extension inside the web client and a .NET service behind it.
Working around the browser. Browsers only let a page open new tabs right after a click, and documents took longer than that to generate. The backend now returns document IDs at once and generates in the background; every tab opens instantly and polls until its document is ready.
Security without headers. Those tabs can only make a plain GET request. Each document gets a random GUID that works as a one-time link: served once, then deleted.
Any company database. The desktop add-on is tied to one company database at startup. My service keeps a data layer per database, picks it per request, and talks to MSSQL and HANA directly with pooled connections, so parallel requests never block each other.
Errors people can see. Request errors appear as native SAP message boxes; errors during background generation show as a readable page in the user's tab.
One service serves every company database, and every finished document exactly once.
result
Partners and customers praised the release for bringing the full feature set to the web.
Sheet 03 · HyperTeam · 2022–2025Taking over a late policy system for Erste Bank
Team lead of six · owned every technical area
Three months after I joined, the senior developers left. I became team lead of a policy management system for Erste that was half built and past its deadline: a half-finished workflow, an unfinished migration and a faulty directory sync. We released it within a year.
A workflow engine with 30+ statuses. Each status is its own class behind shared lifecycle abstractions, decisions with several approvers are calculated, and every step emails whoever owns the next one. I reworked parts of it, including its database transaction handling.
Permissions as derived state. Whenever a policy's status or a responsible person changed, the system recalculated its full read and edit rights and applied them to the policy's SharePoint folder, so access could never drift.
Directory sync and two SharePoints. I rebuilt the Active Directory sync as a daily job covering joiners, group changes and leavers, and put on-prem SharePoint and SharePoint Online behind one interface, swapped by dependency injection.
Migration and reporting. I finished the data migration and built a re-runnable tool that moved thousands of documents, years of history, without duplicates. I also built a report wizard that turns picked fields and conditions into Excel, next to about 40 custom reports.
From one client to a product. We turned the system into a modular template for new clients. I built its multitenancy: a tenant manager app, a database per tenant, middleware that routes each request, and EF migrations applied on startup. It became the standard for HyperTeam's other products.
Every change that affects access triggers one full recalculation for that policy.
result
Released within a year of the handover. We set priorities together with Erste's business side, hunted bugs with their technical owner in their environment, and they thanked the team at release. We kept supporting it afterwards.
Researching and prototyping a Model Context Protocol server that connects our product's AI assistant to SAP Business One data, deployed on the customer's own servers.
every day
Building with Claude Code
I use AI coding agents across the cycle: exploring and documenting unfamiliar code, implementing features and reviewing changes, while I own the design and check the output against the code.
next up
An open-source .NET MCP project
A personal project that combines a .NET MCP server with an AI layer, with all the code in public.
Experience
2018 – now
Aug 2025 – now
Software Engineer · Boyum IT, Budapest
Technical lead for the web side of one of the company's most important projects: web client extensions, the B1UP Web Designer, and the move of the B1UP codebase from TFS to Git with Azure Pipelines and Key Vault.
Oct 2022 – Jul 2025
Software Engineer Team Lead · HyperTeam, Budapest
Led a team of six building policy, contract and agenda management systems for major Hungarian banks and insurers, including Erste Bank and Generali, and turned them into reusable multitenant products.
Sep 2018 – Sep 2020
Fullstack Developer · CollabIT Consulting, Budapest
SharePoint-hosted procurement and contract systems for EGIS Pharmaceuticals and OTP Bank, and internal tools for T-Systems' Hungarian subsidiary.
Education
2015 – 2018
BEng Biochemical Engineering · University College London
Mathematical modelling, thermodynamics and process engineering, with a minor in finance and accounting.