KURTOGLU
SINAN

Context: From Public-Sector Systems to the Commercial Market

I founded the company directly after six years of work on municipal information systems (1998–2004). In that environment, the projects I worked on were institutionally funded, formally scoped, and run as long-term programs with dedicated infrastructure and server budgets.

When I entered the private market, I found that it operated under very different constraints. Budgets were short-term, IT was treated as a cost rather than an investment, and technical decisions were frequently made by non-technical stakeholders. Adapting my public-sector engineering experience to these conditions became the defining challenge of this period.

Market Conditions in Eskişehir and Ankara

Through my field experience in the regional SME market, I observed a consistent set of constraints that directly shaped my product and architecture decisions:

• Limited IT investment. Most companies I worked with did not allocate a meaningful budget to an internal IT function. IT responsibilities were typically held by a single person, combined with other duties, or outsourced on an as-needed basis.
• Accountant-driven software selection. I saw that the choice of business software was usually determined by the company's accountant or external accounting office. Whatever accounting package the accountant worked with became the company's de facto system of record, and every other application had to align with it.
• Prohibitive enterprise database costs. Enterprise relational database platforms such as Oracle Database, Microsoft SQL Server, and IBM Db2 carried licensing, hardware, and administration costs that the majority of regional firms could not justify. I learned that total cost of ownership, not technical merit, decided the platform.
• Lack of qualified in-house staff. Some companies I met were willing to invest seriously in their systems, but could not recruit or retain personnel capable of operating and sustaining those systems internally.
• Talent drain to the public sector. Due to the instability and perceived insecurity of the private market, qualified technical staff generally preferred public-sector employment. This left private companies structurally dependent on external suppliers.

From these observations I drew a clear engineering conclusion: any solution I offered had to be low-cost, compatible with the client's existing commercial package, and maintainable with minimal in-house technical expertise.

Strategic Positioning Around Established Commercial Packages

Instead of competing as a vendor of heavy enterprise platforms, I positioned the company around the commercial business software already dominant in the Turkish SME market:

• Logo
• ETA
• Netsis
• Nebim
• Datasoft

My objective was to gain market share by adding value around these packages rather than replacing them: extending their functionality, integrating them with other systems, producing reports and analyses they did not provide, and migrating data between them.

In this area, I:

• examined the data structures and record logic of each package,
• mapped master data (customer and supplier accounts, stock items, price lists) and transactional data (invoices, dispatch notes, stock movements, account postings) between different packages,
• developed add-on modules and reporting tools that operated alongside the client's existing package,
• built import/export and data exchange processes between commercial packages and custom applications,
• supported transitions from one commercial package to another while preserving historical records,
• identified and corrected inconsistencies introduced by years of manual data entry and partial migrations.

This approach allowed me to deliver engineering value to clients who would never purchase a full custom enterprise system, while keeping their accountant-driven system of record intact.

Database Strategy and Cost-Conscious Architecture

I treated database selection as an economic decision as much as a technical one.

• Enterprise RDBMS platforms (Oracle, Microsoft SQL Server, IBM Db2) were well known to me from my earlier work, but their licensing and operating costs placed them outside the reach of most of my target clients.
• I adopted MySQL as my primary low-cost database option for custom applications. Its open-source licensing, modest hardware requirements, and adequate performance for SME data volumes made it a direct answer to my clients' search for affordable solutions.
• I kept application data access separate from business logic as far as possible, so that I could adapt the same application modules to different database back ends depending on the client's budget and existing environment.
• Toward the end of the period, I evaluated MongoDB as an emerging document-oriented database. I found its schema-flexible model attractive for heterogeneous business records that did not fit rigid relational schemas. I did not adopt it in production, as my priorities had changed by that time.

Product and Software Development

• I defined a product-oriented development strategy focused on reusable solutions rather than repeatedly building one-off customer applications.
• I designed and developed desktop and enterprise software primarily in Delphi, building on my earlier Pascal experience.
• I developed reusable software components to accelerate the creation of customer-specific applications.
• I designed application modules around business rules, data processing, reporting, and operational workflows.
• I worked on migration and modernization of data originating from legacy accounting and business applications.
• I developed solutions for data analysis, data management, and structured transformation of existing business records.
• I built and adapted e-commerce and business-oriented applications according to customer requirements.
• I resolved compatibility, data integrity, and operational issues in existing commercial software environments.
• I applied my prior experience in Pascal, database systems, municipal information systems, and enterprise integration to commercial software architecture.

Teknopark Incubation Period

I later moved Artı Bilişim to Anadolu University Teknopark, an environment focused on software development and product incubation.

During the incubation period I worked on two parallel tracks:

