Offering

Scored Decisions

Kinetric takes one decision your team makes by habit, rebuilds it as a score on your own history, and tests it against what you do today before anything in the list changes. Three depths: a week to find it, four weeks to test it, and a run to keep it tested.

The situation

A rule that feels like policy, set once and kept.

Somewhere in your operation sits a number somebody set years ago. How deep the mailing goes. Which accounts get a call. Where the reorder point sits. Which renewals get a human. It feels like policy, and your own history already knows whether it holds up.

What you receive

Three depths. Each ends with something you can hold.

You can stop after any one and still have something whole.

The entry
01

Rules Review

About a week. We find the rules in your operation that decide something per record and put a money figure on each.

  1. A one-page register of those rules: who owns each, when it was set, and what is at stake per cycle
  2. A ranking by money at stake against how testable each rule is on your history
  3. A first read of your history against the top rule: holds, leaks, or clearly beatable
  4. A written recommendation: test this one first, or leave them all alone, and why
The core
02

Scored Decision

About four weeks. One rule rebuilt as a score on your history, judged once on records it never saw.

  1. The score, written beside your records in the system you already use, with the line that turns it into a decision
  2. A memo and a readout for the budget owner: the recommendation, the comparison against your current rule and the simpler cuts, the checks, and the limits
  3. Holdout cells drawn at your next run, so the following run shows what the change caused
  4. The record: every figure traced to code, every check re-runnable, in a copy you hold
  5. A trained owner on your side who can recut the line when cost or volume moves
The run
03

Decision Run

Per run, optional, after a Scored Decision. The decision stays tested instead of turning back into a habit.

  1. The recut each time cost or volume moves, with the share of the file it clears
  2. The read of the holdout cells after each run: what the change caused, and whether to go deeper or shallower
  3. A refit when the history has drifted, with the forecast against actual that triggered it
  4. A one-page report after each run, written for the budget owner
What changes

The decision runs on a score tested against your own current practice.

On the public mailing sample, that was $6,366 more net on one drop than mailing everyone. It was also 28% to 66% ahead of every simpler cut a planner would have run.

The honest condition: it pays only if the decision actually changes. If the list pull ignores the score, the return is zero. Sometimes the proof says your current rule is fine, and then you have paid for a proof, not a change.

How it is bought

Fixed fees, agreed before the work starts.

DepthDurationAsks of your teamFee
Rules ReviewAbout a weekOne conversation with the person who owns the operation, and read access to the historyA fixed fee for about a week
Scored DecisionAbout four weeks, in parallel with your desk. Nothing in the operation changes until the last week.One owner, one call, one export, one read-only seatFixed once the decision and the data are named, at the scope call
Decision RunPer run, or monthly for decisions that run oftenThe results file after each runFixed at the Scored Decision handover, once the cadence and the data are named. Decline it and the score still runs.

This is not a new system and not a black box. Every input has a stated reason on record.

Fit

For you, and not for you.

For you if

  • A rule decides something per record, and someone on your team could name it
  • You hold past runs with the outcomes attached
  • The decision is made more than a couple of times a year
  • Someone on your side will own the score after handover

Not for you if

  • Your platform already ships the decision as a feature you haven't switched on
  • There is no outcome history yet, only the rule
  • You want a new system rather than a better decision
  • Nobody can be named as the owner
Why Kinetric

The order of work protects you from the vendor.

The expectation goes on record before your data is opened. The score is built on part of your history, frozen, and judged once on the rest. Every simpler way is tried first, and your current rule stays in every comparison. The limits are written down before anyone asks.

The one honest limit: the published proof is a public dataset, and no client engagement has run under the Kinetric name yet. We say that on this page and in the room.

The case that shows it
Next step

Three small steps, and the first is one sentence.

01

Name the decision

One sentence: the decision, the rule that sets it today, and who owns it. If you can't name the rule, the Rules Review starts there.

02

The scope call

A short call to fix the baseline and agree what counts as winning, before the data is opened. The fee is fixed on this call.

03

Access, one afternoon

An export of past runs with their outcomes, and a read-only seat on the system the list comes from. 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