In the late 90s, Ukraine's technological landscape resembled a desert. In Ivano-Frankivsk, as elsewhere across the country, a computer in a government office was viewed more as an expensive typewriter than an analytical tool. Workflow was exclusively paper-based: endless shelves, registration logs, and hand-filled card catalogs where finding a critical document at the right moment was nearly impossible.
Amidst these dusty archives and paper bureaucracy, we saw an opening for an engineering maneuver. SmartDoc became our response to the "Millennium Bug" and a strategic project that laid the foundation for the region's first software product company — Softac.
Today, it is remembered as a digital legend, but on the eve of 2000, a genuine paralysis gripped the world. A technical quirk in databases of the time, where years were recorded using only two digits, had turned into a ticking time bomb. The fatal transition to "00" threatened to throw computer systems back a century — to 1900. Humanity braced for chaos: from wiped bank accounts to power grid failures and the total grounding of aviation.
We were among those who saw this crisis not just as a threat, but as a "window of opportunity." One could simply patch holes in obsolete code, but we proposed SmartDoc. Developed from scratch in just three months, Serhiy Bantush and I designed this software specifically for the challenges of the new millennium. At its core lay a client-server architecture, the latest development tools, SQL databases, and other solutions that were bold and atypical for the local market. Yet, these were the very elements that could ensure rock-solid stability when the world expected a massive meltdown.
In the early 2000s, local software was usually written as a bespoke order for a specific organization and task. I had worked that way myself before. But this time, we took a different path: we decided to create a "boxed" product. SmartDoc featured universal logic, professional documentation, a license agreement, and a clear implementation methodology. We didn't want to sell programming hours; we wanted to sell a ready-made, reliable tool.
Choosing the Regional Council as our launching pad was a deliberate, strategic move. It was the "epicenter" of high-volume documentation, where all information flows converged: from thousands of citizen appeals to parliamentary inquiries and government correspondence. We knew: if our architecture could withstand this level of pressure and bureaucratic complexity, it would become a universal standard for any other structure.
The Transformation Process: It was a genuine information shock. People who had spent decades filling out paper registration cards suddenly had to start thinking in terms of "databases." We were no longer just programmers; we became business analysts and trainers. We had to explain why a document's "digital passport" wasn't extra work, but rather freedom from routine.
The Result: We built a transparent vertical. It became impossible to "lose" a letter under a stack of papers — the system relentlessly reminded users about it every morning. Responses to inquiries began to be issued on time, not just when someone happened to remember them. This was a real victory for digitalization in the region.
The success at the Regional Council became the catalyst for the official founding of the Private Enterprise "Softac." Until then, programmers in the region were isolated IT specialists tucked away inside factories, government agencies, or institutes. We became the first entity to declare: an intellectual product is a legitimate business. Of course, even before Softac, there were groups writing code and selling software, but they were typically formed for a specific client or project, or as an add-on to a computer hardware business.
Our Innovations:
Legal Framework: From day one, we operated within the legal field. In an era of rampant piracy, we sold licenses for intellectual property. Conversely, we purchased licenses for the development tools and components we needed. This laid the groundwork for a civilized IT market.
Service Model: We didn't just sell a CD; we offered maintenance, database updates, and technical support.
Following the success with the council, a "trust effect" kicked in. Organizations began buying SmartDoc: from educational institutions and commercial firms to large enterprises like gas utilities.
The product was gradually refined and became remarkably universal. It turned out that the chaos in documents is the same everywhere, and our solution successfully tamed it. We proved that "boxed software" was a viable idea that allowed a system to be deployed in any institution within days.
SmartDoc was the "maiden flight" for our team. It didn't save the world, but it taught us fundamental lessons that later proved invaluable at SoftServe and in the growth of bvblogic:
Engineering Logic Above All: Every system is a flow of data. If you can understand and organize them, you can manage a system of any scale.
Technology as a Service: A user doesn't need complex code or a trendy tech name; they need a solution for their pain.
Geography Doesn't Matter: In 2000, we proved to ourselves in practice that you don't need a Silicon Valley office to build complex architectural systems. Product quality isn't defined by geography, but by the ability to solve a specific problem through engineering. This experience gave us the self-confidence that later allowed us to enter global markets and create large-scale projects.
Today, as I work with AI agents and Large Language Models, SmartDoc looks like an artifact from a distant era. But without this "dinosaur," without the victory over the Y2K fear, and without Softac's first license agreement, my technological journey would have been entirely different.
SmartDoc will always remain the project that taught me to build architecture that stands the test of time, rather than just writing code. It was our bridge from a paper past to the digital future — a bridge we are still crossing today.
Afterword In those days, a developer was a "one-man band." While creating SmartDoc, I didn't just write the program; I also mastered the roles of technical writer, designer, and layout artist. I spent hours drawing inspiration from the paper manuals for Windows 95, trying to replicate that same logic and aesthetic in our user guides. You can see how it turned out at this link.
By nature man hates change; seldom will he quit his old home till it has actually fallen around his ears.
Bohdan Futerko: programmer, engineer, entrepreneur, and manager. My worldview is shaped by technical expertise, systems thinking, and a passion for innovation. This is where I share my ideas, projects, and insights on technology, systems, and creativity.