DEMO ENVIRONMENT — this is a fictitious company; all data shown is synthetic and illustrative only. Not a real OmniStack client.
← Back to Dashboard
About this demo

How this actually works

Every automation on this page exists for one reason: less time spent chasing debtors and pulling reports, and cleaner numbers to run the practice on. Everything you just navigated on Ferngrove's dashboard is real product UI — the layout, the logic, the components. What isn't real is the data behind it: every figure on those seven views was seeded once for this demo and is static, not pulled from a live system. Below is what actually changes when this gets built for a paying client — where the numbers come from, what runs on autopilot, and where two of the views work differently from a standard, repeatable build.

Debtor reminders

Automation Playbook pattern ② — one of the two patterns this demo is built around.

The result: debtor days come down and cash gets freed up sooner — without anyone in the practice chasing invoices by hand.

Accounting system (Xero / Sage / QuickBooks / Pastel)
Automation engine (Make / n8n) reads invoices & due dates on a schedule
Aging-bucket + reminder-ladder logic runs
Reminder sent — email (Resend) and/or WhatsApp (Meta Cloud API)
Payment status logged back
Same data renders on the Debtors view and Activity Log

Reporting & dashboards

Automation Playbook pattern ④ — the other pattern this demo is built around.

The result: the practice always knows which numbers actually matter — cash, debtors, margin, WIP — without anyone pulling reports by hand at month-end.

Accounting-system API (plus CRM / ads data in a fuller build)
Automation engine runs on a schedule
Numbers transformed and landed
Live dashboard (built the same way as what you're using now) and/or an auto-generated PDF pack

Compliance Tracker & WIP — built differently, honestly

The debtor-reminder and reporting flows above follow a standard, repeatable pattern. The Compliance Tracker and the WIP-from-timesheets view don't — every practice tracks statutory deadlines and logs time slightly differently, so these two are custom-scoped to the practice's own filing calendar and time-tracking tool during the Audit.

SARS doesn't expose a live feed we can pull filing status from, so the tracker runs on a deadline calendar we maintain with you.

This demo vs. a real client build

What's illustrative on the screens you just saw, and what a real client actually gets.

WhatThis demoA real client build
Data behind the numbersSeeded once, fixed as of 24 Jul 2026 — not connected to anythingPulled from the practice's own Xero / Sage / QuickBooks / Pastel
How often it updatesNever — static for this demoOn a schedule agreed during the Audit (e.g. daily)
Reminders / alerts you saw loggedShown as an illustration only — nothing was actually sentReal emails / WhatsApp messages sent to real debtors and staff
BrandingThis page only — everything else you saw wears Ferngrove's own themeThemed entirely to the client's own brand, top to bottom
Connections / accountsNone — no real API keys or accounts anywhere in this repoA real, client-owned connection configured during the Build

Connection Settings

Illustration only — nothing is connected in this demo.
Accounting system (Xero / Sage / QuickBooks / Pastel)
[your Xero API key would go here]
Automation engine (Make / n8n)
[your Make or n8n workspace connection would go here]