// MODULE 01 — PULSE
In pilot

Yesterday, in one quiet message.

A single morning post — yesterday's revenue, ad spend, AOV, refunds, and one anomaly worth your attention. Replaces the spreadsheet someone is rebuilding at 06:50 with a number that's already there when you open Slack.

Cadence: Daily, 07:00 local Surface: Slack or email Runtime: Your cloud Sources: Up to 6
001 — How it works

Three steps. No glue code on your side.

Every module is a fixed shape. We deploy it into your cloud, hand over the keys, and step out of the room.

// 01
STEP 01 — CONNECT

Plug into the systems you already trust

OAuth or service-account access to the surfaces yesterday's number actually came from — Shopify, Magento, Stripe, BigQuery, your warehouse. Plus the ad accounts you actually run on: Meta, Google, TikTok.

// 02
STEP 02 — RECONCILE

One worker, four reconciliations

A scheduled agent pulls yesterday's totals, last-year's same-weekday totals, week-to-date and month-to-date roll-ups. Refund and return offsets are netted in. One number, traceable to its sources.

// 03
STEP 03 — DELIVER

One message, where the operator already looks

A single rendered message lands in the channel of your choice at 07:00. Headline, deltas, anomaly flag, optional rotating quote. No dashboard login, no second tab, no tooling tax.

002 — Inside the module

What's actually in Pulse.

The capabilities that make this module the right shape, not just the right name.

// 01

Same-weekday-last-year deltas

Comparing Monday-to-Monday, not yesterday-to-the-day-before. Honest seasonality.

// 02

Refund and return netting

Yesterday's number reflects refunds posted yesterday — no inflated headlines.

// 03

One anomaly, with context

We don't dump a stats panel. We flag the one signal that deserves your attention.

// 04

Source-of-truth deltas

Each metric carries its source. Click through to the underlying query if needed.

// 05

Rotating closing line

A deterministic daily quote keeps the message human without becoming noisy.

// 06

Holiday-aware compares

Public holidays and Black Friday dates are handled — no false-alarm collapses.

003 — Built for

The operators we built this with, not just for.

A module joins the catalog only after the same shape has been built three times for three different operators. Here's who those were.

Ecommerce CFOs

The number you check first thing, on the surface where you already work.

Multi-store operators

Per-store breakdowns roll up to a single message; one channel, all brands.

Founder-led ops

Replaces the morning spreadsheet someone on the team is rebuilding at 06:50.

004 — Operating notes

The honest answers we get asked first.

If you have a question that isn't here, that's also fine — bring it to the call.

Where does the data live?

In your cloud. Pulse runs in your project, queries your warehouse, posts to your Slack. We don't proxy anything.

What if upstream data is late?

A freshness guard checks before posting. If yesterday's data isn't ready, you get a 'will retry' stub instead of a wrong number.

Can the format be customized?

Yes. Metrics, deltas, ordering, copy tone, quote rotation — all configurable in one YAML.

Slack or email?

Either. Most teams pick Slack for the ops channel and email for the CFO.

Tell us what you're maintaining at 11pm. We'll tell you which module fits.

A 30-minute call. No deck, no demo — just the work. If Pulse is the right shape, we'll say so. If not, we'll point at one that is.

Book a call