Product and operating architecture

    Gustavo Teixeira Cuco

    I design systems for decisions that cross product, operations, capital and risk.

    The work begins when the parts no longer work in isolation: frame the problem, make constraints explicit, connect execution and leave evidence of what changed.

    Gustavo Teixeira Cuco

    Architectures evolving at THE iCON, Q-LIRI and LusiberiaStays

    Observed architecture

    Three systems, three verifiable changes.

    The number is a consequence, not the story. Each example connects a circumstance, a system decision and the boundary of its evidence.

    Sale · €570k · Feb 2024

    From rehabilitation to exit decision

    Three-bedroom flat · 99.8 m² · Campo de Ourique

    End-to-end rehabilitation management, direct contracting, and sale coordination.

    ~€96k of documented labour and materials; excludes acquisition and does not represent a return on total capital.

    View case architecture

    3 assets · 2 jurisdictions

    One operating system across properties

    Lagos · Alvor · Costa Esuri, across Portugal and Spain.

    Direct responsibility for connecting product, operations, compliance and reporting.

    In Lagos, a rehabilitation was completed in 9 months after comparing four proposals; the property then entered short-term rental operation.

    Open LusiberiaStays

    −30% processing time

    Redesigning a public-health workflow

    Public health operation · team of up to 23

    Responsibility for the operating architecture: onboarding, training, dashboards and process optimisation.

    Historical result at ARSLVT; not a Q-LIRI result.

    View experience

    Architecture method

    The problem determines the shape of the system.

    Architecture does not begin with technology. It begins with the failing decision, the constraint that matters and the evidence needed to know whether change worked.

    Problem

    Locate the difficult decision, the affected user and the consequence of staying the same.

    System

    Connect people, data, processes and technology under real constraints.

    Evidence

    Verify the result in the right source and state what remains unproven.

    Inspectable evidence

    Systems you can open.

    The public layer confirms that products exist. Sanitised decisions and private evidence support what the surface alone cannot demonstrate.

    When the parts no longer work in isolation, the problem is architectural.

    For systems crossing product, operations, data, capital, compliance or AI — with responsibility for the decision and its evidence.

    Get in touch