How I Test CRM Modules Using Data from My Own Practice

Throughout my career in landscape design and previous businesses, I encountered the same problem: the lack of an adequate system for managing projects and clients. Standard CRM systems often failed to understand the specifics of our industry, and manual accounting led to constant errors and losses. Therefore, when I started creating formspace.design, it was fundamentally important to me that the future modules for project and client management be as practical and effective as possible. And the best way to ensure this is to test them with real data from my own extensive practice.

My Path to Automation: From Manual Accounting to CRM

My experience as a director at NPF Alkar in the 90s, and then at my own landscape company Dom i Sad (House and Garden) since 2000, showed how critically important accurate accounting is. I remember manually assigning tasks to programmers for management accounting at Alkar, trying to systematize commerce in the post-Soviet market. And at Dom i Sad, for years we tried to reconcile debits and credits, track project profitability, and control every stage of work – from design to site maintenance. It was a tremendous pain. Calculations in Excel, paper contracts, scattered client data – all of this led to me spending up to 30% of my time not on strategic development, but on trying to piece together the operational picture. Errors in profitability calculations could reach 10-15% on large projects, directly impacting profit. This was a very expensive lesson that gave me a clear understanding that I needed the tool I had been searching for my entire career.

Why Standard CRMs Are Not Suitable for the Landscape Business

The specifics of landscape design differ from standard retail or services. We work with long-term projects (often 2-3 months for a 10-15 sotka plot, sometimes even longer), deal with living materials, weather conditions, seasonality, and complex estimates that include both design work and the supply of plants, soil, irrigation systems, lighting, and construction work. Standard CRMs, focused on quick sales and typical funnels, simply do not account for these nuances. They do not allow for effective management of design stages, procurement of specific plants, planning work with consideration for weather risks, or tracking warranty obligations for plant care. For example, tracking the client's lifecycle after project completion, when annual maintenance or replanting is required, often falls outside the scope of standard systems.

Collecting and Preparing Real Data

To test the future CRM modules of formspace.design, I use archival data from my company, Dom i Sad. These are thousands of records: from initial client contacts, briefs, and design projects to estimates, acts of completed work, and correspondence. I digitized old Excel spreadsheets, notebook entries, and project photos to create the most complete picture possible. Of course, this is a colossal amount of work, but it provides that crucial authenticity. I include everything in this data: from the plot area (e.g., 12 sotka) and its slope, to the cost of planting material and labor costs for each type of work. This allows me not just to check functionality, but to literally 'run' the history of my business through the new modules, identifying where the system could have saved time or prevented an error. I've written more about why a quality brief is important for preventing technical debt in the article Why Technical Debt in Business Starts with a Poor Briefing.

Testing Criteria: What I Check in the Modules

When testing, I focus on several key criteria that were my pain points in the past:

1. Financial Accounting Accuracy: The module must correctly calculate project profitability, account for all direct and indirect costs, and track cash flow for each stage. It's important for me to see how expenses are distributed, for example, 30% for materials, 40% for labor, and 30% for overhead, and how this correlates with my actual profit.
2. Project and Task Management: The ability to create a detailed work plan linked to deadlines, responsible parties, and resources. Tracking progress for each stage (e.g., Week 1 – measurements, Week 2 – sketches, Week 3 – dendroplan) and automatic notifications for overdue tasks.
3. Client Interaction: Communication history, storage of all documents (contracts, estimates, acts, photos), and quick access to information about client preferences and specific plot features.
4. Resource Management: Accounting for specialist and equipment availability, inventory control of materials in stock, and automation of supplier orders.
5. Analytics and Reporting: The ability to quickly generate reports on project effectiveness, team workload, and financial indicators to make informed management decisions.

Typical Errors I Identified

Using my real data, I was able to identify many potential problems in the test modules that would have led to serious failures in real-world operations. For example:

• Incorrect Material Write-off: In one test scenario, the system incorrectly debited the volume of fertile soil based on the total plot area, rather than the zones actually laid out in the project, leading to a discrepancy of 20-30 m³ and, consequently, a distortion of the cost price. Such errors could have cost me thousands, if not tens of thousands, of dollars on large projects.
• Forgotten Work Stages: Due to the lack of a clear link to the estimate, the system failed to remind about the need to pay for an intermediate stage of work (e.g., after the completion of earthworks), which delayed the receipt of funds and created cash flow gaps.
• Loss of Important Client Information: In one instance, due to an unstructured comment field, information about a client's allergy to certain plants was lost, which could have led to a serious error in the dendroplan.
• Incorrect Time Calculation: The system might underestimate the time required for caring for complex plant compositions, leading to team overload or incomplete work.

