Onboarding Baseline Verification — Mohamed

Every new client gets an "Onboarding Baseline" record on their wiki page: their survey answers word-for-word, plus the prices and rules agreed on the onboarding call. Mohamed verifies each one. Griffin reviews Mohamed's work. Mohamed works through Discord DM — he does not edit the wiki directly.

The loop — run this for every new client

1. Start when a new client signs. You will see the new client channel appear in Discord, or Griffin will announce it. Start this checklist the same week — do not wait.

2. Confirm the survey answers arrived. Open the Google Sheet "LLM's NICHE Client Onboarding Survey (Responses)". Look for a new row with the client's company name and a recent date. If there is no row within 2 days of the onboarding call, message Griffin: "No survey row for [client] yet." Do not continue until the row exists.

3. Confirm the onboarding call was recorded. Check Fathom for a recording named like "[Owner]'s Onboarding Call". If there is no recording, message Griffin: "No onboarding recording for [client]." Note it — the price and pivot items in step 5 cannot be verified without it.

4. Wait for the checklist DM. The agent will send you a Discord DM with the draft Baseline for the new client, as a numbered list: the survey answers, the agreed prices (the lowest job price and the ad prices), the agreed "if X doesn't work we try Y" backup plans, and any points where the records disagree.

5. Verify every numbered item. Compare each item against the survey sheet and what was agreed on the call. Reply in the same DM, one line per item: - "1 OK" if it is correct. - "3 WRONG — should be $165, the client resubmitted on 6/12" if it is wrong. Give the correct value and where you saw it. - "5 NOT SURE — survey says repairs but we only book replacements" if you cannot confirm. Say why.

6. Follow these rules while checking: - Survey answers must stay exactly as the client typed them — spelling mistakes included. Do not "fix" their words. - Never put a client's phone number, email, or street address in Discord or anywhere else. Company name and city are fine. - If two records disagree (survey says one price, the call agreed another), report the disagreement. Do not choose one and delete the other. - If you are guessing, say you are guessing. "NOT SURE" is always a correct answer; a wrong "OK" is not.

7. Wait for the update. The agent applies your corrections to the wiki page and removes the "draft" marker. Griffin reviews after you.

8. Post one line in the activity-log channel: "Baseline verified — [Client] — [date] — [number] corrections." That single line closes the loop.