01
Design decisions
- The public site’s main action is registering a device — the “Report a device” button is visible from the first screen.
- The site and the panel are one product, so both use the same logic and the same order data.
—FULL-STACK / CRM · 2025
From a repair request to a connected system.

01Context
A platform for a repair business: a public website and a custom CRM for customers and service requests.
02Problem
The website needed to present services while the backend supported repair requests. Both sides required coherent logic and structured data.
03Approach
04Implementation
Custom request handling is part of the application, rather than a separate add-on. The public site and administrative panel form one system based on PHP, JavaScript and SQL.
05Details
The central interaction is customer and service-request management in a custom CRM.
06Technologies
07Result
A deployed platform connecting a service website with repair-management tools.
—Project details
01
02
03
04
→Next step
Write a few sentences about the goal and the current situation. I reply personally — usually with questions that help define a sensible first release.
Have an idea, a website to rebuild or a process that needs its own tool? I don’t need a finished specification — a few sentences about what you want to achieve are enough.
You write. One short form — a few sentences are enough.
I reply personally. Usually with questions that help clarify the scope.
We agree a direction. A short call, then a scope proposal and estimate.