Offering

Reporting That Ends in a Decision

Kinetric turns the report your team skims into one page built around the call someone makes every week. You receive the numbers it turns on, checked against your finance totals, and the line that says when to act.

The situation

A report everyone opens and nobody acts on.

Every Monday somebody opens a report with forty tabs, scrolls, and then decides the way they decided last week. The report shows what the data happens to hold. It was never built around the decision. And when two tabs disagree on gross margin, nobody can say which one is right.

What you receive

Three depths, from one page of thinking to the page your team reads every week.

The entry
01

Decision brief

About a week. The decision written down before any chart is drawn.

  1. The recurring decision the report serves, who makes it, and how often
  2. The three to five numbers that decision turns on, each defined in one sentence
  3. The line on each number that should trigger action, and where that line came from
  4. A list of what the current report shows that the decision never uses
The core
02

The numbers, made reliable

Two to three weeks. The numbers from the brief, computed the same way every week from your own systems.

  1. Each number defined once in writing and computed from your system of record
  2. A tie-out to your finance totals, so gross margin on the page matches gross margin in the books
  3. Checks that flag a number when its inputs break, before anyone reads it
  4. The record: every figure traced to the code that produced it
The page
03

The dashboard

About a week, after the numbers are reliable. One page your team reads before the meeting.

  1. One page built around the decision, in Tableau or as a Python page
  2. The trigger lines drawn on it, so the action is visible without a discussion
  3. A short walkthrough for the people who use it, and a written guide for the next person
What changes

The meeting starts at the decision instead of at the data.

The weekly call is made from a handful of numbers your team agrees on, against a line written down in advance. Arguments move from which number is right to what to do about it.

The honest condition: a report changes nothing on its own. If the meeting still runs on instinct, the page is decoration. The decision owner is named in the brief for that reason.

How it is bought

Fixed fees, agreed before the work starts.

DepthDurationAsks of your teamFee
Decision briefAbout a weekOne conversation with the person who makes the decision, and a look at the current reportFixed once the decision and the data are named, at the scope call
The numbers, made reliableTwo to three weeksRead-only access to the system of record, and one session with whoever closes the booksFixed once the decision and the data are named, at the scope call
The dashboardAbout a weekAccess to the tool the page lives in, and thirty minutes with the people who will read the pageFixed once the decision and the data are named, at the scope call

The brief stands on its own. You can take it to your own team and stop there.

Fit

For you, and not for you.

For you if

  • A recurring decision is made from a report: markdowns, reorders, staffing, spend
  • The numbers in different reports disagree, and the meeting spends time on which is right
  • Someone owns the decision and will use the page

Not for you if

  • You want a library of dashboards for every team
  • There is no recurring decision, only a wish to see the data
  • You want to replace your reporting tool
Why Kinetric

The decision comes first, the picture comes last.

Brendan spent three years presenting results to the people who set a multi-billion dollar account's budget. The lesson was simple. A number earns a place on the page only if it changes what someone does. The brief comes before any build, and the tie-out comes before any chart.

The one honest limit: we build the page in Tableau or in Python, not in every reporting tool. If your team runs something else, we say so at the scope call, before any fee is fixed.

The case that shows it
Illustrative engagementComposite figures. Shows the shape of the work, not a client result.

$310,000 of markdown found on styles already on pace to sell out

A specialty retailer selling by catalog and web swaps its weekly sales pack for one page built around the markdown decision. The readout shows revenue up 6% while gross margin is down 2.1 points, and $310,000 of markdown going to styles already on pace to sell out.

Read the case›
Next step

Three small steps, and the first is one sentence.

01

Name the meeting

One sentence: the weekly decision, who makes it, and the report it is made from today.

02

The scope call

A short call to look at the current report together and agree which decision the page serves. The fee is fixed on this call.

03

Access, one afternoon

A read-only seat on the system of record and a copy of the current report. One session with your admin.

Contact

Tell Kinetric one decision your team makes over and over.

We'll tell you what your own history can say about it, and which offering fits. If none does, we'll say that too.

Start a conversation