AI proactive company brain for ecomm ops

The Brain
That Never Sleeps

The connective layers bringing in context from every creak and crevice of your brand. surfacing, executing monitoring and learning from the most impactful opportunities, trends, and risks, before they even arise.
Demand spike · Linen Field Tee
Today · 09:14
RivenAPP09:14
Heads up — I'm raising a demand spike signal on Linen Field Tee · Sand. Demand intent and sell-through have both crossed your threshold in the last 36 hours.
Signal · demand_spike↑ 36h window
Demand intent
3.4×+241%
vs 14-day baseline
Sell-through
62%+48 pp
last 7 days
14d intent · sell-through14 → 18 → 31 → 47
Why this matters. The last time this SKU tripped both thresholds was Feb 03 → Feb 09. We were out of stock for 4 days and the inventory log shows 161 missed orders (~$8,855 GMV) before the next replenishment landed.
Historical · stock-outFEB 03 — FEB 09
161
missed orders
$8,855
missed GMV
4 days
OOS duration
34%
conversion drop
In the Mar 18 ops weekly, the team agreed: “any SKU that crosses the demand threshold goes on pre-order before the next 48h.” I've drafted the pre-order config based on that rule and historical cover.
Proposed actionderives from weekly-ops/2026-03-18
Open pre-order for 600 units
Cover the 32-day supplier lead-time gap based on projected velocity. Pre-order page goes live to inbound traffic; PO drafted to Mira Textiles.
Volume600 units (90% of last reorder × spike multiplier)Pre-order pageShopify · ships May 28PO draftMira Textiles · $4,860 · NET-30Customer emailKlaviyo · “back in stock” → low-cover segment
1 of 4 steps will auto-execute
Jared Tucker09:18
How sure are we on the demand intent number? Last time the spike was driven by a single TikTok and it cooled off in 3 days.
RivenAPP09:18
Different shape this time. Confidence 0.84 — the spike is distributed across 6 channels rather than one viral source. Sell-through is also moving in lockstep with intent (corr 0.71 over 14d). See full reasoning →
Reply to signal · use /run to execute proposed action

Powering Proactive E-Commerce Operations

Shopify is the heart of your business. Riven is the brain.

Features
The Central Command
No longer just a row in a spreadsheet or a message in a group-chat. Every customer, order, signal and interaction is connected to the whole picture.
LFT
Linen Field Tee · Sand
SKU LFT-S-SND · PRODUCT
In stock
84
7d sales
−38%
Reviews
3.6 ★
Cover
4.2d
9 context links · updated 14m ago
Performance · sales drop▼ 38%
Weekly sell-through 312 → 194 units
Shopify · 7d window
Review · 2★ flaggedsizing
"Runs a full size small after one wash."
Yotpo · 14 similar reviews this week
Memo · pinned
Feb stock-out post-mortem
Notion · cites this SKU · 161 missed orders
Meeting note · Mar 18
Weekly ops · agreed action
Pre-order any SKU crossing demand threshold within 48h.
Integrated with
Escape Spreadsheet Hell
No more manual exports, messy formulas or outdated documents. Upload your data through the UI or your favourite terminal, and let Riven’s agents analyze, connect the dots, and give you the insights you actually need to grow.
claude — ~/work/olive-orchard · zsh

Welcome to Claude Code (v2.4.1)

MCP servers loaded: riven, shopify, filesystem

~/olive-orchard ❯ claude

CLAUDEHey Jared — what are we doing?

> Pull our supplier tracker into Riven — add suppliers as entities and update lead-time + MOQ rules. /attach ./suppliers-Q2.xlsx

CLAUDEOpening the workbook — 3 sheets: Suppliers, Lead Times, Notes.

filesystem::read_xlsx200 OK
#
supplier
lead · MOQ · terms
1
Mira Textiles
32d · 600u · net-45
2
Anvar Knits
21d · 300u · net-30
3
Hojo Print Co.
9d · 50u · net-15
4
Soller Pack
14d · 1000u · net-30
5
Kestrel Trim
7d · 200u · net-30

5 suppliers parsed · sheets "Lead Times" (28 rows) and "Notes" (12 rows) detected

CLAUDECross-checking against Riven — 2 of these already exist as entities, 3 are new. The Notes sheet has rules I'll lift into the glossary.

riven::entities.upsert_batch200 OK

✓ Anvar Knits → created · 14 SKUs auto-linked

✓ Hojo Print Co. → created · backup for screen-print

✓ Kestrel Trim → created · onboarding queued

✓ Mira Textiles → lead_time 28d→32d · MOQ 500u→600u

✓ Soller Pack → no changes · already current

CLAUDETracker is in. Your spreadsheet is the system of record now — Riven keeps it in sync from here.

~/olive-orchard ❯

