# OnePropertee — Admin / Seller Back-Office Teardown

Clean-room research on [onepropertee.com](https://onepropertee.com/)'s **admin / seller back-office surface**,
conducted 2026-07-11, to inform the future admin/CMS and matching-ops roadmap of `property-portal` (bilingual
JP/EN PH real-estate demo). This is a companion to the consumer-facing teardown at
`docs/research/onepropertee.md` (same repo) — tech-stack facts already confirmed there (Meteor.js, AWS
CloudFront/WAF, auth methods, "One Partnership" 50/50 framing) are cross-referenced rather than re-derived.
Facts are observed directly; inferences are marked `(inferred)`; anything not found is marked `not observed`.

**Methodology note.** `onepropertee.com` sits behind an AWS WAF JS bot-challenge (`HTTP 202`,
`x-amzn-waf-action: challenge`) that blocks non-browser HTTP clients, and its `robots.txt` explicitly disallows
`ClaudeBot`/`anthropic-ai`/`Claude-Web` (confirmed in the sibling consumer report, §6). WebFetch attempts against
`onepropertee.com/help/*` and `/pricing` in this session consistently returned empty page bodies for the same
reason. No login, account creation, credential submission, or WAF bypass was attempted. All findings below are
therefore sourced from **WebSearch** (which surfaces Google's indexed cache/snippets of OnePropertee's own public
help-center articles, community forum, and pricing page) and from **public, non-authenticated pages** (app-store
listings). No protected/logged-in admin screen was directly viewed; the "Property Hub" seller console itself sits
behind login and was reconstructed only from what its own help articles describe.

---

## 1. Admin surface overview

OnePropertee's back-office is two distinct layers:

1. **Self-serve seller/agent console ("Property Hub")** — reached after login, where an individual seller,
   agent, or PRC-licensed broker posts listings, manages a Leads CRM, buys promotion (Boost / Lead Boost Direct),
   and tracks LeadCoins credit balance. Functionally this is the demo-relevant "admin" surface for
   `property-portal`.
2. **Internal "Buyer Assistance" matching operation** — a centralized team of OnePropertee-employed staff (RESA
   1RA9646-licensed, per the sibling report's pricing-page reading) who qualify inbound buyer intent and
   endorse/route buyers to sellers, either organically or through the contractual **"One Partnership"**
   commission-share program. This layer is not self-serve; sellers interact with it as a black box (a named
   "Buyer Assistance Officer" persona handles inquiries) and as a counterparty on a signed referral contract, not
   as a configurable admin panel.

There is no evidence of a third, "super-admin"/CMS-editorial layer (e.g., for moderating all listings platform-
wide, managing homepage content, or a white-label back-office product) in any public material — see §4.

## 2. Discovered entry points

All real, publicly reachable URLs found (none required auth to discover; several require login to use further):

- `https://onepropertee.com/login` — unified login for buyers, sellers, brokers (mobile number/email +
  passwordless, WebAuthn passkey, Google/Facebook OAuth — confirmed in sibling report §2)
- `https://onepropertee.com/pricing` — public plan comparison (Free Seller Account vs. One Partnership)
- `https://onepropertee.com/install-app` and `.../download-onepropertee-app-now-topic` — app install funnel
- `https://onepropertee.com/dashboard/help/support` — in-dashboard support/contact form (URL pattern confirms a
  `/dashboard/*` authenticated route namespace exists, though its structure beyond `/help/support` is
  `not observed`)
- `https://onepropertee.com/help/*` — a large public help center, "Selling Properties on OnePropertee" and
  "Buying Properties on OnePropertee" categories, e.g. `/help/how-can-i-post-a-property/SYTtgpYTjpX6eGxhS`,
  `/help/what-is-buyer-assistance/mkPqcb4AdEMpE9brx`, `/help/seller` (a "Selling Properties Questions and
  Answers" index page)
- `https://onepropertee.com/group/self-help-for-real-estate-professionals/XLQxwJsPTr58SazWY/2` — a public
  community forum specifically for licensing/CPD/PRC-process education, plus individually slugged `*-topic`
  posts, e.g. `/online-verification-of-license-with-professional-regulation-commission-topic`,
  `/mandatory-compliance-authority-negotiate-sale-topic`, `/comprehensive-guide-using-leads-crm-onepropertee-topic`
- `https://onepropertee.com/developer/sm-development-corporation-smdc/4i2ktpAEjceNvkhZ8` and
  `https://onepropertee.com/sellers-hub-filinvest` — public per-developer aggregation/landing pages showing live
  project/property counts (this is **OnePropertee's own page about a developer**, not a developer's private
  admin tool — see the important distinction flagged in §4)
- App-store listings (public, unauthenticated): Google Play `id=com.onepropertee.app`, Apple App Store
  `id1471478178`, Microsoft Store `9nt0fdc1t9pb` — all published by developer **"Innovation Love, Inc."**

No `/admin`, `/backoffice`, `/cms`, `/staff`, or similar internal-tooling path was found or searched-for
successfully — such a surface, if it exists, is not indexed/public, consistent with it being internal-only
`(inferred)`.

## 3. Role & account model

- **Buyer / "Principal Buyer."** A help article (`/help/what-is-a-principal-buyer/...`) explicitly defines
  "Principal Buyer" as a distinct concept in OnePropertee's buyer taxonomy — the buyer who is the primary party
  to a transaction, as distinct from e.g. a referred/secondary buyer contact `(article content beyond the
  definition itself: not observed)`.
- **Seller — Free Seller Account.** Default role for anyone posting a listing. Requires mobile-number
  verification before the first post goes live (per `/help/how-can-i-post-a-property/...`). No PRC-license
  requirement to hold this tier.
  Sellers/agents can act with a **single-listing** posting flow. The tier is described as ILS
  "unlimited listings, unlimited Free Refresh, unlimited free leads, free Buyers CRM, free auto-generated
  property video ad, free professional online business card, free seller website" (cross-confirmed against the
  sibling consumer report's `/pricing` reading).
- **Broker/Partner — "One Partnership."** A paid-nothing-upfront but commission-shared tier explicitly gated to
  **licensed PRC brokers** ("Licensed Brokers Only" — confirmed as a public search-filter toggle in the sibling
  report §4, and framed around RESA9646 compliance). Enrollment is formalized via a **signed contract** — see
  §4/§6 — making "Partner" a distinct, contractually-bound account state, not just a UI toggle.
- **Developer.** A separate role/product surface: "Project and Inventory Pages for Developers (Beta)" is named
  explicitly in the app-store feature list (Google Play/App Store listings for `com.onepropertee.app`), and
  distinct public per-developer pages exist (`/developer/<slug>/<id>`) showing live per-developer project/unit
  counts. Whether this is a self-serve developer login role or an OnePropertee-managed aggregation of
  third-party developer inventory is **not confirmed either way** — flagged `(inferred: likely a hybrid — some
  developers self-manage via the Beta feature, others are aggregated/listed by OnePropertee without their own
  login)`.
- **Internal OnePropertee staff — "Buyer Assistance Officer."** Public profile-style pages exist for individual
  staff members acting as the human face of the matching operation, e.g. `onepropertee.com/charly-onepropertee`
  ("Charly OnePropertee — Buyer Assistance Officer") and an inquiry-form persona "Lanie OnePropertee" (per the
  sibling report's listing-detail observation). These are OnePropertee employees, not marketplace sellers, but
  they hold outward-facing "agent-like" profile pages — an internal-ops role made publicly visible as UX design.
- **Verification model.** "Verified" appears to mean *claimed/confirmed profile ownership*, not independently
  confirmed active PRC licensure — OnePropertee's own community content explicitly directs professionals to the
  **government's** PRC LERIS portal (`verification.prc.gov.ph`) for authoritative license-validity checks, rather
  than performing in-house automated verification `(inferred from help/community content emphasis — no
  in-house verification API or process was described)`.

## 4. Admin feature inventory

**Listing management (post/edit, unlimited free).**
Single-property "Post for Free" wizard: mobile-number verification gate → property-details form with a
structured amenities list (e.g. Swimming Pool, Club House) and features list (e.g. Car Parking, Security
Services) with an "add custom" escape hatch → submit → goes live immediately. No bulk-upload/CSV/feed-import
mechanism was found in help docs — `not observed`, despite the existence of "Project and Inventory Pages for
Developers (Beta)" suggesting *some* multi-unit inventory surface exists for developer accounts specifically.
Sellers manage all posted listings from the **"Property Hub"** — described as tracking which properties "need
action" (Refresh, Boost) and running a **property scoring system** that flags "active, non-boosted properties
… ideal for boosting" based on direct-inquiry-completion potential.

**Media.** 360 Photos, an auto-generated property video ad, and auto-generated social-media/Property E-Flyer
images are produced *for* the seller from listing data — a content-generation feature layered on top of plain
photo/video upload, not just a gallery manager.

**Buyer-request / matching operations (how sellers receive matched buyers).** See §6 for the full mechanic.
Sellers receive matched buyers via two paid/unpaid channels documented in help articles: an algorithmic
**"Leads Matching Plan"** (paid packages; buyers "received instantly" on payment confirmation "subject to
availability," plus more "within X days" based on market-trend data — price/location/type variables named
explicitly) and the contractual **"One Partnership"** program (commission-shared, see §6).

**Lead/inquiry handling.** A **"Leads CRM"** is the seller's primary lead-management screen: leads shown with
name, source, and status at a glance; statuses include auto-applied **"New"** (on receipt) and **"Replied"** (on
seller reply), sortable by status and by source (**Free**, **Paid Inquiry**, **Lead Boost Direct**). **Free vs.
Paid Direct Inquiry**: sellers get full lead details free up to a limit; beyond that, unlocking a direct
inquiry's full contact details costs **LeadCoins** (in-app credit currency). **LeadMail** and "Property Update
for Lead Nurturing" are named as separate email-based lead-nurture features.

**Analytics / views.** Narrower than a typical view-counter dashboard: the only analytics artifact documented
is the **"boosted property promotions graph,"** shown per-boosted-listing, breaking impressions into three
counted channels — **Search** (top-of-related-search placement), **Featured** (shown alongside similar
properties to targeted leads), **Email** (shown in emails *actually opened* by targeted leads — unopened emails
are explicitly excluded from the count). No general page-view counter, funnel/conversion dashboard, or
platform-wide analytics surface for sellers was found — `not observed` beyond boost-specific metrics.

**Promotion management (boost/feature).** Confirmed to exist, structured around two tiers: **Free Refresh**
(unlimited, unpaid — bumps a listing back toward the top of results) and **Lead Boost Direct** (paid — a
package purchase that promotes a listing until a chosen *number of guaranteed leads* has been delivered, not
just a fixed time window; guaranteed leads land in the Leads CRM tagged with a "Lead Boost Direct" source
label). Boost purchases can be paid for at a discount using **LeadCoins** instead of cash.

**Billing / commission.** Multiple monetary/credit mechanisms coexist: **LeadCoins** (a purchasable, shareable
in-app credit — a "Free Credits" sharing feature lets users gift credits to other users), a **"LeadCoins
Subscription Plan and Packages"** (named in a February-2025-dated help update, pricing itself `not observed`),
paid **Leads Matching Plan** packages, and — layered on top of all of this — **commission-based billing** under
the One Partnership / One-Away Deal contracts (§6). This is a materially richer monetization stack than a
simple "boost credit" system: transactional (LeadCoins spend), subscription (LeadCoins plan), and
commission-on-close (One Partnership) models all run concurrently.

**Team / brokerage management.** **Not observed.** No help article, forum post, or app-store feature description
describing multi-seat/sub-agent account management (e.g., a broker inviting salespersons under their own
account, shared team lead pools, or role-based permissions within a brokerage) was found. The "PARTNER" party in
the One Partnership Referral Program Agreement (§6) appears to be a single contracting entity (an individual
broker or a brokerage firm, ambiguous which), with no documented internal team-seat UI.

**Developer / project management.** "Project and Inventory Pages for Developers (Beta)" is a named, confirmed
app feature (both Google Play and Apple App Store listings), implying a distinct multi-unit/project inventory
surface for developer accounts, structurally different from a single-listing seller flow. Separately,
**important distinction**: a public page titled "Sellers Hub Filinvest" exists *on onepropertee.com*
(`/sellers-hub-filinvest`), but Filinvest also operates its own, entirely separate "Sellers' Hub" mobile app
(`com.filinvest.sellershub`, `kiosk.filinvest.com.ph`) — a third-party developer's own internal sales-kiosk tool,
unrelated to OnePropertee's platform. The two should not be conflated; OnePropertee's page is a
listings-aggregation/landing page about Filinvest inventory, not evidence that Filinvest manages listings
through OnePropertee's own developer admin tooling `(inferred distinction — not directly confirmed either way
from public docs)`.

**Verification / moderation.** Mobile-number verification is a hard gate before a seller's first listing goes
live. The **"Licensed Brokers Only"** designation gates access to the One Partnership commission-share tier and
is user-facing as a public search filter (confirmed in the sibling report). OnePropertee's own community content
(`/online-verification-of-license-with-professional-regulation-commission-topic`) points professionals at the
**government** PRC LERIS portal for authoritative verification rather than describing an in-house automated
check — consistent with "Verified" meaning claimed-profile confirmation, not license validation, per §3. No
listing-level moderation/flagging/duplicate-detection workflow (report-a-listing, admin takedown queue, etc.) was
found in public docs — `not observed`.

**Notifications (OneSignal push).** OneSignal's web-push SDK is confirmed loaded on the consumer site (per the
sibling report's DOM/script scan: `cdn.onesignal.com/sdks/OneSignalSDK.js`), consistent with push notifications
being used for lead/inquiry alerts. A help article "Notification for Inquiries" and a "Why am I not receiving
any emails from OnePropertee?" troubleshooting article confirm a parallel email notification channel. Sellers
can also register alternate **contact channels** (e.g., adding a **Viber** number under "Other Contact
Channels" in Account settings) so that buyers see a click-to-open-Viber option on the seller's contact card —
a lead-routing/notification-adjacent feature rather than an admin-notification setting per se.

**White-label CRM product.** **Not observed.** No evidence found that OnePropertee licenses/resells its Property
Hub, Leads CRM, or matching engine as a standalone branded product to third parties (contrast with, e.g., a
dedicated brokerage-CRM SaaS vendor).

## 5. Implementation & tech

Cross-referenced from the sibling consumer teardown (independently confirmed there via interactive browser
DOM/network inspection, not re-derived here):

- **App framework: Meteor.js**, confirmed via `window.__meteor_runtime_config__` / `__bootstrap_data__` /
  `ReactiveVar` globals and a `?meteor_js_resource=true`-tagged JS bundle. No REST/GraphQL `/api/*` traffic was
  observed on the consumer site; the data layer is inferred to be Meteor's DDP/WebSocket protocol, which would
  extend to the authenticated Property Hub/Leads CRM screens too `(inferred — dashboard screens themselves were
  not inspected, since login was out of scope)`.
- **Edge/security:** AWS CloudFront + AWS WAF with a JS bot-challenge in front of the entire domain, including
  presumably the `/dashboard/*` and `/login` routes.
- **PWA + native app:** installable PWA (`manifest.json`, service worker) plus native apps on Google Play
  (`com.onepropertee.app`), Apple App Store (`id1471478178`), and Microsoft Store (`9nt0fdc1t9pb`), all published
  by **Innovation Love, Inc.** (company confirmed via WebSearch to be co-founded by Arianne David and RJ David,
  the same team behind Sulit.com.ph/Carousell Philippines).
- **Auth for the admin surface:** mobile number or email passwordless flow, WebAuthn passkey login, per-device
  biometric enrollment (separate help articles exist for *adding*, *using*, and *removing* a biometric device),
  with an explicit **fallback to a regular password** ("Use Regular Password" button on the login page) — i.e.
  password auth still exists as a fallback path even though it's not the primary flow, plus Google/Facebook
  OAuth. This same login gate presumably fronts both buyer and seller/broker/developer roles (no separate
  admin-specific login URL was found).
- **Notifications infra:** OneSignal (push), plus a conventional transactional-email pipeline (LeadMail,
  inquiry-reply emails) and Viber deep-linking for contact routing.

## 6. How the matching operation works from the seller side

The seller-facing surface (Property Hub / Leads CRM) treats "Buyer Assistance" and "One Partnership" leads as
just another lead **source label** — but behind that label sits a real ops-and-legal pipeline, reconstructed
from help articles as follows:

1. A buyer completes the free **Buyer Assistance Form**, submitting a needs/budget profile (see the "Principal
   Buyer" concept, §3).
2. OnePropertee's own RESA-licensed, in-house brokerage staff — publicly represented by named
   **"Buyer Assistance Officer"** personas (e.g. "Charly OnePropertee," "Lanie OnePropertee") — qualify the
   buyer. A **"Qualified Referral"** is the resulting artifact: an umbrella term for "Standard" and "Premium"
   referral tiers, defined as leads that have "undergone a thorough evaluation process" for buying capacity,
   interest, and readiness to transact.
3. Matched/qualified buyers are delivered to sellers through one of two tracks:
   - **Leads Matching Plan (paid, non-contractual):** a straight package purchase; some leads arrive "instantly"
     on payment confirmation "subject to availability," others "within X days," calculated from market-trend
     data (price/location/type).
   - **One Partnership (contractual, commission-share):** formalized by signing a **"One Partnership Referral
     Program Broker Agreement"** directly with **Innovation Love, Inc. ("ILI")**. Key terms found: **1-year
     term** from the Effective Date; **non-exclusive** on both sides (either party can run equivalent programs
     with others); explicitly **not** a legal partnership/JV ("Nothing in this Agreement shall be deemed to
     constitute… a partnership, joint venture, or any… fiduciary… relationship") despite the "Partnership"
     branding; the PARTNER must self-report sales made to Buyer-Users and pay amounts due on time, with
     **1.0%/month interest on late/short payment**, and ILI may suspend the partnership after **two written
     reminders plus one prior warning** for non-compliance.
4. Commission economics on a closed deal vary by structure — two documented variants:
   - General "One Partnership" framing (per the sibling report's `/pricing` read): **50/50** commission share
     between OnePropertee and the partner broker on OnePropertee-sourced, pre-qualified leads.
   - A specific **"One-Away Deal"** variant (used when the closing party isn't the direct seller but holds a
     signed **Authority to Sell, ATS**): **40% OnePropertee / 20% referring broker / 40% authorized seller**.
   - A further named tier, **"One Partnership Commission Plus,"** exists as its own help article, but its exact
     split was **not observed** (WebFetch blocked, and WebSearch snippets did not surface the percentages).
5. From the seller's Property Hub, all of this ops/legal machinery is abstracted down to: a lead appears in the
   Leads CRM tagged by source, a signed contract governs the money owed on the ones sourced via One Partnership,
   and OnePropertee enforces payment compliance contractually (interest + suspension) rather than through an
   in-app billing/escrow mechanism `(inferred — no in-app payment-collection or escrow feature was found; the
   Agreement text implies payment is tracked/reported and enforced off-platform via the contract)`.

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

Prioritized, most relevant to our saved-search/matching feature first:

1. **Build an internal "buyer-intent triage" concept, not just a saved-search feed.** OnePropertee's most
   distinctive *admin*-side idea isn't a seller feature at all — it's that buyer intent funnels into an
   internal ops queue (named human personas qualify and route it) before it ever reaches a seller. For our CMS
   roadmap, consider a lightweight "match queue" admin view: incoming buyer requests/saved-searches shown
   alongside candidate listings with a manual "route to seller" action — even mocked with static data, this
   gives the admin surface a matching-ops story instead of being a plain listings CRUD panel.
2. **Model commission/referral as its own ledger object, separate from listings and leads.** The One-Away Deal
   (40/20/40) and One Partnership (50/50) splits show that "who gets paid what" is a first-class data model, not
   a side effect of a lead record. Even for a demo, a `Deal`/`Commission` entity (parties, split percentages,
   status, source: direct/matched/referred) would let a future admin/CMS demo a partner-broker or referral
   story convincingly.
3. **Give the Leads CRM auto-transitioning statuses and source attribution, not free-text notes.** "New" and
   "Replied" auto-apply on system events (lead received / seller replies); leads are filterable by source (Free
   / Paid / Boost / Referral). This is a cheap, concrete pattern to copy for our own admin lead/inquiry view.
4. **Separate "free unlimited bump" from "paid guaranteed-outcome boost" as two distinct promotion primitives.**
   Free Refresh (unlimited, unpaid visibility bump) vs. Lead Boost Direct (pay for N *guaranteed leads*, not
   just impressions) is a sharper monetization story than a single generic "Boost" button — worth reflecting in
   any future promotion/CMS admin design, even as a mocked feature.
5. **Route verification outward to the authoritative registry instead of building an in-house verifier.**
   OnePropertee's "Verified" badge appears to mean claimed-profile confirmation only, paired with educational
   content that sends professionals to the government PRC LERIS portal for real license validation. This is a
   low-cost, defensible pattern for any "verified agent" badge our demo/CMS might want to show.
6. **Keep "developer/project" as its own future account type, not an extension of the seller role.** The
   "Project and Inventory Pages for Developers (Beta)" naming and separate per-developer aggregation pages
   suggest OnePropertee treats multi-unit developer inventory as a distinct product surface. If `property-portal`
   ever adds bulk/multi-unit listings (e.g. a "development project" concept), model it as its own role/entity
   from the start rather than retrofitting the single-listing seller flow.

---

## 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
Roles: Buyer/"Principal Buyer"; Seller (Free Seller Account, mobile-verified); Broker/Partner (PRC-licensed, gated into "One Partnership" via signed contract); Developer ("Project and Inventory Pages for Developers," Beta); internal OnePropertee staff acting as public "Buyer Assistance Officer" personas
Admin entry points: `/login` (mobile/email passwordless + WebAuthn passkey + Google/Facebook OAuth, password fallback); `/dashboard/help/support`; login-gated "Property Hub" seller console (URL not observed); public `/pricing`; public help center at `/help/*`; public community forum (`/group/self-help-for-real-estate-professionals/...`, `*-topic` posts)
Listing mgmt (bulk/feed?): Single-listing "Post for Free" wizard confirmed (mobile-verify → structured amenities/features form → submit → live immediately); no CSV/feed/bulk-import mechanism found — not observed, despite a named developer multi-unit feature existing separately
Lead CRM: Yes — "Leads CRM" with auto-applied statuses (New on receipt, Replied on seller reply, others unenumerated), filterable by status and by source (Free / Paid Inquiry / Lead Boost Direct)
Analytics: Narrow — only a per-boosted-listing "promotions graph" (Search / Featured / Email impression counts, opened-email-only); no general view-counter or funnel dashboard found — not observed beyond boost metrics
Promotion/boost admin: Yes — Property Hub "Boost" button; Free Refresh (unlimited, unpaid bump); Lead Boost Direct (paid, guaranteed-lead-count packages, payable in cash or LeadCoins); a property-scoring system flags "boost-worthy" listings
Billing/credits: LeadCoins (purchasable/shareable in-app credit); "LeadCoins Subscription Plan and Packages"; paid "Leads Matching Plan" packages; plus contractual commission billing under One Partnership (self-reported sales, 1.0%/month late-interest, suspension after warnings) — pricing amounts largely not observed
Team/brokerage mgmt: Not observed — no multi-seat/sub-agent or role-based team management feature found in public docs; "PARTNER" in the referral contract is a single contracting entity of unclear (individual vs. firm) scope
Developer/project mgmt: "Project and Inventory Pages for Developers (Beta)" confirmed by name (app-store listings); public per-developer aggregation pages exist (`/developer/<slug>/<id>`, `/sellers-hub-filinvest`) — but note Filinvest's own separate "Sellers' Hub" app (`com.filinvest.sellershub`) is an unrelated third-party tool, not OnePropertee admin tooling
Verification/moderation: Mobile-number verification gates first listing; "Licensed Brokers Only" gates the One Partnership tier (RESA9646-framed); own community content directs professionals to the government PRC LERIS portal rather than describing in-house verification; no listing-level flag/moderation/takedown workflow found — not observed
White-label CRM product: Not observed — no evidence the Property Hub/Leads CRM/matching engine is licensed or resold to third parties
Tech/implementation: Meteor.js (DDP/WebSocket data layer inferred, no REST/GraphQL traffic observed) behind AWS CloudFront + AWS WAF JS challenge; installable PWA plus native apps (Google Play `com.onepropertee.app`, App Store `id1471478178`, Microsoft Store `9nt0fdc1t9pb`) published by Innovation Love, Inc.; OneSignal push + email (LeadMail) + Viber contact-channel routing; passwordless/passkey/per-device-biometric login with password fallback and Google/Facebook OAuth
Standout admin capability: The matching operation is backed by a real signed commercial contract layer — a 1-year, non-exclusive "One Partnership Referral Program Broker Agreement" between Innovation Love, Inc. and each broker/brokerage partner, explicitly disclaiming legal-partnership/JV status, governing self-reported sales, commission remittance, 1.0%/month late-interest, and suspension-after-warning enforcement — turning "buyer matching" from a lead-routing feature into a full broker-agreement + commission-ledger + arrears-enforcement back office