Portfolio: Integrated Systems

Re-architecting the Data Model

We introduced Spaces within Properties related to Sublistings within Listings to represent buildings containing multiple units that could be let or sold separately, with configurations that evolved over time. For property complexes—where one owner might have several buildings at a single address—we created Complex Building Listings that grouped individual Building Listings whilst preserving space-level detail. We also accommodated co-ownership scenarios where different owners marketed separate spaces within the same building.

The financial tracking layer was built entirely from scratch: Requirement Mandates and Listing Mandates captured fee structures on both sides, with Buyside and Sellside Fee objects flowing through the Favourite → Offer → Closing process, supported by Invoice Requests and Commission Forecasts broken down by company and negotiator. This gave RealCorp full financial visibility across its sales pipeline.

Technical Implementation

The core architecture included the new data objects for Spaces, Sublistings, and Complex Building Listings at each deal stage. Financial structures comprised Requirement Mandate, Listing Mandate, Buyside Fees, Sellside Fees, Invoice Requests, and Commission Forecasts. Integration covered XML feed generation, SOAP and HTTP APIs, automated prospectus and newsletter generation, and website property search with CRM synchronisation.

The Outcome

The result was a fully re-architected commercial real estate platform capable of handling the complexity of the Luxembourg market on infrastructure originally built for a different business model. Migrating from LogiPro, ACT!, and negotiators’ individual contact lists to Salesforce/Propertybase unified RealCorp’s data and processes across sales, marketing, and management. The new system reduced duplication, improved collaboration, and provided real-time insight into relationships between negotiators, clients, and properties.

By leveraging Salesforce’s flexibility, RealCorp gained a future-proof foundation: cloud-based mobility, advanced reporting, and the capacity to adapt its business logic as market conditions evolved. The transformation delivered not just a new CRM, but an integrated operational platform supporting transparency, data integrity, and sustained business growth.

Eyal’s Technical Leadership

As Magic expert and leader of the Media Library team, Eyal developed core functionality for tracking versions of purchased TV programmes through Editorial, Certification, and Promotions processes—critical for rights management. He also built the Workflow module singlehandedly. As the company expanded, Eyal joined four other Senior Team Leaders in coordinating 85 developers across multiple countries.

He co-led the migration from Magic to C#, advised the .NET infrastructure team on architecture decisions, and trained other leaders on complex migration patterns. Eyal established coding standards to prevent single-client fixes from affecting others, managed remote bug-fixing teams across time zones, and resolved high-impact issues for international broadcasters where downtime could affect millions of viewers.

Tia’s Quality & Documentation Leadership

Managing QA and Documentation concurrently, Tia built the company’s first systematic approach to both disciplines. She recruited and led a blended team of 14 testers and writers, established quality standards and testing procedures, and introduced early GUI reviews to ensure consistency across complex multilingual interfaces. She also introduced single-sourcing documentation using AuthorIT and created functional specifications and user guides for software that operated differently for each client yet required consistent documentation.

The Outcome

IBMS became a robust, scalable system serving major broadcasters worldwide with mission-critical reliability. The quality processes ensured dependable operation where downtime meant lost advertising revenue, and the technical leadership enabled successful migration to .NET without interrupting service.

While Magic had offered rapid development and portability, the move to C#.NET reflected broader enterprise trends of the mid-2000s: reducing runtime licensing costs, aligning with mainstream enterprise technology stacks, and ensuring stronger market acceptance in North America. The transition secured IBMS’s longevity and reinforced Pilat Media’s credibility in a global marketplace increasingly standardised on Microsoft technologies.

Technical Leadership and Architecture

Eyal redesigned the Oracle database schema to improve data integrity across complex relationships, enhance performance for high-volume transaction processing, and support distributed agency operations. He coached nine junior developers in object-oriented techniques, database architecture, and quality standards while overseeing debugging for the entire project.

Eyal also created Pascal utilities for user interface translation, accelerating localisation and deployment. His leadership ensured that the development team could continue maintaining and extending the system independently after project completion.

The Outcome

The converted system delivered enterprise-scale stability and flexibility across hundreds of agencies. By moving from COBOL to Magic, Koc Allianz gained faster development cycles, improved integration capabilities, and easier adaptation of products and workflows—critical in a dynamic insurance market.

Beyond the technical transformation, the project built long-term capability within the client’s own team, enabling sustained system evolution and self-reliance.

The Architectural Solution

Eyal designed a parameter-driven architecture enabling bespoke functionality for each international client while maintaining a single core codebase. This approach embedded configurability directly into the system rather than relying on client-specific modifications.

The system included full rental transaction processing, fleet maintenance tracking, integrated accounting, management analytics, user access controls, automated data conversions, licence protection, and multilingual support. It was deployed across multiple platforms—Magic 7 on Windows 95/Btrieve and Magic 5.7 on VMS/VAX with RMS—requiring careful handling of platform-specific differences to preserve functionality and consistency.

The Outcome

Each client benefited from every bug fix and upgrade while retaining its individual workflows. The architecture enabled rapid onboarding of new clients without compromising stability, demonstrating how thoughtful design can balance customisation with maintainability. The project anticipated principles later central to multi-tenant SaaS systems—shared infrastructure with client-specific flexibility.