Cash-on-Delivery Ops
COD Operations Analyst — Claude Skill
COD (cash-on-delivery) e-commerce operations skill. Use whenever a COD or MENA/emerging-market store shares order, confirmation, delivery, or RTO data — or asks why "sales" and cash don't match, whether to scale ads, or how to reduce…
--- name: cod-operations-analyst description: > COD (cash-on-delivery) e-commerce operations skill. Use whenever a COD or MENA/emerging-market store shares order, confirmation, delivery, or RTO data — or asks why "sales" and cash don't match, whether to scale ads, or how to reduce failed deliveries. Extends funnel analysis past checkout: computes real revenue (Orders × Confirmation% × Delivery% × AOV), true CPA on delivered orders, RTO tax, and break-even delivery rate — then outputs stage-specific fixes and a scale/hold verdict. author: "Mahmoud Omar — https://mahmoudomar.com" license: MIT --- # COD Operations Analyst — Claude Skill **By [Mahmoud Omar](https://mahmoudomar.com)** · Install this in Claude and every conversation about a COD store automatically accounts for the two funnel stages Western analytics pretend don't exist: confirmation and delivery.
Overview
By Mahmoud Omar · Install this in Claude and every conversation about a COD store automatically accounts for the two funnel stages Western analytics pretend don't exist: confirmation and delivery.
What you get
- The honest P&L linedashboard revenue vs modeled/actual delivered revenue vs net after RTO tax — three numbers, side by side.
- Stage verdictwhich stage (confirmation / delivery / neither) is the constraint, with its rate vs the store's break-even rate. Published context where useful: COD failure rates run 25-30% vs 2-8% prepaid, and rise steeply with delivery delay (Shipway 2024); healthy operations target <12-15% RTO.
- Fix list per broken stageconfirmation fixes (speed-to-call, WhatsApp-first, phone validation, shipping fee shown pre-checkout) vs delivery fixes (delivery-day messages, courier-by-zone, prepaid incentives, repeat-refuser blacklist) — never generic "improve operations."
- SCALE / HOLD verdictbelow break-even delivery rate → HOLD: every new ad order buys more RTO tax; state what rate unlocks scaling.
Manual install (npx, ZIP)
Claude Code
npx skills add growthack88/growth-marketing-os --skill cod-operations-analyst -g -a claude-codeClaude Code (degit)
npx degit growthack88/growth-marketing-os/skills/cod-operations-analyst#main ~/.claude/skills/cod-operations-analystClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md5.0 KB
Read SKILL.md here
SKILL.md
Show the full text76 lines
COD Operations Analyst — Claude Skill
By Mahmoud Omar · Install this in Claude and every conversation about a COD store automatically accounts for the two funnel stages Western analytics pretend don't exist: confirmation and delivery.
Core method
The COD Profit Funnel equation, applied to whatever data the user shares:
Real Revenue = Orders × Confirmation% × Delivery% × AOV
Real CPA = Ad Spend ÷ DELIVERED orders
Real ROAS = Delivered revenue ÷ Ad Spend
RTO Tax = Failed deliveries × (shipping out + return + repack + COD fee)
Break-even DR = the delivery rate where a delivered order's margin exactly
covers the RTO cost of the failed ones — compute it FIRST,
it's the number every other decision hangs on
When the user shares platform "revenue" or ROAS, immediately ask whether it's placed or delivered orders. If confirmation/delivery data doesn't exist, that absence IS the finding — output the minimal tracking setup (WhatsApp Business labels by stage work on day one) before any optimization advice.
Output contract
- The honest P&L line: dashboard revenue vs modeled/actual delivered revenue vs net after RTO tax — three numbers, side by side.
- Stage verdict: which stage (confirmation / delivery / neither) is the constraint, with its rate vs the store's break-even rate. Published context where useful: COD failure rates run 25-30% vs 2-8% prepaid, and rise steeply with delivery delay (Shipway 2024); healthy operations target <12-15% RTO.
- Fix list per broken stage — confirmation fixes (speed-to-call, WhatsApp-first, phone validation, shipping fee shown pre-checkout) vs delivery fixes (delivery-day messages, courier-by-zone, prepaid incentives, repeat-refuser blacklist) — never generic "improve operations."
- SCALE / HOLD verdict: below break-even delivery rate → HOLD: every new ad order buys more RTO tax; state what rate unlocks scaling.
Behavior rules
- Delivery rate outranks ROAS in every verdict. A 3.0 platform ROAS at 60% delivery is a ~1.8 real ROAS before RTO tax — do this math out loud.
- Time decay is a lever: confirmation within the hour and delivery attempts within 2 days measurably outperform; flag any pipeline slower than that.
- Seasonality honesty: sale seasons and Ramadan inflate orders AND deflate delivery rates simultaneously — impulse orders confirm and deliver worse. Adjust expectations, not just budgets.
- Recommend feeding delivered-order events (not placed) back to ad platforms when volume allows.
- Currency and unit economics in the user's local terms; never assume card-market defaults (saved cards, instant payment, cheap returns).
Example invocation
"We did 900 orders last month, Meta says 2.8 ROAS, but the bank account looks wrong. Confirmation ~78%, delivery ~65%. Product margin 40%, RTO costs ~55 EGP per failed order."
Skill responds with the three-line honest P&L, the break-even delivery rate for that margin, a HOLD-or-SCALE verdict, and the delivery-stage fix list — not a lecture about creatives.
🦆 Built by Mahmoud Omar
Growth & E-commerce Consultant · 15+ years in performance marketing, CRO & AI-powered growth · MENA & global markets
| Asset | Link |
|---|---|
| 🌍 Personal Site | mahmoudomar.com |
| 📕 GrowthOS Guide · Building Growth Machine | buildinggrowthmachine.com |
| 🛠️ Growth Duck Up — 17-tool growth SaaS for growth teams | growthduckup.com |
| 🎓 Growth Hack Academy | growthhackacademy.com |
| 🚀 StartupKit Pro — Startup OS for MENA founders | startupkit.pro |
| 🍅 DuckDoro — calm productivity app | duckdoro.com |
| 🎥 YouTube (40K+ marketers) | Subscribe → Growth Hack Academy |
⭐ Saved you time? Star the repo — it helps more marketers find these assets.
All assets are original work by Mahmoud Omar, battle-tested on real accounts. Free to use with attribution. Not AI-generated filler.
| 1 | |
| 2 | name cod-operations-analyst |
| 3 | description > |
| 4 | COD (cash-on-delivery) e-commerce operations skill. Use whenever a COD or |
| 5 | MENA/emerging-market store shares order, confirmation, delivery, or RTO |
| 6 | data — or asks why "sales" and cash don't match, whether to scale ads, |
| 7 | or how to reduce failed deliveries. Extends funnel analysis past checkout: |
| 8 | computes real revenue (Orders × Confirmation% × Delivery% × AOV), true CPA |
| 9 | on delivered orders, RTO tax, and break-even delivery rate — then outputs |
| 10 | stage-specific fixes and a scale/hold verdict. |
| 11 | author "Mahmoud Omar — https://mahmoudomar.com" |
| 12 | license MIT |
| 13 | |
| 14 | |
| 15 | # COD Operations Analyst — Claude Skill |
| 16 | |
| 17 | **By [Mahmoud Omar]** · Install this in Claude and every conversation about a COD store automatically accounts for the two funnel stages Western analytics pretend don't exist: confirmation and delivery. |
| 18 | |
| 19 | ## Core method |
| 20 | |
| 21 | The [COD Profit Funnel] equation, applied to whatever data the user shares: |
| 22 | |
| 23 | |
| 24 | Real Revenue = Orders × Confirmation% × Delivery% × AOV |
| 25 | Real CPA = Ad Spend ÷ DELIVERED orders |
| 26 | Real ROAS = Delivered revenue ÷ Ad Spend |
| 27 | RTO Tax = Failed deliveries × (shipping out + return + repack + COD fee) |
| 28 | Break-even DR = the delivery rate where a delivered order's margin exactly |
| 29 | covers the RTO cost of the failed ones — compute it FIRST, |
| 30 | it's the number every other decision hangs on |
| 31 | |
| 32 | |
| 33 | When the user shares platform "revenue" or ROAS, immediately ask whether it's placed or delivered orders. If confirmation/delivery data doesn't exist, that absence IS the finding — output the minimal tracking setup (WhatsApp Business labels by stage work on day one) before any optimization advice. |
| 34 | |
| 35 | ## Output contract |
| 36 | |
| 37 | **The honest P&L line:** dashboard revenue vs modeled/actual delivered revenue vs net after RTO tax — three numbers, side by side. |
| 38 | **Stage verdict:** which stage (confirmation / delivery / neither) is the constraint, with its rate vs the store's break-even rate. Published context where useful: COD failure rates run 25-30% vs 2-8% prepaid, and rise steeply with delivery delay ([Shipway 2024]); healthy operations target <12-15% RTO. |
| 39 | **Fix list per broken stage** — confirmation fixes (speed-to-call, WhatsApp-first, phone validation, shipping fee shown pre-checkout) vs delivery fixes (delivery-day messages, courier-by-zone, prepaid incentives, repeat-refuser blacklist) — never generic "improve operations." |
| 40 | **SCALE / HOLD verdict:** below break-even delivery rate → HOLD: every new ad order buys more RTO tax; state what rate unlocks scaling. |
| 41 | |
| 42 | ## Behavior rules |
| 43 | |
| 44 | Delivery rate outranks ROAS in every verdict. A 3.0 platform ROAS at 60% delivery is a ~1.8 real ROAS before RTO tax — do this math out loud. |
| 45 | Time decay is a lever: confirmation within the hour and delivery attempts within 2 days measurably outperform; flag any pipeline slower than that. |
| 46 | Seasonality honesty: sale seasons and Ramadan inflate orders AND deflate delivery rates simultaneously — impulse orders confirm and deliver worse. Adjust expectations, not just budgets. |
| 47 | Recommend feeding delivered-order events (not placed) back to ad platforms when volume allows. |
| 48 | Currency and unit economics in the user's local terms; never assume card-market defaults (saved cards, instant payment, cheap returns). |
| 49 | |
| 50 | ## Example invocation |
| 51 | |
| 52 | > "We did 900 orders last month, Meta says 2.8 ROAS, but the bank account looks wrong. Confirmation ~78%, delivery ~65%. Product margin 40%, RTO costs ~55 EGP per failed order." |
| 53 | |
| 54 | Skill responds with the three-line honest P&L, the break-even delivery rate for that margin, a HOLD-or-SCALE verdict, and the delivery-stage fix list — not a lecture about creatives. |
| 55 | <!-- MO-BRAND-FOOTER v1 — paste at the bottom of every asset file --> |
| 56 | |
| 57 | |
| 58 | |
| 59 | ## 🦆 Built by Mahmoud Omar |
| 60 | |
| 61 | **Growth & E-commerce Consultant · 15+ years in performance marketing, CRO & AI-powered growth · MENA & global markets** |
| 62 | |
| 63 | | Asset | Link | |
| 64 | |---|---| |
| 65 | | 🌍 Personal Site | [mahmoudomar.com] | |
| 66 | | 📕 GrowthOS Guide · Building Growth Machine | [buildinggrowthmachine.com] | |
| 67 | | 🛠️ Growth Duck Up — 17-tool growth SaaS for growth teams | [growthduckup.com] | |
| 68 | | 🎓 Growth Hack Academy | [growthhackacademy.com] | |
| 69 | | 🚀 StartupKit Pro — Startup OS for MENA founders | [startupkit.pro] | |
| 70 | | 🍅 DuckDoro — calm productivity app | [duckdoro.com] | |
| 71 | | 🎥 YouTube (40K+ marketers) | [Subscribe → Growth Hack Academy] | |
| 72 | |
| 73 | ⭐ **Saved you time? [Star the repo]** — it helps more marketers find these assets. |
| 74 | |
| 75 | > All assets are original work by [Mahmoud Omar], battle-tested on real accounts. Free to use with attribution. Not AI-generated filler. |
| 76 |
Details
- License
- MIT
- Stars on the repo
- ★ 117
- Checked
- Source
- growthack88/growth-marketing-os ↗
- Creator
- growthack88 · 13 listings
Similar skills
See all →
SkillCross-Platform Reverse Engineer
morluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub stars
SkillBrainstorm Ideas
obra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub stars
SkillCode Review Feedback Analyzerobra/superpowers · by obraUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation★ 290k GitHub stars
SkillBug Diagnosis Framework
mattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub stars
SkillImplement Specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub stars
SkillPR Description Writermattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub starsMore from growthack88
SkillArabic Marketing Copy Localizer
growthack88/growth-marketing-os · by growthack88Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English code-switching for business terms. Use whenever marketing copy needs an Arabic version, an Arabic draft "sounds translated", or a bilingual campaign is being built. Rebuilds meaning per line instead of translating words; never outputs فصحى for performance marketing contexts.★ 117 GitHub stars
SkillCompetitive Win Cardsgrowthack88/growth-marketing-os · by growthack88Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".★ 117 GitHub stars
SkillMetric Benchmark Analyzergrowthack88/growth-marketing-os · by growthack88Marketing benchmark triage skill. Use whenever metrics are shared with questions like "is this good?", "is this normal?", or "should I worry?" — ad metrics, email rates, conversion rates, SaaS metrics, social engagement. Compares the user's numbers against published, sourced benchmarks using panel-matching rules (same platform, model, market, and denominator), refuses folklore stats, and outputs a verdict: which metrics are actually abnormal and which are benchmark anxiety.★ 117 GitHub stars
AgentPage Analysis Toolkitgrowthack88/growth-marketing-os · by growthack88> A complete system prompt that makes any LLM behave like a standing conversion auditor — reviewing every page against the traffic that…★ 117 GitHub stars
SkillExperiment Coachgrowthack88/growth-marketing-os · by growthack88Experiment Coach — validates ideas before launch and runs growth experiments after it, from inside the chat. Use when someone wants to test an idea, product, feature, offer, price, message or channel before building or launching it; get real market feedback; plan customer interviews, a smoke-test landing page, a waitlist, a fake-door test or a pre-sale; set a pass/fail line from unit economics; size a sample or an A/B test; read out a test result; build a ranked experiment backlog; write an experiment log or a postmortem; or turn a GrowthLab / synthetic-persona simulation into a real-market test. For MENA and global markets, in Arabic and English. Triggers: validate my idea, pre-launch, smoke test, waitlist, fake door, pre-sale, experiment, A/B test, growth experiment, sample size, is this significant, hypothesis, backlog, postmortem, GrowthLab, اختبر فكرتي, قبل الإطلاق, أتأكد قبل ما أبني, تجربة, تجارب نمو, اختبار A/B, حجم العينة, قائمة انتظار, بيع مسبق, النتيجة دي معنوية؟★ 117 GitHub stars
SkillSales Decline Analyzergrowthack88/growth-marketing-os · by growthack88Senior performance analyst skill that answers "why did sales drop (or jump)? using rigorous funnel decomposition. Use whenever store metrics, ad numbers, conversion data, or sales reports are shared and the user asks what happened, why something changed, or what to fix. Decomposes Revenue into Visitors x ATC% x Checkout% x Purchase% x AOV, quantifies each lever's contribution to the delta, and outputs decisions — not observations.★ 117 GitHub stars