GLEMO - Proof Status & Evidence Map
Purpose: make diligence concrete by separating claims already operating from proof that will be opened under NDA.
Evidence Map
| Claim / Metric | Current Status | Evidence To Provide | Diligence Notes |
|---|---|---|---|
| 30K AI Agent interactions/day | Operating claim | Usage dashboard export or client-side usage screenshot | Provide last 30-90 days where available |
| USD 400K annual savings | Methodology claim | Savings methodology, before/after cost basis, client validation if available | Keep language as client-specific and source-backed |
| 20x capacity improvement | Methodology claim | Capacity comparison against prior human workflow | Avoid implying universal performance |
| USD 6M+ cumulative GMV | Operating history | CRM/BI export and transaction summary | GMV is not revenue; keep commission separated |
| ~100 active partners | Network claim | Partner list by country, type, status, and relationship owner | Separate signed, active, pipeline, and strategic |
| 4 countries active | Operating footprint | Country-by-country operating status | Use only active countries, not pipeline countries |
| USD 1M+ founder capital invested | Founder commitment | Bank/accounting summary or capex ledger | Provide under NDA or accountant-prepared summary |
| Anchor relationships | Commercial claim | Contracts, LOIs, emails, or status memo | Disclose identities under NDA where needed |
Diligence Principle
The public package should remain concise. Source files should be made available in a controlled data room after NDA, with every metric tied to a document owner and timestamp.