Your accounting software stays where it is. We take the work that runs on Excel, WhatsApp and the foreman's notebook in facilities across Başpınar and Şehitkamil, and bring it into a system. Not an off-the-shelf package but a program written for your own flow; the source code and the data stay with you. The first step is visiting your factory and walking the shop floor together.
Not every business needs custom software; be wary of any supplier who does not tell you this. Where an off-the-shelf package is enough, buy the package and keep your money. Custom software makes sense where the work is specific to your company and that specificity is what earns you money. Below we set out both where we stand and what we concretely do.
If most of the need uncovered in discovery is covered by an unused module of your existing ERP or by a package on the market, we say so openly. Writing software is our business, but paying for unnecessary software is your loss. We only recommend custom development where you have reached the limits of the package.
This is the model we build most often. Your Logo, Mikro or Netsis accounting backbone stays in place; your e-invoicing and account structures are never disturbed. We write production, subcontracting, waste, quality and dispatch as a separate layer and connect it through the ERP's database or services. We have applied this model before, as a production layer running alongside an installed Netsis system without touching it at all.
The screen the operator uses and the screen the owner looks at should be two faces of the same program. For the floor we write big-button screens that finish a job in two steps with a barcode scan and lose no data during outages; for the office, a dashboard showing work orders, waste and deadline deviation at a glance. We have previously built an 11-module factory management panel; the approach is the same — plain screens that drive decisions.
If you have a program that runs but nobody can get inside, we analyse it on an evidence basis. We have previously extracted the daily calculation formula of an enterprise application from the running system; we analysed a cutting-and-order system in 29 sections, documented the call contracts of 61 database objects (which parameters each one takes and which results it produces) with evidence, and rebuilt some of their bodies. In that work the monthly calculation layer remained missing and was marked as missing in the report; we write down what we do not know as much as what we do.
In most companies what is missing is not a new program but the bridge between the existing ones. We connect accounting, production, weighing, labelling, e-commerce and dealer systems via API (the connection through which programs pass data to each other) or at database level. The goal is for a piece of information to be entered in one place and flow correctly to the others; double entry and the 'which report is right' argument lose their footing.
The source code of everything we develop and all of the data belong to you. We put the installation steps, dependencies and known risks into a written handover file, so that another team could carry on. We want the reason you work with us to be that we know the shop floor — not that you have no choice.
We talk about what you do, how many people you employ, which software you use and where it hurts most. We do not quote a price in this call, because a number given without seeing the shop floor burns either you or us. The aim is to honestly understand whether the job is right for us.
We come to your facility and chase a single question: how many times is the same piece of information entered by hand in this company? We count, one by one, the duplicate records travelling between the foreman's notebook, the production manager's Excel and the accounting screen. For Başpınar and Şehitkamil this step is on site and face to face.
We turn the discovery findings into a written document: which screen does what, where each piece of data comes from, and what is out of scope. Budget and timescale are discussed on the basis of this document. If the scope is not in writing, the project ends in a dispute anyway; we do not allow that from day one.
We do not build everything at once. We start with the single heaviest problem found in discovery and show a working version at short intervals. The foremen and operators on the floor try the screen on real work; we adjust it to the way they actually use it.
Instead of a single cut-over, we run a parallel period: the old method and the new system run side by side for a while. We train operators, foremen and managers according to their roles. Afterwards we continue with maintenance and development support.
Yes — this is the foundation of how we work. We travel to the Başpınar OSB zones and to facilities in Şehitkamil and walk the production floor. Production software cannot be understood through remote meetings; a program written without seeing which hand the operator uses and how fast they touch the screen will not be used on the floor.
If a package is enough, do not commission anything — we will tell you so ourselves. Custom software makes sense in three situations: the part of your business that is specific to you does not fit the package's mould; data is constantly carried by hand between multiple systems; or the package's licence and user costs have outgrown the size of the job. If none of these apply, custom development is an expense.
No. The model we build most often is an operations layer written alongside your accounting backbone without touching it; we have done exactly this next to an installed Netsis system. Your e-invoicing, e-ledger and account structures stay as they are. The layer we write talks to the ERP through the database or its services, so you do not end up running a second accounting system.
We do not quote without seeing the shop floor; made-up prices and timelines go against our principles. Price is set by scope: how many screens, how many integrations, how many users, how many terminals on the floor. After discovery we present a staged budget together with a written specification, so you can see what you are paying for. For a general framework, see our custom software pricing guide.
In most cases yes, but we give no guarantee. If you hold the compiled application and the database, most of what the program does can be recovered. We have done this end to end before: we worked out the daily calculation logic of an enterprise application and produced a 29-section analysis of a cutting-and-order system. In those same projects some sections remained missing and were marked as such; some knowledge lives only in source code and does not come back. Our first deliverable is not a commitment but an honest map of what can be recovered.
You do. The source code, database and installation documentation are handed over to you; the data sits on your own server or in a cloud account opened in your name. The aim is not to tie you to us, but to leave you in a position to continue with another team in the future.
Yes. According to our own field research, most companies in the Gaziantep OSB are micro or small; at that scale the right approach is not to build a big system but to write a plain program that properly fixes one bleeding point. We prefer to start small and grow as the need grows.
The work on this page is the software side: production, ERP integration, shop-floor systems and takeovers. The marketing side of Pan Innovation House (search visibility, advertising, e-commerce) is a separate practice, described on a separate page. We do not mix the two; we approach software work with a software mindset.
Let us come to your facility in Başpınar or Şehitkamil, walk the flow with you and pinpoint together where the data breaks. You end up with a written scope framework in hand; only then do you decide whether you want to continue. A phone call is the cheapest step in this whole process.
