I look before I rebuild
Most systems don't need replacing. I start by finding out what actually goes wrong, then fix that. A rewrite is my last suggestion, and if I make it, I'll explain why.
MDSolutions is my company in Embrach, near Zurich. When you hire MDSolutions, I'm the person on the first call, the person writing the code, and the person you call when something needs to change a year later.
Most of my projects sit where a website stops being a brochure and starts running part of the business: a booking flow, a customer login, a registration desk, a link between the shop and the warehouse. I design and build those systems, and I take over existing ones that have become hard to change.
For the Geneva Supercar Show I built the platform behind registration, tickets, QR entry, and guest transport, including the sync with the physical gate. For a luxury watch brand's private event I built the operations platform that dispatched drivers live and kept staff in touch over push-to-talk. For a Swiss watch manufacturer I kept the retail backend running and extended it with catalogue, regional pricing, stock, and video for its retailers around the world.
Event software has to work on the day. Doors open at a fixed time, and guests don't wait while someone fixes a bug. I plan every project that way, whether it's a company website or the system your team opens every morning.
Most systems don't need replacing. I start by finding out what actually goes wrong, then fix that. A rewrite is my last suggestion, and if I make it, I'll explain why.
The person you explain the problem to builds the solution and picks up the phone afterwards. What you said in the first meeting is still known in the last one.
I build with widely used, well-documented technology and write down how things work, so another developer could take over. Access to code and hosting can sit with your company from the start.
You get the scope and the price in writing first. If something changes along the way, we agree on it before it's billed.
A short message is enough. I'll reply personally with an honest first take and a concrete next step.