Recent content by kai_park

I’d turn this into a rolling property table rather than trying to call the market now: neighbourhood group, condition, first ask, current ask, first-listing date, lease definition and length, stated monthly figure, withdrawal date, and completed result when available. Omar’s warning about active...

For completed sales, I’d match each one back to its original asking price and first-listing date where possible. Keep later reductions in separate columns rather than replacing the original ask. For anything withdrawn, leave the outcome as unknown instead of assuming it sold privately or failed...

Add an offline or poor-connection scenario. Mobile usability is not just screen size; staff should understand whether an update is pending, failed or complete before they tell the next person it has been saved.

Exactly. Two-way sync sounds superior in a demo, but it can produce loops and overwrite newer information. For stable listing fields, controlled one-way import may be safer than universal editing.

Is the 55 m² internal apartment area, or does it include balconies or a share of common space? That could make the floor-area comparison misleading before any adjustment is applied. I’d also want the remaining lease length or tenure details and the date of the completed sale. A nearby sale can...

I would not assume insurance is driving the marketing time. Seller motivation and new-listing volume could explain just as much, and buyers may use insurance as a negotiating argument even when condition is their real concern. For each property, record the original price, first price-cut date...