Our process
We run a project in four stages.
Planning, architecture, modelling and development. Below is what we do at each stage, what we need from you, and what you end up with.
Decisions come before code
A decision costs more the longer you leave it. At AlgoKlima a technician can create a service record where there is no signal; asking for that at the start is a design choice, while asking for it after launch means rewriting a large part of the system. So before any code we sit down and work out how the job actually has to run: which step comes in what order, who sees what, and where each piece of information is kept.
Planning
The rules of the job and the scope of the first release get written here.
What happens
- Discovery
We work out together how the job runs today: which steps happen by hand, in a spreadsheet or over the phone, and what decides the order and the price. All we need from you is to describe it; there is no document to prepare.
- Requirements
We put what we discussed in writing: which operation follows which rule, what each calculation is based on, and who sees what. Anything we have not agreed on becomes visible here.
- Roadmap
We decide what goes into the first release and what waits. Order is a decision too: a working piece of the job ships first, and the extras arrive on top of it.
- Risk & feasibility
If something is uncertain we test it before building on it. At Vipkurum we checked at this stage whether optical forms could be read without reader hardware.
What you get
A written scope: how each piece of information is kept, the rule behind each calculation, and the build order, all on paper before any code.
Architecture
The parts of the system and the place of each piece of information are settled here.
What happens
- System design
We decide what parts the system is made of and how those parts connect. If the app also has to work without an internet connection, that is settled here as well; adding it afterwards is one of the most expensive changes there is.
- Technology decisions
We do not pick something new for each project; staying on a foundation we know is what makes long-term maintenance possible. If a job has to leave it, we write down why: the Çatalca Merkez Kasap QR menu was a single-page job, so it stayed on its own.
- Infrastructure
Where the software runs, where files are kept and how backups are taken get agreed up front. On the KGM SsangYong corporate site that is why we rebuilt the way vehicle images are stored.
- Data architecture
We draw where each piece of information is kept and how it stays separate from the rest. At Vipkurum, 7 institutions use one system and each institution's data stays apart; that separation sits in the data itself, not in the interface.
What you get
The technology decision and the reasoning for it, the call on working without a connection, and where hosting and file storage sit.
Modelling
The flow is drawn and the screens are clicked through before any code.
What happens
- Data modelling
We draw the kinds of information in the job and how they relate. In the dental clinic CRM, appointment, treatment plan and invoice are kept separately, because all three change at different times.
- Flow modelling
We map the steps an operation goes through from start to finish. At AlgoCar, opening a service takes the part used out of stock and passes the entry to accounting.
- Interface prototyping
We make the screens clickable before any code, so a missing step in the flow shows up before development starts. You are the one who signs it off.
- Content modelling
We set up how pages and text are managed from the admin panel. If more than one language is needed, each language gets its own address; this site works that way itself.
What you get
A flow mapped step by step and a clickable prototype, checked on screen before development starts.
Development
The software is built, tested and left in a state someone else could take over.
What happens
- Writing the code
We build against the model you approved. Because we stay on a foundation we know, the team does not relearn the file layout on every project and the time goes into the work itself.
- Iteration
You look at working pieces, tell us what needs to change, and we carry on from there. Our own products run the same loop: two are live and three are still being developed.
- Quality & testing
We test that the software behaves as expected, above all that a calculation comes out right and that nothing is lost. Get the mark threshold wrong in optical reading and the exam result comes out wrong.
- Launch & handover
We put the software live and settle who keeps it running. If your own team continues, we leave the code and the file layout readable for them. On the KGM SsangYong corporate site we were the party taking over, so we know what a handover has to leave behind.
What you get
Working software, behaviour tested against failure, and a code base the next team can read on day one.
After launch
Taking over a working system is a service of its own: if what you have has aged but still runs, you are not forced into a rewrite. The KGM SsangYong corporate site reached us already running. Who holds maintenance is settled before launch, and if your own team will keep it, we leave the structure ready for them.
What stays the same on every project
- Decisions before code
The rules of the job go into writing before any code. At Diotek, keeping a survey appointment separate from a service request was settled before the form was written.
- Progress in working pieces
You see progress in screens you can use. At Vipkurum the institution management went live first; optical reading, question cropping and content management followed as separate deliveries.
- Remote and in writing
Decisions go into documents, so nobody has to be in the same room. Some things do go faster in a short call, and we talk those through too.
- Documented and maintainable
Because we stay on the same foundation, a developer joining opens a file layout they already recognise. Nobody hunts for where something is defined, and what is left to learn is the work itself.
Have a project in mind?
The first conversation covers how the work runs today and where to start. Send the form and we reply within 2 business days.