Roadmap & governance #

Technical excellence alone does not make a standard. A standard needs trust, a community and a credible path to formal recognition. Here is the plan.

Governance — who owns the standard #

Prexfo is meant to belong to no one alone. The recommended model is “liberal contribution”: influence arises from current work, decisions are reached by consensus. The standard is carried by a non-profit consortium (in Germany a registered association) acting as a neutral steward.

  • Specification & schema — open under Apache 2.0 for maximum adoption.
  • The “Prexfo” brand & logo — owned by the association and protected, so that use stays consistent and trustworthy.
  • Steering committee — representatives of the key members secure the strategic direction and give competing companies the assurance of a neutral playing field.

The path in three phases #

graph LR P1["Phase 1: Foundation (months 1-6)"] --> P2["Phase 2: Growth (months 7-18)"] P2 --> P3["Phase 3: Establishment (months 19-36)"]

Phase 1 — Foundation (months 1–6) #

Validation through real use cases.

  • finalize specification 1.0 and the legal framework
  • develop an SDK MVP (Python)
  • win 2–3 design partners — a technically capable manager, an innovation-friendly bank or insurer
  • pilot a real exchange process (e.g. a credit check)
  • first case studies with measurable results
  • found the consortium (registered association)

Phase 2 — Growth (months 7–18) #

Build awareness and community.

  • public launch on an open platform (specification, SDK, docs, case studies)
  • talks, articles, presence in PropTech communities
  • contact with industry associations, in particular the German ZIA
  • extend the SDK to Java and JavaScript
  • win further consortium members

Phase 3 — Establishment (months 19–36) #

Critical mass and formal standardization.

  • initiate a DIN SPEC process — an agile, official seal of quality
  • based on it, evaluate the path to a DIN standard and later an ISO standard
  • develop the standard further through the open governance process (1.1, 2.0)
  • foster an ecosystem of third-party tools

Where Prexfo stands today #

Schema version 1.0.0 is defined; the workflow engine, importers and the document stock run in production at Berlus (see Practice). The next major step is the transition from internal testing to public, community-driven standardization.

Get involved. Prexfo thrives on the contributions of others — managers, banks, developers. Whoever wants to shape the standard early finds the way via Contact.