# Competitive study — Filipino Homes admin / agent CRM surface

**Target:** https://filipinohomes.com/ (public Next.js site)
**Brokerage of record:** Leuterio Realty & Brokerage ("Leuterio Realty & Filipino Homes"), founded 2008 by Anthony Gerard "Tonton" Leuterio. HQ: 133F Aznar Road, Sambag 2, Urgello St., Cebu City.
**Method:** clean-room, public-data-only review — `robots.txt`, `sitemap.xml`, `llms.txt`, HTTP response headers (CSP), rendered HTML of public pages, app-store/press coverage via web search. No login, no credential submission, no authenticated routes were accessed. Everything under the disclosed `/admin/`, `/client/`, `/editor/`, `/dashboard/`, `/asa-gpt` paths was left untouched — their existence is noted from `robots.txt` only, contents are **not observed**.
**Date of capture:** 2026-07-11.

---

## 1. Admin surface overview

Filipino Homes is the *public storefront* of a much larger private operating system run by its brokerage, Leuterio Realty. The public Next.js app (`filipinohomes.com`, hosted on Vercel behind Cloudflare) exposes only consumer-facing pages (listings, agent directory, blogs, magazines). Everything an agent, team leader, or staff member would use to run the business lives behind a constellation of authenticated sub-systems, most of which sit on **separate hostnames with separate accounts**, not under one unified `/admin` panel:

| Sub-system | Host | Apparent purpose |
|---|---|---|
| Public site auth + agent/client login | `filipinohomes.com/login` | Shared entry point for buyers, renters, and agents |
| Protected app surfaces (disclosed, not crawled) | `filipinohomes.com/admin/`, `/dashboard/`, `/editor/`, `/client/`, `/asa-gpt` | Staff admin, agent dashboard, agent website builder, buyer/client portal, AI assistant |
| Core "CRM platform" / brokerage portal | `leuteriorealty.com` (`/login`, `/forgot-password`, `/business-card`) | Agent/broker account system, described by Leuterio Realty's own contest site as "our CRM platform" |
| Realtime chat/notification backend | `system.leuteriorealty.com` (Socket.IO, `wss://`) | Live chat / lead-messaging transport wired into the public site's CSP `connect-src` |
| Social-media contest platform | `contest.leuteriorealty.com` (`/auth/login`) | Gamified engagement tool for agents and "team leaders" tied to company events |
| Training / LMS | `realestatetraining.ph/login` ("FIRE") | Agent onboarding/continuing-education platform; explicitly a *separate* account system from Leuterio Realty, though it requires an existing Leuterio Realty account to register |
| API backends | `api2.filipinohomes.com`, `laravel.filipinohomes.com` | Laravel-based application APIs (whitelisted in CSP `form-action`) |

The picture is a **federated ecosystem of siloed logins** built around one brokerage identity, not a single consolidated CRM product — closer to how a large enterprise accretes internal tools over a decade (2008–present) than a modern unified admin.

---

## 2. Discovered entry points (real, public paths)

From `robots.txt` (identical block repeated for every declared user-agent, including AI crawlers):

```
Disallow: /admin/
Disallow: /client/
Disallow: /editor/
Disallow: /login
Disallow: /api/
Disallow: /_next/
Disallow: /dashboard/
Disallow: /cookies/
Disallow: /maintenance/
Disallow: /asa-gpt
```

From navigation, headers, and search-indexed pages (all fetched as plain public pages, no auth):

