Owned product
Last updated: September 2026
Buy Houses Japan: from a search request to editable filters
An Urbano DX product we build and operate. This case shows a software delivery pattern, not a client testimonial or a claim about property availability.



The problem
Property requests mix location, budget and preferences in one sentence. Buyers need to see how that request becomes a search.
- Input: a buyer describes the property they want.
- Output: structured search criteria, results and a map.
- Control: criteria remain visible and editable.
What the product demonstrates
The useful result is an inspectable path from a request to source information.
- Connect natural-language input to ordinary product controls.
- Keep results, map and listing details part of the same journey.
- Present derived signals as aids to review, with source details available.
How to review the evidence
Open the public product and inspect the current search experience. The captures above show an earlier public version; their counts and listings are not current inventory.
- Check whether you can inspect and correct the criteria.
- Follow a result into its detail and source information.
- A search match does not verify availability, condition or suitability for purchase.
What this means for your project
The transferable pattern is a small, usable workflow with human control. Your own PoC still needs representative inputs and agreed acceptance checks.
- Use the sample acceptance report to define what you will inspect.
- Agree the boundaries and data access before estimating a build.
Scope the first sprint
Bring the app, API, LLM feature, or AI workflow you want to test. We will turn it into a clear first-sprint scope.
Start a conversation