Skip to the paper

Runink Whitepapers

Papers that open with what can be proven.

Four long-form documents on the Runink platform and the products built on it.

They carry no case studies, no customer names and no return-on-investment figures. Those things are easy to write and impossible to check, and a buyer who has read three vendor decks this month has learned to discount them. What these papers explain instead is the mechanism: what the software looks at, what it produces, who approves it, and where it all runs.

Each paper marks its own claims wherever the footing changes — where something runs, where a passage is an illustration rather than a record, and where the paper is describing architecture. The marks are the papers’ own words, and they are used only where the footing genuinely differs.

Runink FACE

The evidence of your next loss is already in your systems.

Fulfilment Autonomous Claims Engine

Scattered across a dozen systems that were never designed to talk to each other. FACE assembles it, works out what the combined picture means, and produces a specific, reviewable recommendation with the underlying records attached — for a named person to approve.

37 pages · 28 chapters not measured hypothetical self declared

Runink CORE

One operations layer, on hardware you already own.

The operations layer for companies that keep their own data

The layer beneath a company's software that runs it, shows a named person what is happening across all of it from one screen, holds the connections that software uses to reach the company's own information, and carries changes from written to running.

22 pages · 20 chapters hypothetical not measured

Runink PULSE

A marketing engine that runs inside your own business.

Prescriptive Unified Lead & Social Engine

One application a marketing team operates directly. It audits your website and social presence, researches your market, prospects the public web for leads, and writes the material that carries somebody from first hearing of you to buying from you — staging every draft for a named person to approve.

25 pages · 21 chapters hypothetical first party not measured

Runink CORE With Logical Leap

Continuous oversight, with a second opinion on every finding.

A joint architecture paper with Logical Leap's Atlas

Atlas watches a company's capital spending as it happens. CORE's automated assessors read Atlas's findings and score them before a person is asked to act on any of them. This is an architecture paper: it states on pages 12 to 14 exactly which half of the design runs today and which half is drawn, and every claim in it should be read against those pages.

27 pages · 26 chapters drawn runs hypothetical not measured