Dashboards & analytics
Branditify builds custom dashboards that bring metrics, reports, operations and decisions into one role-based interface — built on the systems you already run.
Explore all softwareYour systems
Metric layer
One dashboard
Revenue, last 12 weeks
Pipeline by stage
Revenue by channel
Needs attention
Six places hold the truth
Your systems
Metric layer
One dashboard
Revenue, last 12 weeks
Pipeline by stage
Revenue by channel
Needs attention
Six places hold the truth
Role-based views
A founder, a sales lead, an operations manager and a finance controller are looking at one system. What each of them needs on screen has almost nothing in common.
Where the business stands, and what needs a decision this week.
What is in the pipeline, what is going cold, and who owns it.
What is in flight, what is stuck, and where the queue is building.
What is owed, what is ageing, and what is likely to land this month.
Revenue vs target, last 12 weeks
Pipeline by stage
Work in progress
Receivables by age
Collections, last 12 weeks
Needs a decision
Revenue by channel
Deals going cold
Pipeline by source
Where the queue sits
Past SLA
Chasing this week
Not in this viewIndividual salaries, personal performance records
Not in this viewCompany cash position, payroll, supplier terms
Not in this viewDeal values, margins, customer pricing
Not in this viewLead sources, campaign spend, individual rep activity
How it works
A dashboard is only as good as what sits behind it. Every number on screen has a path: a system it comes from, a rule that cleans it, a definition that makes it comparable, a surface that shows it and something it lets you do.
Lead stages normalised, duplicates merged, owners resolved
Chase what is going cold, forecast the month
Order status mapped to one set of stages across plants
Clear the bottleneck before it becomes an SLA breach
Invoices matched to payments, credit notes netted off
Chase the right invoice, in the right order
Campaign spend attributed to leads that actually arrived
Move budget off what is not converting
We scope which of these applies to each source before anything is built, and the dashboard always shows how fresh a number is. Nothing here is promised as real-time in general.
Dashboard playground
Six of the dashboards we are asked for most. Each one is laid out for the questions that function actually asks — not the same chart set with different labels.
Where is the revenue coming from, and what is about to slip?
What is owed, how old is it, and what lands this month?
What is in flight, what is stuck, and where is the queue building?
What is the spend buying, and which channel deserves more?
What is selling, what is not shipping, and what is running out?
Is the business on track, and what needs me this week?
Pipeline by stage
Collections, last 12 weeks
Work in progress
Qualified leads by channel
Revenue by product line
Revenue vs target, last 12 weeks
Lead ageing
Receivables by age
Queue by stage
Cost per lead by channel
Fulfilment status
Revenue by channel
Closed by owner, this quarter
Invoices to chase
Exceptions
Qualified leads, last 12 weeks
Not shipping
Needs a decision
Illustrative interface. Sample data, not Branditify or client results.
The control room
A dashboard is not a type of chart. It is a working surface designed around who is looking and what they have to decide — which is why these eight look nothing like each other.
Who it is for — Founders, directors
Who it is for — Sales leads, reps
Who it is for — Controllers, accounts
Who it is for — Ops managers, plant leads
Who it is for — Marketing leads, agencies
Who it is for — Category and fulfilment teams
Who it is for — Your customers, logged in
Who it is for — Whoever runs the system
Revenue vs target
Pipeline by stage
Receivables by age
Work in progress
Qualified leads by channel
Fulfilment status
Your account
What belongs here
Executive dashboard
Sales dashboard
Finance dashboard
Operations dashboard
Marketing dashboard
Ecommerce dashboard
Client-facing dashboard
Admin & internal dashboard
Connections
Connections depend on the source's API, database, export or other available access. We confirm what is genuinely reachable for each system before it is scoped — some expose everything, some expose very little, and a few expose nothing at all.
The same architecture applies to
The refresh model follows the source system, not a marketing promise.
Beyond looking
A metric on its own is something to check. A metric with a condition against it is something that finds you. These are illustrative rules, not a configuration we ship — what gets watched is decided with you.
Three different things get called a dashboard.
Plenty of dashboards should stay read-only — a board view or a client view usually should. Whether yours acts on anything is a decision, not a default.
Access
Access is decided per role, and often per field. An illustrative matrix — every business draws these lines differently, and yours is agreed before anything is built.
Nothing in this zone for client.
ClientNothing in this zone for client.
ClientNothing in this zone for founder.
FounderNothing in this zone for sales.
SalesNothing in this zone for operations.
OperationsNothing in this zone for finance.
FinanceNothing in this zone for founder.
FounderNothing in this zone for finance.
FinanceThese are access controls designed into the system. Security and compliance requirements are scoped per project — no certification or compliance standard is implied unless expressly included in the agreed scope.
What gets shaped
Two businesses can run the same systems and still need different screens, because they decide differently. These are the dimensions that actually change between builds.
Delivered
One direct case, not three. ProMedia's own record names this system; most Branditify projects list "analytics and tracking" as a deliverable, and that is analytics setup, not a dashboard, so it is not evidence for this page.
Royalty operations platform
A royalty operations platform whose operator side is a reporting surface: statements, artist-side views and the admin console behind them. Its own record names this system, which is what makes it evidence of the thing this page sells rather than work that resembles it.
The scope lines above are taken verbatim from that project's recorded deliverables.
View case studyRelated reporting work
Reporting & performance visibility
Cost
Two businesses asking for "a dashboard" can be a long way apart. These are the things that decide it, roughly in the order they usually matter.
Where to go next
Questions
A single screen that shows the current state of your business, built on the systems that already hold the data. A good one carries more than charts: the tables and queues someone has to work through, the filters that let a number be opened up, and often the exceptions that need attention. It is not a report you produce and file — it is the view you work from.
Yes, and that is usually the point. A CRM, an ERP, an accounting system and a spreadsheet can all feed one view. What makes it work is the metric layer in between: each number gets one definition, so revenue means the same thing on every screen regardless of which system it came from.
No, and anyone promising that is describing your source systems rather than their own software. Where a source exposes an API or a database, numbers can move within seconds to minutes. Where it only allows a periodic export, the dashboard refreshes on a schedule and says when it last ran. Where there is no API and no schedulable export, someone imports a file. The refresh model follows the source system, not a marketing promise.
Yes. Access is decided per role and often per field — a role can see an order without seeing its margin, or see only its own team, branch or region. Customers and partners can be given a logged-in view of their own records on the same underlying data. What each person sees is designed into the build rather than switched on afterwards.
They can. A metric with a condition against it becomes an exception that finds you: invoices past their ageing threshold, stock below reorder, a deal with no activity, a job past its SLA. Where a role is permitted to, the resulting action can happen from the screen. Plenty of dashboards should stay read-only, though — a board view or a client view usually should.
That is the normal case — a dashboard is built on your systems rather than replacing them. A database can usually be read directly; a spreadsheet can be synced or uploaded, which is often the right answer for targets, budgets and anything that has not moved into a system yet. What is genuinely possible depends on the specific tool: connections depend on the source's API, database, export or other available access, and we confirm what is reachable for each system before it is scoped rather than promising integrations in general.
A responsive dashboard can be part of the web system, with a compact mobile view built around the few numbers and actions that matter on a phone rather than a shrunken desktop screen. A native mobile app is a separate product scope, not something a dashboard build includes by default.
A report tells you what happened — it is produced, read and filed. A dashboard shows the current state and lets you look into it. An operational dashboard goes further and carries the conditions and actions, so the work starts from the screen. All three are useful; they are not the same thing, and which one you need changes what gets built.
Mostly the data rather than the screens: how many sources, how reachable each one is, and what state the data is in. After that, how many views and roles, how complex the metric definitions are, whether reports and alerts are in scope, how much history has to migrate, and how many surfaces it runs on. The pricing page explains how we scope it; a number needs a conversation.
