A real estate promotion software should not be judged solely on its commercial brochure. Amid promises of automation, hastily added CRM modules, and superficial GDPR certifications, actual friction points emerge after the contract is signed, sometimes only after several months of operation. We review the technical blind spots that most comparisons do not address.
Software Liability and AI Compliance: What the European Framework Changes for Developers
Several recent European texts extend the notion of defective products to software, including when they operate autonomously. Specifically, if a software defect causes harm to the developer (margin calculation error, failure in buyer tracking), the publisher’s direct liability may be engaged.
The EU Regulation 2024/1689 on artificial intelligence will impose, starting in August 2026, obligations for transparency and labeling for AI features integrated into business tools. Prospect scoring, visual generation, land decision support: even when the system is not classified as “high risk,” the publisher must document its models and implement a bias correction process.
We observe that the majority of developers do not check their publisher’s AI compliance strategy before signing. This is a blind spot that exposes them to risks of algorithmic discrimination or regulatory non-compliance. Before making any decisions, common errors are detailed in a dedicated guide on real estate promotion software on Spy Immo, which covers this legal aspect in particular.
GDPR and Data Subcontracting: The Developer Remains Responsible for Processing
Displaying “GDPR compliant” on a product sheet does not transfer any responsibility. Legally, the developer remains responsible for processing under the GDPR, even when delegating the hosting and processing of personal data to a SaaS publisher.
The classic trap: signing a Data Processing Agreement without checking the entire chain of subsequent subcontractors. A publisher that uses an American host or a data enrichment provider outside the EU can create a breach in the developer’s compliance, without them being informed.
- Request a comprehensive list of subsequent subcontractors and their geographical location before any contractual agreement.
- Check the actual retention periods for identity documents and buyer documents in the software settings, not just in the commercial documentation.
- Request a portability audit: in case of a change of publisher, your data must be recoverable in a standard format and within a contractually defined timeframe.
A software that does not allow for proper export of the buyer database, attachments, and exchange history creates a technical dependency that is difficult to break.
RE2020 Interoperability and Budget Management: The Features That Set Apart
Comparisons focus on CRM and multi-broadcasting. For a developer, the core of the software remains the financial management of the operation and its ability to communicate with the technical ecosystem of the project.
Since the generalization of RE2020, energy performance data (Bbio, Cep, Ic) must circulate between the thermal study office, the operation setup software, and investor reporting. A software that does not offer structured import of these indicators forces manual re-entries, which are a source of errors in forecast balances.
Technical Criteria to Check During a Demonstration
- Native connectors to RE2020 calculation tools and the open data platforms of the Ministry of Ecological Transition.
- Granularity of budget tracking: does the software allow for breakdown by batch, phase, and item (land, work, fees, taxes) with real-time updates?
- Management of buyer fund calls with automatic calculation of VEFA deadlines and generation of regulatory letters.
- Traceability of changes: each price change, grid, or plan must be timestamped and attributed to an identified user.
A tool that ticks all the functional boxes on paper but requires manual CSV exports to feed accounting or investor reporting is not an integrated management software. It’s a dressed-up spreadsheet.
Hidden Costs and Publisher Lock-In: The Clauses to Read Before Signing
The displayed price of a SaaS subscription almost never reflects the actual operating cost. Several items go under the radar during the demonstration phase.
The initial setup, first. Most publishers charge for startup support (data migration, workflow configuration, team training) in addition to the monthly subscription. This item can represent an amount comparable to several months of licensing.
The scaling up, next. Some pricing models index the price on the number of active operations or the volume of document storage. A growing developer may see their bill increase significantly without having added any functionality.
Contractual Clauses to Watch Out For
The reversibility clause deserves careful reading. It defines the conditions under which the developer retrieves their data at the end of the contract. A vague timeframe or proprietary format makes migration to a competitor costly and risky.
We recommend negotiating in writing three points before signing: the data export format (ideally an open standard), the maximum timeframe for restitution after termination, and the absence of overcharging for extraction. A publisher that refuses these clauses indicates a business model based on lock-in.
The choice of real estate promotion software commits the organization for several years of operation. The visible criteria (interface, number of modules, catalog price) matter less than the legal solidity of the contract, actual regulatory compliance, and the real capacity for interoperability with your technical ecosystem. Testing these points in real conditions, on a pilot operation, remains the only reliable filter before a portfolio-wide deployment.
