An admin panel written around the flow of your business.

Before having custom software and an admin panel built

Custom software is a program developed from scratch or on top of ready-made components to manage a company's own specific business processes. A web-based admin panel is the interface of that software, which can be used from a browser, without installation, from anywhere, by the people who are given access.

Its difference from a corporate website is that it serves the inside rather than the outside. A presentation site tells your customer who you are; custom software organizes how your team runs things like quotes, orders, appointments, stock or service every day. If you only want to add an appointment form or a calculation tool to your existing site, what you need is most likely not a full software system but a module.

Off-the-shelf program or custom software?

For accounting, payroll or common CRM needs there are mature ready-made programs, and they are often the right choice. Custom software becomes meaningful in cases like these:

• The flow of your work does not fit the general pattern of the sector and an off-the-shelf program forces you into its own way.
• You use several programs side by side and enter the same data again and again in different places.
• Your team, dealers or customers need to reach the same data with different permissions.
• You want to keep the data you collect on your own server and report on it in any way you like.

In the first meeting, if your need can be met with a ready-made program, we say so openly. Sometimes the best solution is to complete a ready-made program with a small integration.

Why is process analysis so important?

Software is the way work is done, put into code. A program written before the process is clear does no more than carry the existing confusion into a digital environment. That is why in the first stage we talk to the people who do the work and map which steps a request goes through, who approves it, where which information is kept and where mistakes usually occur. The resulting process diagram becomes both the plan for the software and a reference document so your team can talk about the work in a common language.

In the analysis it is necessary to talk not only with managers but also with the people who will use the system every day. The small problems met by the person in charge at the warehouse, the technician in the field or the employee in the accounts office often decide whether the software will really be useful. Trying the drafts of the user screens together with these people considerably reduces the corrections needed after development.

Phased development: starting small

Trying to write all the needs at once both lengthens the time and makes it harder for the team to adopt the system. We find the step that wastes the most time or produces the most errors and build the first version around it. Feedback that comes once your team starts using this version on real work decides the priority of the next phases. This approach prevents the development of features that look good on paper but go unused in the field.

Each phase is first developed in a test environment. You and your team try the new screens without touching real data, and after you approve, the change is moved to the live system. That way the daily workflow is not interrupted during development. Where integration is needed, for example data exchange with your accounting program, SMS provider or email service, we use the official connection methods offered by the relevant system.

Permissions, security and KVKK

Admin panels contain personal data such as customer, staff or supplier information. That is why we treat security as part of the design rather than a feature added afterwards:

• Role-based permissions: Each user sees only the screens and data needed for their work.
• Activity logs: Who added or changed which record, and when, can be traced.
• Encrypted connection and strong login: Connections are encrypted and two-step verification can be added if wanted.
• Regular backups: Database backups are taken automatically and restoring is tested.
• Data minimization: Personal data the work does not require is not collected; the privacy notice and retention periods are determined together with your legal adviser.

Ownership, source code and hosting

The server on which the software runs and the domain are opened in your company's name. The handover of the source code, the licenses of the components used and the documentation are set in writing in the contract. That way, when you later build your own software team or want to work with another team, you are not dependent on the system. We also discuss from the start how maintenance, updates and new feature requests will be handled after go-live. The programming language, framework and database are chosen from common, well-documented technologies; unusual structures that only one person could maintain are not preferred.

On-site and online work

In process analysis, seeing the place where the work is done makes a big difference. With companies in Adapazarı, Serdivan, Hendek, Arifiye and around Sakarya, we can examine the flow in the warehouse, office or field on site and give user training face to face. With companies in other regions of Turkey, analysis meetings are held by video and test versions are tried at a shared address. On both paths, progress is recorded through regular meetings and written notes. In the first weeks after go-live, answering users' questions quickly is critical for the system to be adopted; during this period we collect and prioritize the notes coming in through our 24/7 online support channel and put small fixes live quickly.