How My Experience with Alkar-Teleport Shapes Integration Architecture at formspace.design

My business journey began in the challenging 90s when I served as deputy director, then director, at the Alkar group of companies. Among the many projects we launched back then – from concrete production to an advertising agency – was Alkar-Teleport, a telecommunications division. It was there that I first encountered the large-scale task of integrating completely different systems. This experience, gained a quarter-century ago, still forms the foundation for how I approach integration design at formspace.design.

Alkar-Teleport: A School of Systems Thinking

In the early 90s, establishing a telecommunications division to provide communication services was an innovative and highly complex undertaking. There were no ready-made, "out-of-the-box" solutions, and we had to build the entire infrastructure from scratch. This included not only physical equipment but also software for traffic accounting, tariffication, billing, and, of course, customer interaction. My role as a manager involved setting technical specifications for programmers to create management accounting systems. This required a deep understanding of how data would move between different modules: from the moment a subscriber made a call to its reflection in financial statements. This was my first serious lesson in systems thinking: how to break down a complex task into manageable parts and how these parts should interact harmoniously.

Lessons in Integration: From Telephony to Data

Working with Alkar-Teleport showed me that successful integration is not just about connecting two software products. It's about creating a unified, logically connected flow of information. We dealt with various communication protocols, databases developed by different specialists, and the need for instant information exchange. For example, a change in a client's tariff plan had to be immediately reflected in the tariffication system and their personal account. A common mistake was underestimating the complexity of converting data from one format to another, which led to failures and inaccuracies. We spent weeks debugging each new integration, and this taught me to meticulously consider every aspect: from data structure to error handling. This principle – not just to connect, but to ensure a seamless and reliable flow – I carry through all my activities, right up to the development of formspace.design.

The Importance of a Unified Information Space

One of the main problems we faced in those years was fragmented information storage. Departments worked in their own programs, and data was often duplicated or, even worse, contradicted itself. For example, a sales manager might update a client's contact details in their spreadsheet, but these changes didn't always reach the technical support or accounting departments. This led to customer loss and financial errors. I realized that a unified information space, where all data is stored centrally and accessible to everyone who needs it, is critically important. My experience as a business consultant in the 90s, described in the article "How My Experience as a 90s Business Consultant Shapes the Logic of formspace.design Modules", also emphasizes this point. This is why at formspace.design, I strive to create a platform where all aspects of a landscape project – from zoning to plant selection and client communication – will be unified.

Designing 'with Reserve': Why Scalability is Critical

When we first started, it was difficult to foresee how quickly our subscriber base would grow and what new services we would have to implement. But it soon became clear that systems not designed with future scalability in mind become a "bottleneck." Reworking the architecture when you already have thousands of active users is expensive and risky. I learned to always build in potential for growth: to provide for modularity, flexibility in changing parameters, and the ability to add new functions without completely rebuilding the entire system. For example, even then we understood that network bandwidth and request processing speed should be many times higher than current needs to avoid problems during peak loads. This meant investing in more powerful equipment and more complex algorithms, even if it seemed excessive at the time. This lesson is extremely important for formspace.design, where I initially lay out an architecture capable of handling both simple sketches and complex multi-component landscape projects, as well as integrating with future modules such as CRM or a project management system.

The Human Factor in Automation: Beyond Technology

System integration is not just about code and databases. It's also about the people who will work with these systems. At Alkar-Teleport, we realized that even the most perfect system is useless if users don't understand how to use it, or if it's too complex and inconvenient. We paid great attention to staff training, creating clear instructions, and gathering feedback. Often, we had to adapt interfaces and workflows to the needs of operators, rather than the other way around. The process of implementing a new system could take several months, including the user adaptation period. This experience convinced me that user experience is not just a buzzword, but a key factor in the success of any automation. At formspace.design, I strive to make the interface as intuitive and user-friendly as possible, so that landscape designers can focus on creativity, not on struggling with the software.

How I Plan Integrations at formspace.design

My many years of experience, starting with Alkar-Teleport and continuing at the "Dom i Sad" company, where the lack of a full-fledged CRM cost me clients (I talked about this in "How the Lack of CRM Cost Me Clients at 'Dom i Sad'"), is the foundation for designing the architecture of formspace.design. I am not just creating a tool for landscape planning; I am building an integrated ecosystem.

When planning each module, whether it's working with a site plan (modules 1.0–1.7, where we define zones and place objects) or using AI for conceptual sketches (module 2.1 "AI Concept"), I immediately think about how this data will interact with other systems. For example, information about the plot size, selected plants, and materials should be easily transferable to a future estimate module or to a CRM for managing the client base. This means that data must be structured and standardized from the outset. I envision a designer uploading a photo of a site for analysis (module 3.1 "Design by Photo"), and the AI not only suggests options but also generates a set of structured data (e.g., a list of plants, area sizes) that can then be used for a commercial proposal or further design. My goal is for formspace.design to become not just a set of tools, but a smart platform where each step automatically prepares data for the next, minimizing manual input and errors.

FAQ

How relevant is the experience of the 90s in modern IT?

The experience of the 90s, despite the seemingly ancient technologies, is incredibly relevant. It teaches basic principles of systems thinking, the importance of reliability, scalability, and understanding business processes. Back then, everything had to be created from scratch, which forced a deep understanding of the essence, rather than just using ready-made solutions without understanding their internal workings. This is the foundation upon which all modern, more complex systems are built.

What are the main mistakes in system integration?

The most common mistakes are the lack of clear technical specifications and understanding of data flows, underestimating the complexity of format conversion, ignoring error handling mechanisms, and lack of testing. It's also critical not to account for the human factor: if a system is inconvenient for users, it will not work effectively, even if it is technically flawless.

How does formspace.design ensure data security during integrations?

During the design phase of formspace.design, I embed security principles from the very beginning: minimizing data access, encrypting critical information, and strict control over user rights. If external integrations are implemented, they will be done through secure APIs with thorough authentication and authorization, ensuring that data is transmitted only via a secure channel and only to authorized systems.

Can one do without deep integrations at the start of a project?

At the start of a small project, it is possible to do without complex integrations, using manual data transfer or simple synchronizations. However, as the project grows and the volume of data increases, the lack of deep integrations quickly becomes a "bottleneck," slowing down work and increasing the risk of errors. It is better to immediately lay down an architecture capable of future integrations, even if they are implemented in stages.

How to choose the right tools for integration?

The choice of tools depends on the project scale, the types of systems to be integrated, and the required data exchange speed. For small tasks, ready-made connectors or automation platforms are suitable, while complex enterprise solutions may require custom APIs and specialized integration buses. The main thing is to start from business needs and available resources.

What role does AI play in formspace.design's integration projects?

AI in formspace.design plays a key role in automation and intelligent data processing. For example, AI can analyze site images and automatically extract structured data about terrain, existing objects, or vegetation types. This data can then be automatically transferred to other modules (e.g., for cost estimation or irrigation planning), significantly simplifying and accelerating the design process and further integration with other systems.

How to avoid a "zoo" of systems?

You can avoid a "zoo" of systems by adhering to a unified IT infrastructure development strategy and prioritizing integrated platforms or systems with open APIs. It is important to regularly audit the tools used, eliminate outdated or duplicating functions, and train employees to use the same centralized tools for information exchange.

Step by Step Towards an Integrated Platform

The journey from Alkar-Teleport to formspace.design is a path of continuous learning and application of systems design principles. I am convinced that only a deeply integrated platform can truly simplify the work of a landscape designer and help a property owner realize their dreams. Every day I work to make formspace.design precisely such a tool, taking into account all the lessons that practice has taught me.

Related Materials

• Read more