How to Combine Interface Simplicity and Accounting Depth – My Search for a Compromise

As the founder of formspace.design, I daily face a fundamental dilemma: how to create a tool that is both simple and intuitive for every user, yet provides the necessary depth and accuracy for professional accounting and planning. This is not just a technical challenge, but a philosophical question about trust in the system and work efficiency, which I address at every stage of development.

The Problem of Choice: Why Simple Doesn't Mean Superficial

Often, two extremes are encountered: programs are either so simple that they don't allow for full accounting and analytics, or they are so overloaded with features that they become overwhelming to learn and use daily. My experience shows that such 'simplicity' often turns into superficiality, and 'depth' into unjustified complexity. For example, in my business 'Dom i Sad' (Home and Garden), which specialized in landscape design and cottage construction, we encountered systems that promised universality but in reality required enormous time investments for staff training or failed to provide necessary reports without complex manual adjustments. A typical mistake was trying to encompass everything: instead of focusing on key processes, we tried to implement a system that would literally account for everything, from nail purchases to client psychology, and ended up with a monster nobody wanted to use. This led to important data about projects, deadlines, and most importantly, real profitability simply getting lost.

My Experience with CRM and Management Accounting in the 90s and 2000s

My business journey began in the 90s when I worked as Deputy Director of NPF Alkar, and then as Director of Alkar-Invest. Even then, I faced the need to automate management accounting. I assigned tasks to programmers, trying to explain what reports I needed for decision-making, and how document flow should look to control finances and supplies. This was a real 'generation gap': my experience as a director in the 90s demanded reliable tools that simply didn't exist or were extremely primitive. This experience gave me a deep understanding that a good system must first and foremost be useful for decision-making, not just a data repository. I elaborated on this in the article “My Personal Generation Gap: A 90s Director Meets 2026 Tools”.

When I founded 'Dom i Sad' in 2000, the problem hadn't disappeared. We designed and built dozens of projects, landscaping plots ranging from 6 to 20 sotkas. Accounting for materials, working hours, seasonal plant cycles, and object maintenance – all of this required a system that would save time, not consume it. It was then that I realized I needed a tool that would allow me not only to see the big picture but also to delve into details when necessary, without extra effort.

Criteria for Balance: What I Consider in formspace.design

When developing formspace.design, I am guided by several key principles to achieve that very balance:

1. Principle of 'Layered' Complexity: Basic functions should be obvious and accessible at first glance. The user should be able to get a quick result without delving into intricacies. But when necessary, they should be able to 'unfold' additional options and detailed settings. For example, for a landscape project, one can quickly draw a general zoning scheme, and then for each element (plant, paving), obtain detailed information for an estimate or care.
2. Visualization as a Foundation: People perceive information differently. For landscape design, the visual component is critically important. The simple interface of formspace.design allows for quickly creating visual concepts, while the depth of accounting enables linking these visualizations with real figures: paving area, number of plants, volume of earthworks.
3. Modularity and Extensibility: I build formspace.design as a system of interconnected but relatively independent modules. This allows the user to activate only the functions they need, avoiding overload. If today you are simply planning the arrangement of objects on a plot, you don't need detailed financial accounting functions. But when it's time to prepare an estimate, that module will be available.
4. Focus on the Subject Area: Instead of trying to create a universal combine harvester, I focus on the specifics of landscape design and plot management. This allows me to develop functions that are truly needed in this niche, rather than copying general solutions from other industries. For example, accounting for plant seasonality or automating watering and pruning reminders – these are specific but very important details that make the system deep and useful.

Common Mistakes When Implementing Complex Systems

Over the years, I have seen many examples of good ideas failing due to an incorrect approach to automation. Here are some common mistakes I try to avoid in formspace.design:

• Overload at Startup: Attempting to implement all possible functions at once. The user gets lost, becomes demotivated, and abandons the system. I, however, follow the path of gradual functional growth, starting with the most essential features.
• Lack of Flexibility: Rigid structures that do not allow adapting the system to the unique processes of a specific business. In formspace.design, I strive to ensure that key parameters can be easily customized.
• Ignoring the Human Factor: Developers often forget that end-users are not programmers. The interface must be as intuitive as possible, even if complex algorithms are hidden under the hood. I remember how we had to redo estimates in 'Dom i Sad' multiple times because the initial data was entered incorrectly due to a complex interface.
• Lack of Feedback: Development in a vacuum leads to a product nobody needs. I actively collect feedback from potential users and constantly analyze it. Sometimes, even a mundane detail like a driveway width of 1.2 meters or a curb height of 15 cm can turn out to be a critical detail that cannot be overlooked.

From Director to Developer: An Inside Look

At 61, I started coding with the help of AI to create formspace.design. This transition from director of a large landscape company to an independent developer is not just a career change, but a logical continuation of my search for the ideal tool. I am not a programmer by education, but my many years of management experience and understanding of business needs allow me to approach development with a unique perspective. I know what needs to be considered, why it's important, and how it should be presented to be maximally useful. I don't need to explain the essence of the landscape business or management accounting to programmers – I am the one who sets these tasks and solves them. This allows me to build formspace.design exactly as plot owners and landscape designers would want to see it – efficient and understandable. My personal stack of development tools, as well as my approach to using AI in this process, allow me to create a fairly complex product alone. I wrote about this in the article “My Solo Development Tool Stack: An Honest List”.

