A dashboard you have to read vs a pulse that reads for you.

What a dashboard asks of you

A dashboard is honest about everything and helpful about nothing in particular. It shows revenue, stock counts, open invoices, and headcount side by side — then waits for you to figure out which tile changed, which change matters, and what to do about it.

That's fine work on a quiet afternoon. It's expensive work at 7:40 in the morning before the shop opens. The cost isn't the dashboard itself — it's the interpretation tax: every day, you re-derive "what needs attention" from raw numbers, and some days you get it wrong or run out of time before the invoice that was 12 days overdue becomes 30.

What a pulse does instead

A business pulse inverts the flow. Instead of you scanning the data, the system scans it — then shows you a short, ranked list of what it found:

• It detects. Deterministic checks run over your real records — orders, payments, inventory, purchase orders, expenses, payroll, attendance — looking for known patterns: an invoice past due, a product about to stock out, a regular who's gone quiet.
• It prioritizes. Findings are ranked onto a single card — the top things needing attention, not a feed of everything that happened.
• It hands you the action. Each signal carries its evidence — the actual numbers — and a recommended next step, so the path from "noticing" to "doing" is one tap.

Dashboards answer "what is happening?" A pulse answers "what needs me?"

Where each one wins

This isn't dashboards-are-bad. Each tool wins in a different moment:

• Pulse wins for triage. Morning check-ins, catching problems early, knowing where to start. Thirty seconds, not thirty minutes.
• Dashboards win for exploration. Month-end review, spotting a slow trend no single threshold would catch, answering a question nobody wrote a detector for.

The failure mode to avoid is using a dashboard for triage — because the day you skip the scan is the day the stockout, the drifting customer, or the overdue invoice slips through. A pulse doesn't get tired, and it runs even on the mornings you don't.

How TUKO's Business Pulse works

Business Pulse is TUKO's intelligence layer, and it's deliberately un-magical. Detectors — ordinary rules, not a black box — scan your business data across 25 signal types: overdue invoices, low stock and stockout risk, slow movers, expense spikes, supplier delays and price increases, customers due to reorder or going quiet, payroll pressure, unusual absences, and "outside your normal" days measured against your own trailing 84-day baselines.

The results land on the Business Pulse card in the Command Center, ranked. Every item shows its numbers — the amount, the days, the count — and offers a concrete action: open the record, create a task, record a payment. You dismiss, snooze, or act; the list stays short.

An optional decision-model enrichment can re-rank the top items — and TUKO is honest about the mechanics: it's off by default, sends only minimized numbers and categories (never names or notes), falls back to standard ranking whenever it's unsure, and logs every evaluation so it's auditable. Whether it's on or off, the pulse you see is grounded in your records — estimated values are always labeled "est."

One more thing worth knowing: the pulse learns your normal, not an industry's. "Unusual" is measured against your own trailing 84-day baselines, so a sari-sari store and a machine shop each get judged by their own rhythm. And if you ever wonder why something surfaced — or how a feature works — every workspace ships a built-in Help Center with searchable articles and quick guides, under the ? icon in the top bar or Help in the sidebar.

Reports and dashboards stay underneath, unchanged. Business Pulse just means you check them because you want to — not because it's the only way to find out what broke overnight.