KEYSTROKEK

How we count.

A keystroke is one thing a person had to type or click. This is how we count them, so you can check any figure on this site.

  1. What counts

    A character typed, a click, a copy, a paste or a file attached, when the rebuilt job no longer needs it. Reading and deciding are not counted.

  2. How we count

    We record the job once, with you watching, and count from the recording. Then we multiply by how often your own records say it happens.

  3. When it counts

    Only after the rebuilt job has run for four weeks with nobody stepping in. A job that is half automated counts for nothing.

The full counting method

What counts as a keystroke

One keystroke is one deliberate input a person makes that the rebuilt system no longer requires. Counted inputs:

  • A character typed into a field.
  • A click or tap that selects, confirms, submits or navigates.
  • A copy and a paste, counted as two.
  • A file attachment, counted as one.

Not counted: reading, deciding, a person choosing to check something, or any input the new system still requires. Time saved is not converted into keystrokes, and keystrokes are not converted into dollars anywhere in KEYSTROKE's own copy.

How a baseline is established

Before a build, the task is recorded once, start to finish, with the client watching. Inputs are counted from the recording, not estimated. The count is multiplied by the client's own stated frequency, invoices a week or jobs a month, taken from their system's records, not from what anyone remembers.

The baseline is agreed in writing with the client before any figure is published. If the client disputes the frequency, their figure is used.

How the cleared figure accrues

A task's keystroke count moves from baseline to cleared only after the rebuilt process has run in production for four consecutive weeks without a manual fallback. A task that is half automated contributes nothing. There is no partial credit.

The running total accrues at the rate the process actually runs. If a client's invoicing runs 60 times a week and each run cleared 32 inputs, the counter advances 1,920 a week, not in a lump on the day it went live.

Stating the figure

  • The homepage counter states the current calendar year. It resets on 1 January and the previous year's total is archived on this page, not deleted.
  • Client figures are stated per year and rounded down to the nearest hundred.
  • Any published figure carries its date and its scope. "14,600 a year, across quoting and invoicing, from March 2026."
  • A figure that cannot be traced to a recorded baseline does not get published. There is no house average and no industry benchmark.

Audit

The counter reads from a ledger with one row per cleared task per client: baseline count, agreed frequency, go-live date, four-week confirmation date, and the accrual to date. Any client may ask for their own rows and gets them the same week.

If a client stops using a rebuilt process, its accrual stops and the total stops rising. It is not clawed back, because the keystrokes were cleared while it ran, but the ledger records the stop date.

The ledger.

One row for each job we have cleared. The counter on the homepage is the sum of these rows.

The ledger has no rows yet. No figure is published until it has one.

Book a free consultation, or start with the quiz.

Book a free consultation