Your core systems were chosen one at a time. None of them agree on the portfolio.

Your operation on a unified architecture.

For CIOs, CFOs and boards at residential operators and REITs who are choosing or replacing a core platform, or carrying the cost of one that never quite fitted.

Start an Architecture AssessmentSee what three weeks include

Does this sound familiar?

Every system in your operation was chosen for a good reason, one at a time. Now none of them agree. Two departments report two occupancy rates for the same building, and someone reconciles them by hand before the board sees either.

Connecting anything new is quoted in months and tens of thousands, so the business has stopped asking. The spreadsheet between two systems has quietly become a person's job.

And a core platform is about to be chosen on the strength of demos by people who will not be there when the integration bill arrives.

  • Occupancy, arrears and valuation each have more than one answer, depending on which system you ask.
  • New integrations are quoted in months and tens of thousands, so nobody proposes them any more.
  • Nobody has written down what the next core platform has to do before the demos start.
  • The shortlist came from the vendors' own reference customers.
  • Every AI initiative stops at the same place: the data underneath it.

If you want one answer for every figure, your systems need a unified architecture.

That means assets, units, leases, tenants and contracts defined once, your systems on one integration layer, and the core platform chosen on evidence from your own portfolio rather than a demo. Here is what that gives you.

  • A single source of truth for assets, units, leases, tenants and contracts
  • Systems you can connect in weeks or replace one at a time, without the change breaking everything
  • A core platform selected on proof, and a build-out shaped to your operation

The path from here

You commit one stage at a time. Each stage leaves you something you can use whether or not you go on, and nothing ties you to a platform we recommend. 6 to 9 months to a running architecture, then a 12 to 24 month term underneath it.

  1. Architecture Assessment Start here3 weeks. Systems, integration debt, data model, shortlist.
  2. Proof of conceptAn 8-week gated proof of concept on your shortlisted platform or target architecture, before you sign anything.
  3. Build-outA composed architecture or a vertical platform, whichever the proof supports.
  4. Managed ServicesWe run it under a 12 to 24 month term, if your team does not have the capacity.

Start an Architecture Assessment

Three weeks to a clear picture of your systems, your data model and the platform shortlist. Or start with a 30-minute working session.

Independent. We recommend what works, not what we sell.

One reply, within a working day, from the person who would lead the engagement.

Rather talk it through first? Book a 30-minute introduction call

What we have done in real estate

Three engagements, one for each step of the ladder, and what each one settled.

  • Agentic Readiness, for a European property software vendor

    Every new client was configured by hand, from knowledge in consultants' heads. In a few weeks we built a working agent against their live platform, using standards derived from their own past implementations. Their consultants judged the standard and output good enough to take over much of the work. They left with the agent, the evidence, and a rollout plan.

  • Architecture Assessment, for a pan-European real estate organisation

    A core platform was about to be chosen with no picture of what it had to fit into. We designed the target architecture first, then scanned the market against it: an independent shortlist with a cost range per option, where quotes for the same scope differed by a factor of three. The board got a shortlist it could defend and the figures behind its business case.

  • Agent Development, for a proptech platform

    Tenant and back-office agents on a live portfolio, connected to the property management and service ticket systems. Answers are benchmarked before release and monitored after, each agent sees only what the person asking may see, and GDPR and the AI Act are designed in. Tenants get answers at any hour; the team gets the exceptions and a record of every action.

Three starting points, one discipline: prove the output on real data before building the plumbing, keep what the existing systems can carry, and the same people from first session to handover.

Based in the Netherlands and built for European enterprises: data sovereignty, GDPR and AI Act compliance from day one.