About us
Lunmark is a development studio in Serbia. For years we have been finding the bottlenecks inside companies, measuring them and taking them out. We build sites, online stores, applications and business systems, and we develop on Bitrix24. Part of the work comes to us directly, part through Bitrix24 partners who hand us the development.
Bottlenecks
Every company has places where the work jams: orders somebody retypes from one screen into another, a report rebuilt by hand every month, an approval that sits for days because it is waiting on one person. We find those places quickly, because we know where they hide.
Then we measure what they cost you in hours and in money, and what you gain once the bottleneck is gone. Only then do we build software, and exactly the software that solves it. The scope, the deadline and the price reach you before a line is written.
What it has to return
The software has to speed up something that takes too long today, give back the hours that go into retyping, or bring in work that was not coming in before. By the end of the year those are the same number, and that is the number we start from.
That is why we are still asking how a system is doing long after the handover. Software nobody uses did not solve the problem.
Delivery
When the project ends the system is yours in full: the code, the data, the accounts, and the knowledge of how all of it works. That claim is one you can test. A developer who never worked on the project brings the whole system up from the documentation alone, without a single call to us.
The source code, with its full history, sits in your account rather than ours. Domains, credentials and third-party services are in your company’s name from the first day, so nothing has to be moved across at the end and nothing stays behind with us. The code comes with documentation written for somebody who never worked on the project, and with a deployment your own team can run.
At the start we measure what the bottleneck costs you in hours and in money. At delivery you get that same arithmetic again: what it was, what it is now, and where the difference sits. That is how you see whether the project returned what it cost, by a number rather than by an impression.
We train the people who will use the system on their own real work rather than on demo data, the way they will be working on Monday morning. For whoever runs it day to day there is a separate walk through the administration and through the places where something usually needs changing.
If you already have developers in house, or you work with another agency, they do not wait for the end of the project. They come into the repository, into code review and into the architecture decisions while the work is happening, and we walk them through the code until they have it. The same holds when somebody else carries the project on: their team is brought into the system while we are still in it, so the work continues without a gap.
Backups and a restore are run in front of you before the system goes live. After that we stay reachable when something stops outside office hours, and development carries on at whatever pace suits you: changes, new integrations, and the next phase when it is time.
LunmarkAntibiro put Bitrix24 into companies across the former Yugoslavia and the rest of Southeast Europe: CRM, project management, contact centre, sites, and the everyday administration that ends up running on top of all of it.
A Bitrix24 project that arrives this way is still one project. The platform decisions and the code decisions get made against each other rather than one after the other, so what the client ends up holding is a system, not a rollout with development bolted onto the side of it. It hands over on the same terms as everything else built here.
Get in touch. One conversation and you will know what can be made faster, and what it costs.