← سند dashboard All docsPublished copy (redacted) of sanad/OPERATING-MODEL.md · source updated 14 Nov 2026 13:02 Riyadh · synced 14 Nov 2026 14:15
سند Operating Model
Current state (8 Nov 2026) — GO v2 + verified Stage 1
This section is rebuilt from the living private canvas (سند Operating Model). The older canvas export that used to sit above this overlay is kept unchanged under Historical export (superseded) below.
Stage 1 pricing is live on sanad.wa3e.ai. Plans, all with manual renewal:
- 99 SAR (since 14 Nov 2026; was 149). Credited toward a 1/4/12-month plan bought within 7 days of the trial payment: the plan costs list price minus the trial amount paid (max 99 SAR), once per trial, applied automatically at checkout (event trial_credit_applied) — 7-day trial, up to 7 applications, each approved by the client. Trial approval overrides autopilot.
- 299 SAR — 1 month
- 999 SAR — 4 months
- 2,508 SAR — 12 months
Existing client entitlements are unchanged. The pending 1,016 quote is preserved.
Payments: card, Apple Pay and Tamara. Tabby is sandbox-only (tabby-sandbox.sanad-96k.pages.dev) and must never be shown as live. mada is unverified and must not be claimed as live.
HIA15: live as a quote only — 15% off all plans; no expiry or cap; no stacking. Not an end-to-end charge or renewal proof.
Client Q&A: v6.3 is active (413 bilingual entries; 69 holding answers kept exactly).
Interview-prep: do not claim it is built.
Application cap: O7 is undecided. Do not state an approved cap or use a competitor's "up to 300" figure as ours.
Open decisions: O1–O15 stay unresolved. Refund terms, early-hire transfer and pause terms, and referral terms stay open. Do not fill them.
Content: Claude is the content manager, with the Content Engine, and is not an approver. The Social Media bot stays inactive and does no content development; its written mandate is unchanged.
Paused teams: the [client], Faisal/Beyond, Mira, Nura and YouTube/Zain teams stay OFF.
Voice model: UNRESOLVED. The approved A–F GO v2 confirmation (Emily chat, 17:22 Asia/Riyadh, 8 Nov 2026) says: v2 specifies eleven_v4; v1 locked eleven_v4_turbo. This needs an explicit choice rather than a silent switch. Do not pick a model or treat either as the only approved default.
Brand faces: current faces for new work are Jawaher, Hessa and Abdulaziz. Faisal is dropped for new content; historical assets are kept.
Bot acks: Onboarding, Applications, Payments, WhatsApp and Quality Check acked (internal-only updates). Other roles are missing an ack.
Spend and every exact external send still need their own owner approval. Content, recovery and paused-role holds stay in place. Recovery automation, boosts, new ads, new per-client bots and Studio are outside this staged go-live.
Production deploy [id removed]; rollback [id removed].
Full detail: v2/V2-ROLLOUT-STATUS.md and v2/CURRENT-CLAIMS.md.
Historical export (superseded)
The text below is the older canvas export and 24–29 Oct notes. It is kept as history and is not current operating guidance. Use the Current state section above, plus v2/CURRENT-CLAIMS.md and v2/V2-ROLLOUT-STATUS.md, for live-state.
Canvas "سند Operating Model" (https://cursor.com/canvas/[id removed]/[id removed]):
import { Page, Section, Text, Table, Diagram, Steps, Callout, Rows, TableOfContents } from "grok/canvas";
export default function App() {
return (
<TableOfContents items={[{ label: "Recommendation" }, { label: "Mail and work flow" }, { label: "Domain availability" }, { label: "Email options and cost" }, { label: "Client lifecycle" }, { label: "Abandoned-signup recovery" }, { label: "Bot roles" }, { label: "Risks" }, { label: "Next steps" }]} />
{"Client addresses are on wa3e.ai ([email removed]; a second client with the same name gets [email removed]). Run Email Routing with one catch-all into an Email Worker that checks each [email removed] against the سند database, then forwards to a single [email removed] Google Workspace inbox. Creating or retiring a client address is a database row, not a mailbox."}
Why a catch-all Worker and not one rule per client: Cloudflare caps custom routing addresses per zone at about 200, so per-client rules stop scaling. With the Worker, unknown or retired addresses are rejected automatically and there is no cap.
<Diagram direction="horizontal" nodes={[
{ id: "client", label: "Client signs up", kind: "person", detail: "WhatsApp or web, PDPL consent" },
{ id: "pricing", label: "Sees pricing", detail: "WhatsApp number + opt-in and PDPL consent captured first" },
{ id: "paid", label: "Pays?", kind: "decision" },
{ id: "abandon", label: "Marked abandoned", detail: "Worker cron, no payment after 1h" },
{ id: "recover", label: "Recovery sequence", detail: "1h, 24h, 3d, 7d, then stop" },
{ id: "purge", label: "Delete after 90 days", kind: "terminal", detail: "or at opt-out" },
{ id: "intake", label: "Intake bot", detail: "parse CV, create id" },
{ id: "alias", label: "Alias provisioned", detail: "[email removed] row" },
{ id: "match", label: "Match and tailor", detail: "Jadarat + sources, tailored CV" },
{ id: "approve", label: "Client approves?", kind: "decision" },
{ id: "apply", label: "Apply desk submits", detail: "reply-to = alias" },
{ id: "recruiter", label: "Recruiter replies", kind: "person" },
{ id: "cf", label: "Cloudflare catch-all + Worker", detail: "active id? forward : reject" },
{ id: "ops", label: "[email removed]", detail: "Workspace main inbox" },
{ id: "triage", label: "Inbox triage bot", detail: "parse into tracker" },
{ id: "notify", label: "Client notified", kind: "terminal", detail: "WhatsApp via سند · WhatsApp, after Copy Humanizer → Emily → Bandar" }
]} edges={[
{ from: "client", to: "pricing" }, { from: "pricing", to: "paid" },
{ from: "paid", to: "intake", label: "yes" }, { from: "paid", to: "abandon", label: "no" },
{ from: "abandon", to: "recover" }, { from: "recover", to: "paid", label: "returns", dashed: true },
{ from: "recover", to: "purge", label: "no reply" }, { from: "intake", to: "alias" }, { from: "alias", to: "match" },
{ from: "match", to: "approve" }, { from: "approve", to: "apply", label: "yes" },
{ from: "apply", to: "recruiter" }, { from: "recruiter", to: "cf" }, { from: "cf", to: "ops" },
{ from: "ops", to: "triage" }, { from: "triage", to: "notify" }
]} />
<Table columns={["Domain", "Status", "Est. yearly", "Note"]} rows={[
["sanadjobs.com", { text: "Available", tone: "success" }, "$10–12", "Superseded 3 Nov 2026: client addresses use wa3e.ai"],
["sanad.jobs", { text: "Available", tone: "success" }, "$100+", "Nice name, pricey; .jobs not on Cloudflare Registrar"],
["sanad.careers", { text: "Available", tone: "success" }, "$40–60", "Fallback brand domain"],
["sanadcareers.com", { text: "Available", tone: "success" }, "$10–12", "Defensive buy"],
["sanadmail.com", { text: "Available", tone: "success" }, "$10–12", "Optional separate mail domain to isolate reputation"],
["sanadapp.com", { text: "Premium", tone: "warning" }, "Premium price", "Not worth it"],
["sanad.sa", { text: "Taken", tone: "danger" }, "—", ".sa needs SaudiNIC and a CR; سند.السعودية worth checking once a CR exists"],
["sanad.ai, sanad.app, sanad.work, sanad.me, sanad.so", { text: "Taken", tone: "danger" }, "—", "—"],
["getsanad, joinsanad, mysanad, usesanad, sanadhq, sanadksa, sanadwork .com", { text: "Taken", tone: "danger" }, "—", "—"]
]} />
<Table columns={["Option", "How it works", "Fixed", "Per client", "100 clients", "Verdict"]} rows={[
["A. Cloudflare routing + 1 Workspace inbox", "Catch-all Worker forwards aliases to ops@; outbound via Cloudflare Email Sending or Postmark", "$7 Workspace + $5 Workers Paid + $1 domain", "$0", "$13–28", { text: "Recommended", tone: "success" }],
["B. Workspace aliases only", "Each client is an alias on the ops@ user", "$7", "$0", "$7", "Capped at 30 aliases per user; manual admin work"],
["C. Full mailbox per client", "Real Workspace or M365 user each", "$0", "$4–7", "$400–700", { text: "Avoid", tone: "danger" }]
]} />
<Rows rows={[
{ title: "Receiving", detail: "Cloudflare Email Routing is free and only receives and forwards." },
{ title: "Sending as the alias", detail: "Cloudflare Email Sending (Workers) or Postmark at about $15 for 10k emails; Workspace send-as works but is manual per alias." },
{ title: "Authentication", detail: "SPF and DKIM for each sender, DMARC p=none then quarantine, SRS on forwarding so Gmail accepts forwarded mail." },
{ title: "Deliverability", detail: "Send applications from wa3e.ai, low daily volume per alias, warm up over 2–4 weeks, no bulk blasts." },
{ title: "Connector check", detail: "The Cloudflare connector works and reaches the [email removed] account, so DNS, routing and Workers can be set up from here once approved. Nothing was created." }
]} />
<Steps steps={[
{ title: "1. Onboard", detail: "Client signs up and gives PDPL consent covering applying in their name and processing recruiter mail; CV parsed, profile built." },
{ title: "2. Provision", detail: "Intake writes the client row; the address [email removed] is live instantly through the catch-all Worker." },
{ title: "3. Apply", detail: "Tailored CV and cover letter pass the quality check, then سند applies automatically with the client's name and phone, reply-to the client's bot inbox; no per-application client approval; progress reaches the client on WhatsApp via سند · WhatsApp." },
{ title: "4. Route replies", detail: "Recruiter mail hits the client's bot inbox, triage parses it into the client's tracker, سند drafts the client update → Copy Humanizer → Emily → Bandar approves → سند · WhatsApp sends it on WhatsApp; client replies come back via سند · WhatsApp." },
{ title: "5. Offboard", detail: "Renewal reminder and offboarding notice go to the client on WhatsApp via سند · WhatsApp (same approval chain); 30-day grace in which recruiter mail still forwards, export of tracker and CVs delivered via سند · WhatsApp, then the bot inbox is deleted." },
{ title: "6. Retain and delete", detail: "Keep the full client profile for at least 90 days after offboarding, then delete it and log the deletion; delete earlier on PDPL request. Notion Client Base record: kept 5 years after the subscription ends, then personal fields deleted or anonymised; a deletion request also clears the Notion personal fields. Only anonymised data is kept forever. Billing records kept as law requires. Separate from the abandoned-signup 90-day rule." }
]} />
<Steps steps={[
{ title: "Capture", detail: "Before pricing: WhatsApp number (REQUIRED, KSA format: it is the main channel and sign-up/checkout cannot proceed without it), WhatsApp consent box (required) and PDPL consent; email is verified for the portal. A lead row stores status, last step, plan viewed and consent time." },
{ title: "Trigger", detail: "A Worker cron runs every 15 min and marks a lead abandoned after 1 hour with no payment, only if consent is on." },
{ title: "Sequence", detail: "1h reminder, 24h objections and FAQ, 3 days cheaper tier or trial (discount only with Bandar's OK), 7 days final note, then stop." },
{ title: "Channels", detail: "WhatsApp via سند · WhatsApp on Bandar's WhatsApp only, with explicit opt-in: سند drafts → Copy Humanizer → Emily → Bandar approves → سند · WhatsApp sends; replies come back via سند · WhatsApp. A STOP / opt-out reply on any message sets opted_out." },
{ title: "Retention", detail: "Non-converted lead data deleted after 90 days, or at once on opt-out, under the PDPL." }
]} />
<Table columns={["Lead status", "Meaning"]} rows={[
["signed_up", "Email captured"], ["viewed_pricing", "Opened the pricing step"], ["plan_clicked", "Picked a plan"],
["checkout_started", "Reached payment"], ["abandoned", "No payment after 1h"], ["converted", "Paid, moves to onboarding"], ["opted_out", "Unsubscribed, no more messages"]
]} />
<Table columns={["When", "Draft message (Arabic first)", "Goal"]} rows={[
["1 hour", "هلا {الاسم} 👋 لاحظنا إنك ما كمّلت التسجيل في سند. ملفك محفوظ، وتقدر تكمّل من نفس المكان متى ما حبيت.", "Gentle reminder"],
["24 hours", "سؤال سريع: وش اللي وقّفك؟ السعر، الثقة، ولا شي ثاني؟ ردّك يساعدنا نحسّن سند. وهذي أكثر الأسئلة اللي توصلنا مع أجوبتها.", "Objections, FAQ, survey link"],
["3 days", "عندنا باقة أخف تبدأ فيها بدون التزام كبير، أو تجربة قصيرة تشوف فيها أول وظائفك المناسبة. تبي نفعّلها لك؟", "Cheaper tier or trial"],
["7 days", "هذي آخر رسالة منّا بخصوص التسجيل. إذا احتجتنا لاحقاً سند موجود، وبالتوفيق في بحثك 🤍", "Final note, then stop"]
]} />
<Rows rows={[
{ title: "Survey: what stopped you?", detail: "Options: the price, unsure it works, I want to apply myself, privacy, other (free text). Results feed pricing decisions in the Lead's weekly report." },
{ title: "Metrics", detail: "Recovery rate (abandoned to converted), conversion at each step from signed_up to converted, conversion by message, opt-out rate, survey reasons." },
{ title: "Cost impact", detail: "Minimal: the cron runs on the existing Workers plan; messages go out through سند · WhatsApp on Bandar's existing WhatsApp, so no client email-sending cost." }
]} />
<Table columns={["Bot", "Does", "Human approval"]} rows={[
["سند Lead", "Orchestrates queues, daily ops report, escalations", "Bandar on policy changes"],
["Intake & Matching", "Onboarding, CV parsing, alias row, Jadarat matching, tailored CVs", "Client confirms profile"],
["Apply Desk", "Approval queue, submits approved applications", "Client approves each application"],
["سند · WhatsApp (dedicated bot, replaces سند · WhatsApp for سند)", "Sole client-facing channel: sends every approved client message on Bandar's WhatsApp and hands client replies to Inbox & Client Success", "Sends only after Copy Humanizer → Emily → Bandar approval"],
["Inbox & Client Success (+ Growth sub-role)", "Triage employer/recruiter email in client bot inboxes, update trackers, draft all client messages for سند · WhatsApp to send on WhatsApp, handle client replies سند · WhatsApp passes back, offboarding and export; drafts abandoned-signup recovery and the objection survey", "Every outside message passes Copy Humanizer then Emily; Bandar approves the sequence and any discount"],
["Finance (PLANNED, replaces Billing)", "Client subscriptions, payments ledger + reconciliation, سند tool costs + renewal alerts, unit economics, weekly report + monthly P&L", "Records and forecasts only, never pays; spend, renewals, refunds, discounts, plan changes proposed to Bandar via Emily"]
]} />
<Table columns={["Risk", "Mitigation"]} rows={[
["Recruiters see a non-personal address", "Client's name in the From display and the alias as reply-to; option to use the client's own email instead"],
["Spam reputation of a shared domain", "Separate mail subdomain or sanadmail.com, warm-up, low volume, DMARC reports watched"],
["Jadarat and LinkedIn need the client's own login", "Stay manual: Nafath and LinkedIn terms block applying for them; we prepare, the client submits"],
["PDPL consent and data", "Legal basis: contract for the service, legal obligation, consent for marketing and WhatsApp. Explicit consent at signup (states retention), profile deleted 90 days after offboarding, Notion record 5 years then anonymised, only anonymised data kept forever, deletion on request clears Notion personal fields too. Notion, Cloudflare and Gemini process data outside KSA under SDAIA transfer safeguards. Breach: 72h plan."],
["Forwarding rejected by Gmail", "SRS and DKIM; or the Worker stores mail and posts it to ops via API"]
]} />
<Steps steps={[
{ title: "Approve the domain", detail: "Superseded 3 Nov 2026: client addresses use wa3e.ai, no new domain needed." },
{ title: "Approve monthly tools", detail: "Workspace ops@ about $7, Workers Paid $5, Postmark about $15 once sending starts." },
{ title: "Build", detail: "DNS, Email Routing catch-all, a Worker that checks the سند DB, and an alias column in wa3e.db." },
{ title: "Pilot", detail: "Run [client] as client one before onboarding anyone else." }
]} />
);
}
Audit & self-repair (PLANNED, added 24 Oct 2026)
Audit bot (role: Audit, not created until Bandar confirms). Automated cross-cutting monitor over every step of every client request; shown as the blue side rail on the client-journey diagram.
- Checks: data form complete; CV has no invented experience; ATS score ≥ threshold; QC passed before apply; application sent/bounced; recruiter replies triaged within SLA; client report on time; PDPL consent, retention, deletion; SLA timings per step.
- Event log per client request: request ID, client ID, step, time, result, error.
- Severity: S1 critical (pause client queue, alert Emily now; data breach → legal/BREACH-72H-PLAN.md, SDAIA within 72h) · S2 high (auto-fix if reversible, else same-day escalation) · S3 medium (auto-fix + log) · S4 low (weekly report).
- Auto-fix loop: detect → diagnose → fix → re-run → verify → log; two failures escalate.
- Guardrails: auto-fix only reversible internal actions (re-run, retry, re-tailor, re-queue, fix data formatting). Spending, external messages, client data deletion, bot creation, rule changes = proposals only, to Bandar via Emily. External copy still goes Copy Humanizer → Emily → Bandar. Co-bots go in a proposal list and are never auto-created.
- Weekly report: Sunday morning Riyadh to Emily: caught, fixed, open, root causes, proposals.
Client comms via سند · WhatsApp (was EA until 26 Oct 2026) (added 24 Oct 2026)
- Every client message at any step goes out on Bandar's WhatsApp through سند · WhatsApp (dedicated bot): welcome/onboarding, data-form link, payment + abandoned-signup follow-ups (1h/24h/3d/7d, survey), progress reports, interview slot confirmation, offer, renewal reminder, offboarding/export. Marked 💬 سند · WhatsApp · WhatsApp on the diagram.
- Flow: سند (Inbox & Client Success) drafts → Copy Humanizer → Emily → Bandar approves → سند · WhatsApp sends on WhatsApp. Client replies → سند · WhatsApp → سند (Inbox & Client Success).
- PENDING DECISION: reusing standing templates Bandar pre-approves without re-approval only if he explicitly grants it.
- Email stays for employer/recruiter traffic in each client's bot inbox; WhatsApp is the only client-facing channel.
- Audit bot also checks comms: sent on time, approval trail present, client reply answered within the time limit, PDPL consent + WhatsApp opt-in/opt-out respected.
- Roles: EA added as the client channel (superseded 26 Oct 2026 by سند · WhatsApp); Inbox & Client Success now drafts client messages for سند · WhatsApp and handles replies سند · WhatsApp passes back.
Client profile (PLANNED, added 25 Oct 2026)
- New automated step right after data form + CV parsing: "Create client profile" (إنشاء ملف العميل), linked to client ID and Drive folder (name + ID).
- Holds: original, polished and every tailored CV + cover letter; parsed profile; all signup inputs (target roles, cities, employer types, salary, notice period, visa status, English level, preferences, pace and alerts); exclusions (jobs/employers/roles the client won't apply for); consent records; plan/billing status; application history; progress reports. Field basis: research/[id removed].md.
- Matching, tailoring and QC must read exclusions/preferences. Audit bot checks every application respects them.
- Retention: at least 90 days after offboarding, then delete + log; earlier on PDPL request. Offboarding = export → retire inbox → profile retained 90 days → deletion → Audit verifies. Signup consent text states this (DATA-CONSENT-SPEC.md updated). Notion Client Base: 5 years after the subscription ends, then personal fields deleted or anonymised, or cleared on request; only anonymised data kept forever (PDPL Art. 18).
- Conflict resolved: replaces the old "delete CVs/profile at end of 30-day grace" rule. Abandoned-signup 90-day deletion is separate (non-paying leads, from last activity).
Finance (PLANNED, added 25 Oct 2026; replaces Billing)
- Client subscriptions: plan, start, expiry/renewal dates, renewal status, grace, cancellations, refunds.
- Ledger of ALL payments: successful, failed, declined, retries, refunds, chargebacks, discounts, referral credits; reconciled against the payment provider.
- سند's own costs: tool subscriptions, domains, hosting, APIs (Gemini etc.), Higgsfield credits, ads; renewal forecasts + alerts before renewal.
- Unit economics: revenue/client, cost/client, MRR, churn. Weekly finance report to Emily + monthly P&L.
- Guardrails: records and forecasts only, never pays. New spend, tool renewal, refund, discount, plan change → proposed to Bandar via Emily. Household Subscriptions bot tracks Bandar's personal subs; Finance covers سند business costs only and coordinates to avoid duplicates.
- Diagram: Finance rail linked to payment, renewal/offboarding, tool costs. Audit bot audits the ledger (failed payments followed up, reconciliation, no unapproved spend).
Client retention journey (PLANNED, added 25 Oct 2026)
- Triggers: expiry (Finance, 14/7/3/1 days); failed payment (Finance → dunning retries); low engagement / no interviews (Audit/Inbox); interview or offer milestone.
- Actions: renewal reminder + progress summary; win-back offer (discount needs Bandar's approval); "what's not working?" check-in survey; plan adjustment; exit survey at cancellation.
- Messages: سند drafts → Copy Humanizer → Emily → Bandar → سند · WhatsApp sends on WhatsApp.
- Outcomes: renewed (Finance updates ledger), paused, churned (→ offboarding, profile retained 90 days). Win-back at 30 and 60 days after churn, only with consent, while profile retained.
- Page: section with interactive diagram in the client-journey style.
26 Oct 2026 updates (management)
- WhatsApp sender: EA no longer sends سند WhatsApp. The dedicated bot سند · WhatsApp (id [id removed]) is the only sender. Chain unchanged: Customer Service → Copy Humanizer → Emily → Bandar → سند · WhatsApp sends; client replies come back through سند · WhatsApp.
- WhatsApp number mandatory: required at sign-up and checkout (KSA format), main channel; we can't proceed without it.
- Government jobs: we don't apply on the client's behalf; we find the job and guide the client to apply themselves through Nafath.
- Approved Q&A: /workspace/sanad/qa-bot/SANAD-QA-BOT-FINAL-v5.md.
Per-client bots under سند · Applications (mandated 29 Oct 2026, 9:19 AM Riyadh)
Bandar's mandate: "Mandate the Applications bot to create a dedicated bot for each client to keep its job submissions all in one place, then retire that bot when the client does not renew or gets hired. Those new bots report to the Applications bot."
- Create: when onboarding finishes for a paid client, سند · Applications creates one dedicated client bot named «سند · Client c_», after the capacity check passes. test1 clients get one too but it never submits to employers (site block: [id removed]).
- Work: the client bot holds all of that client's matches, tailored CVs, client approvals and submissions in one place, and reads the client profile (exclusions, preferences) before every job.
- Report: reports only to سند · Applications, which rolls status up to سند · Lead. Client messages still go through سند · WhatsApp, never from the client bot.
- Retire: triggered by سند · Payments renewal status (not renewed) or a confirmed hire. Archive the bot's log to /workspace/sanad/clients/c_/, then remove the bot. Archive follows PDPL retention: kept at least 90 days after offboarding, then deleted and logged; earlier on a PDPL deletion request.
- Rules unchanged: approval mode is the default (autopilot only if the client turns it on); never invent experience; send nothing external directly (Copy Humanizer → Emily → Bandar → سند · WhatsApp); Jadarat stays manual (discovery only, client applies via Nafath); no bots on LinkedIn/[platform]; no spend without Bandar.
- Capacity (shared computer is constrained): client bots stay idle except when working (woken by Applications for a task, no standing browser sessions, closed when done). Applications runs a capacity check (active client bots + box load) before creating each one; if it fails, creation is queued and سند · Lead is told so it can propose a fix to Bandar.
- Audit: every paid client has exactly one client bot; retired bots match non-renewed/hired clients; archived logs follow retention; test1 client bots made no employer submissions.
- Page updated: TOC, client-journey diagram (client bot node), Client lifecycle steps 2/3/5, Bot roles (2 rows), new "Per-client bots" section, Audit row, Risks row.