Almogim Exec-Visibility Brain — POC Design
Definition
A concierge POC of the Brain (context-os-brain) for almogim, an Israeli general contractor whose CEO is a personal friend of saar-arbel. Scope: an executive-visibility brain built from the CEO’s email (Microsoft 365) and uploaded documents (meeting protocols, contracts), exposed through a simple web app — Outlook connect + file upload + Hebrew chat. The brain is maintained behind the scenes (concierge model: Saar is the harness). Origin: Saar-CEO conversation, 2026-06-11; grounded in the 2026-06-13 directions discussion.
Strategic framing
- What this tests. matan-amram rated generic project-visibility “tolerated by personality” — at the PM level (construction-project-management). Hypothesis under test: at the CEO/owner level, cross-project visibility is a painkiller because the buyer is the champion and personally absorbs the cost of not knowing. This POC is the direct experiment on vitamin-vs-painkiller-framing in construction.
- What this is not. Not a pivot from account-management-vertical (the lead vertical). It is a low-cost design-partner experiment — the access the construction-margin-protection-wedge analysis said was needed, arriving warm instead of via the queued matan-amram tendering-dept intro.
- Built-in escape hatch to the wedge. Every CEO query is logged. If queries cluster on money seams (change orders, budget-vs-priced, subcontractor scope disputes), the POC pivots to the margin-protection wedge with usage evidence — the strongest possible justification.
- Vertical determines data model (vertical-use-case-led-brain, 2026-05-31): this POC forces the first concrete construction brain schema, an asset regardless of outcome.
Evidence
- 2026-06-13-directions-revenue-cycle-and-construction-poc — Saar described the construction contact’s requested pain points: meeting-protocol memory, executive prep, follow-up tracking, daily updates from VPs, departed-exec email knowledge recovery, and a WhatsApp-style company brain.
Architecture (concierge POC)
Surface (what the CEO sees):
- Single-tenant web app, Hebrew/RTL. Three capabilities: (1) “Connect Outlook” (Microsoft Graph OAuth,
Mail.Readdelegated, read-only), (2) drag-and-drop file upload (PDF/DOCX protocols, contracts, Excel reports), (3) chat with the brain. - Chat answers cite their sources (which email / which protocol) — conflict-surfacing UX per the harness principle in context-os-brain, never an opaque oracle.
Behind the scenes (what we run):
raw/layer: synced emails (nightly Graph delta query) + uploaded files, immutable, per this repo’s own pattern.- Ingest: Claude-based pipeline builds an LLM-wiki per the Karpathy pattern — index-first traversal like the Harmony prototype; RAG/chunk layer only if scale demands.
- Concierge step: Saar reviews ingest output before it lands in the brain (human-in-the-loop = the agent harness, manually). Automate only what repeats.
Construction brain schema (v1):
| Page type | Construction meaning |
|---|---|
| project | One site/project: status, phase, budget posture, key dates |
| company | Subcontractors, suppliers, developers (יזמים), supervision firms |
| person | PMs, VPs, sub principals, developer contacts |
| meeting | One page per protocol/site meeting |
| decision | Commitments, approvals, change-order resolutions |
| issue | Open problems/risks per project (delays, disputes, blockers) |
| action-items | Rolling cross-project, owner + source + due |
Security/trust (CEO’s mailbox of a major GC):
- Read-only scopes; single tenant; no training on his data; simple mutual NDA before any sync; data deletable on request. Decide Israel-region storage early.
Milestones
- Week 0 — value before software. NDA. Get one project’s bundle (protocols + key email threads, even as manual export). Build the brain offline, demo chat on his real data in person. Gate: does he lean in and ask a second question unprompted?
- Weeks 1–2 — chat + upload live. Web shell with chat and upload only; ingest still manual. He uses it on his own.
- Weeks 3–4 — Outlook connect. Graph OAuth + nightly delta sync + incremental ingest with conflict surfacing.
- Ongoing — query log review weekly. Classify every question: status-shaped vs money-shaped vs people-shaped.
Success / kill criteria
- Success: ≥3 unprompted queries/week by week 3; queries that would otherwise require phoning someone; he asks to extend to his VPs/PMs or raises payment unprompted.
- Pivot gate (week 4): if ≥30% of queries are money-seam-shaped → re-scope to construction-margin-protection-wedge ingestion (tender docs, BOQ, change-order threads) with his tendering dept.
- Kill: zero engagement for 2 consecutive weeks, or he delegates usage to an assistant (signal: it’s a reporting tool, not a brain — vitamin confirmed at exec level too).
Open questions
- Does the CEO’s mailbox actually contain project state, or does it live in PMs’ WhatsApp (construction-project-management says WhatsApp is the real medium)? If chat answers are thin, WhatsApp export ingestion becomes the v2 requirement.
- Hebrew construction-domain extraction quality (scanned protocols, RTL PDFs) — first real test of ingest robustness outside hi-tech English data.
- Time-boxing vs account-management-vertical: how many Saar-hours/week does the concierge model consume? Set a cap.
- Who at Almogim beyond the CEO becomes the second user — and does that user prove or break the champion hypothesis?