01 / Leadership change
Your next CTO needs context.
A search, planned departure, or interim-to-permanent handover creates a reason to investigate what the new leader will inherit.
Explore CTO transitionIndependent business & technology diagnostics
Understand what's happening.
Know what to change next.
Our senior diagnostic team investigates your systems, workflows, responsibilities and data around an agreed business question. You get a scoped map, findings with evidence and a practical action plan.
When to bring us in
Before a consequential decision, get a clearer picture.
02 / Unexplained friction
The reports or explanations disagree.
Work stalls between teams. Numbers do not reconcile. We trace the question across people, records, and systems rather than accepting the first explanation.
03 / A proposed change
You need to know what to change.
Before replacing a system or investing in AI, check the data, permissions, dependencies, and operating reality. The evidence may support a change, a smaller step, or no change yet.
How it works
From approved sources to a team-reviewed diagnosis.
01 / Approved sources
- Task trackers
- Code repositories
- Chats & messengers
- Documents
- Meeting transcripts
- Databases & reporting
- Targeted interviews
02 / AI-assisted research
Connected research
MemoryOS organizes approved records, connects sources and surfaces explanations for the team to investigate.
The team checks AI interpretations against the sources.
03 / Expert diagnosis
Senior diagnostic team
Our technology, HR and analytics leads review the findings together and identify what needs attention.
The review produces source-linked findings and proposed priorities, with uncertainties made clear.
Scoped map
Systems, processes, people and dependencies within the agreed area.
Diagnosis with evidence
Source-linked findings, confidence levels and open questions.
Action plan
Priorities, proposed owners and implementation briefs for the next steps.
What you receive
A scoped map, diagnosis and action plan.
One connected handover for your leadership and delivery team to review, challenge and adopt.
01 / Map
A map of the agreed scope
The systems, workflows, responsible roles, and dependencies involved in your question. A bounded view, not a promise to map the entire company.
02 / Diagnosis
Findings you can inspect
What the sources support, why it matters, and what remains uncertain. Evidence, interpretation, and open questions are kept distinct.
03 / Action plan
A practical order of work
Proposed 30/60/90-day priorities, owner roles, dependencies, and completion criteria, with an implementation brief for the first recommended change.
An organized research record accompanies all three outputs, so your team can revisit the reasoning and continue the work.
See diagnostic scope and deliverablesClient work / Publishing & e-commerce
Following the question across the business.
In work with a publishing and e-commerce business, Blatt followed operational questions across conversations, code, reporting, and product records.
Anonymized past engagement
An example of Blatt's diagnostic method, not a result attributed to today's team or evidence of CTO-transition outcomes.
Question
Why do operational and financial views lead to different decisions?
Sources
Leadership interviews, team conversations, reporting logic, product records, and system definitions.
Findings
The investigation documented inconsistent cost treatment, mismatched reporting periods, and missing checks between product promises and product content.
Boundary
Findings were separated from hypotheses. Financial impact remained subject to corrected calculations and policy decisions.
Senior judgment
Different disciplines. One reviewable conclusion.
Technology, people and analytics specialists challenge the explanation together, including what to retain or defer.
Michal is the accountable lead. Expert participation and responsibilities are agreed in the proposal, not a promise of full-time staffing or participation in every past case.
Meet the experts and their rolesScope & engagement
One question.
A bounded investigation.
We agree a decision, one workflow or connected area, relevant sources, and the outputs before work begins. The standard engagement is four weeks once agreed access is available; source volume and access constraints determine what can be covered.
Read the service scope and deliverablesA written proposal before you commit.
The proposal confirms scope, schedule, access, team involvement, deliverables, and a fixed fee. Missing access or a broader question may require a revised scope or schedule.
Diagnosis is not automatic delivery.
Hiring, interim CTO responsibility, broader implementation, and specialist security, compliance, or financial audits are not included. One focused change may be agreed explicitly; further delivery is scoped separately.
Frequently asked questions
Before the work begins.
Do we need to know exactly what is wrong?
No. Start with a concrete concern or decision: conflicting reports, a stalled workflow, a leadership transition, or a proposed investment. We agree an investigation question and achievable scope before starting. The four-week schedule depends on the agreed access being available.
What access will you need?
Access is agreed for the selected scope. It may include conversations, transcripts, documents, code, configurations, and read-only system data. Necessary sources, exclusions, and access restrictions are documented before work begins.
How much time will our team need to contribute?
A typical engagement includes 10–20 stakeholder interviews and 10–20 detailed written discovery questions, adjusted to the problem and team structure. A sponsor must also be available to resolve access and ownership decisions.
Where is our information processed?
Work is performed remotely in a Google Cloud environment provisioned and controlled by your company. Blatt does not require company records to be uploaded to a Blatt-owned production environment.
How are language models used?
AI helps organize approved records and connect sources. Our senior team checks interpretations, findings and proposed priorities against the evidence. Model requests use your company's API access and an agreed provider configuration set not to retain request data. Approved requests may leave your GCP environment for that provider's API.
Will you implement the recommendations?
The core engagement covers investigation and an implementation-ready plan. One focused change can be included when its requirements, access, dependencies, and acceptance criteria are agreed in advance. Broader delivery is scoped separately.
What if the evidence does not support the suspected problem?
The finding will say what was checked, what the records support, and what remains unknown. That can change the recommendation—including a decision not to proceed with a proposed system change or AI investment.
Can we keep using MemoryOS afterward?
Ongoing access can be arranged separately. The proposal distinguishes the portable project deliverables from access to Blatt's proprietary research infrastructure, hosting, updates, and support.
Start with your situation
What do you need to understand?
Tell us the decision, what seems unclear, and your timing. We will discuss whether a bounded diagnostic is the right next step.