Theme

Know

Analytics and Business Intelligence

Numbers you can trust, in one place. Bonzai’s analytics and business intelligence shows where your traffic, leads and revenue come from, in dashboards that say what your team should do next.

  1. 01A dashboard that never tells you what to do
  2. 02A view of the business, not a pile of exports
  3. 03Start from the decision, then find the numbers
  4. 04A Monday-morning reading, not a wall of tiles
  5. 05A leadership view, a client portal, or a fuller warehouse later
  6. 06The reports that look impressive and still mislead
  7. 07Exports and slide decks versus a living view
  8. 08What it costs on the published price table
  9. 09Analytics practices we are using now
  10. 10Questions about analytics and business intelligence
  11. 11Work that already lives on this site
Numbers without a recommendation. 1 Traffic; 2 Leads; 3 Revenue.
WordsA dashboard should also recommend an action
LeadersBuilt for the people who have to decide
FresnoAnd for Central Valley and national teams

Why this matters

A dashboard that never tells you what to do

“No dashboard should exist without including a cogent set of insights (in words) that summarize performance and recommend action.”

Avinash Kaushik, Analytics author, Occam’s Razor. Five Rules for High Impact Web Analytics Dashboards, Occam’s Razor

Most teams are not short of charts. They are short of a view that a manager can trust on Monday morning: what moved, why it might have moved, and what is worth doing next. A wall of green tiles can hide a stalled pipeline just as easily as a spreadsheet can.

Avinash Kaushik’s rule is the one we design against: no dashboard should exist without a cogent set of insights, in words, that summarize performance and recommend action. The charts are there to support that reading, not to replace it.

Bonzai builds leadership dashboards and reporting that can bring traffic, leads and revenue into one place, including client-facing portals when your customers need their own view, and with legacy data mapped and documented when the history lives in a tool you are leaving.

The anatomy of a useful report. 1 The question; 2 The measures; 3 The written insight; 4 The next action.
LeadersDashboards for the people who decide
PortalsClients can have their own view, with their own login
HistoryLegacy data mapped and documented

What you get

A view of the business, not a pile of exports

Work here includes leadership dashboards; reporting on traffic, leads and revenue; client-facing report portals; and the unglamorous job of mapping and documenting data you already have. We do not assume you need a warehouse on day one. If a warehouse is justified, we will say why.

  • Leadership dashboards
  • Traffic, leads and revenue reporting
  • Client-facing report portals
  • Legacy data mapped and documented

For owners and operators who want traffic, leads and revenue in one place, with a sentence that says what to do next — not another export no one opens.

  • Leadership teams that need a short, trusted view of the week
  • Staff who should see only the numbers that belong to their work
  • Companies with legacy systems that have never been clearly mapped
Question, source, view, words. 1 Name the decision; 2 Trace the source; 3 Shape the view; 4 Write the insight.
DecisionEvery view starts with a question a person actually asks
SourceEach measure should name where it came from
WordsA short reading sits with the chart

How a dashboard is built

Start from the decision, then find the numbers

We begin with the questions leadership already asks — often out loud, in a meeting, while someone hunts for a spreadsheet. “Are we generating enough of the right leads?” “Which work is profitable?” “What changed this week?” Those questions become the views.

Then we trace each measure back to a source: the website, the CRM, billing, ads, or a file you already export. If two sources disagree, we document that rather than averaging it away. The first useful dashboard is often narrower than people expect, and more honest because of it.

You review a working view early, while the definitions are still cheap to change. When a client-facing portal is in scope, that review includes what a customer should and should not see.

Typical timelines for Analytics and Business Intelligence
ProjectTypical timelineWhat shapes it
Dashboard or reporting2 to 4 weeksDepends on how many data sources and how clean they are.
Insight first, chart second. 1 The headline reading; 2 The supporting chart; 3 The suggested action.
WordsA written summary sits on the same view as the chart
NamedDefinitions are visible, not buried in a footnote nobody opens
CurrentThe view says when it was last updated

What good looks like

A Monday-morning reading, not a wall of tiles

“No dashboard should exist without including a cogent set of insights (in words) that summarize performance and recommend action.”

Avinash Kaushik, Analytics author, Occam’s Razor. Five Rules for High Impact Web Analytics Dashboards, Occam’s Razor

A good dashboard can be read in a few minutes by someone who does not live in the data. It answers a small set of questions well. It shows when the numbers were last refreshed. It does not make a person compare three exports to find out whether a dip is real.

The written insight is not marketing copy. It is a short, specific reading: what moved, over what period, compared with what, and what a reasonable next step might be. If we do not know why something moved, the dashboard should say that too.

Client-facing portals follow the same rule, with a tighter scope: a customer should see their work, their activity or their results — not your whole operation.

<10

As a rule of thumb, a dashboard should contain fewer than 10 metrics, each with a goal and, usually, a segment.

