An independent technical assessment before you decide – code review, evaluation of quotes and architecture proposals, technical due diligence.
Code Review & Technical Second Opinion
Without in-house developers, technical decisions have to be made on trust: Is the agency's quote reasonable? Is the code we paid for any good? Is the proposed architecture sensible or just expensive? I give you an independent, understandable assessment – with no stake in the follow-up job and in language you can use in the meeting.
Typical tasks
Code review of delivered work
Plugin, integration or application from an agency or freelancer: quality, security, maintainability, test coverage, adherence to Shopware or Symfony conventions. As a report with concrete findings and priorities.
Evaluate quotes and estimates
You have a €40,000 quote for a feature that seems small to you – or the other way round. I put effort, approach and risks into perspective so you can negotiate or decide.
Architecture second opinion
Headless or not? Custom ERP or standard? Plugin or standalone service? I check proposals against your actual requirements and name the consequences for cost and operation.
Technical due diligence
Before an acquisition, investment or purchase of a store: state of codebase, infrastructure, dependencies, licences and team knowledge – with risks and estimated modernisation effort.
Security check
A targeted review of typical vulnerabilities in PHP applications and Shopware plugins – input validation, permissions, data access, outdated dependencies. Not a full penetration test, but a realistic picture.
Sparring partner for technical questions
Regular short sessions for day-to-day decisions: vendor selection, prioritisation, hosting, security questions. A developer at your side without having to hire one.
What you get
- A written report: findings, ranked by risk, concrete recommendations
- A call where we go through the points – questions explicitly welcome
- On request the implementation of the recommendations, but never as a condition
How I work
Three principles that apply in every project
Understand before building
First the short technical assessment: what is the actual problem, where is the lever, what makes economic sense? Then the implementation.
Build instead of forwarding
You talk to the developer who does the work – no handover chain, no black box, clear status updates and early warning about risks.
Hand over instead of holding on
Code in your repository, tests, documentation and a deployment process your team understands. No vendor lock-in – your system does not depend on me afterwards.
Background
Experience at a glance
- Today
- Senior freelancer in ongoing Shopware projects of several agencies and merchants – at home in foreign repos, processes and deadlines.
- Since 2021
- Self-employed as Stefan Pilz Ltd. – remote for merchants and agencies: Shopware 5 and 6, Symfony, migrations, maintenance.
- 2015 – 2020
- E-commerce backends: inventory, PIM and Amazon/eBay integrations for around 3.5 million products, then the Drillisch mobile-carrier web stores.
- Since 2012
- Full-time web developer – first at an agency: websites and stores with Joomla, xt-Commerce and Shopware.
- 2002
- Completed vocational training as a software developer (C/C++). First own PHP websites from 2004.
See current and completed projects Career and stack in the CV
Good fit
Works well when...
- you have a concrete business requirement that standard software does not cover cleanly.
- you need an experienced PHP/Symfony developer who implements directly instead of forwarding tickets.
- you run existing systems, stores or integrations that have to work together.