Integrated with
The Signal Spotter
Riven doesn’t just connect the dots, it takes action on them. With native automations and API access, you can close the loop between insights and action. It’s the difference between a teammate who actually gets things done, and one who just talks about it in meetings.
1
Chat · #merch-opsToday · 14:02
RivenAPP14:02
Flagging Linen Field Tee · Sand — demand spike +340% units sold in the last 24h vs. 30d baseline (612 units, 4.2× normal velocity). Inventory at 18 days cover, down from 41. Pulled from Shopify, cross-referenced with Klaviyo campaign send 36h ago.
No prior playbook in action memory for a spike on this product class — first time I've seen this signal on a "hero SKU". How does the team handle it?
ER
Jared Tucker14:05
A hero SKU is anything in the top 5% of last-30d revenue. When demand spikes on a hero, do this every time:
  1. 1.Ping #merch-ops, tag @Maya
  2. 2.Email Mira Textiles for lead time + 600u quote
  3. 3.Run a competitor scan on linen tees in our band
  4. 4.Draft a pre-order page — wait for me
RivenAPP14:05
Got it. Running it now and saving this as the standard for hero-SKU spikes →
2
Running procedure
Riven · internal execution
  1. Posted to Slack #merch-opsTagged @Maya · 312-word summaryDone
  2. Email · Mira TextilesLead time + 600-unit quoteDone
  3. Web research · 4 competitorsPricing pulled · 1 underprice flaggedRunning
Step 3 / 4
~12s left
The brains and the brawn
Once Riven understands the connections in your data. Getting the answers and closing the loop between insights and action becomes second nature. Answering the questions of “what” and “why”, and also taking care of the “how”
A customer just emailed asking for a refund on their Linen Field Tee · Sand — it shrank. Repeat customer. How do we usually handle this?
ER
Riven

Short version: this isn’t isolated — Linen Field Tee · Sand has a known shrink issue, you have an existing playbook, and the recommended response is a no-questions replacement plus a 15% credit.

🚨
14 similar refunds this week — all on this SKU. +340% vs trailing 4w.
All cite "shrinkage after first wash." Same wash batch (lot LFT-W11).
⚠️
This customer is high-LTV. $847 lifetime · 7 orders.
Falls into the "VIP repeat" segment — your policy allows more latitude.
Shopify · customer + SKUcustomer 41208
LTV
$847
Refunds
14
Return %
11.2
Margin
$22
Gorgias · last 7d14 tickets
#8421
Shrunk a full size after one cold wash.
Lana C · same lot
SHRINK
#8434
Was a perfect fit, now it's a crop top.
Marcus T · 2-time customer
SHRINK
Internal · memos · meetings3 references
Memo · Refund & replacement playbook
Notion · pinned by Maya
For VIP repeat customers (LTV > $500, ≥ 3 orders), default to no-questions replacement plus a 15% next-order credit. Don’t ask for the item back unless cost > $80.
Meeting · Weekly ops · Apr 22
5 attendees
"The Sand colorway lot LFT-W11 has a wash issue — Mira confirmed." Every refund on this SKU is auto-approved through end of month.
Recommended response & follow-ups
RIVEN · GROUNDED IN YOUR PLAYBOOK
Send templated apology + free replacement + 15% credit
Drafted in Jared's voice · approved Apr 28 template
Review & send
Auto-approve refund in Shopify · issue replacement
Ships from stock · 15% credit · expires 90d
Run
Notify #merch-ops · tally now 15 on lot LFT-W11
Tag @Maya with the new ticket + count
Send
Integrated with
We remember. Do you?
Riven learns from every interaction and remembers everything, but will never hallucinate what it does not know. It’s the difference between a teammate who actually knows their stuff, and one who just sounds good in meetings.
M
Hero-SKU spike — response
New memory · learned from Jared
SAVED
Triggerdemand_spikehero_sku
ScopeApplies to any SKU matching hero_sku.
v1runs automatically next time

Connect Everything. Lose Nothing

Plug in the systems you already run on, and access Riven wherever you work. With native integrations across all your tools, and an open API, CLI and MCP for anything else, Riven becomes the central nervous system of your operations, connecting everything together and surfacing insights and actions right where you need them.

  • Slack

    Bring the context of your data into your conversations, and the insights of your conversations, meetings and announcements back into your data.

  • Shopify

    The heart and soul of your e-commerce operations. It sees everything. But Riven takes it a step further. Connecting the dots between customers, orders, inventory, and acting on those insights

  • Gmail

    Your team’s knowledge, decisions and plans are buried in email. Riven brings that context into the brain, and surfaces insights and actions right where you work.

  • Klaviyo

    Your marketing automation is only as good as the data and insights behind it. Riven connects the dots in your data, and gives you a direct line to your customers, so you can send the right message, at the right time, through the right channel.

  • Intercom

    Your support tickets, feedback and complaints are a goldmine of insights. Riven connects the dots between your customers, their interactions and your operations, so you can turn that feedback into action, and close the loop between support and operations.

  • Sheets and Documents

    Spreadsheets are the original no-code tool, but they don’t have to be the end of the line. Riven connects the dots in your data, and gives you a direct line to your spreadsheets, so you can get the insights you need, without manual exports or messy formulas.

  • Meetings

    Meetings are where decisions are made and plans are hatched, but they’re also where insights go to die. Riven connects the dots between your meetings, their outcomes and your operations, so you can turn those insights into action, and close the loop between meetings and operations.

  • Cin7

    Your inventory and supply chain data is crucial for making informed decisions, but it’s often siloed away from the rest of your operations. Riven connects the dots between your inventory, supply chain and operations, so you can get a complete picture of your business and make smarter decisions.

  • Meta Ads

    Your advertising data is a treasure trove of insights, but it’s often disconnected from the rest of your operations. Riven connects the dots between your advertising, customers and operations, so you can get a complete picture of your marketing performance and make smarter decisions.