- `https://filipinohomes.com/login` — prerendered Next.js/MUI page. Observed form copy: **"Sign In / Email Address / Continue / OR / Continue with Google / By submitting, I accept Filipino Homes' Terms of use"**. No password field is visible in the prerendered markup — this reads as an email-first flow (magic-link/OTP and/or a second client-rendered step) plus a Google OAuth option (`accounts.google.com` is whitelisted in the CSP `form-action` and `frame-src`). One login screen appears to serve both client and agent accounts.
- `https://filipinohomes.com/agents` — public directory, "1,596 Real Estate Agents in the Philippines." Each card exposes **Message**, **View Profile**, and a **"My Page"** action — enabled only for agents who have published a page (most cards show a disabled "No page available" button), strongly suggesting **"My Page" is the published output of the `/editor` website builder**, gated behind adoption rather than a hard paywall.
- `https://filipinohomes.com/page/{agent-slug}` — an agent's published micro-site, e.g. `https://filipinohomes.com/page/kproperties` (Krystle Gayle Avila Tolentino / "KProperties"): agent bio, phone, "MESSAGE ME" CTA, full site chrome reused from the parent app. This is the public artifact of the agent website builder.
- `https://filipinohomes.com/page/agents` — "Agent Pages" hub, an aggregator/directory of agents who have published a "My Page."
- `https://filipinohomes.com/agents/{agent-slug}` — individual agent profile pages (e.g. `/agents/krystle-gayle-avila-tolentino-302`), distinct from the "My Page" microsite.
- `https://leuteriorealty.com/login`, `https://leuteriorealty.com/forgot-password` — standalone credentialed account system for the brokerage portal.
- `https://leuteriorealty.com/business-card` — "LR | Business Card" (title only observed; content not accessible via automated fetch — **not observed** beyond the page existing).
- `https://contest.leuteriorealty.com/`, `https://contest.leuteriorealty.com/auth/login` — social-media contest platform for agents/team leaders (live example seen in search index: "NATCON 2025 Reels Contest," Oct 19–30).
- `https://realestatetraining.ph/login` — "FIRE" training/LMS login, offering (a) email+password and (b) "Leuterio Realty Account" sign-in.
- `https://filipinohomes.com/p/join-us-/mKagoQ===/` — a search-engine-indexed recruitment landing page ("Join our Team of Highly Skilled and Top Performing Brokers and Real Estate Agents in Filipino Homes"). **No longer live** — as of capture date it 301/308-redirects to the homepage, so current recruitment funnel entry point is **not observed** directly (only via stale search index).
- Sanity-checked: nonexistent slugs return real `404`s, but slugs that collide with the location-search catch-all router (e.g. `/join`, `/system`) return `200` because they're silently absorbed as fake city/location searches ("Properties For Sale in Join") — a false-positive trap for path-guessing that is worth noting for our own catch-all routing design.

---

## 3. Role & account model (inferred from public signals)

- **Buyer / renter (client)** — no login required to browse, save, or message agents. A dedicated `/client/` path is disallowed in `robots.txt`, implying an authenticated client portal exists (post-inquiry tracking, saved searches, or transaction docs) — contents **not observed**.
- **Agent / broker** — PRC-licensed Real Estate Salesperson (RES) or Real Estate Broker (REB), "accredited" under Leuterio Realty. Site copy is explicit that listing/selling is **not open to the public**: *"Listing or selling a property isn't open to the general public — to post listings you join as an accredited agent under Leuterio Realty, the brokerage behind Filipino Homes."* Agents get a public profile, optional "My Page" microsite, and (inferred) access to `/dashboard/`, `/editor/`, `/asa-gpt`, and the `leuteriorealty.com` CRM.
- **Team leader** — a distinct tier above individual agents, evidenced by the contest platform's own copy: *"Team leaders can create their own contests through our CRM platform at leuteriorealty.com for their specific events and team activities."* Consistent with a multi-level agent-network structure (see §6).
- **Developer / project accounts** — the homepage's "Featured Developers" module (Cebuland Masters, Primary Homes, Sterlingland, Johndorf Ventures, Wee Community Devt., AppleOne Properties) and the `/projects` inventory imply a developer/project-management workflow feeding pre-selling listings, but no developer-facing login surface was discovered — **not observed**.
- **Staff/admin** — the `/admin/` path in `robots.txt` implies an internal operations panel (site content, moderation, listings QA) separate from the agent-facing `/dashboard/` — contents **not observed**.

---

## 4. Admin feature inventory (public-signal-derived; unverified items marked)

