Clients & serious prospects

From 05_CLIENT_PROJECT_REGISTRY · last updated 2026-09-02. This is the complete list — no other client or prospect is confirmed in the new Agency OS yet.

PropCRM
SERIOUS PROSPECTREPORTED — REQUIRES VERIFICATION
Sales/client opportunity (Nazem-confirmed: not a formal partnership, despite the meeting title). Originated via LinkedIn outreach.

Verified contact: Salim Alberkdar, salim@propcrm.com
Verified timeline: 2026-08-04 partnership-discussion call held & accepted · 2026-08-17 WhatsApp AI lead-capture demo sent (testing guide + PDF) · 2026-08-18 Meta/Facebook Developer app switched to live mode.

Current status: No reply found in Gmail through 2026-08-31. Salim reported on vacation, conversation expected to resume after 2026-09-10. No follow-up sent after the demo — flagged as potentially overdue.
Father's Company
CONFIRMEDCLIENT
Real production engagement — Nazem's father's company, a family-business relationship rather than an external sales prospect. Nazem is the direct technical point of contact, building by hand in UiPath Studio (Claude Code intentionally not used for this project).

Project: UiPath robot to run daily 6:30 PM: connects via Remote Desktop (192.168.10.213) to a remote machine, logs into Shamel Pro (Arabic regional ERP), extracts Accounting & Transaction Reports for the current day, saves them as “acc DD-M”, and emails a compiled daily sales/business analysis. 16 discrete manual steps documented.

Security: passwords never appear as plain text in any UiPath field, screenshot, or shared content — secure credential retrieval only. The 6:30 PM trigger will not be scheduled until the full flow is built and manually tested end-to-end.

Internal projects (registry cross-reference)

Custom TrueBuilt Agency OS
INTERNAL SYSTEMREPORTED — REQUIRES VERIFICATION
Target future official system of record, not a client engagement. Tracked in detail on the Engineering & Automation page.
Source: 00 Master Knowledge / 05_CLIENT_PROJECT_REGISTRY (modified 2026-09-02). This registry is an index, not a duplicate knowledge store — full history lives in each client's dedicated chat. Read live from Google Drive; this page reflects the state at last build, not a live per-request fetch.