Wildau, 1 April 2026 — Boomerent is part of the second batch at the Reaktor Wildau startup incubator, where it continues developing its AI-powered analysis of commercial leases and service-charge statements. Boomerent serves commercial tenants in Germany: retailers, restaurants, pharmacies, medical practices and office users who carry rent and service charges permanently, yet rarely have in-house specialists who can assess statements and lease clauses systematically. The software analyses leases, addenda and statements automatically, surfaces anomalies and cost drivers, and shows where a closer look is worthwhile. What draws us to the batch most is the surroundings: several founding teams in one place, facing comparable questions — which tools hold up, what scales, and where working together pays off. The company was founded by Stephan Thiel and Dr. Ron van de Sand. Reaktor Wildau is also the company's registered address: Boomerent is registered at the incubator's address on Schmiedestraße 2a. Reaktor Wildau announced the start of its second batch publicly in spring 2026.
What draws us to the batch
Reaktor Wildau is a startup incubator south-east of Berlin. For us the value of a batch lies less in the address than in the people next door: several teams building at the same time, solving the same unglamorous problems — how to run customer interviews without steering the answers; which tool to skip; what actually breaks an integration.
It gets interesting where paths cross. We work with leases and statements — documents you can pull structure out of. Other teams work with processes, sensors or sales. Those edges are where the obvious ideas live: shared analyses, shared tooling, a pilot customer better served by two companies than one.
If you're in the batch, or building something in the region that touches those edges, get in touch. We would rather trade notes on tools and approaches than attend another conference.
Note on the relationship
Reaktor Wildau is at once incubator, registered address and a user of Boomerent. We state this multiple role explicitly so the context stays transparent.
