I work where the outcome depends on IT systems, data and processes: I design and build new solutions, remove the causes of problems that keep coming back, and independently check that what you are paying for works as agreed.
You don’t need a technical background. What matters is that you are accountable for the outcome and are deciding whether to bring in outside help.
ServiceIndependent verification. I check how a solution really behaves — on data and the system’s actual behaviour, also when someone else built it — and point out where it departs from what was agreed.
ExampleIndependent verification of software changes — establishing what really changed between releases, independently of the supplier’s release notes.
ServiceProcess diagnosis and implementation. I look at how the work is really done, find the patterns that repeat and build a solution that takes them over.
ExampleAutomation built on observing real work — work patterns identified and more than 50 automations deployed.
ServiceAnalysis and solution design. I assess the options and constraints, design the route to the goal and, if you want, help you follow it through.
ExampleA repeatable application-migration model — a model that let subsequent teams carry out the typical steps of the change on their own.
ServiceDiagnosis and analysis. You invest in people, tools and growth, but do not see the improvements you expected. I help identify constraints and dependencies across systems, processes and how teams work — before deciding what actually needs to change.
ExampleShared deployment logic for multiple applications — duplicated deployment logic and inconsistent parameters caused errors; with application configuration, shared logic and run parameters separated, a change is made in one place and teams keep control of their own settings.
You can commission the diagnosis, the solution design, the implementation or an independent verification on its own. You do not have to hand over the whole initiative.
Each of these four stages can be commissioned on its own.
Get in touchI reconstruct how systems and processes work, identify dependencies, test assumptions and establish root causes.
What you receive: A report of the actual state: the dependencies identified, confirmed findings, open questions and risks. The document includes recommended courses of action with the reasoning behind them.
You receive material on which you can decide about next steps — also without commissioning me to carry them out.
I develop an approach to the problem, the architecture, alternative options and an implementation plan.
What you receive: Design documentation covering the objective, assumptions, requirements, the proposed approach, dependencies, constraints and acceptance criteria.
The documentation states unambiguously what the solution covers, what it does not cover and which conditions it has to meet.
You can use it to deliver the project with your own team or commission the work from another supplier.
I design and build the solution, integration, automation or improvements to existing systems and processes — on my own or together with your teams and specialists chosen for the scope.
What you receive: An implemented and verified solution together with as-built documentation.
Depending on the agreed scope, I also hand over standard operating procedures (SOPs), user and maintenance instructions, and train the people responsible for running the solution.
The aim is to hand over a solution the organisation can use on its own and develop further.
I independently assess assumptions, how a solution works, its correctness, performance or readiness for deployment — against data and the system’s actual behaviour, also when someone else built it.
What you receive: A report setting out the scope of the checks performed, the criteria applied, the test results and the evidence behind the findings.
The document identifies what conforms, the irregularities found, the limits of the verification and the risks, with recommendations on acceptance or the corrections required.
You receive a basis for judging whether the solution really meets the agreed requirements.
The form, level of detail and scope of the materials handed over are agreed before work begins. You receive the results in an agreed electronic form, so that you can keep using them after the engagement ends.
Every engagement is priced individually. Problems that appear similar may differ significantly in scale, system complexity, dependencies and expected outcomes.
I do not offer standard price lists or fixed packages. I first establish the objective, constraints and delivery conditions. Before paid work begins, we agree on the scope, expected outcome, acceptance criteria and price or payment terms.
If a reliable estimate requires further investigation, we can agree on a separate, clearly bounded discovery engagement.
Before proposing anything, I check whether what is taken as true actually is — whether a plan rests on facts, whether “success” means a change, whether an identifier really links one operation end to end.
Assumptions confirmed or disprovedI analyse data, logs and how people actually work until it is clear what repeats and why — first on a sample, then at full scale.
Recurring mechanisms instead of isolated symptomsI rebuild the data flow, dependencies and operating model of the system from data, logs and observation of its actual behaviour — independently of what the vendor declares, also without access to source code.
A model that matches how the system really worksI propose a solution proportionate to the objective. The choice follows from the findings, not from a favourite technology.
An agreed plan of actionI deliver the agreed scope — often as a purpose-built tool — and check that it achieved the intended effect. For analysis or design only, verification means acceptance of the agreed deliverable.
A result checked against agreed criteriaSelected solutions I designed and built, organised by the class of problem — not by client, project or chronology. Each one shows the problem, the methodology, and the solution I built with its outcome. Organisation names and details of their environments remain confidential.
Architecture, dependencies and control over execution.
Recognise repeated work and make knowledge reusable.
Test assumptions about data, identity and availability.
Reconstruct system logic and prepare meaningful tests.
More work
Facing a similar objective or problem?
Get in touchI don’t start with a technology choice or a ready-made solution. First I establish the real need, work out the mechanisms behind the problem and assess which actions will bring the organisation lasting value — operational and economic.
We can start with a no-obligation conversation of up to 30 minutes. You tell me what you want to achieve or what is not working, and together we establish whether, and in what scope, I can help. The conversation itself does not commit you to commissioning anything.