Say a forklift and stacker rental business in Gebze has ninety machines out on customer sites. Faults are reported through WhatsApp groups, email and voice notes. Technicians get their jobs in a spreadsheet, and only the operations lead knows which units have missed their periodic service. Management says “we need an app”, which is true but is not yet a project. Most software projects fail not because the code is bad but because they build the wrong thing very well. So our starting point is reducing uncertainty rather than writing code. First we watch where information goes missing and for whom, then define the smallest version that is useful, put it in front of real users and only scale it once the data backs it up. Everything runs remotely over screen sharing and video calls. Each stage begins with its own quote and ends with its own deliverable, so at no point are you locked into something half-built.
The ground we cover when an idea becomes a working product. All of it is documented so that a different team could make sense of it tomorrow.
We hold screen-sharing sessions with four or five future users and watch how they get the job done today. The gap between the process described in meetings and the one people actually follow is usually what the project is really about.
The project gets one figure to aim at, for example the average time from a fault report to a technician being assigned. Months later that figure, not a debate, tells you whether it worked.
Every feature request goes into one of three buckets: essential for release one, later, or maybe never. The first release usually ships with under a third of the list and still solves the problem.
If SaaS tools, sector packages or modules for Logo and Mikro already cover the need, they go on the table too. We only recommend building from scratch when ready-made options genuinely fall short.
Screens drawn in Figma become a flow that users try on their own phones. Moving a button at this point takes minutes; in a live system it takes days.
Laravel and Vue, PostgreSQL, automated tests, a staging environment and a CI pipeline that runs on every change. We pick technology that someone can still maintain years from now, not whatever is fashionable.
If personal data is processed, a KVKK privacy notice and a permissions model are designed in from the start. If documents are issued, so is the e-Fatura and e-İrsaliye flow through the özel entegratör you have chosen.
At the end of every step you choose to continue, adjust or stop. Time and budget for the next step are confirmed in writing based on what the previous one revealed.
Interviews, a process map, the success metric, a comparison with ready-made products and a rough effort estimate. You could hand the result to any other software firm.
Tappable screens and two or three rounds with users. The scope of release one is signed off at the end.
A small team does its real work in the new system, with a fresh build and a short demo every fortnight.
We check the success metric, rank the next features by value and move the system into routine operation and maintenance.
Keep a “not for now” list. Good ideas will keep arriving throughout the project, and each one pushes release one back a little further. Do not reject them; write them on a separate list and leave it alone until the first release is in users' hands. Genuine feedback from the pilot tends to make half of that list unnecessary.
Yes, that is exactly what discovery is for. What we need from you is access to the people living with the problem and one decision-maker who can answer questions about the process. We draw up the requirements together.
Each stage comes with its own quote and hour estimate. Time is billed at €55 per hour plus VAT with a weekly breakdown. If an estimate looks likely to be exceeded, we ask you before doing the extra work.
The repository lives in your GitHub or GitLab account, and servers and domains are registered in your name. The contract transfers usage rights to you. When the collaboration ends, removing our access is all it takes.
We begin with a code and infrastructure review lasting a few days. You then receive a short report explaining whether it makes more sense to carry on or to rewrite particular parts, and why.
We can, with a small monthly pool of hours covering security updates and minor changes. Or we hand it over to your own developers or another company with documentation and walk-through sessions.
Which problem do you want to solve, and who deals with it today using which tools? We will reply with a quote for the discovery stage.
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
No such city in our list. Try another spelling, or just pick the closest big city: we work entirely over remote connections, so nothing about the service changes from one province to the next.
The only cookies here are the essential ones: they keep the site running and remember the city you picked. Nothing is used for advertising or tracking. See our privacy notice for more.