Source: Avinash Kaushik, Occam’s Razor
Narrow first, wider when it is earned. 1 Leadership dashboard; 2 Client-facing portal; 3 A warehouse, if it is justified.
First viewStart with the decisions you already make
PortalWhen customers need their own login and their own numbers
WarehouseOnly when the sources and the questions need one

Decision guide

A leadership view, a client portal, or a fuller warehouse later

Start with a leadership dashboard if

  • The same questions come up every week, and the answers live in more than one tool.
  • You want traffic, leads and revenue readable together, with definitions you agree on.
  • You do not yet need every customer to log in and see a private view.

Add a client-facing portal if

  • Customers already ask for a current picture of their work or their results.
  • You are sending the same PDF or spreadsheet on a repeating cycle.
  • Each client should see only their own records.

Talk about a warehouse if

  • The same joins and clean-up are being repeated by hand.
  • You have several sources that need a stable, documented model before they can be trusted together.

You do not have to start there. Many useful dashboards read from the systems you already have. Get an estimate or book a call and we will say which path fits.

Vanity, drift, and a missing definition. 1 Vanity measures; 2 Undefined fields; 3 A stale refresh.
Define“Lead” and “revenue” should mean one thing on the page
StampShow when the data was last updated
ActionIf nothing is recommended, the view is unfinished

Pitfalls

The reports that look impressive and still mislead

  • Charts with no written reading. If the view cannot recommend an action, it is decoration.
  • A “lead” that means three different things in three tools. The dashboard should pick a definition and show it.
  • A last-updated time that is missing, or a number that is still being compared against an old export.
  • Building a warehouse before anyone has agreed the questions. You will model the wrong thing very carefully.
  • Giving a client a portal that exposes more than their own work. Scope is a feature.
The weekly ritual, redesigned. 1 Manual exports; 2 A dashboard with a reading.
TogetherTraffic, leads and revenue can sit in one view
SharedLeaders and, when needed, clients see the same definitions

Compared

Exports and slide decks versus a living view

A dashboard is not a guarantee that a particular number will move. It is a way to see, agree and decide faster than a stack of exports allows.

A dashboard that recommends action, not just a pile of charts
A typical exportHow Bonzai builds reporting
What you seeMany tabs, many metrics, no orderA short set of numbers, each with a goal or a comparison
The “so what”Left for the reader to inventInsights in words, plus a recommended next step
Who it is forThe same sheet for everyoneLeadership and team views, and client portals when you need them
How it stays currentA manual export someone has to rememberFeeds from the systems you already run, updated automatically

Dashboard design here follows Avinash Kaushik’s published rules: context for every metric, a critical few, and insights in words. We do not invent benchmarks you do not have.

Published ranges, then your estimate. 1 Dashboard work; 2 Broader BI work; 3 Your quote.
QuoteThe exact figure comes from an estimate or a call

Costs and timelines

What it costs on the published price table

These are the published ranges on Bonzai’s price table. Your exact price and timeline come from the live estimate or a short call.

Typical timelines for Analytics and Business Intelligence
ProjectTypical timelineWhat shapes it
Dashboard or reporting2 to 4 weeksDepends on how many data sources and how clean they are.
Guidance we fetched, then applied. 1 Written insights; 2 Clear definitions.
WordsInsights in language, not only in charts

What we follow now

Analytics practices we are using now

The notes below come from sources we fetched on 22 November 2026 and from how we build reporting. They are not a claim about any one analytics vendor.

Guidance we fetched on 22 November 2026, used when we design dashboards and client report portals.

Measure the experience people actually have

Core Web Vitals are field metrics, judged at the 75th percentile, split by mobile and desktop. Lab scores are useful in development; they are not a substitute for what real visitors saw, including after they click around the site.

web.dev, Core Web Vitals

Keep a dedicated view of new search surfaces

Impressions in AI Overviews and AI Mode now have their own Search Console reports, rolled out worldwide on 31 August 2026. When we connect analytics and Search Console, we include that view so you can see those visits without mixing them into a guess.

Google Search Central Blog, 3 June 2026
Straight answers.
Your dataWe start from the systems you already have

FAQ

Questions about analytics and business intelligence

What data can go into a dashboard?

Website analytics and Search Console, your CRM, accounting, phone and help-desk systems, and data from older systems once it is mapped.

Can our clients see their own reports?

Yes. We build client-facing report portals where each client signs in and sees only their own numbers.

How long does a dashboard take?

Typically two to four weeks, depending on how many data sources there are and how clean they are.

Do we need a data warehouse?

Not usually to start. Many businesses get what they need from one well-organised database; we add more only when the volume calls for it.

Live cards, and recent reading. 1 Related work; 2 Latest in this category.
Our workOnly live cards already on /work
MonthlyThe latest-news list is refreshed by hand

Work and what’s new

Work that already lives on this site

We only link to Our work cards that are already live. The “Latest in …” list is curated, dated, and checked about once a month.

Official measurement updates we are tracking for dashboards and reporting. Last checked 22 November 2026.

Related services

Works best with

Next step

Talk it through with Bonzai