Revenue Intelligence System
A weekly reporting run for Mortals. Seven agents pull Shopify, Klaviyo, Triple Whale, Finaloop, Judge.me, Intercom, and Gmail in parallel. One synthesis pass grades them against a rule table and writes a Revenue Summary and an action list into Obsidian.
- One read
- replaces seven dashboard checks
- Rule-graded
- every source checked against a named table
- Routed fixes
- each item points to the owner
- In Obsidian
- next to the follow-up work
A weekly report builder for Mortals. Seven source pulls, one rule-graded synthesis, one action list.
Weekly internal reporting for Mortals.
The workflow pulls seven business sources, applies a rule table, and writes the weekly brief and action list into the Mortals Obsidian vault.
Pull source files
Seven source agents collect sales, attribution, email, accounting, reviews, support, and business-email context into the ISO-week folder.
Seven sourcesGrade against rules
A synthesis pass reads the returned files together and checks them against explicit condition-action rules.
Named condition-action tableWrite the brief
The Revenue Summary captures what changed, which rules fired, and what needs attention this week.
Executive snapshotRoute follow-ups
The Opportunities file routes each fix to the owning surface: flow, product page, support answer, campaign, SKU, or books.
Routed action listFive pieces: source pulls, decision rules, synthesis, Obsidian delivery, and the master skill that runs them.
Seven source pulls.
Each source has its own agent and access path, so Shopify, Klaviyo, Triple Whale, Finaloop, Judge.me, Intercom, and Gmail can run in parallel.
Concurrent pullsAn editable rule table.
The rules turn raw metrics into actions: reorder risk, broken email flows, CAC movement, low AOV, support themes, and compliance flags.
Condition → actionTwo weekly outputs.
Two weekly outputs. A Revenue Summary on what changed, and an Opportunities file where each fix is routed to a flow, page, campaign, SKU, or the books.
Summary + OpportunitiesObsidian delivery.
Obsidian delivery. The weekly folder plus running Product Performance and Customer Cohorts dashboards, all in the vault.
No second contextA prompt-run workflow.
It is a master skill invoked from a fresh Claude Code session. No SaaS dashboard, cron runner, or separate app is required.
Skill · no cron · no runnerThe rule table turns the weekly source files into decisions. Each rule names a condition, the action to take, and the surface that owns the fix.
- Inventory under thirty days of stock → critical reorder alert with a projected stockout date.
- Subscription revenue under forty percent of total → subscription-push recommendation.
- Klaviyo revenue under twenty percent of total → flag broken email marketing.
- CAC up twenty percent week-over-week → marketing review.
- ROAS under two-point-zero → creative refresh.
- AOV under forty-five dollars → upsell strategy.
- Owner funding above fifty percent of cash inflow → personal-capital dependency flag.
- Complaint theme in both Judge.me and Intercom → high-confidence friction.
- Reply containing a 'cures / treats / prevents' claim → FDA-compliance review.
Seven pulls, one synthesis, an Obsidian vault.
Anthropic Claude (Opus). Primary model class. Rule grading and cross-source reconciliation need interpretation, not pattern matching.
One weekly action list instead of seven dashboard checks.
The weekly run surfaces the work that would otherwise stay buried in separate tools: broken Klaviyo flows, unprofitable marketplace SKUs, legacy subscription cleanup, missing SEO pages...
The weekly outputs are private.
Every run writes into a private vault: seven source files, two synthesis files, two dashboard updates. The folder convention and rule set are shown above. The numbers behind each week...
The structure is public here. The weekly numbers and source files stay in the private vault.
Operator-run workflow that pulls seven sources, grades them against the rule table, and writes the weekly source files, Revenue Summary, and Opportunities list.
private · on demandEditable condition-action rules for inventory, subscription mix, email performance, CAC, ROAS, AOV, customer friction, funding dependence, and compliance language.
editable markdown · lives next to the runsMaster weekly skill plus follow-up prompts for SEO pages, Klaviyo repairs, campaigns, subscription win-back, missing flows, PDP copy, and FAQ fixes.
private · operator-invoked workflowProduct Performance and Customer Cohorts dashboards, updated in the same pass as each weekly run.
private