← Home

Unpacking legal complexity to unblock German market launch

Crowdhouse2022Proptech

Role

UX/UI cover within cross-functional squad

Team

Legal advisor, Product Manager, Developers, Partner Squad

Challenge

  • Crowdhouse, an online property investment platform, was poised to expand internationally into the German market.
  • A critical German legal requirement was identified late in the process: sellers must include specific energy efficiency data in their listings.
  • A German seller was ready to list but blocked until the platform properly supported this requirement.

Impact

First German seller retained and unblocked

A minimal compliant path shipped quickly while we worked on a fuller solution, keeping a seller in the funnel at a critical moment in the company's market expansion.

Reduced potential for seller error with our iterated version

We followed up with a dynamic form, adapted to each certificate type, steering sellers to the right fields and improving data clarity for potential buyers.

Wider team equipped to scale energy efficiency work

Full documentation of certificate logic and requirements gave the whole department the knowledge to progress the work without repeated discovery.

What Shipped

Energy certificate form — seller guided through required details

German sellers could easily add all mandatory energy information to the property listing

Clear guidance and easy inputs were integrated into the existing listing creation flow. The form adapted dynamically based on property and certificate type.

Energy certificate form — seller guided through required details

Internal admin team could double-check details before publishing

Submitted details and uploaded certificate pulled through into the admin interface, to ensure listings were fully compliant.

Energy certificate form — seller guided through required details

Potential buyers could scan energy information within the property listing

This valuable information was presented cleanly within the existing listing page structure, with the certificate itself available to view alongside other property documents.

My Part

I rapidly unpacked a complex legal requirement before touching design.

(Uncovering legalities & exploring competitors.)

Different certificate variants and their associated data fields
Just a few of the German energy certificate variants
What initially seemed straightforward turned out to be more complex.

Required energy information depended on:

  • Residential vs commercial use.
  • Age of the building.
  • When the certificate was issued.
  • Requirement vs consumption certificate type.

I created and maintained a flow diagram to make the logic navigable for the whole squad.

(Turning complexity into shared reference point.)

Different certificate variants and their associated data fields
Many variables dictated the information that must be placed in the property listing.

I formed multiple design proposals with varying levels of complexity.

(Efficient exploration using our design system)

Sellers' needs:

  • Do I need to provide energy information for this property?
  • Why is the information required?
  • How do I get a certificate if I don't have one?
  • Which type of certificate do I have/need?
  • Which information do I need to include and where do I find it?

Potential buyers' needs:

  • How energy efficient is this property?
  • How can I trust the information?
Noone wants to spend time filling out forms. In an ideal world we'd 'magically' pull the information from the certificate.
Sharing multiple variants with differing complexity provoked discussion around priorities & scope.
Version A wireframe — seller energy certificate input
Seller view: Guidance added to free text description as part of listing creation.
Version A wireframe — energy data on property listing
Buyer view: Information displayed simply within listing description.
Different certificate variants and their associated data fields
Seller view: Form logic displays fields relevant to the selected certificate type.
Energy certificate form — seller guided through required details
Seller view: Fields are hidden when no certificate is needed.
Buyer view: Information displayed clearly within listing description.
Buyer view: More granular input allows energy information to be displayed clearly within existing listing structure.

Most basic: free text

Pros

  • Very quick to deliver.

Cons

  • More risk of manual entry error.
  • Certificate upload could still be missed.
  • Information is not as easily digested on the listing.

Most logic: dynamic inputs

Pros

  • Guides sellers to provide the right information.
  • Reduces manual entry errors and missing details.

Cons

  • More complex to build.
  • Required clearer logic for different certificate types.

I pushed for a pragmatic call to ship a simple solution fast, with a better one already in motion.

(Progress over perfection.)

Outcome

Reflections