All articles

    Architecture note

    15 July 2026by Gustavo Teixeira Cuco4 min read

    Building PropTech as an Asset Operator

    Architecture context

    Architecture decision

    Operating modelEconomics and measurement

    Applied in

    LusiberiaStays
    Building PropTech as an Asset Operator
    View on LinkedIn

    I run three short-term rentals across Algarve and Andalucía. The platform that runs them is React + Supabase + Lovable Cloud. People ask whether the stack scales. It does — just not the way the blogs assume.

    I started by reading PropTech advice. The advice was uniform: build for tenants, design for scale, abstract the property model so it works across asset classes. Generic enough to license to other operators eventually.

    That advice is right — for one kind of PropTech.

    There are two kinds, and they look the same from the outside.

    The first kind sells governance to other operators. The product is the abstraction: a multi-tenant model that works across asset classes, configurable per customer, decoupled from the actual operations of whoever buys it. Horizontal scale: more customers, each running their own operation on top.

    The second kind runs the operator's own assets. The product is the integration: deep coupling to how I onboard guests, price properties, sync calendars, handle compliance. Vertical scale: more of my own assets, more jurisdictions, more owners under my management — but the platform is mine, not licensed.

    Both scale. Both are real businesses. They just scale on different axes.

    I'm building the second kind. Here's what that means in practice.

    The platform is multi-tenant — for my owners, not for other operators. Row-Level Security and MFA are there because I manage assets on behalf of property owners who need scoped access to their own financials. Adding the tenth owner is a config change, not an architecture rewrite. But "tenant" here means "property owner I work with," not "PropTech customer paying me a SaaS fee."

    Compliance is encoded for the jurisdictions I operate in. RNAL in Portugal. NRUA in Spain. GDPR everywhere. The platform encodes these as defaults because I know which property sits in which jurisdiction. Adding a third jurisdiction (UAE, France) is a fork of the compliance defaults — same architecture, more rules. The platform supports horizontal-by-jurisdiction even when it doesn't support horizontal-by-customer.

    Edge functions automate my recurring operations. Five production edge functions run things that would otherwise eat my time: iCal sync from Airbnb (sync-ical-feeds), owner portal token lifecycle (generate / validate / revoke tokens), and contact email routing. Each one replaces a manual task that recurs per property. Adding the fourth property doesn't add four hours of weekly admin — the edge functions absorb it. That's vertical scale.

    The constraint isn't capacity, it's positioning. Could I license this to another operator tomorrow? Technically, yes — Supabase is multi-tenant, the codebase is clean enough. But the day I'd want to sell this as SaaS, the architecture would change: configurability over defaults, abstract workflows over hardcoded compliance, customer success layer, billing. That's a different product, not a refactor. And it's a strategic choice not to build it.

    The trap with operator PropTech isn't pretending it's a future SaaS. It's pretending the choice doesn't exist. There's a real fork in the road: do you sell governance to operators, or do you operate? Selling means investing in abstraction, configurability, customer onboarding, support. Operating means investing in deep integration with your own operations, compliance for your own jurisdictions, automation of your own recurring tasks.

    Both lead somewhere. They lead somewhere different.

    For now, I'm operating. The platform scales with me — more properties, more owners, more jurisdictions, automated where it counts. The day the strategic question is "should LusiberiaStays become a PropTech SaaS?" is the day the architecture conversation starts. Today it's not that day.

    The PropTech I run runs me. That's not a limitation. That's the design.

    Sources

    • LusiberiaStays operations stack: React 18 + TypeScript + Supabase + Lovable Cloud
    • Compliance frameworks: PT DL 128/2014 (consolidated DL 76/2024), ES Decreto 28/2016, GDPR
    • Edge functions in production: sync-ical-feeds, send-contact-email, generate-portal-token, validate-portal-access, revoke-portal-token
    • Properties under management: 3 (Algarve, Algarve, Andalucía)
    • Multi-tenant architecture: Row-Level Security on Supabase, MFA TOTP on admin, owner portal with token-scoped access