ISAAC

AI-enabled systems design that diagnoses before it recommends

Isaac helps organisations define the real problem, build the context required to understand it, and evaluate potential interventions against explicit objectives and constraints.

A better answer begins with a better diagnosis.

I
Intelligent
S
Solutions
A
Architect
A
Advisory
C
Consultant

Isaac is Prospect’s structured intelligence and systems-design capability. It coordinates specialised AI workflows to investigate organisational problems, organise business context, compare options and produce traceable outputs for human review.

A structured route from operational problem to defensible decision.

Isaac combines diagnostic workflows, persistent organisational context and solution evaluation within one governed process.

It asks successive questions, identifies missing information and separates symptoms from root causes before considering technology or implementation.

The Result
A clear problem definition, structured organisational context, ranked options, and the evidence, assumptions and trade-offs behind them.
Symptoms Isaac Recognises
Slow Reporting Manual Work Disconnected Systems Repeated Errors Delayed Decisions Tools That Almost Fit Single-Person Dependencies

Operational problems rarely exist in isolation. A visible symptom may originate in fragmented information, unclear ownership, unsuitable systems or a process designed for an earlier stage of the organisation.

Reporting slows because information must be gathered and reconciled manually.
Information is fragmented because systems and processes developed independently.
Systems accumulate because immediate needs were solved without a coherent operating design.
Improving the final report alone leaves the underlying structure unchanged.

A general AI system can respond convincingly to the question it is given. Isaac is designed to test whether that question reflects the underlying problem.

The solution process begins only when the cause, impact and required outcome are sufficiently clear.

Recommendations are only useful when the underlying options have been examined.

Isaac is designed to maintain structured records of relevant software, services and implementation approaches, including capabilities, limitations, integrations, vendor risks and evidence quality. Automated research can accelerate coverage, while material findings remain subject to source traceability and human review.

Why It Matters
Options can be evaluated against the organisation’s requirements using consistent criteria, rather than selected from memory, familiarity or marketing claims.
01 Diagnose the Real Problem
Isaac dissecting a structural block into layers, identifying root causes and bottlenecks

Isaac conducts an iterative discovery process in which each answer produces more specific questions. This allows the system to test assumptions, expose missing information and move beyond the initial description of the problem.

The Diagnosis Maps Six Connected Areas
1
Revenue & Growth
2
Cost & Efficiency
3
Operations & Workflows
4
People & Capability
5
Technology & Systems
6
Strategy & Governance

For each material issue, Isaac establishes the current state, target state, size of the gap and business impact of leaving it unresolved. It then creates an objective hierarchy.

Objective Hierarchy
TierRequirement
Non-NegotiablesConditions every viable option must satisfy.
Critical RequirementsImportant outcomes where limited trade-offs may be acceptable.
PreferencesUseful additions that should not distort the core decision.
Output — Problem Brief
A precise account of what is happening, why it matters, what is causing it and what a successful outcome must achieve.
02 Build Organisational Context
Isaac assembling a stacked, indexed data structure from client, market, risk and performance information

A recommendation can only be judged within the environment in which it must operate. Isaac structures the information required to reason accurately about the organisation.

Operating Model Objectives Constraints Workflows Systems Data Sources Roles Permissions Terminology Dependencies Risk Boundaries Decision Structure

New information is connected to what has already been established. Contradictions are surfaced, assumptions are tested and unanswered questions remain visible rather than being replaced with guesses.

Why It Matters
Organisational context distinguishes an option that appears attractive in theory from one that can work within the organisation’s actual constraints.

The context can also support continuity across workstreams by preserving relevant decisions, assumptions, dependencies and unresolved questions.

03 Architect the Right Solution
Isaac at a drafting table architecting a solution blueprint

Once the problem and context are sufficiently clear, Isaac evaluates the available paths forward. Platforms, integrations, process changes and bespoke systems are assessed against the organisation’s objective hierarchy.

Valid Conclusions
Use an existing solution
Combine multiple existing solutions
Redesign the process before changing the technology
Build a bespoke system because no suitable solution exists
Change nothing because the cost or disruption outweighs the value

Ranking Criteria

Objective Coverage Implementation Effort Operational Disruption
Risk Dependencies Expected Value
Output — Solutions Report
A ranked set of options explaining what should be done, why each option fits, where it compromises and what must be validated before implementation.

An intelligent answer is not the same as a governed decision process.

General-purpose AI chats are useful for research, drafting, brainstorming and exploration. However, their output depends heavily on the question posed, the context supplied and the constraints the user remembers to mention.

ISAAC’s Starting Point
The user should not need to know the correct question in advance. Isaac follows a structured process to identify missing information, model the organisation, define objectives and evaluate options against explicit criteria.
A General AI Chat Isaac
Responds to the prompt and conversation in front of it. Follows a staged diagnostic process before producing a recommendation.
Works with the context the user provides. Builds structured organisational context and identifies material gaps.
Can generate plausible options. Filters and ranks options against requirements, constraints and trade-offs.
Provides a flexible intelligence interface. Provides a purpose-built process with defined stages, outputs and human review.
The quality of the process depends heavily on how the user operates it. Diagnostic questions and evaluation checks are embedded within the workflow.
Draws on broad model knowledge and the information available in the conversation. Uses structured solution research, source traceability and organisation-specific criteria.

Isaac may use leading AI models as components of its system. Its value lies in the methodology, organisational context, controls, validation and decision structure built around them.

The model is a component. The method is the capability.