Findings
Findings with evidence
Each material issue includes its supporting sources, confidence status, decision impact, limitations, and the next validation step.
AI & Operations Diagnostic
Four weeks to investigate a business problem and define the work that follows.
Blatt works with founders, operators, and technical teams to investigate conflicting reports, stalled workflows, and opportunities for AI. We connect the team's account of the problem with the relevant records, code, and data.
$10,000–$20,000
USD · Fixed after scope
Included
One connected investigation.
- A defined investigation question and agreed source scope
- Typically 10–20 stakeholder interviews and 10–20 detailed written discovery questions
- Review of relevant conversations, transcripts, documents, code, and read-only data
- Technical verification of key explanations where access permits
- A findings register separating evidence, inference, and open questions
- A blocker map, 30–60–90 day plan, and first implementation brief
- An exportable evidence pack and handover to leadership and the delivery team
Deliverables
Map
Dependencies and blockers
A practical map of the workflows, systems, data, and responsibilities involved—showing where a problem originates and what must happen first.
Plan
A prioritized 30–60–90 plan
Recommended changes sequenced by impact, dependency, effort, owner role, and acceptance criteria rather than by opinion or departmental urgency.
Build
An implementation brief
Requirements for the first recommended change: what it should do, what it depends on, and how the team will know it works.
Record
An organized research record
An exportable evidence register and handover so the team can inspect the reasoning, revisit open questions, and continue the work.
Evidence scope
Records, people, systems.
Slack and internal messaging
Meeting transcripts
Documents and operating records
Detailed written discovery responses
Selected codebases and configurations
Read-only reporting and operational data
Discovery is part of the evidence.
Interviews establish how people understand the workflow. Detailed written responses let key participants answer questions that need dates, examples, or careful explanation. Those accounts are compared with records and technical mechanisms rather than treated as system facts.
Timeline
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
Investigate 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
Turn supported findings into sequenced changes, ownership decisions, measurement requirements, 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.
Optional implementation
One focused change can be included when access, dependencies, and acceptance criteria are agreed in advance. Broader delivery is scoped separately.
Client-controlled environment
Work is performed in client-provisioned GCP using client-supplied model API access configured not to retain request data.
After the diagnostic