Working With Us

Written for the people who have to take us through procurement.

Most firms make you discover their engagement model one sales call at a time. We would rather you walk into the first conversation already knowing how we work, how we price, and how we treat your data — so the conversation can be about your operation instead.

Engagement Shapes

Three shapes. One sequence.

Every engagement follows the Method's sequence — leakage, workflow, intelligence, system, measurement. The shapes differ only in how far along that sequence we travel together.

Shape 01

The Diagnostic

2–3 weeks · fixed fee

A bounded, senior-led examination of one operation. You receive the leakage model, the workflow map, and a build/no-build recommendation — including, when warranted, the recommendation not to proceed.

  • Quantified leakage model, with assumptions stated
  • Workflow map of where value actually breaks
  • Ranked intervention options with effort estimates
  • Yours to keep — and to execute with anyone
Shape 02

The Build

6–16 weeks · scoped against the diagnostic

Design and delivery of one production system against the diagnostic's findings — with the measurement plan agreed before the first line of code.

  • Production system, integrated where work happens
  • Controls: auditability, security, human oversight
  • Adoption plan and operator training
  • Outcome measured against the pre-agreed plan
Shape 03

The Operating Partnership

Ongoing · quarterly recommitment

For clients scaling from one proven system to an intelligent operating model. We extend, maintain, and measure — and we re-earn the engagement every quarter.

  • Roadmap governed by measured recovery, not feature lists
  • Systems maintained, evolved, and documented
  • Quarterly value review with auditable numbers
  • Exit-ready by design: your data, your systems, documented

The First Two Weeks

What actually happens after you say yes.

The opening of a Diagnostic, day by day — so there is no mystery about what you are committing to.

Days 1–2 · Framing

The problem, in business terms

A working session with your leadership: which operation, what "better" means financially, and who owns the outcome. We leave with access requirements and a written framing you sign off on.

Days 3–7 · Observation

Watching the work, not the org chart

We sit with the people who do the work — estimators, coordinators, reviewers — and trace real items end to end. Leakage hides in handoffs and waiting states; that is where we look.

Days 8–11 · Quantification

The leakage model takes shape

Observed time, error, and dependency costs become a model your finance team can interrogate. Every assumption is written down precisely so it can be challenged.

Days 12–14 · The Recommendation

Build, fix, or stop

A ranked set of interventions — or the honest conclusion that AI is not the answer here yet. Either way, you hold a document worth more than the fee, and no obligation to continue with us.

Pricing Philosophy

How we price, and why.

Numbers depend on scope, so they belong in proposals. The principles behind them do not change, so they belong here.

PR-01

Fixed-fee diagnostics

The Diagnostic is a fixed price agreed before we start. Discovery should never be a meter running — you are buying an answer, not our hours.

PR-02

Builds scoped against the model

Build proposals reference the leakage model directly: what the system costs against what the leak costs annually. If that ratio does not clear a sensible bar, we will tell you — it is the same test we apply to ourselves.

PR-03

No black-box time and materials

Where ongoing work is genuinely open-ended, we work in pre-agreed increments with visible burn — never an unbounded monthly invoice you have to take on faith.

PR-04

You own what we build

Code, documentation, models of your data, and the leakage analysis itself are deliverables, not hostages. Our retention strategy is being worth retaining.

Security & Data Posture

Built for the questions your IT team will ask.

A summary of our standing posture. Detailed responses to security questionnaires are available under NDA, typically within five business days.

Data minimization by default

We request the narrowest access that the engagement requires, document every grant, and relinquish access at engagement close. Production data never leaves your approved environments without written agreement.

Your data is not training data

Client data is never used to train models for other clients or for ourselves. Model and vendor choices respect your data-residency and processing constraints, and are documented in the system design.

Auditability as a design constraint

Systems we ship log their decisions. Outputs trace to inputs; extractions trace to source passages; human overrides are recorded. If a regulator or an internal auditor asks "why did it do that," the system can answer.

Contract-ready

NDA before any data is discussed — yours or ours. We contract under MSA/SOW structures your legal team will recognize, and we are accustomed to vendor onboarding, security review, and insurance requirements.

We would rather state our posture plainly and let your security team probe it than decorate this page with badges. Send us the questionnaire.

The first conversation costs nothing and commits you to less.

Talk to a Partner