The diagnostic / Scope, fit & deliverables

A fixed-scope
operating diagnostic.

You buy an agreed diagnostic and its results, not an open-ended block of consulting hours. Over four weeks a senior team reconstructs how one operating area actually works across decisions, people, data and software, verifies what matters, and hands leadership a decision package it can examine and challenge.

Duration
Four weeks after agreed access is available.
Commercial basis
A fixed fee for an agreed scope and deliverables. The proposal is written before work starts; there is no public price list.
Team
Senior specialists in technology and systems, people and organization, and analytics direct the inquiry and verify what matters.
Method
AI-assisted evidence research prepares the material: connected records, timelines, contradictions and candidate research cases. Senior experts decide what merits depth and verify it against primary records.
Output
An operating map, evidence-backed findings with a research register, a 30/60/90 intervention plan and a management handover.
Not included
Implementation, long-term system hosting and executive replacement. Each requires a separate agreement.

When this is the right instrument

An expensive decision, and explanations you cannot fully trust.

The diagnostic is most useful when leadership faces a consequential operating decision and the existing accounts of the situation are incomplete or contradict each other.

  1. 01 / An executive transition

    A CTO, CFO or COO is changing, and the incoming leader needs to know what they are inheriting before committing to priorities.

  2. 02 / Metrics that disagree

    Revenue, margin, attribution or operational figures conflict across teams, and nobody can say which definition should drive the decision.

  3. 03 / Growth without delivery gains

    Headcount and the tool budget keep rising without corresponding improvements in delivery or reliability.

  4. 04 / A founder who has lost line of sight

    The founder no longer sees how decisions travel through a growing organization or where they change on the way.

  5. 05 / Repeated hand-off failures

    Work keeps breaking down between commercial, product, finance, operations and engineering teams, and each explains it differently.

These are entry points, not industry verticals. Whether we can take on the work depends on retained evidence, leadership cooperation and a consequential question, not on the sector label.

Fit assessment

What must exist before we can begin.

We cannot reconstruct a history the company never recorded. Meaningful operational records and authorized access are prerequisites, not optional upgrades.

Strong fit

The organization retains meaningful history in task systems, workgroup communications, meeting records, code or configuration repositories and operational data. Leadership can authorize relevant access and will cooperate in resolving gaps.

Conditional fit

Some sources are missing, but enough primary records exist to examine a bounded question. The scope and the strength of conclusions must reflect the gaps.

Poor fit

Most decisions, customer interactions and work assignments happen without accessible records, or leadership cannot or will not authorize the sources the central question requires. We decline the standard diagnostic or propose a clearly different, narrower engagement rather than imply that AI can infer what was never documented.

Source volume alone is not enough: records must be relevant, accessible, interpretable and legally available for the agreed purpose. Group communications, meeting transcripts, email and other personal data are examined only under the client's authorization and applicable privacy rules. We do not require unrestricted access to private messages. Legal permissions, provider processing, exclusions, retention and deletion are agreed before any data is ingested.

Read how engagement data is handled

What you receive

Four connected deliverables your team can use and challenge.

01 / Operating Map

See how the work connects

Systems, workflows, decisions, responsibilities and dependencies around the question leadership needs answered.

02 / Evidence-Backed Findings

Understand what's driving the result

Findings linked to source evidence, with competing explanations, confidence and the questions that still need an answer.

03 / Intervention Plan

Know what to change first

30/60/90-day priorities, proposed owners, dependencies and checks for progress, with a brief for the first recommended change.

04 / Management Handover

Make the next decision together

A working session with leadership to examine the evidence, challenge the conclusions and agree how to use the findings.

The findings rest on a research register: the material cases with their primary-source references, verification status (verified, partially supported, rejected or unresolved), competing explanations and known gaps. Lower-priority or unresolved leads stay in the register, but they are never presented with the confidence of verified conclusions.

Sources and access

Connect accounts to the records.

Sources are selected around the question, not by department. Targeted interviews establish context and competing explanations; they complement the contemporaneous records of decisions, operational events, transactions and implementation, and do not replace them.

  • Slack and internal messaging
  • Meeting transcripts
  • Documents and operating records
  • Detailed written discovery responses
  • Selected codebases and configurations
  • Read-only reporting and operational data

We select the available sources and arrange access around your question.

Four-week working sequence

Research, test, review, and hand over.

Week 1

Establish the question and sources

Define the decision, map the selected workflow, confirm access, and begin stakeholder interviews and written discovery.

Week 2

Trace and test

Trace the leading explanations across conversations, code, configurations, calculations, and read-only system data. Review the first findings with the client.

Week 3

Define the changes

The senior team reviews technical constraints, ownership and reporting definitions together, then proposes sequenced changes and a specification for the first improvement.

Week 4

Review and hand over

Walk leadership and the delivery team through the evidence, unresolved questions, blocker map, and 30–60–90 day plan.

The schedule starts after agreed access is available. Missing sources, delayed decisions, or scope changes can require a revised plan.

Commercial terms, plainly

An agreed diagnostic and its results.

Scope and fee are agreed in writing for each engagement. Nothing is sold by the hour, and nothing beyond the four deliverables is implied.

  • A fixed fee covers the agreed scope and the four deliverables. Hours are not billed.
  • The four weeks begin when the agreed access is ready, not when the contract is signed.
  • A written proposal states scope, sources, exclusions, recipients and fee before work starts.
  • Implementation, system hosting, executive appointments and ongoing monitoring are separate agreements, if wanted at all.
  • Any continued access to Blatt's research infrastructure after the handover is a separate arrangement, distinct from the portable deliverables.

What this is not

Seven things we are sometimes mistaken for.

The boundaries matter as much as the offer. Each of these is a different product, and in several cases one we think would mislead you.

Not a self-service AI platform

The research systems are proprietary infrastructure operated and supervised by Blatt's team, with significant manual work. There is nothing to install or learn.

Not an AI-generated business diagnosis

AI proposes leads and organizes records. Senior people choose, challenge, verify and interpret. A retrieval hit or generated narrative is not evidence of causation.

Not a code-style audit

Code is inspected when business rules, dependencies, data flows or operational risk bear on the agreed question, not to catalogue inefficiencies for their own sake.

Not an interview-only management report

Interviews explain competing accounts. Wherever a conclusion claims to reconstruct what actually happened, primary operational records are required.

Not a complete company X-ray

The diagnostic has a fixed timeframe, an agreed scope and uneven depth across research cases. Missing or unauthorized sources constrain the conclusions.

Not an implementation contract

The output is findings and a recommended sequence of actions. Remediation, long-term hosting and new executive appointments need separate agreements.

Not covert employee monitoring

Access and analysis are approved in advance and limited to legitimate purposes. We do not offer hidden personnel surveillance or automatic performance rankings.

Start with a fit conversation

Which decision, and do the records exist?

Bring the decision, the disagreement and the sources you may be able to authorize. The first step is a fit assessment of the question and the available evidence, not uploading your company's history. No confidential records or credentials are needed for that conversation.

Discuss your situation