About
CS-Code Bilişim — Software, Consulting and Training
We build software for fields where auditability is mandatory.
Fields such as laboratory, quality, IT and site management share one question: “where is the evidence?” The answer should be produced by the system, not remembered by a person.
Our products are built around that question. The one object they all share is an audit-trail line: the old value, the approval that closes it, and the new value. Who changed a record, when and why stays inside the system; it does not depend on a separate logbook, a spreadsheet or someone’s memory.
Alongside that, we do two more things: consulting on how processes are tied to the standard, and training to hand the installed system over to the people who will use it.
The fields we work in
Laboratories working under ISO/IEC 17025 — not built for a single laboratory
Quality managers and process owners; organisations within certification scope
IT managers, service desk, system and network administrators — and every employee as a requester
The principal employer: the OHS, Legal, HR and Health departments of factories, construction sites and facilities
How we make decisions
All six are the result of a choice, and each has a cost. We write the costs down too; a principle without a stated cost is not a principle but a slogan.
No record is ever deleted
Records are not deleted; they are deactivated. A wrong record is corrected, and the old value, the person who corrected it and the reason remain. A record that can be deleted does not count as evidence in an audit. Physical disposal happens only when the retention period ends, and it leaves a trace.
The cost: A wrong record stays in the system too; correcting takes one step more than deleting.
Organisation-specific rules are not hard-coded
Which department requests what, who holds which approval and how a formula is calculated are set up through configuration. A rule embedded in code means waiting for a release every time it changes — and it ties the organisation’s way of working to the software’s calendar.
The cost: The first installation takes longer than writing the rule straight into code.
One installation per organisation
A separate installation for every organisation — on your own servers or hosted by us: separate database, separate permissions and backup scheme. Data from different organisations never sits in the same database. This is a design decision.
The cost: Each installation is operated separately; we gave up the cost advantage of one shared system.
No figure without a measurement
Every figure on this site has a source, and the source is a required field: without it, the site does not build. The products follow the same approach: records and trails are produced by the system itself, never written in by hand afterwards.
The cost: The figures we can show are limited to what we can measure.
Boundaries are stated up front
What we don’t do is written clearly on the home page and on its own page, not in a footnote. Stating a boundary before the first meeting is cheaper than stating it in the first meeting — in the second case, we both lose time.
The cost: Some conversations end before they begin.
Delivery ends with handover
The team that installs the system, ties it to the standard and hands it over to its users is the same team. When the three are split between different parties, for every gap found in an audit the three point at each other.
The cost: The number of installations we can take on at the same time is limited.
What you won’t find on this page
Things found on most “about us” pages are missing here: the founding year, the team size, customer logos, a reference list, the “X years of experience” line. The reason is simple: we cannot state any of them in a verifiable way, and we don’t write what we cannot verify. A single reference that cannot be verified in the first meeting casts doubt on everything else that is written.
What we can measure, we write as it is: the most mature member of the family is in daily use with real samples in an accredited laboratory. For the other products, the only thing we can measure is that they are running live. “Running live” and “in customer use” are not described with the same words; each product page says which one applies.
Let’s talk about your scope
Tell us what you are working on and which questions you face in audits; our first reply will not be a price list but how the scope should be set up.
We reply the same day.