approach

discovery · specification · harness

Find the invariants.
Encode them. Ship the harness.

Every operation is a mix of rules that are always true and judgments that are never the same twice. We tell them apart — and by the end, your operation runs on rule instead of memory, decisions stop being re-argued, and your team's judgment goes only where it counts.

the principle

The rules can run themselves.
The judgment stays with your people.

Some rules hold in every case, every reviewer, every year — they were just never written down, so they get rediscovered each quarter. Those, a system can run. The rest is judgment: the calls that need taste, appetite, and someone accountable for them. That part stays with your people. The work is not automation — it is telling the two apart.

the engagement

14 weeks · three phases

  1. one 4 weeks

    Discovery

    We read the history, not the org chart. Three years of decisions tell you what the operation actually does — regardless of who was on shift.

    → The handful of rules we found — and the one part that stays human.

  2. two 6 weeks

    Specification

    We write the rules down — once, where everyone can see them. The spec is not documentation of the system; it is the system’s source of truth.

    → A spec the operators recognise as their own.

  3. three 4 weeks

    Harness

    We ship the thing that runs the spec: applies the invariants, surfaces the judgment calls, and records every decision against the rule it followed.

    → A running system, not a deck.

pricing

Starts-at pricing. We don't sell hours.

An AI-fit diagnostic starts at $5,000 (¥30,000); a full workflow-to-system engagement is quoted in phases — discovery, specification, harness. The starting price is not the cost of a tool; it is the cost of seeing one workflow clearly.

what we read

  • past orders & project briefs
  • chat logs & SOPs
  • quotes, request queues, rework logs
  • meeting notes, CRM, tickets, review comments
  • deliverable versions — the good cases and the bad ones

An org chart only helps at the edges; what we actually read is the record the work left behind.

what we need from you

  • a named business owner
  • access to the history
  • one-line people willing to validate
  • tolerance for a 4–14 week rhythm

the boundary

What follows a rule, the system runs.
What needs a person stays with your people.

This is the line every engagement draws — and refuses to blur. The repeatable work runs on its own; the calls that need judgment, taste, and someone to answer for the outcome stay where they belong. Any system that claims to take that part off your hands is one you should not trust.

request an engagement →