- **Listing management (post/edit)** — agents post and must "keep current" their own listings (site FAQ copy: *"Agents post their own listings, are required to keep them current, and are monitored for activity and responsiveness."*). Listing detail pages show region/office-linked identifiers — a sample agent-authored listing blurb includes a bare **listing code** ("code: JES"), consistent with the pre-existing research note about region-prefixed codes. **Bulk import/feed tooling: not observed** (inventory scale — 18 sitemap shards of listings — makes some bulk/CSV or MLS-style feed plausible but unconfirmed).
- **Media** — listing and profile images are served from a dedicated S3 bucket, `filipinohomes123.s3.ap-southeast-1.amazonaws.com` (whitelisted in CSP `object-src`/`frame-src`), implying a managed upload pipeline behind `/editor` or `/dashboard`. Upload UI itself **not observed**.
- **Agent website builder (`/editor`)** — disallowed path confirms existence. Its output is publicly visible: the `/page/{slug}` microsites (e.g. `/page/kproperties`), reused from the main site's design system (branded hero, bio, phone/CTA block, standard footer/nav). Adoption looks partial — most agent cards on `/agents` show "No page available."
- **AI assistant (`asa-gpt`)** — disallowed path (`/asa-gpt`) confirms an agent-facing AI tool exists, separate from the small public **"AI ON / OFF"** toggle visible on the homepage hero search (a consumer search-assist feature, not the agent tool). Per press coverage (not a primary Filipino Homes page, so marked **inferred**): Anthony Leuterio announced **ASA GPT**, described as "proprietary AI software designed to empower real estate agents in the Philippines by helping them communicate better, respond faster, and achieve bigger results," positioned alongside a planned secondary-market/MLS portal, "integrated with 135 offices nationwide and powered by 9 proprietary AI tools." Exact in-product capabilities (lead-reply drafting? listing description generation? chat routing?) are **not observed**.
- **Lead/client CRM & chat** — `system.leuteriorealty.com` is wired into the public site's CSP as a live `wss://` Socket.IO endpoint, i.e. the public "Message" buttons on agent cards and listing pages likely stream into the same realtime backend the CRM/dashboard uses. This is the clearest evidence of one shared messaging substrate spanning public site and internal CRM.
- **Analytics** — listing pages show public view counters ("1,551 Views," "17 views" on agent cards) — a lightweight, publicly surfaced popularity metric. Deeper agent-facing analytics (lead conversion, response-time SLAs) **not observed**, though the FAQ claim that agents are "monitored for activity and responsiveness" implies internal analytics/scoring exists.
- **Agent recruitment/network/downlines** — see §6. A "team leader" role, a "co-agent" support model, and a stale-but-indexed `/p/join-us-/...` recruitment landing page were found. Formal downline/sub-agent hierarchy tooling **not observed** directly.
- **Commission/earnings** — commission structure is **not observed** on any public page (site FAQ only states buyers/renters never pay agent commission — seller/landlord side pays). A third-party-hosted "Leuterio Realty Partnership Handbook" (Scribd) surfaced in search results but was not fetched (out of scope / not a primary Filipino Homes property).
- **Verification/moderation** — every agent is stated to be PRC-licensed and "verified through our network"; buyers are told they can independently cross-check via the PRC website (RES/REB lookup). Internal verification/moderation tooling **not observed**.
- **Notifications/chat** — see CRM row above; `wss://system.leuteriorealty.com` is the shared transport.
- **Training / continuing education** — `realestatetraining.ph` ("FIRE") is a distinct LMS product, requiring (but not identical to) a Leuterio Realty account.
- **Gamification / social contests** — `contest.leuteriorealty.com`, run "through our CRM platform," lets team leaders spin up event-tied social-media contests for their agents.

---

## 5. Implementation & tech