Don't change for the brain.

Integrate with your existing tools, analytics and workflows to create a seamless experience.

claude — ~/work/olive-orchard · zsh

Welcome to Claude Code (v2.4.1)

MCP servers loaded: riven, shopify, klaviyo

~/olive-orchard ❯ claude

CLAUDEMorning Jared — what are we digging into?

> 60-day repeat purchase rate dropped ~9pp last month. Where's the bleed? Break it down by acquisition channel.

CLAUDEPulling the last two cohorts from Riven — comparing Mar vs Apr buyers across channels.

riven::analytics.cohort_diff200 OK
#
channel
repeat 60d
Δ vs Mar
1
Klaviyo Flows
22.1%
−11.8pp
2
Meta Ads
18.4%
−6.2pp
3
TikTok
14.0%
−2.3pp
4
Email Broadcasts
19.8%
−0.6pp
5
Organic / Direct
31.2%
+1.4pp

5 channels · 12,847 buyers analysed · weighted Δ −8.6pp

CLAUDEKlaviyo Flows is doing most of the damage — down 11.8pp on its own. Checking what changed upstream.

riven::insights.surface200 OK

● Welcome Series → paused 11 days ago · −38% flow revenue

● Repeat-buyer segment → email frequency 3.2/wk → 1.1/wk

▲ Meta Ads CAC → up 22% · prospecting-heavy mix

▲ Klaviyo + Meta overlap → cross-touched buyers down 41%

✓ Olive Oil 500ml → reorder rate stable · not a SKU issue

CLAUDEThe welcome flow is the bleed. Restart it + rebuild the repeat-buyer cadence — model says you recover ~70% of the dip inside 2 weeks.

~/olive-orchard ❯

Access Everywhere

In the new world of AI and Agents. Riven is accessible wherever you work, through native integrations, an open API, and a MCP that lets you interact with your data and operations directly from your terminal.

What you get with Riven.

Agents watch the data, surface what matters, and execute the next step with context from your internal SOPS, meeting notes and brand guidelines. So your team stops drowning in triage, meetings, and manual follow-ups, and starts moving at the speed of the business.

Action in days, not weeks or months.

Like a team member that doesn't sleep. Riven spots problems, patterns and opportunities before you even see them. Acting on it automaticlaly or giving you everything you need to act fast.

4–6 hours per week

No more pulling context from Shopify, Klaviyo, Slack and Support to figure out what's actually happening before anyone can decide what to do about it.

Cut the 5+ syncs per decision

Standups, threads, and follow-ups to get everyone on the same page before a single action gets taken. Context-switching eats the day.

Automate repetitive tasks

Riven studies the outcomes of past actions to know exactly what to do, and when, to get the best outcome. Then it does it, autonomously (or with your approval), every time.

Action in Weeks → Days

Skip the useless meetings

10+ hours back

1 autonomous loop

A city of connections. Built in minutes.

Building a brain has never been easier. Connect your data sources in minutes with our native integrations, or use our API to connect anything else. Watch as Riven learns from your data, identifies patterns, and starts making connections you didn't even know existed. It's like having a team of analysts working 24/7, but without the overhead.

Add Riven to Slack

Connect Riven to your Slack workspace and start making connections in your conversations.

Connect your Business

Connect Riven to your business tools to bring in data about your customers, orders, inventory, and more.

Connect Your Team

Your team lives in email, spreadsheets, and meetings. Connect Riven to these tools to bring that context into the brain.

Latest from the blog.

How to Find Your Most Valuable Customer Cohort in 30 Minutes

Operational Intelligence

How to Find Your Most Valuable Customer Cohort in 30 Minutes

Most operators analyse churn. The higher-leverage question is who stays and what they share across every tool in your stack. Here's how to trace it in an afternoon.

Operational Intelligence

Which Channels Produce Customers Who Stay?

Your best-performing channel by CAC might be your worst by 90-day retention. A framework for measuring true channel quality.

9 min read

Operational Intelligence

You Are the API: The Hidden Cost of Being the Human Integration Layer

DTC operators spend 9.3 hours per week being the glue between tools. Here are the 5 ways it is costing your business more than you think.

9 min read

Operational Intelligence

How to Track Customer Churn When Your Data Lives in 6 Different Tools

52% of subscribers churn in year one, but no single tool shows you why. A cross-tool churn tracking framework for DTC operators.

14 min read

View all posts →

Frequently Asked Questions

View all questions →

Join the Waitlist

The fastest way to see how Riven transforms your e-commerce operations is to see how it fits into your business. Join the waitlist, and be the firs