Independent analytical advisory for organisations approaching a consequential decision: what the decision depends on, what is established, what is assumed, and what should be verified first.
Decisions about platforms, vendors, AI adoption and operating models often rest on dependencies and assumptions nobody has written down. This engagement sets them out, with the evidence for each, before the decision is taken.
Observations are evidence-led. Where evidence is incomplete, the report recommends what should be verified and by whom. It does not select vendors, prescribe implementations or make the decision on the organisation's behalf.
Renewing, replacing or consolidating a platform or vendor
Introducing AI agents or automation into operational processes
Restructuring teams, outsourcing or changing operating models
Preparing a significant proposal for executive or board review
Responding to an incident that exposed unexpected reliance
A short written brief for executives or the board: the decision examined, the key observations, and the material uncertainties that remain.
The systems, vendors, people, processes and integrations the decision relies on, set out as a table with a supporting diagram.
Each observation recorded with its source, the date it was established and its evidence status: established, vendor-documented, client-reported, assumed or unresolved.
Observations organised under the Operational Clarity methodology: dependency, concentration, resilience, operational assumptions, reversibility, governance patterns and implications.
What would be difficult to undo after the decision, and where reliance is concentrated on a single system, vendor, team or person.
Evidence-based recommendations on what should be verified before the decision is taken, and with whom — framed as checks, not as instructions to choose a vendor or solution.
The agreed scope, the research cut-off date, the sources consulted and the limits of what the evidence can support.
See an illustrative sample of the written output — a fictional example showing the structure of a decision brief and evidence register.
Leaders accountable for whether everyday operations continue to work through a change.
Teams who need an independent view of platform reliance before committing to a direction.
Functions that need dependencies and assumptions documented with their evidence status.
Decision-makers who want an independent written basis for questions before approving a proposal.
No passwords, credentials or sensitive technical evidence are requested at enquiry stage. Evidence is shared only after scope is agreed, through a channel agreed with you.
A description of the decision under consideration and its expected timing
The systems, vendors and processes believed to be involved
Existing documentation the organisation chooses to share, once scope is agreed
Named contacts who can answer factual questions during the engagement
This service does not test controls, perform penetration testing or provide security assurance. Cybersecurity assurance is a separate discipline offered under Cyber Analysis.
SoftTech Reviews publishes independent research on individual software vendors. This service examines a specific organisation's decision and the dependencies around it, and may draw on that published research as a source.
The organisation remains responsible for the decision. Operational Clarity does not select vendors, design or manage implementations, make management decisions or certify compliance.
Scoping conversation, written scope with research cut-off date, research and evidence review, draft report, then a read-through with your team before the final version.
Timescales depend on scope and on how quickly evidence and contacts are available; they are agreed in writing before work begins.
Every commissioned engagement includes:
A defined, written scope
A stated research cut-off date
Documented sources
Stated evidence limitations
Agreed deliverables
Commissioned work does not provide certification, endorsement, privileged vendor access, penetration testing or continuous monitoring. Research into documented vendor capabilities is separate from examining an organisation's own implementation. Any review of client-supplied configuration evidence must be explicitly agreed and its verification limitations stated.
Paying for research cannot buy favourable findings or changes to published research conclusions. Commissioned reports are treated as confidential under the agreed engagement terms. Published research remains independent of commercial engagements.
Engagements are individually scoped and quoted. Fees are agreed before work begins.
Enquiries are made by email. Scope, feasibility and evidence availability are discussed before any work is agreed.
Please include your organisation, the service of interest, the software platforms involved and a brief description of what you need to understand. Do not send passwords, credentials, system diagrams or sensitive technical evidence; evidence is requested only after scoping, through a channel agreed with you.