- **Public frontend:** Next.js App Router (RSC headers: `vary: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch`; `x-nextjs-prerender: 1`), deployed on **Vercel** (`x-vercel-cache`, `x-vercel-id`) and fronted by **Cloudflare** (`server: cloudflare`, `cf-ray`, Cloudflare NEL reporting). UI is built on **Material UI (MUI)** — atomic `mui-*` class names and MUI component markup throughout (`AppBar`, `OutlinedInput`, etc.).
- **Backends:** two Laravel-family API hosts allowed in `form-action` — `api2.filipinohomes.com` and `laravel.filipinohomes.com`. Auth also federates to **Google OAuth** (`accounts.google.com` / `apis.google.com` allowed for script and frame).
- **Realtime layer:** `system.leuteriorealty.com` over `wss://`/`https://`, explicitly named in the CSP `connect-src` — a **shared Socket.IO-style chat/notification backend** spanning the public site and (inferred) the internal CRM/dashboard.
- **Media storage:** AWS S3, `filipinohomes123.s3.ap-southeast-1.amazonaws.com`, ap-southeast-1 (Singapore) region.
- **Third-party integrations visible in CSP:** Google Tag Manager/Analytics, Google Maps, YouTube, Cloudflare Insights, TikTok/Instagram/Facebook embeds.
- **AI-crawler policy:** the site explicitly serves `llms.txt` and `llms-full.txt` (Creative Commons BY 4.0 licensed content summaries for AI grounding) — a deliberate, current (2026) SEO/AEO strategy — while simultaneously blocking the same AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) from the admin/CRM/editor/AI-assistant paths. This is a clean split: *market the public catalog to AI answer engines, keep the operating system private.*

---

## 6. The agent-network operating model

Filipino Homes/Leuterio Realty runs on a classic large-brokerage **agent-network** model, not a marketplace of independent listers:

- **Gatekept posting** — only PRC-licensed, Leuterio-Realty-accredited agents can list; the public is explicitly excluded ("Listing or selling a property isn't open to the general public").
- **Branch/office backbone** — `llms.txt` states **63 physical branch offices nationwide** (Cebu HQ); a separate press description (via search, **inferred**, not fetched from a primary source) cites **135 offices**. Both numbers are cited as observed/reported without reconciling the discrepancy. Listing pages surface a **"Nearby Filipino Homes Office"** module that geolocates the closest branch to a given property (distance in km), tying every listing back to a physical office.
- **Co-agent support** — 2019 app-launch coverage (Sunstar/Philstar, **inferred** — press, not primary) describes a "three-sided model where agents can help agents, buyers can choose their preferred agents on the listing, and agents can look for buyers and ask support from their co-agents" — i.e. built-in agent-to-agent referral/support baked into the original mobile app.
- **Team-leader tier** — the contest platform explicitly differentiates "team leaders," who get CRM-level contest-creation rights beyond a rank-and-file agent — evidence of a hierarchical (team/branch lead → agents) structure typical of PH real-estate "network marketing"-style brokerages.
- **Recruitment funnel** — historically a dedicated landing page (`/p/join-us-/mKagoQ===/`, now redirecting to home) advertised open recruiting with concrete eligibility gates (Filipino citizen, ≥72 college units, computer-literate, willing to attend online training/webinars, submit NBI clearance + transcript of records) — sourced from search-engine-cached copy, **inferred**, not currently live.
- **Separate-but-linked tool silos** — CRM (`leuteriorealty.com`), training/LMS (`realestatetraining.ph`, requires but is distinct from the CRM account), and social contests (`contest.leuteriorealty.com`, built "through" the CRM) form a loosely federated back-office stack agents must learn piecemeal — this looks like organic growth over ~15+ years rather than a single platform team's product.
- **AI as the new differentiator** — ASA GPT (agent-facing) is being positioned (per secondary coverage) as the unifying "give every agent superpowers" layer on top of this fragmented back office, rather than a UI consolidation.

---

## 7. Takeaways for property-portal's future admin/CMS