• Business development: I positioned the company for higher-level corporate clients with larger budgets and more complex requirements. Sales cycles for such clients were long, and I spent much of this period waiting for these engagements to materialize.
• Product development: I used that time productively to develop a new commercial business application in-house, which I designed from the outset as a product rather than a customer-specific implementation.

I centered my technical direction on the progression:

Reusable Components → Application Frameworks → Business Solutions → Productization

rather than conventional computer sales or technical-service operations.

Enterprise and Custom Software Projects

I worked with organizations that required purpose-built software rather than standard off-the-shelf applications, or whose needs exceeded what their commercial package could provide.

In these projects, I carried out:

• requirements analysis,
• process modeling,
• database and data-flow design,
• development of customer-specific application modules,
• legacy data examination,
• data conversion and migration,
• business-rule implementation,
• reporting,
• system integration,
• deployment and technical support.

A significant part of my work involved understanding existing operational processes, often undocumented and dependent on individual staff knowledge, and converting them into maintainable software structures.

Ankara-Based Development Projects

I worked intensively on software development projects in Ankara through a technology partner operating within the ODTÜ-related technology ecosystem.

In these projects, I developed purpose-specific software components and applications for companies participating in technology and incentive-supported programs.

My development work frequently required long periods of concentrated on-site engineering, during which I carried out:

• analysis of customer requirements,
• component design,
• application development,
• data modeling,
• adaptation to existing business systems,
• testing and deployment.

This period significantly strengthened my transition from application programming toward software architecture and modular system design.

Data and Legacy System Work

A recurring requirement across my projects was handling data produced by earlier-generation business software and by commercial packages that had been in use for many years.

In this work, I carried out:

• analysis of legacy data structures, frequently without vendor documentation,
• identification of inconsistent, duplicated, or incomplete records,
• definition of transformation and cleansing rules,
• database restructuring,
• import/export processes between legacy, commercial, and custom systems,
• reconciliation checks to verify that migrated data matched the source,
• compatibility between old and new applications during parallel operation,
• preservation of historical business data during software transitions.

Through this work, I extended the data migration and systems integration expertise I had developed during municipal information-system projects into the private sector, where data quality was typically lower and documentation scarcer.

Entrepreneurial and Technical Role

As founder, my responsibilities extended beyond software development and included:

• technical architecture,
• product concept development,
• software implementation,
• customer requirements analysis,
• market and pricing positioning against established commercial packages,
• project planning,
• system integration,
• data migration,
• deployment,
• technical documentation,
• troubleshooting,
• customer support,
• commercial and operational management of the company.

My role therefore combined software architecture, engineering, systems analysis, product development, and entrepreneurship.

Technical Environment

• Development: Delphi, Pascal
• Databases: MySQL (my primary low-cost platform); working knowledge of Oracle Database, Microsoft SQL Server, and IBM Db2; early evaluation of MongoDB
• Commercial packages (integration, reporting, migration): Logo, ETA, Netsis, Nebim, Datasoft
• Application areas: business applications, reporting, data migration, e-commerce, system integration

Period Outcome

Artı Bilişim marked my transition from primarily implementing and integrating systems designed by others to building reusable software products and proprietary technical solutions.

During this period, I consolidated the experience I had accumulated across:

hardware → enterprise systems → databases → municipal information systems → software development → data migration → system integration

into a product-oriented software engineering approach.

Due to changes in market dynamics and a shift in my career focus toward larger-scale infrastructure and automation projects, I decided to conclude the company's operations after successfully completing its ongoing engagements.

Key Takeaways from This Period

• Cost-aware architecture. I learned to treat licensing, hosting, and operating cost as primary design inputs alongside technical requirements, and to select platforms that my clients could realistically afford and sustain.
• Designing for the real operator. I developed the habit of designing systems around the skills of the people who would actually run them, keeping deployment, maintenance, and recovery simple enough for organizations without a dedicated IT department.
• Legacy data expertise. I gained extensive hands-on experience in analyzing undocumented data structures, cleansing inconsistent records, and reconciling migrated data, which became one of my core professional strengths rather than a side activity.
• Integration with established commercial systems. I built practical knowledge of how widely used Turkish commercial packages structure and process business data, and how to extend and integrate them without disrupting the client's system of record.
• Product thinking. I moved from delivering individual applications to thinking in terms of reusable components, frameworks, and productization.
• Entrepreneurial and commercial experience. I gained direct experience in running a technology company, including customer acquisition, pricing, partner relationships, and the risks of dependency on external project partners and payment terms.

These experiences became an important foundation for my subsequent work in telecommunications, infrastructure, automation, IoT, and later AI-assisted system development, and shaped my lasting preference for low-cost, self-hostable, and locally maintainable systems.