Design IOI
← All clientsBrand kit
colours the generator renders with — without these nothing can be generated4 worth re-confirming before acting on
Nothing has contradicted these, so they are still on the record — but they are old enough that the client may have moved on. Treat them as questions, not instructions.
- contextbilling-cycle2025-12-15307d ago
The invoice sent 15 Dec covers the cycle from 20 Dec to 20 Jan.
Atlas clarified the billing cycle runs 20th to 20th when Jack asked whether the invoice was for January.
WhatsAppDesign IOI x Atlas· Atlas
- preferencead-approval2025-12-30292d ago
Jack wants to review the ad creative/ad ID before it goes live
On 30 Dec Jack asked "can i check the advid first?" before processing payment; approved on 31 Dec with "looks good".
WhatsAppDesign IOI x Atlas· Jack (client)inferred, not stated
- risklate-payments2026-03-16216d ago
A Facebook-side payment issue on the ad account required Jack to settle it before ads could continue.
Jun Kai flagged it 16 Mar; Jack asked how to settle; cleared by 17 Mar.
WhatsAppDesign IOI x Atlas· Jun Kai
- risklead-volume-results2026-03-03229d ago
Repeated lead-volume complaints alongside chronic late payment suggest churn risk.
Inferred from the combination of results dissatisfaction (Dec 15, Dec 28, Jan 7) and slow payment behaviour.
WhatsAppDesign IOI x Atlasinferred, not stated
Log meeting notes
Paste the notes; extraction pulls the facts and flags what contradicts the record. Add the doc link so the full detail stays one click away.
Facts
only approved facts may anchor a claimNothing known yet. Ingest a script or add facts the team already knows.
Documents
drafted by the system, edited by people — then the edits are read back into the recordNothing yet. Drafting is instant and free — agreement, invoice and deck from the client record, with [AM: …] markers where a human must fill in what the system must not invent.