1. **Ship the agent "My Page" pattern early, but gate it behind an editor, not a required feature.** Filipino Homes' partial adoption (most agents show "No page available") shows a lightweight, opt-in personal micro-site (`/page/{slug}`) reusing the main design system is low-cost to build and high perceived value, but doesn't need to block MVP — a simple template-driven landing page (bio, phone, CTA, listing list) captures most of the value seen here.
2. **Put one realtime channel behind everything.** Filipino Homes' single Socket.IO backend (`system.leuteriorealty.com`) serves both public "Message agent" buttons and (inferred) the internal CRM — i.e. lead messaging and internal notifications share one pipe. For our CMS, design the lead/chat transport once and reuse it for buyer↔agent messaging, agent↔admin notifications, and future AI-assist hooks, rather than bolting on separate systems later.
3. **Treat "AI assistant for agents" as a lead-response tool, not a chatbot gimmick.** ASA GPT's stated pitch — help agents "communicate better, respond faster" — targets the highest-leverage admin pain point (lead response time), not novelty search. If we build an AI feature into our future admin, prioritize draft-reply/lead-triage assistance for agents over consumer-facing chat.
4. **Avoid Filipino Homes' tool fragmentation.** Their CRM, LMS, and contest platform are three separate logins loosely federated ("you must register separately for FIRE" even with a CRM account). For a from-scratch build, a single admin identity with role-scoped modules (listings, leads, training, gamification) is materially better UX and should be an explicit design constraint, not an afterthought.
5. **Region/office attribution is a real differentiator worth copying at small scale.** The "Nearby Filipino Homes Office" module and office-prefixed listing codes tie every listing to a physical branch and searchable distance — useful for trust-building in a market where physical presence matters. A lightweight "nearest office/agent" widget is cheap to build and reinforces legitimacy.
6. **Design the public/admin boundary the same way: disallow, don't obscure.** Filipino Homes cleanly declares its private surfaces in `robots.txt` (`/admin/`, `/dashboard/`, `/editor/`, `/client/`, `/asa-gpt`) for every crawler including AI bots, while simultaneously publishing `llms.txt`/`llms-full.txt` to court AI answer engines on the public catalog. Adopt the same explicit split for our own future admin/CMS: clear `robots.txt` disallow rules plus a curated `llms.txt` for the public listing catalog, so we control AI-engine visibility deliberately rather than by accident.

---

## Admin matrix row

| Roles | Admin entry points | Listing mgmt (bulk/feed?) | Lead CRM | Analytics | Promotion/boost admin | Billing/credits | Team/brokerage mgmt | Developer/project mgmt | Verification/moderation | White-label CRM product | Tech/implementation | Standout admin capability |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Buyer/renter (client, no login needed to browse); Agent/broker (PRC-licensed, accredited); Team leader; Staff/admin (inferred); Developer/project accounts (inferred) | `filipinohomes.com/login` (public, email+Google OAuth); `filipinohomes.com/dashboard/`, `/editor/`, `/client/`, `/admin/`, `/asa-gpt` (disclosed via robots.txt, not observed); `leuteriorealty.com/login` (CRM); `contest.leuteriorealty.com/auth/login`; `realestatetraining.ph/login` (FIRE) | Agents post/maintain own listings (confirmed); bulk/feed tooling not observed | `system.leuteriorealty.com` realtime Socket.IO backend shared with public "Message" feature; CRM described as living at `leuteriorealty.com` | Public view counters on listings/agent cards observed; internal analytics not observed (implied by "monitored for activity and responsiveness") | Not observed | Not observed (commission model referenced but not detailed) | Team-leader tier confirmed via contest platform copy; 63 (llms.txt) vs. 135 (secondary press, inferred) branch offices; "Nearby Office" locator module on listings | Featured-developer/project inventory (`/projects`) exists; no developer login surface observed | Agents stated PRC-licensed/verified; public PRC self-verification suggested; internal moderation tooling not observed | `leuteriorealty.com` self-described as "our CRM platform"; not offered to outside brokerages as white-label (not observed) | Next.js (App Router, RSC) on Vercel + Cloudflare; MUI component library; Laravel backends (`api2.filipinohomes.com`, `laravel.filipinohomes.com`); S3 media (`filipinohomes123.s3.ap-southeast-1.amazonaws.com`); Google OAuth | ASA GPT — brokerage-wide AI assistant for agent communication/response speed (per secondary coverage), paired with agent-built micro-sites (`/page/{slug}`) as the public face of the `/editor` website builder |