Tool Evaluation Checklist: Finding the Golden Mean

When I evaluate any tool or develop features for formspace.design, I ask myself a series of questions that help find that golden mean between simplicity and depth:

• Ease of Learning: How quickly can a new user perform a basic task? Is there intuitive onboarding?
• Sufficiency of Functionality: Does the tool cover basic needs without redundancy? Can it be used to plan a plot of, for example, 12 sotkas, from zoning to plant selection?
• Scalability: Can the tool 'grow' with the user's needs? Can one start with a simple sketch and then add a detailed dendroplan and estimate?
• Flexibility of Customization: Does the system allow adapting processes to the user's specifics without needing to write code?
• Visual Clarity: How clear is the information presented in the interface? Is there no element overload?
• Value for Decision-Making: Does the tool help make more informed decisions, rather than just collecting data? For example, can one quickly estimate the cost of selected paving materials or understand how the budget will change if different plants are chosen?
• Feedback and Support: Is there an easy way to send feedback or get help if questions arise? This is critically important for depth of use.

How to Plan in formspace.design

formspace.design is specifically designed to provide this compromise between simplicity and depth in landscape planning. I want every plot owner to be able to start planning without special skills, yet have the option to delve into details when needed.

Imagine you have a 15-sotka plot, and you want to create a functional and beautiful space on it. You start with Module 1.1 'Plot Zoning': simply drag and drop ready-made blocks – 'BBQ relaxation area', 'children's playground', 'fruit orchard' – onto your plan. This is intuitive and fast, taking literally 10-15 minutes. At this stage, you simply outline the main functional areas without delving into details. Then, you move to Module 1.3 'Objects on the Plot' and start adding specific elements: gazebos, paths (remembering that their width should be at least 1.2 meters for comfortable passage), small architectural forms. Here, more detailed elaboration begins, but the interface remains simple and visual.

If you want fresh ideas or don't know where to start, Module 2.1 'AI Concept' will come to the rescue. You describe your wishes, for example: 'I want a minimalist garden with a pond and ornamental grasses,' and the neural network generates several concept options, offering specific solutions for style, plants, and materials. This gives you not only inspiration but also deep elaboration, which can then be detailed in Modules 1.x, specifying the dimensions and arrangement of elements, and also considering, for example, the plot's slope or orientation to the cardinal directions. And if you have a photo of an existing plot, Module 3.1 'Design from Photo' will allow you to see how certain changes will look in reality, which greatly helps avoid costly mistakes where things were built first and then redone.

FAQ

Why are most programs either too simple or too complex?

Developers often either simplify functionality to a minimum to lower the entry barrier or try to include all possible features, making the system cumbersome. My experience shows that this is due to a lack of deep understanding of real user needs and an inability to find that balance between speed and detail.

How does formspace.design help avoid feature overload?

In formspace.design, I use a modular approach and the principle of 'layered' complexity. This means that core functions are immediately available, while more advanced and detailed options are revealed as needed, without cluttering the interface for beginners. You only see what is relevant to the current task.

Can I start with simple planning and then delve into details?

Yes, that's precisely what formspace.design is designed for. You can start with a general plot zoning scheme and then gradually add details: select specific plants, paving materials, and plan the lighting system. The system allows for a smooth transition from general to specific, without losing context.

What specific data can I account for in formspace.design, besides the visual plan?

Beyond the visual plan, formspace.design allows for accounting for data on zoning area, quantity and types of plants, and material volumes (e.g., how many cubic meters of soil will be needed for a flowerbed or how many square meters of tiles for paths). In the future, integration with cost estimates is planned so you can see the project budget in real-time.

What if my accounting needs are unique and don't fit into standard modules?

I strive for formspace.design to be as flexible as possible. If your needs go beyond standard functions, you can always use the system as a basis for visualization and basic accounting, and manage missing details in external tools. Additionally, I actively gather feedback and develop the product, adding new features that are in demand by users.

How did my experience as a manager influence the vision for formspace.design?

My many years of experience as director of 'Dom i Sad' allowed me to see all the 'pains' and needs of the landscape business from the inside. I know how important it is to have quick access to information, control budgets and deadlines, and effectively interact with clients. These insights formed the basis of the formspace.design concept, which I am building for myself and other practitioners.

Is there a risk that interface simplicity will hide important details?

I pay special attention to ensuring that important details are not hidden, but are easily accessible when needed. Interface simplicity does not mean a lack of depth, but rather an intuitive presentation of complex information. For example, when selecting a plant, you will see its main characteristics, and if necessary, you can access a full description and care requirements.

How often are accounting features updated in formspace.design?

As a solo developer, I am constantly working on improving and expanding the functionality of formspace.design. Updates are released regularly, as new modules and features are ready. I adhere to the principle of frequent, but small and thoroughly tested updates, so as not to disrupt the system's stability.

Next Step: Find Your Balance

The search for the ideal balance between simplicity and depth is an ongoing process that underlies the development of formspace.design. I am confident that this approach allows for creating tools that not only make life easier but also help make more thoughtful and informed decisions. Try formspace.design and see for yourself how easy it is to start planning your plot and then delve into details when truly needed.