These specific examples convince me that testing with live data is the only way to create a truly functional tool.

Iterative Approach: Test, Refine, Repeat

My work on formspace.design is a continuous process of iterations. I am not a programmer by profession, but my experience and business understanding allow me to clearly define tasks and control the outcome. After each testing cycle, I gather feedback, record errors, and propose improvements. Then we refine the modules, and the process repeats. This is similar to how I explained my tasks to programmers many years ago, but now I am the one building this tool and can speak the same language as AI. I discussed this in the article Years When I Explained to a Programmer What I Needed, and Got Something Else. This approach allows me not just to create a CRM, but to build a system that truly solves the problems of the landscape business.

How I Use formspace.design to Validate CRM Concepts

While formspace.design currently focuses on AI-powered landscape planning and design, its modules already lay the groundwork for future CRM functionalities and serve as a testing ground for the concepts themselves. For example, using modules 1.x (Planning, Zones, Objects), I can create a detailed site project, define functional zones, place landscape elements, and visualize them. All this structured information – dimensions, plant types, materials, object placement – forms an ideal basis for a future CRM. I can take such a 'ready-made' project and simulate how the CRM will track the procurement of each plant, plan its planting work, and control budgets for earthworks or irrigation system installation. This allows me to see how project data will 'flow' between modules and how it will be used for further management.

Module 2.1 'AI Concept' also plays a key role. It allows for generating preliminary design concepts based on client input data, which, in turn, helps me test how the CRM can automatically form initial commercial proposals, preliminary estimates, or even tasks for the team based on the AI-suggested concept. I can upload a client's site photo, get several layout options, and then imagine how these options will be integrated into the CRM for tracking client preferences, making changes, and final project approval. This approach allows me to check not only the technical implementation but also the logic of business processes, ensuring that formspace.design will be not just a set of features, but a cohesive system.

FAQ

Can a CRM fully automate a landscape business?

Fully automating all aspects of a landscape business, given its creative and living nature, is quite challenging. However, a CRM can significantly automate routine processes: accounting, task planning, client management, and document flow. This frees up time for creativity and strategic development, allowing you to focus on design and quality rather than paperwork.

Why spend so much time on testing when I could just buy an off-the-shelf CRM?

Most off-the-shelf CRMs do not account for the unique characteristics of the landscape business, leading to the need for numerous customizations or compromises. My approach with thorough testing on my own data ensures that formspace.design will perfectly match the industry's needs. This is an investment in long-term efficiency and avoiding 'workarounds' in the future.

How difficult is it to migrate old data to a new system?

Migrating old data is always a challenge, but it is absolutely necessary for a new CRM to function fully. I use my experience to develop import mechanisms that will simplify this process as much as possible. It's important to structure your data in advance to ensure the transition is as smooth and painless as possible.

What if my practice differs from yours?

My practice serves as the foundation for testing, but formspace.design is being created as a flexible tool. Future versions will include options for customization and configuration to suit the individual specifics of your business. The goal is to provide a universal yet adaptable framework that everyone can tailor to their unique processes.

Can a CRM increase profit?

Yes, a properly implemented CRM can significantly increase profit. It helps optimize expenses, improve project management, minimize calculation errors, enhance client loyalty, and effectively track new opportunities. Through more accurate accounting and control, you can make more informed decisions and avoid financial losses.

Can formspace.design modules replace a full-fledged CRM?

In the long term, I envision formspace.design as a comprehensive platform that will include not only planning and design tools but also full-fledged CRM functionalities adapted for the landscape business. Today's modules are the foundation upon which this system will be built. My goal is to create precisely such a tool that can replace many disparate programs and spreadsheets.

Next Step to Effective Management

My experience and data from real-world practice are my main assets in creating formspace.design. I am building a system that not only solves problems but prevents the issues I myself have faced for decades. This is a long and meticulous process, but I am confident that the result will be worth the effort. Stay with formspace.design to see how this tool, created for the real needs of landscape professionals, develops. Together, we can make your business more transparent and profitable.