Ahmad Bukhari← Back to case

PULSE · reporting service

One agreed view. A daily pulse.

The original dashboard, reporting map and Slack output pattern.

Revenue · One agreed view

Last 7 days · all sources

Spend$12,480
Leads312
Cost per lead$40
Booked58calls
Revenue$41,200
Workstream 1Source structure

One agreed view

The original service flow: agree a metric dictionary and source inventory, reconcile the numbers, then put a dashboard and a Slack pulse on top.

Explore the source use case

Service scope

  • An agreed metric dictionary and source inventory
  • Scheduled collection and normalization for a bounded dataset
  • A dashboard with freshness indicators
  • Checks for missing, duplicate and inconsistent records
Reporting flow · Paid ads and CRM

Scroll graph horizontally to inspect each stage. A text node list is below.

Sources

Reconcile

Reconcile & defineMetric definitionsDe-duplicationAttribution rules

Warehouse

Dashboard + Slack

Source dates on every number
Read the flow as a node list

    Scoped service flow · local selection only
    Use-case intent

    Workstream 2Scheduled outputs

    Daily pulse in Slack

    Pulse is the module inside this reporting service: a morning Slack summary, an alert when a metric leaves its agreed range, and weekly report drafts that wait for a person to approve them.

    1. 08:00

      Daily pulse

      Yesterday's spend, leads, bookings and revenue land in the channel your team already reads.

      Internal
    2. Any time

      Anomaly alert

      When a metric breaks its agreed range or a source stops refreshing, the owner is pinged with what changed.

      Internal
    3. Monday

      Weekly report draft

      A weekly report is drafted per team or per client from the same agreed numbers.

      Draft only
    4. Before sending

      A person approves

      Nothing goes to a client until a person has read and approved it.

      Person approves
    5. Month end

      Month-end summary

      A month-end summary of spend, leads, bookings and revenue, with notes on any data gaps.

      Internal

    Client-facing reports always wait for a person to approve themEvery step runs on a schedule

    One pulse, one place

    Each morning the team gets a short summary: what was spent, what came in, what booked and what earned. If a source is late, the pulse says so instead of quietly leaving it out.

    PulseAPP08:00

    #leadership · Daily pulse, yesterday

    Spend
    $412
    Leads
    11
    Booked
    3
    Revenue
    $1,380

    GA4 refreshed 6 h late, so it is marked stale.

    • Spend, leads, bookings and revenue on one set of definitions
    • Freshness shown for every source
    • An owner named on every alert
    Cost per lead vs agreed range
    Cost per lead, last 7 daysFri · today

    Agreed range $30 to $45Outside the range

    Pulse alertAPP11:42

    Cost per lead is $58, above the agreed $30 to $45 range.

    Spend rose while leads stayed flat. Owner: Sam. Source dates attached.