Shops
B2B and B2C, with configurators and pricing logic nobody else will touch — rebuilt cleanly instead of patched further.
Evidence: case 305 — shop rebuild in steel tradingFormat · Implementation · Fixed price per milestone
Implementation: when it has to be built.
Shops, tools, interfaces, platforms — lean and native, without framework ballast. My AI pipeline delivers in weeks what used to take months; every line is signed off by me personally. You pay a fixed price per milestone — no open-ended invoice.
AuthorMatthias EgerCertified Manager for Applied AI Transformation (IHK)Last reviewed17 Jul 2026
To the verification recordWhat gets built
I build four things.
All the same way: lean, native, maintainable.
No page builder, no framework ballast, no dependence on fashions. What is built here is something your business understands — and so does every developer who comes after me.
Tools
Internal tools that mirror your actual workflow — instead of off-the-shelf software that is 90 per cent ballast and missing the one click that matters.
Interfaces
ERP, shop, logistics, accounting — data flows automatically instead of being retyped. Connected once, quiet for good.
Platforms
Portals and own products on a database structure that can take growth — from the first user to full operation.
Evidence: case 313 — this website was built in days
The principle above all
You stay the owner. I remain the judgement. Full source code, all access credentials, no lock-in — that is written into the contract. And nothing goes live before I have personally checked and signed it off.
How a project runs
Four steps —
from the first conversation to handover.
01
First assessment: does anything need building at all?
30 minutes, free. You tell me what you do and where it hurts — I tell you whether a new build pays off or whether a 30-euro off-the-shelf tool will do. Even when I earn nothing from it. You get three starting points in writing.
02
A plan in numbered points.
No novel-length spec: every point is a verifiable statement, ordered by what brings in money first. For the shop rebuild in steel trading it was 100 points across four phases — the pricing engine with 16 discount tiers first, then the rest. Evidence: case 305 — shop rebuild in steel trading
03
Delivery in milestones — the most important part first.
The core that carries your business goes live first — no all-singing, all-dancing system that never gets finished. My AI pipeline builds, I check and sign off. You keep seeing clickable results instead of waiting for months. Every milestone has a fixed price; you pay for what has been signed off.
04
Handover with full source code.
Code, access credentials, documentation — it all belongs to you, without lock-in. If you want, I stay on as Operator and take responsibility for running the system. If not, any other developer can take over — that is exactly why the code is built this way.
Why it is this fast
The AI pipeline builds.
I sign it off.
Code drafting, review and documentation run in fixed slots through my own pipeline — local models where your data has to stay in-house, large models where performance counts. Whatever the machine makes faster, I pass on as a saving in time and price. What it cannot do — decide what gets built and what goes live — stays with me.
Rein
Dokumente
Sprachnotiz
Fotos & Daten
Pipeline
Mensch führt · KI arbeitet
Raus
Angebot
Code & Tool
Text & Plan
The proof in front of you
The page you are reading right now is case 313: conceived, built and written with AI — in days, not weeks. Same pipeline, same sign-off, same principle as in your project. View case 313 →
Frequent questions
What owners want to know before a project.
Why without framework ballast?
Frameworks bring thousands of lines you will never need — but still have to maintain, update and secure. Native code is leaner, faster and still readable in ten years: for me and for every developer after me. Your business stays independent of fashions and update cycles.
What does fixed price per milestone mean?
The plan breaks the project into milestones — each with a verifiable result and a fixed price. Payment follows sign-off: no timesheets, no open-ended invoice. And after every milestone you decide again whether and how to continue.
How fast is this?
Small tools and interfaces: often days. A new shop build: weeks instead of months. This website was built in days — case 313. Reliable dates are in the plan, per milestone — not as a vague overall estimate.
What is the AI pipeline?
My own development environment: code drafting, review and documentation run in fixed slots through AI models — local ones where data has to stay in-house, large ones where performance counts. It makes me faster, but it does not replace the judgement: every line is checked, nothing goes live without my sign-off.
Does something need building at your place? Then let's talk about the first milestone.
First assessment · 30 minutes · three starting points in writing — free