TESWA — REAL ESTATE EXPANSION · THE DECISION BOARD
Every card is one decision. Tap an option to choose it — it saves instantly to the server, so your choices follow you between devices. Add a note on any card if you want to explain or adjust. My recommendation is marked “My pick” on each card. To discuss one in chat, just mention its id (for example B5).
Loading saved decisions…
Locked in from your kickoff message. Still editable if you change your mind.
The structural choices everything else hangs on. Decide these first.
Where: Database + every server job
Today there is ONE "listings" shelf and no category tag anywhere. This choice drives everything else.
Where: Algolia (the text-search engine)
Cars use one index with car-tuned ranking and car nickname synonyms.
Where: Links (/listings/TW-1001078), receipts, support
TW stands for Teswa, not for cars.
Where: The lookups system (the admin dictionary)
Car lists (makes, models, colors…) live as one flat set of lists; the editor and the site read them by name.
Where: Filters, prices, sorting — every property surface
Half the property market in Kuwait is rentals. A rental shows price per month (د.ك/شهر), and “sold” becomes “rented”.
How users enter, switch worlds, and what the front door looks like.
Where: The home page
Your idea: first-time users choose their world. The safe version keeps a real home page underneath (Google needs one) and shows the chooser on top, once.
Where: Site header (desktop AND phones)
A fact from the scan: the «الكويت» chip you pointed at only exists on wide screens — it is decoration, hidden on phones. The switcher must exist everywhere. The final look goes through «أفكار» design options later; this question fixes the DIRECTION.
Where: teswa.net front door
Today’s home is 100% cars: maker logos, body types, most-viewed cars.
Where: Links + Google
Car pages use English URL words: /cars/toyota, /cars-in/salmiya.
Where: The bottom of every page
The confirmed strip says «عندك سيارة؟ … اعرض سيارتك» on every page.
What a property listing IS: types, details, trust, titles, photos.
Where: The property vocabulary
The type list shapes the filters, the create flow, and the office pages.
Where: Create flow + ad page + filters
Cars carry make/model/km/year…; property needs its own set.
Where: Ad cards + the ad page
Cars have «شرط الفحص». Property has no inspection equivalent yet.
Where: Cards, ad page, share cards
Cars auto-build a title like «كامري 2023» when the seller doesn’t write one.
Where: Create flow + storage
The photo pipeline (private originals, auto WebP versions) is category-free and works as-is.
Identity, buyer tools, seller lists, and the business cockpit.
Where: Business identity, approval, subscription
Today a business IS a car showroom. You decided one phone can hold both worlds — this question decides the shape.
Where: المفضلة · البحث المحفوظ · سجل المشاهدات
Your lean from the kickoff: separated, with small indicators.
Where: The seller’s ads list
Car ads and property ads have completely different columns (km/year vs rooms/m²).
Where: The dealer/office daily screen
The cockpit design is confirmed and works well — the question is how offices enter it.
Free ads, the coin wallet, office subscriptions, welcome gifts.
Where: Publish gates
Cars currently run the coin wallet (رصيد الإعلانات). The simplest property launch avoids coins entirely.
Where: رصيد الإعلانات
Follows F1: if property launches on a simple limit, the wallet question disappears for now.
Where: Business money
You decided pricing is separate. This confirms the shape.
Where: First-time grants
Today’s welcome gift fires once per account, ever.
The real-estate answer to showrooms.
Where: What «المعارض» is for cars
The showroom directory design is confirmed and works.
Where: The public office profile
Dealers live at /showroom/[uid] and their links are already shared around.
Where: The directory rows
Dealer rows show live make tallies («تويوتا 12 · نيسان 5») from the stock record.
Where: Admin
Showrooms apply and admin approves before they appear anywhere.
The app, alerts, where we build, share cards, the brand line.
Where: The (outdated) Flutter app — still live for car users
Your standing rule: the site leads, the app follows later.
Where: Saved searches
A finding from the scan: the SITE never registers for push — today alerts only reach the old app. That is true for cars too, not just property.
Where: Engineering approach
test.teswa.net shares the production database — there is no separate sandbox today.
Where: The image that shows when an ad link is shared
The card renderer can’t shape Arabic text; car cards solved it with English labels.
Where: Site description + the fallback share card
Today: «سوق السيارات الموثوق في الكويت» — wrong the day property exists.
Born from the 4-lens hunt after your challenge. Your first 36 stay locked exactly as decided.
Where: Ad details + filters + the nested lookups being built (B4)
Kuwait property is quoted by block — «سلوى ق5» — and land prices swing block by block. Cars stop at المنطقة. If the block is not structured data from day one, it rots as free text in titles and can never be backfilled for early ads.
Where: The ad page + the listing schema (geo is captured at creation or lost)
Property IS location; cars never needed geo, so the schema has no coordinates at all. Whatever is not captured at creation is permanently missing for every early ad. And exact pins on lived-in homes are a privacy question.
Where: The rent price model (B5) + filters + sorting
B5 locked rent display as د.ك/شهر — but شاليه and مزرعة rent by the day/weekend in Kuwait, and commercial is often quoted yearly. One number assumed monthly means two whole launch types cannot price honestly, and the rent filter compares 80/day against 350/month as equals.
Where: The create flow + price filters + sorting
Cars force a number. Kuwaiti sale culture runs on السوم — forcing a price gets junk numbers (1 or 999999) that poison filters; allowing no-price means those ads leave the price filter. A schema decision that cannot be retrofitted cleanly.
Where: Ad creation + the ad page + a buyer filter
«من المالك مباشرة» is the #1 buyer demand in Kuwaiti property — and with D3 removing badges, this is the only trust marker property has. It also protects office subscriptions from brokers riding the free indi track. Must exist at creation or the back-catalogue stays unlabeled forever.
Where: The listing schema + cap math + directory tallies (G3)
Offices advertise whole buildings; cars are strictly one-item-one-ad. All four hunt lenses flagged this. It decides whether caps count units or ads, what the stock-record tallies mean, and whether browse drowns in near-duplicates. Retrofit = schema surgery.
Where: The ad lifecycle + stats + «إعلاناتي»
In cars, sold is terminal — relist creates a NEW ad. A rental unit re-enters the market every year. Left unasked, «تم التأجير» inherits terminal semantics and landlords stop closing ads at all.
Where: Browse ordering + the property catalogues (A3/F3)
Bump is the heart of car money AND the browse ordering. Property moves slowly and is browsed by filters and area, not freshness — classic property portals sell FEATURED placement instead. A3/F3 gave property its own catalogues but never said which TOOLS live inside them.
Where: The free-limit model you chose in F1
F1 fixed the cap but not the clock. Car ads inherit their lifetime from a purchased package; a free property ad has no package — its expiry semantics are literally undefined. The day count is admin config; the MECHANISM is the decision.
Where: Publish flow + admin moderation
Cars publish instantly (only an automated photo check). Property fraud is heavier — phantom listings, deposit scams, fake brokers — D3 removed the badge, and H5 promises «الموثوق». The publish gate is the trust stance.
Where: Reports + ad freshness
Reports today land in a passive admin queue — nothing happens automatically. For property, calling about long-gone units is THE trust killer, and it scales with the market.
Where: The property vocabulary being built now (B4) + land/building search
The legal classification drives Kuwaiti land and building value and permitted use — it is the first question anyone asks about an أرض or عمارة. D1’s types and D2’s fields skip it. B4’s nested lookups are being rebuilt right now — the cheapest moment to add it.
Where: The غرض lookup being built now (B4) + browse separation
On Kuwaiti platforms, a big share of property ads are مطلوب — buyers and renters posting needs, brokers replying. B5 decided the OFFER side only. The answer shapes the غرض vocabulary being rebuilt right now.
Where: The areas model + brand + office review (G4)
International projects are heavily marketed to Kuwaitis and are real paying volume on local classifieds. The entire decided model assumes Kuwait (areas, URLs, «الموثوق في الكويت»). The first office asking to post Istanbul flats forces the answer — better to rule now.